Currency and accounting
Keep units, network identity, balances, and settlement rules explicit.
One network, one currency context
MINT, BITS, and test SIG belong to distinct networks. Do not mix balances, fees, faucet expectations, or signing previews across them. Configured genesis supply is not a real-time circulating-supply measurement.
| Item | Details |
|---|---|
| evolve-canary-1 | BITS · 1,000,000 base units per display unit |
| sigil-mainnet-1 | MINT · 1,000,000 base units per display unit |
| sigil-velocity-testnet-1 | SIG · 1,000,000 base units per display unit |
Preserve integer precision
Balances and supply use base-unit integers. Avoid floating-point arithmetic for signing or accounting. Use arbitrary-precision integers and a lossless JSON strategy when numeric values can exceed your runtime’s safe-integer range.
curl --fail-with-body --show-error --silent --max-time 15 'https://rpc.sigil.ml/rpc' \
-H 'content-type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"sigil_getBalance","params":{"did":"YOUR_ACCOUNT_DID"}}'Read policy before estimating outcomes
Transfer, staking, delegation, and rewards have concrete code paths, with system-contract and policy considerations. Fee levels, stake minimums, reward settings, and allocations must come from the selected network configuration rather than a fixed marketing example.