Install & Run

The web app is self-contained: the entire engine runs in your browser. There is nothing to install — open the app and the vault gate greets you.

The web app

No build step, no backend, no wallet extension:

• Static hosting — the deployed site is the product.
• The engine ships with the page as plain JS modules: JBCore (chain + Pons calldata), JBVault (the encrypted vault), JBFund (relay.link distribution), JBTerm (launch-day terminal).
• ethers v6 is vendored under assets/js/vendor/ — no CDN, no npm.

The first run walks the Setup pipeline in order: seed phrase (shown once), wallet derivation, fund wallet 0, distribution window, relay distribution, launch.

Keep the tab open during the funding and auto-buy windows — execution happens in the page. If you close it, the funding plan is persisted and resumes where it stopped on the next open.

Optional: the standalone Python engine

Advanced users can still run the original engine from bundler/ — a CLI plus an optional local server. It is not required by the web app; the two share no state.

Requirements — Python 3.10+ and three packages:

pip install eth-account mnemonic pycryptodome

Generate the vault, then either drive the local server:

cd bundler
python3 wallets.py generate --count 25   # steps 1+2
python3 server.py                        # http://127.0.0.1:8787/app

The server binds to 127.0.0.1 only. It serves the same frontend as the public site plus the /api/* endpoints the Python engine drives.

Or skip the server entirely and use the terminal interface for direct control:

python3 pons_terminal.py                 # token / auto / holders / sell / dump

State

Everything the Python engine writes lives in bundler/out/:

File	Contents
vault.json	encrypted vault (seed + keys, AES-128-CTR)
addresses.csv	derived bundle wallet addresses
funding-plan.json	the distribution plan and per-transfer status

out/ is git-ignored and never deployed. Delete it to start completely fresh — the seed cannot be recovered afterwards.

The browser engine keeps its own, separate state in the site's localStorage: the encrypted vault (jb:vault), the funding plan (jb:fundplan), and the terminal session (jb:term). Clearing site data is the browser equivalent of deleting out/ — same warning applies.