Contracts & events

Current deployment

The current v2 public manifest targets Monad testnet, chain ID 10143, starting at block 70697469. Deployment addresses below are from that manifest, not a claim that a new v2 mainnet release has happened.

BondlineCore
0x7b37d3be163f10af7662e083709aea9102530823

CircleFactory
0x27c527934b115e64eed61c5f783a1060b540a6c4

Circle implementation
0xb96f540bf5df893a06670705dc43f40cfc75ada6

Important entry points

• openBond / openVerifiedBond: escrow a new commitment with its frozen reviewers and verifier rule.
• backCommitment: record encouragement independently of evidence voting.
• declareDone / cosign / object: submit evidence and record peer responses.
• verifyBalance / attest: apply the selected automatic or trusted external rule.
• resolveExpired / crossMissed: settle expired commitments without a privileged operator.
• closePeriod / claimReward: close a ready deadline week and distribute reserved rewards.
• withdrawRefund: receive a credited refund to a payable address.
• invite / join: issue and accept later Circle invitations.

Event catalog

• CircleCreated, MemberInvited, CircleJoined: group membership and invitations.
• BondOpened, VerificationConfigured: commitment creation and completion rule.
• CommitmentBacked: social encouragement, never evidence approval.
• BondDeclared, Cosigned, Objected: evidence review and peer decisions.
• CommitmentVerified, BondResolved, RefundCredited: outcome and returned-stake accounting.
• PotPeriodClosed, PotRewardClaimed: weekly pool closure and claims.
• PayoutProposed, PayoutCosigned, PayoutExecuted: legacy/unreserved payout proposal path.
• TesterJoined: explicit evaluation enrollment, not proof of a unique real human.

Indexing and compatibility

Keep strict ABI decoding for recognized events. Filter housekeeping logs before decoding Circle membership. Every event projection is scoped to the configured chain and cursor. Numeric values can exceed JavaScript’s safe integer range; the snapshot path preserves amounts as strings/BigInt.

Legacy v1 mainnet addresses exist in repository history. Their Pot governance differs from v2 reserved weekly rewards. Do not mix chain IDs, old deployments, or database cursors.

Source and audit status

See contracts/src and contracts/test for implementation and tests. These contracts are not independently audited. UI wording is explanatory; the deployed bytecode and ABI determine behavior.