Guld

Address people by name.

Guld is in beta on the Simba testnet. Sign up for a name, keep keys on this device, and send tGULD without pasting addresses.

Sign up Log in

Build a dapp Run a peer Explore the chain

2.0 beta

Names, not addresses

On Guld you are reachable as a name. Friends send to you the same way they talk about you — no long hex strings on the happy path.

  1. Sign up or log in

    Claim an available name and protect this device with a passphrase — or unlock a key you already keep here.

  2. Use your wallet

    See your balance and activity. Send to people you know; keys never leave the browser unless you export a backup.

  3. Look around

    Browse live blocks in the explorer, or the genesis import under legacy block 0.

Sign up Log in

For developers

Build a Guld dapp

Early Guld is a developer protocol: register a name, keep app state in a leaf (files + hashes), and tip the chain with UpdateMaster when keys agree. Validators never run your game logic — they witness that the right people authorized the new head.

  1. Use the JS SDK

    @guld/js covers HTTP client, cosign, site-login, txs, and leaf master_hash helpers — guld-js README.

  2. Ship a leaf, not a VM contract

    Put software and state under a home tree. Tip when parties cosign. Pattern notes: reference dapp · spec 11.

  3. One name across sites

    Extension site-login demo shows dapps verifying “log in as alice” without a per-site wallet.

Play the demo guld-tic-tac-toe How it works

For peer operators

Install & run a node

This site is the open-source tree served by your peer. Run guld-node to expose the HTTP API, wallet, explorer, and /repos/ package clones. 

cargo run -p guld-node -- \
  --datadir ./.guld-data \
  --rpc 127.0.0.1:8545 \
  --http 127.0.0.1:8080 \
  --http-static . \
  --dev \
  --miner alice

Then open http://127.0.0.1:8080/. Flags and legacy import: README · Docs · Settings

Authorize by proof. Leave leaf law to the leaf.

Guld 2.0 is a hard fork of Guld 1.0: preserve historical balances where possible; move header consensus to open PoW while keeping identity-first names, groups, and leaves. Validators stay lean — fixed transaction schemas, hashes, signatures, and a small set of built-in state updates. Custom operations live in leaves.

Identity-first

Transfers and tips bind to usernames and groups — not opaque key hashes alone.

Network as witness

Guld verifies enumerated leaf-consensus proofs and records new master hashes.

Lean validators

No general VM. No requirement to index social graphs or execute leaf interpreters.

FAQ

Does Guld 2.0 replace Guld 1.0?
No. 2.0 is a hard fork from a 1.0 ledger snapshot. Guld 1.0 keeps running — 1.0 coins and software still work there.
How do 1.0 balances show up on 2.0?
Snapshot balances import at 2.0 genesis and unlock when you claim your name (ClaimLegacy key upgrade).
Why PoW instead of 1.0 stake?
1.0 used identity/contribution-weighted stake; staker agreement broke down and trust fell. 2.0 keeps names and leaves but anchors headers in conservative open PoW.

Full FAQ