2.0 beta

Address by name. Commit by hash.

A global, identity-focused DeFi layer-0 — currently in beta on the Simba testnet. Run a node, open the wallet, and use names — not opaque key hashes alone.

Sign up Log in Install & run a node

Get started

The site and wallet are this open-source tree (Guld 2.0 beta on Simba testnet). Your peer runs guld-node; the browser talks to its HTTP API.

  1. Sign up or log in

    Pick an available name, generate keys in the browser, and get sponsored on-chain (testnet faucet, a friend, or an optional paid desk) — or log in with a key you already have.

  2. Use your wallet

    Look up balances and activity. Send and sponsor flows live in this PWA; keys stay on device.

  3. Explore the chain

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

Sign up Log in Explorer

Install

From a checkout of this repository (Rust toolchain required). Serves the HTTP API and this static tree — including /repos/ for 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/wallet/. Full flags and legacy import: see the repo README.

How Guld compares

Guld 2.0 sits below general-purpose L1s as an L0 witness hub — names and proofs first, not a general VM. Side-by-side with Guld 1.0, Bitcoin, Ethereum, Solana, and Cosmos Hub (representative IBC L0).

Whitepaper §1.5 · Markdown source

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, bonds, 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