Open source · A small fix is a good start
MoneySwitch is a programmable cloud wallet you host on your own server: one payer, multiple agents, separate spending keys. Improve the docs, smooth an agent integration, or fix a bug you found while trying it.
Already have a branch? Open the comparison and select it. First contribution? Fork the repository and follow the steps below. You can read this guide without signing in; GitHub requires an account to fork, post an issue or submit a PR.
Pick a useful change
Fix a confusing setup step, a broken link, a translation or an agent integration example. A small, specific correction can go straight to a PR.
Edit the Chinese trial guide on GitHub ↗GitHub can guide you through creating a fork and proposing the edit. Preview the page before submitting.
Share the steps, expected result and actual result. A minimal reproduction helps; if you have a fix, include the relevant verification in your PR.
Share trial feedback ↗For a new feature or a substantial change, describe the use case before building it. This helps keep contributions aligned with the wallet’s scope.
Propose a contribution ↗Your first pull request
Start with something you can reproduce or explain in a sentence. Read CONTRIBUTING.md. For deployment or payment behavior changes, also read SPEC.md and discuss substantial changes first.
Click Fork. Replace YOUR_GITHUB_USER below with your GitHub username, or copy the clone URL from your fork’s Code menu.
git clone https://github.com/YOUR_GITHUB_USER/moneyswitch.git
cd moneyswitch
git remote add upstream https://github.com/dongsheng123132/moneyswitch.git
git switch -c docs/my-first-fixChange only what your fix needs. The homepage, trial and contribution pages live in site/. Blog text lives in docs/blog/; after editing it, run node scripts/build-blog.mjs and include the generated pages.
Follow the test requirements in CONTRIBUTING.md. Preview website changes in both languages and at phone width. Say what you actually checked, and what you could not check.
Review the diff first. Replace the example path with the files you intentionally changed; keep credentials and local wallet data out of the commit.
git diff
git add path/to/changed-file
git commit -m "docs: clarify the trial setup"
git push -u origin docs/my-first-fixOpen the upstream comparison and choose compare across forks. Use dongsheng123132/moneyswitch with base: main; use your fork as the head repository and docs/my-first-fix as the compare branch.
Review the diff, explain what changed and how you verified it, and personally read the CLA before checking its agreement box. Submitting a PR starts maintainer review; it does not mean the change is approved or merged.
“The trial guide repeated a payment instruction. I clarified that the generated skill already makes that request, and checked both language pages.” That is more useful than “improve docs.” Include screenshots when they help explain a visual change.
No mainnet payment is required. Start with the testnet trial or a documentation issue. Follow the contribution guide for offline tests; live-payment testing uses your own test wallet, never a maintainer’s shared wallet.
One deployment spends for one payer using budget-limited MoneyKeys. Payments currently cover supported x402 APIs in USDC. This is a self-hosted hot wallet: access to its wallet data and unlock file grants access to funds. Changes to payment policy, deployment or trust boundaries need to follow the spec.
The contributor personally reads CLA.md and checks the PR agreement box if they agree. Reading this page does not sign anything, and the guide does not accept terms on your behalf.
Rewards may be offered at our discretion based on participation and feedback, with details announced separately. Opening or merging a PR does not guarantee a reward or a fixed amount.
MoneyKeys, approval PINs, recovery phrases, private keys, administrator tokens and sign-in links, raw logs containing credentials, and wallet data. Share redacted examples. Report vulnerabilities through private security reporting, following SECURITY.md.
You do not need a fix to tell us where setup failed or which agent workflow is missing.