Nothing in Parts A, B or C needs this. It is included only because the window is open: two settled events today, a production state migration on the money path after the first funded campaign, and one audit round instead of two.
Today DataKey::EventSubmission(u64, Address) allows one anchor per wallet per event. That does not block one submission entering several tracks; it blocks several separate submissions in one bounty.
Done when
- The key carries a third dimension
- submit, withdraw, count and anchor lookups updated
- Backend subscribers that resolve anchors updated
Kill switch: if the audit is scoped and priced before implementation starts and this materially increases it, drop this issue. It is first on the cut list.
See plan 1.3, 4.3 and 7.8.
Plan: boundless-bounty-programs-implementation-plan.md
Nothing in Parts A, B or C needs this. It is included only because the window is open: two settled events today, a production state migration on the money path after the first funded campaign, and one audit round instead of two.
Today
DataKey::EventSubmission(u64, Address)allows one anchor per wallet per event. That does not block one submission entering several tracks; it blocks several separate submissions in one bounty.Done when
Kill switch: if the audit is scoped and priced before implementation starts and this materially increases it, drop this issue. It is first on the cut list.
See plan 1.3, 4.3 and 7.8.
Plan:
boundless-bounty-programs-implementation-plan.md