For developers

Build on Guld

L0 witnesses names, tips, and proofs. Leaves run your gapps. Choose one path — we will show that walkthrough only.

Which path fits you?

Core Protocol & node Consensus, crates, specs — contribute to L0 itself. Most builders Gapp Product leaf Ship a gapp under a name — SDKs, remotes, site-login. No consensus hacking. Agents Scripts & AI clients HTTP, SDKs, MCP — draft tips and ledgers; keys authorize.

Core

Protocol & node

Check out the Guld leaf, build the node, and contribute to consensus, wallet UI, and specs.

  1. Thesis in two minutes

    Skim the whitepaper or FAQ — L0 is a witness hub, not a VM.

  2. Clone the umbrella

    git clone https://guld.io/repos/guld.git then init the packages you need — REPO_LAYOUT.

  3. Browse packages

    /software/ is the map of every Guld leaf package (protocol, SDKs, reference gapps).

  4. Build & run a node

    Follow the install guide (macOS / Linux / Windows), then guld-node --dev or a Simba peer — HOSTING, SIMBA.

  5. Where rules live

    Specs, rule bundles (spec 17), SOURCE_AND_RELEASE.

  6. Contribute

    CONTRIBUTING, GIPs, software flow (leaf → trunk commits).

Open software catalog Specs

Gapp

Product leaf

Run against a peer, use the JS or Python SDK plus extension login, and ship a leaf — without hacking consensus.

  1. Mental model

    Name + tip + leaf law; validators do not run your gapp — reference gapps (including forking guld-apps as a starter).

  2. Run or point at a node

    Install guld-node locally, or set a public Simba API base in wallet settings — full peer notes in install.md.

  3. Register a name

    Register on Simba (faucet when ready) so your gapp can address you by name.

  4. Publish remotes

    In wallet account tools, add git + http hints so hosts and /apps/ can find your leaf — remotes standard.

  5. Extension + site-login

    Site-login demo — then use the same identity in your gapp (spec 14 §10).

  6. SDK

    @guld/js (browser / Node) or guld (pip — Flask/Django/ops) — HTTP client, txs, cosign, leaf hashes, remotes.

  7. Copy or fork a reference leaf

    Play /ttt/ and clone guld-tic-tac-toe for the smallest tip loop — fork guld-apps for a full leaf host — or study the HTLC atomic-swap desk /dex/ / guld-dex ([GIP-41](/docs/?src=/docs/gips/gip-41.md)). Federation tips can use stake-weighted leaves ([GIP-42](/docs/?src=/docs/gips/gip-42.md)) — no dedicated wallet UI.

  8. Leaf standards

    docs/leaves/ — app manifest, remotes kinds, Postgres seal, cross-leaf.

  9. Discover & publish

    /apps/ — log in, list your gapp (prefills from remotes), seal under the apps tip.

Browse gapps Atomic swap DEX Play TTT Leaf standards

Agents

Scripts & AI clients

Coding agents and ops scripts use the same L0 as wallets — names, tips, proofs — via HTTP and SDKs. People first; agents draft, keys authorize.

  1. Machine entry

    Fetch llms.txt or AGENTS.md — peer URL, Simba chain_id, SDK lines.

  2. Talk to a peer

    GET /api/v1/chain/status on guld.io or your guld-node.

  3. SDK loop

    @guld/js or guld — status, name check, draft Transfer / UpdateMaster (see README agent sections).

  4. Optional MCP

    guld-mcp (@guld/mcp) — stdio tools (read + draft on; submit off by default). Ecosystem software — not inside guld-node — agent help · GIP-39.

  5. Name / subaccount

    Register or use a subaccount under a human name for attributable bots.

  6. Ship as a gapp

    Tip leaf state under that name; add site-login for human users — agent help · research.

llms.txt @guld/js guld (Python) Agent help