Design and implement $BORO treasury claim distributor #11
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
symphony
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Borodutch/borodutch-tools!11
Loading…
Reference in a new issue
No description provided.
Delete branch "bdt-kaneo-12-boro-distributor"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
BoroMerkleDistributoras the recommended mainnet $BORO treasury claim path.envsecret files while keeping.env.exampletrackedDesign
The PR chooses an on-chain Merkle distributor over a centralized backend treasury wallet for mainnet $BORO. The Merkle root is immutable, claims are keyed to
msg.sender, double claims are blocked on-chain, and owner withdrawal is allowed only after the claim deadline for unclaimed tokens.Validation
forge fmt --checkforge testbun run checkbun run testbun run buildgit diff --checkgit check-ignore .env .env.productionconfirms secret env files are ignored;.env.exampleremains tracked/not ignoredManual QA: not required for this contract/docs-only change. Review should focus on the Solidity distributor design, Merkle leaf convention, Base mainnet deployment envs, and funding/claim handoff in
docs/boro-merkle-distributor.md.Kaneo: BDT-KANEO-12