`TokenVault` is a workspace contract with no connection to the protocol

[Jaydbrown]

contracts/token-vault/ is a full Cargo.toml workspace member with its own tests, but DripStream / DripFactory / DripGovernor never reference it, and it does not appear in docs/architecture.md or the ADRs. Clarify its role (is it a planned escrow backend? an experiment?) in the docs, or remove it from the workspace so cargo build --all / audits don't cover dead surface.

---

Filed from a codebase review pass.

[Fabluchy]

@Fabluchy has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’m interested in contributing to this task because I enjoy understanding and improving smart contract architecture. I’d like to investigate the TokenVault implementation, clarify its relationship with the protocol, and help document or address the separation where needed.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Fabluchy to this issue.

[Toyosi5566]

@Toyosi5566 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'd like to take this issue on and clean up the unlinked surface area.
​Audit TokenVault against DripStream, DripFactory, and DripGovernor to verify whether it's dead code or an intended escrow backend.

​Update docs/architecture.md and ADRs with the explicit scope, or decouple contracts/token-vault/ from the root Cargo.toml members list to streamline cargo build --workspace and audit passes.
​Verify clean workspace compilation, unit tests, and CI builds post-refactor.

​Let me know if you'd prefer deprecation/removal or documentation update, and I can open a PR right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Toyosi5566 to this issue.

[harmondconsultant-png]

@harmondconsultant-png has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to take this issue. I’ve reviewed the scope and I’m ready to work on it immediately. I’ll keep the implementation focused, follow the existing code patterns, and test the relevant changes before opening the PR.

I can take it from implementation through review and keep the PR straightforward to verify.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @harmondconsultant-png to this issue.

[Pro-builder]

@Pro-builder has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I have looked at this issue and I'm certain I can deliver you a good solution and a satisfactory pr .

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Pro-builder to this issue.

[drips-wave]

Congratulations, @Pro-builder! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Pro-builder: 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]

This issue has been completed by @Pro-builder as part of the Stellar Wave Program's 8th Wave 🥳

😎 @Pro-builder: 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.