Broadcaster
Broadcaster is an optional transaction relay. It receives completed public transaction data and proofs, checks deployment, quotation, and authorization, simulates execution, then pays native gas using its own EVM wallet. Wallet keys, private Notes, decryption materials, and witnesses stay with the client.
Users can also submit directly. The registry helps discover services; registration grants no on-chain submission privilege and establishes neither reputation, availability, nor payment guarantees. A relay observes public requests and network origins; HTTPS does not provide network anonymity.
Responsibilities across services
| Component | Integration responsibility |
|---|---|
| SDK / wallet | Build intent, freeze fees, authorize, prove, and retain recovery materials |
| Protocol RPC | Supply trees, outputs, Credit data, and registry snapshots |
| Broadcaster | Quote, simulate, reserve, submit, and observe receipts |
| Chain RPC | Allow independent application checks of canonical receipts and native finality |
| Provenance | Validate public source proofs when policy requires them; it does not change the on-chain Protocol proof |
Broadcaster accepts neither private keys nor witnesses. It provides no wallet custody, arbitrary EVM forwarding, public fee-withdrawal method, or subscriptions.
Discover and authenticate identity
Obtain endpoint, quoteSigner, and feeRecipient from trusted service configuration or an authenticated BroadcasterRegistry snapshot. Compare service identity fields chainId, protocol, runtimeCodeHash, sender, and feeRecipient against expected configuration and registry credentials, then verify signed quotes using the trusted quoteSigner. An API version or enabled flag alone does not establish trust.
These read-only examples require a POSIX shell and curl. Set BROADCASTER_BASE_URL to the operator-provided service root without /v1, and CHAIN_ID to the target canonical decimal chain ID. Use HTTPS for remote endpoints.
: "${BROADCASTER_BASE_URL:?Set the trusted service root URL}"
: "${CHAIN_ID:?Set the expected decimal chain ID}"
BROADCASTER_BASE_URL="${BROADCASTER_BASE_URL%/}"
BROADCASTER_RPC_URL="$BROADCASTER_BASE_URL/v1/chains/$CHAIN_ID"
curl --fail-with-body -sS "$BROADCASTER_BASE_URL/v1"
curl --fail-with-body -sS "$BROADCASTER_RPC_URL" \
-H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"broadcaster_getStatus","params":[]}'
Status includes versions, deployment identity, submissionHalted, and scheduling/provenance capabilities. Operators choose capabilities and pricing. Before integration, confirm that the selected deployment supports the methods, scheduling capabilities, and proof formats you need. An interface described here does not establish availability on a public service.
Freeze fees before authorization
The service accepts SDK-generated canonical single-request calldata for transact, shield, createCredit, creditDraw, updateCredit, and revokeCredit. Callers cannot supply their own outer aggregates; address registration is not a supported relay entry point.
estimateQuote prices a concrete public intent; getQuote signs the final fee-bearing intent. Fees can alter change, inputs, and funding authorization, so rebuild and re-estimate until stable before authorization and proving. A quote is not wallet spending authorization.
The user pays an agreed fixed public fee in the same token; the service pays native gas. Successful execution accrues fees to the Protocol token/feeRecipient ledger. Reverts roll fees back with business state. Credit draw usage is gross while the ordinary receiver Note is net of fees. Credit create/update/revoke fees come from the owner's authorized wallet; creating a grant generally prepays no principal.
Separate sending from final confirmation
The durable id returned by submission identifies a service job. It differs from the JSON-RPC request id and the wallet's local operation ID. Save the complete original request before sending. If the response is lost, replay it unchanged to recover the same record; do not obtain a new quote or change inputs as a retry.
confirmed means successful receipt execution and reverted means reverted execution. Neither implies finalized. Read the separate confirmation and authenticate canonical chain facts according to business policy. An HTTP timeout does not prove the service rejected the request.
Continue integration
- Quoting, submission, and recovery: workflow, methods, and states.
- Scheduling and cancellation: signed time windows and cancellation boundaries.
- Security and trust: signatures, privacy, and service trust.