Bring a machine

The Commons grows on spare compute. If you have a laptop, a free Kaggle GPU, or a spot VM sitting idle, you can lower a substrate's error bars — and be credited for it. Here's the whole loop.

Pull a target's contract and geometry, walk one shard with a random seed, sign it, and push it to the inbox. No orchestrator, no coordination call. Come back whenever; the floor is a little lower.

Get started

pip install "substrate-bank"          # pulls the dmipy-sim engine + cryptography

# contribute to the neediest open target (auto-picked), signed by default
python -m substrate_bank.contribute \
    --repo dmrai-lab/substrate-bank \
    --walkers 5000 --gpu --loop 4 --name "Your Name"

That's it. Each shard is walked, signed with your key, and submitted to the target's inbox. Size --walkers to your time budget; a coordinator's QA pass promotes good shards into the pool.

• Any idle box

  ---

  The mesh walk is the same everywhere. A free GPU (Kaggle) is far faster than free CPU for sub-micron substrates, but a laptop overnight is a real contribution too.

• No secrets in the open

  ---

  A public bank means workers need no read token. Where a token is needed (private engine, write access), it goes through environment variables or platform secrets — never pasted around.

• Give what you can

  ---

  There's no minimum. Ten thousand walkers or ten million, every disjoint shard only helps. Nothing you submit in good faith can make a target worse.

Want credit by name?

Signing is on by default, so your walkers are always attributable to your key. To be credited by your name on the solved substrate, claim your key once with a pull request.