WARTIME
WARTIME · FIELD ISSUE · NO. 001

WAR
CHEST

No KYC. No accounts. No surveillance.
The wallet talks to the chain and nothing else.

PulseChain Ethereum Robinhood Chain

v0.1.0 is a field-test build: load it unpacked, keep small balances in it, report what breaks. Built on the open-source Rabby engine (MIT) with the DeBank backend, analytics and error reporting cut out at the source. Not affiliated with Rabby or DeBank.

WAR CHEST wallet dashboard and network list

The promise, in plain words

STANDING ORDERS

No KYC, no accounts

You never sign up for anything. Keys are generated on your device and encrypted with your password. There is no cloud backup, no email, no phone number, no "account" anywhere to freeze.

How it is enforced: self-custody keyrings from the Rabby engine; nothing in the code base can send a key off the device.

No surveillance

Rabby ships with a portfolio backend (DeBank), Google Analytics, Matomo and Sentry. WAR CHEST compiles every one of them out and blocks their hosts twice — once in the HTTP layer, once by wrapping fetch and WebSocket themselves.

How we know: every build is booted in a real browser and every outbound host is logged. The list is: the wallet itself, the chain RPC, and whatever dapp you open. Nothing else.

Direct RPC only

Balances, gas, sends and signatures go straight to the chain's RPC node. No middleman API reads your addresses to "enrich" them. That also means no portfolio charts, no swap aggregator and no DeFi dashboards — on purpose.

Default nodes are public (publicnode.com). You can point every chain at your own node in one tap — see Field Comms.

Field comms

WHO CAN SEE WHAT
READ BEFORE USE

The one thing a self-custody wallet cannot hide

Every wallet has to ask a node for your balance. WAR CHEST asks the chain's RPC node directly — and that node sees your IP address together with the addresses you ask about. With the default public nodes, that is the whole of what leaks. With your own node, nothing leaks at all.

Most people will keep the public nodes, and that is fine. The card on the dashboard just makes sure you decided that yourself.

  1. Open the wallet. The FIELD COMMS card names the node each chain is on.
  2. Tap USE MY OWN NODE, pick the chain, paste your RPC URL.
  3. The card now marks that chain · yours. Tap PUBLIC IS FINE to dismiss it for good.
— WAR CHEST field manual, v0.1
The Field Comms card on the WAR CHEST dashboard

Three fronts

SHIPPED CHAINS
PRIMARY · CHAIN ID 369

PulseChain

Where WARTIME lives. $WARTIME is pre-listed on first run.
Default node: pulsechain-rpc.publicnode.com
Fallbacks: g4mm4.io, rpc.pulsechain.com
CHAIN ID 1

Ethereum

Mainnet ETH and every ERC-20 you add.
Default node: ethereum-rpc.publicnode.com
Fallbacks: llamarpc, ankr
CHAIN ID 4663

Robinhood Chain

The Robinhood L2, ETH gas.
Default node: rpc.mainnet.chain.robinhood.com
Fallback: robinhood-rpc.publicnode.com

Any other EVM chain can be added under Settings → Add Custom Network. It runs over direct RPC exactly like the three above.

Enlist the wallet

INSTALL · v0.1.0 FIELD TEST

CHROME · EDGE · BRAVELoad unpacked

  1. Download the zip and unzip it somewhere it can stay.
  2. Open chrome://extensions (or edge://extensions) and switch on Developer mode.
  3. Load unpacked → pick the unzipped folder.
  4. Pin WAR CHEST to the toolbar. Create or import a key. Done.
Why no store listing yet: forks of wallets get a slow, thorough review. It is coming; the unpacked build is the same code.

FIREFOXTemporary add-on

  1. Download the xpi and unzip it (it is a zip file).
  2. Open about:debugging#/runtime/this-firefox.
  3. Load Temporary Add-on… → pick manifest.json in the unzipped folder.
  4. Firefox drops temporary add-ons on restart; reload it the same way.
Signed build: a Mozilla-signed package is next; once it is up, the same link installs permanently with one click.
Onboarding Network list Dapp connect approval Signing approval Custom RPC settings

Read the fine print

HONEST LIMITS · v0.1

What v0.1 does not do

  • No portfolio value, price charts, NFT gallery or DeFi positions — those all came from the backend we removed.
  • No built-in swap or bridge. Use the dapp of your choice; WAR CHEST connects like MetaMask.
  • No transaction simulation or scam scoring on approvals. Read what you sign.
  • Transactions are sent as classic (type-0) transactions on all three chains — valid everywhere, occasionally a little dearer on Ethereum.

What you are trusting

  • Yourself. Self-custody means no reset button: lose the seed phrase and the funds are gone.
  • The RPC node you talk to — see Field Comms. Your own node removes even that.
  • A fork that has not had an independent audit. The Rabby engine underneath has; our changes have been reviewed internally and every build is host-audited. Keep field-test balances in it.
  • Hardware wallets (Ledger, Trezor, Keystone, OneKey) work through the engine's own connectors; nothing about them changed.

Source: MIT, published with the v0.1 release. Read the privacy statement and terms — both fit on one screen.