Repository navigation
Beneficiary-scoped work identity and third-party proposals - #220
Merged
Merged
Conversation
…se pool. Explore lists configured content checks instead of static kind labels. The noninflammatory board shows capped registry posts, with hide and channel scopes. Funding the property opens Aligning and a prefilled delegation deposit.
The scratch brainstorm is now findable from the CSM founder reading list, structured fundable work, and the composability notes. The existing structured-work TODO points at the boundary to preserve. Nothing in the notes is a new task.
Ordinary projects and content contracts share ContentRegistry occupancy. The creator is recorded for history and does not get a separate slot for the same id. Testnet redeploy, history UI, and a browser pass are filed as follow-ups.
Scope ordinary work to its intended beneficiary (derived from direct recipient or stable named beneficiary, independent of initiator/owner); ContentRegistry.registerBeneficiaryWorks hashes (beneficiaryId, localIdHash). Allow third-party ordinary proposals with explicit per-project acceptance, seven-day veto window before the funding deadline, and a new WorkFundingCondition that expires unaccepted/too-late proposals. Veto releases the batch atomically; expired reservations release permissionlessly via SDK/UI. Status reads now use actual condition success/failure. Fix creation/discovery to also track ProjectCreated from FixedControllerFactory. Update SDK/indexer ABIs, specs, and ADR 0019.
AdamSpitz
commented
Oct 13, 2026
AdamSpitz
left a comment
AdamSpitz
left a comment
Owner
Author
There was a problem hiding this comment.
Review receipt.
Reviewed ContentRegistry work occupancy, ProjectFactory beneficiary scope and veto release, WorkFundingCondition accept/veto/success rules, and the SDK work-id hash. No findings.
Reviewed-with: grok
Reviewed-files: 93
Reviewed-commit: 5a4956a
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
(stable beneficiary identity, exact local work id), so unrelated beneficiaries no longer compete for one slot and a second initiator cannot fund the same beneficiary's work again.Decision:
specs/decisions/0019-beneficiary-scoped-work-identity.md.Test plan
hardhat/test/BeneficiaryWork.test.js,WorkItems.test.js, andProjectFactory.test.jssdk/src/subsystems/work-items/ids.test.tsand lazy-giving work-item integration tests