evotools

Where DASH, credits and identities actually sit, and every move between them. Paste a name or an address and see the whole picture — including what an identity was funded with.

Mint an identity and claim a .dash name, then walk away with a ready .env. Testnet from a generated wallet, mainnet from your own key.

Make the funding address and the five identity keys with nothing sent anywhere. Download the page and run it on a machine that stays offline.

What an identity holds and how to move it: top it up from a platform address, pay out to one, or withdraw back to layer 1.

Run the cookbook recipes live against testnet or mainnet, right in your browser. Edit and run — no install.

Look up identities, DPNS names, data contracts and documents on testnet and mainnet, and read the shielded pool — with the SDK snippet that fetched each one.

Claim a .dash username for your identity — check and register, on testnet or mainnet.

Every contested .dash name masternodes are voting on right now, and every one they have decided — contenders, votes and dates.

The Orchard pool on Platform: how much is in it, how it moves week by week, what the six shielded moves cost, and whether an address is a shielded one.

Verified, runnable recipes for @dashevo/evo-sdk v4 — tested against testnet, ready to copy and run.

Scaffold a working Dash Platform app in one command — npm create evo-app. SDK wired up, identity handling in place.