Documentation

SatoshiCore is an independent, non-commercial study project: it exists to understand — by building and running — how a coin, a ledger and a wallet really behave. Nothing here is sold, there is no presale or token offering, and nothing on this site is investment advice. The first phase has one goal: a chain and wallet that simply work, send and receive included. If NSAT ever comes to have value, that would be a later, openly discussed chapter — this page makes no claims about it today.

• Own chain: SatoshiCore, with its own genesis — not a token on another network and not a Bitcoin account.
• Supply: fixed at genesis and never re-minted — no inflation and no halving schedule. The exact figure is a ledger fact, not a marketing number.
• Decimals: 0 — one atomic unit is one NSAT; the wallet refuses fractional amounts.
• Fee: 10 NSAT per operation, read from the live ledger header before signing.
• Base reserve: 100,000,000 NSAT; a brand-new account needs 200,000,000 NSAT on its first deposit (2× reserve, a CREATE).
• Accounts: Ed25519 · G… strkey (CRC16) — the same address works on the iPhone app, the desktop wallet and this site.

• satoshicore.org is a static export (output: 'export') served by Caddy from this machine — no Node.js server runs behind the page itself.
• The page calls its own origin: /api/v1/* goes to the Web Wallet API Gateway and /v1/* to the block indexer. One domain, no CORS preflight, and the same build works on any hostname Caddy answers on.
• Three separate services sit behind it: the nsat-core node (loopback only), the API gateway (read-only lookups + relay of already-signed envelopes), and the read-only indexer that powers the search page.
• If a service is down the UI says so — it never shows a fabricated balance, fee or history row.

# build with the same-origin API switch
NEXT_PUBLIC_API_SAME_ORIGIN=1 npx next build

# publish the export to the directory Caddy serves
rsync -a --delete out/ /usr/local/var/satoshicore/web/

• Seeds are generated in the browser, encrypted with PBKDF2-SHA256 (600k) + AES-GCM and stored only as ciphertext. Signing happens client-side; the gateway receives signed envelopes only.
• A signature is refused unless the gateway reports the exact network identity NSAT Mainnet ; October 2026 ; bc3098829fffc717.
• Shielded operations need the native prover and are desktop-only; this site states that instead of faking the feature.
• See SECURITY.md in the repository for the full review.