Transaction lifecycle

Follow the public write flow from prepared calldata to wallet signature, EVM receipt, GenLayer transaction id, and consensus state.

Step 1

Prepared

Server validates inputs and encodes consensus calldata.

Step 2

The connected wallet signs and sends the EVM transaction.

Step 3

The app waits for the Bradbury EVM receipt.

Step 4

The app extracts the GenLayer tx id when logs expose it.

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, their lifecycle appears here and updates automatically.

Deployment

0x2a568e2f999401ca3f53de5df0f03f8ea01762feaf0670bb0897416476570d0c