Heraldor PublisherPublish official Notices
Publisher User Guide

Overview

Heraldor Publisher is the operational side of the platform. It lets authenticated users manage asset registrations, define reusable notice types, and publish official notices to the Heraldor contract on the configured network.

The app is split into Notices, Assets, Settings, and this Guide page. Notices is the publishing and review surface, Assets is the registry management surface, Settings is for publisher-owned configuration, and the Guide documents how the workflow fits together.

Access and Wallets

Authentication

  • • The app requires a signed-in publisher session for protected pages.
  • • Route guarding redirects unauthenticated users to `/login`.
  • • Auth hydration happens before the shell exposes protected content.

Wallet connection

  • • Wallet connection is separate from authentication.
  • • You need a connected wallet to publish notices and to create or edit assets.
  • • If the wallet chain does not match the configured network, the app warns you before proceeding.

Assets

Assets represent the token contracts or registrable targets that your publisher account can manage. They are network-bound and wallet-bound, which means the app loads them from the backend for the active configuration.

Asset rules

  • • Assets are network-specific and wallet-specific in the backend registry.
  • • Viewing the asset list does not require a wallet connection, but creating or editing assets does.
  • • The app only uses assets that are loaded from the current configured network.
  • • Disconnecting the wallet clears transient wallet state, not the authenticated session or loaded assets.

Practical notes

  • • Asset viewing is available even before wallet connection.
  • • Registering, editing, and deleting assets should be done carefully because it affects publisher identity.
  • • The backend may truncate the list after 200 items and will surface that limitation in the UI.

Notice Types

How they work

  • • Notice types are publisher-owned configuration used to classify notices.
  • • The settings screen shows only editable types for the current publisher.
  • • Type codes are trimmed and encoded with `keccak256(toHex(trimmedCode))` before publishing.
  • • Keep codes stable and human-readable so imported notices stay consistent over time.

Operational guidance

  • • Use concise, stable IDs that can be reused in imports and downstream filtering.
  • • Keep labels human-friendly because they appear in the settings surface and notice composition flow.
  • • Archived types are hidden from the editable list but still preserve historical context.

Publish Flow

End-to-end steps

  1. 1Sign in to the publisher app and connect the wallet that is allowed to publish for the selected asset.
  2. 2Confirm that the app network matches your wallet network and the backend network configuration.
  3. 3Select one or more registered assets and choose the notice type you want to publish.
  4. 4Enter the notice title, summary, body, and severity.
  5. 5Upload the notice document, review the transaction, and send it from your wallet.
  6. 6Wait for confirmation, then let the app import the published notice into the registry.

Validation and safety

  • • The form requires a selected asset, a connected wallet, a title, summary, body, and notice type.
  • • The publish request uploads the notice document, sends the transaction, and then imports the notice after confirmation.
  • • Gas estimation is buffered and falls back to a safer fixed path if the wallet cannot estimate gas.
  • • The app computes the notice type identifier with the trimmed type code before sending the transaction.

Notices

Notices page

  • • The Notices page is the main dashboard for reviewing published notices.
  • • It contains the primary Publish New Notice action when a wallet is connected.
  • • Notice severity, type, publisher, and asset relationships are shown in the shared list component.

Notice detail

  • • The detail page shows the stored summary, document body, and raw text.
  • • The metadata panel includes copy/open actions for address, publisher, and transaction hash.
  • • Failed or missing lookups show a clear loading, error, or not-found state.

Settings

Settings is where publisher-owned notice types are created, updated, and archived. It is intentionally narrow in scope so the publisher can keep classification rules simple and consistent.

What to expect

  • • Editable types are loaded with `editableOnly=true`.
  • • New types can be created from the form in the left panel.
  • • Existing types can be edited or archived from the table.

Best practice

  • • Use a small, stable type catalog that your team can reuse across campaigns.
  • • Avoid renaming types unless the meaning truly changes.
  • • Keep labels understandable to both publishers and readers.

Troubleshooting

I cannot publish

Publishing requires a signed-in session, a connected wallet, at least one selected asset, and a configured Heraldor contract address.

The app sent me back to Notices

The publish page is wallet-gated. If no wallet is connected, the shell redirects back to the Notices page.

The asset list is empty

Your authenticated session may be active but the current network has no matching assets loaded yet, or the backend returned only the first 200 entries.

The notice import did not finish

Import runs after the transaction is confirmed. If confirmation fails, times out, or the backend rejects the payload, the notice will not be imported.