Skip to content

fix(bridge): record proposer on bridge proposals for relayer attribution - #505

Open
Anuoluwapo25 wants to merge 1 commit into
rinafcode:mainfrom
B-Hands:fix/495-bridge-proposal-proposer
Open

fix(bridge): record proposer on bridge proposals for relayer attribution#505
Anuoluwapo25 wants to merge 1 commit into
rinafcode:mainfrom
B-Hands:fix/495-bridge-proposal-proposer

Conversation

@Anuoluwapo25

Copy link
Copy Markdown

Summary

  • Add a proposer: Address field to BridgeProposal, captured and authenticated (require_auth()) at creation time in BFTConsensus::create_proposal
  • Emit the proposer in ProposalCreatedEvent so off-chain indexers can attribute proposals without an extra storage read
  • Update create_bridge_proposal contract entrypoint and all existing tests for the new signature
  • Add a test confirming the stored proposal and emitted event both carry the correct proposer address

Closes #495

Test plan

  • cargo test (full suite, including new create_proposal_records_and_emits_proposer test)
  • cargo clippy --all-targets — no new warnings
  • cargo fmt --check — clean

Bridge proposals had no way to attribute a proposal to the relayer that
submitted it, blocking per-relayer accountability and analytics for the
indexer. create_proposal now takes and authenticates a proposer address,
stores it on the BridgeProposal, and emits it in ProposalCreatedEvent.

Closes rinafcode#495
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bridge proposals have no proposer field, blocking relayer attribution

1 participant