Sign and Submit

You only need signing material when an action changes chain state.

Configure the signer

1. Open Signer settings from the header.
2. Load a public key for identity-only use, or provide the matching private key when you need to sign.
3. Confirm the displayed signer identity before continuing.

Private keys remain in memory and are cleared by a refresh. Do not paste a production key into an untrusted device, shared browser profile, or copied Web UI deployment.

Compose a transaction

1. Open Submit.
2. Choose the transaction type.
3. Complete its required fields.
4. Review identifiers, target buckets or contracts, permissions, and payloads.
5. Sign and submit the transaction.

The interface prepares a canonical transaction envelope before signing. The node still performs protocol, authorization, signature, and state validation.

Follow the result

After submission, note the transaction identifier. A successfully accepted transaction can appear in the mempool before it is committed. Use Mempool and Transactions to follow it to a final result.

Do not resubmit automatically when the outcome is unclear. Search for the first transaction identifier and check the node response before creating another signed transaction.