Wallet transactions

What your wallet signs, and what it does not.

ForkReason never signs a transaction on your behalf. Reads require no wallet at all; writes require your own signature.

What needs a wallet

Recording a resolved case on chain.
Submitting a challenge that produces a new revision.

What does not

Tracing a relationship.
Reading any case report, evidence item or revision.
Browsing Explore.

The transaction lifecycle

ForkReason displays the real status from the GenLayer client. A transaction moves through submitted, awaiting decision, and then either accepted or failed.

A decided transaction is not a successful one. The status ACCEPTED means the committee agreed on the receipt; ForkReason also requires a successful execution result before reporting success.

Fee and rejection errors

A rejected transaction, an insufficient balance, and a wrong network each produce a specific, actionable message rather than a generic failure.