Repository navigation
[SC-76] contracts/README.md's ownership-split section needs updating once contrib's dead code is resolved #1347
Description
Overview
contrib/src/lib.rs's doc comment explicitly defers to contracts/README.md "for the full entrypoint, storage, event, and error tables" and "the ownership split" between assetsup and contrib — once [SC-57] resolves which of kyc/oracle/staking/escrow/detokenization/restrictions/tokenization actually end up compiled (if any), that root README's capability table needs to be checked against the new reality, since right now it presumably reflects the current, not-yet-cleaned-up state.
Tasks
- After [SC-57] lands, re-read
contracts/README.md's ownership/capability table and update every row affected by the change. - Cross-check
contrib/README.md's own tables (it already has one, referenced in earlier greps) for the same drift.
Acceptance Criteria
-
contracts/README.mdandcontrib/README.mdaccurately describe the post-cleanup capability split with no stale rows.
Dependencies
Depends on [SC-57].
Notes for Contributors
Requires Rust + Soroban. Workspace: contracts/ (soroban-sdk 23, members: assetsup, contrib, multisig-wallet, multisig-transfer, asset-maintenance). Run cargo test --all, cargo fmt --all -- --check, and cargo clippy --all-targets --all-features -- -D warnings before opening a PR — CI enforces all three. Comment below to be assigned.
Activity
josephokunbor96-cmd commentedon Aug 24, 2026
@josephokunbor96-cmd has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @josephokunbor96-cmd to this issue.
onakijames-droid commentedon Aug 24, 2026
@onakijames-droid has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @onakijames-droid to this issue.
hmhidey111-collab commentedon Aug 24, 2026
@hmhidey111-collab has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @hmhidey111-collab to this issue.
AGWAM001 commentedon Aug 24, 2026
@AGWAM001 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @AGWAM001 to this issue.
danielships commentedon Sep 24, 2026
@danielships has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @danielships to this issue.
drips-wave commentedon Sep 24, 2026
Congratulations, @danielships! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @danielships: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
drips-wave commentedon Sep 24, 2026
This issue has been completed by @danielships as part of the Stellar Wave Program's 9th Wave 🥳
😎 @danielships: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.