Repository navigation
Conversation
Adds /security/ to the site: key separation (the agent holds only an agent token; wallet, payment, email and social credentials live only in the guard), what the agent can and can never do, the fixed-order policy that triggers approvals, and exactly what the freeze and loss stop do. Links it from every footer, the safety section, and the sitemap. Board card #828
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
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.
What
Adds a
/security/page to the Cashmaxx website (cashmaxx.neu.so) stating the guard's threat model, and links it from every page footer, the landing page's Safety section, andsitemap.xml.Why
Serious self-hosting buyers compare against custodial pitches (e.g. MetaMask Agent's advertised $10k transaction protection + 2FA, Coinbase's KYT screening + TEE key isolation, June 2026). The landing page lists "budget caps · approvals · kill switch" but never explains the actual boundary — that the agent never sees wallet, payment, email or social credentials. This page answers that question directly, and honestly positions self-hosted key separation against insured custody instead of pretending to compete with it.
Contents (all grounded in the code, not invented)
~/.cashmaxx/guard.json(0600); agent holds only an agent token (SHA-256 digest, constant-time compare; no approve/patch/unfreeze scope); owner PIN as scrypt hash, in-memory 12h sessions; guard Telegram bot on its own token, owner chat id checked. —cashmaxx/guard/auth.py,docs/cashmaxx/ARCHITECTURE.mdcashmaxx/guard/policy.py,watchers.pyapp.py,watchers.pyHow it was tested
html.parser): passes.site/public: no broken links; new/security/URL resolves viasite/public/security/index.html.cashmaxx/guard/policy.py,auth.py,app.py,watchers.py,config.pyanddocs/cashmaxx/ARCHITECTURE.md; no claim on the page that the code doesn't enforce.Board card #828