Bradbury live0xC11b90c7...Bc3F6f87
Bradbury required
Transactions
Transaction lifecycle
Follow the public write flow from prepared calldata to wallet signature, EVM receipt, GenLayer transaction id, and consensus state.
Prepared
Server validates inputs and encodes consensus calldata.
Wallet signature
The connected wallet signs and sends the EVM transaction.
EVM receipt
The app waits for the Bradbury EVM receipt.
Consensus status
The app extracts the GenLayer tx id when logs expose it.
Local transaction history
Stored in this browser only. It is not a backend source of truth.
No local transaction history
When you create campaigns, submit projects, or run reviews from this browser, confirmed EVM receipts will appear here.
Submit project