For developers

Build on Lineage

Lineage is a Layer-1 where market policy itself is programmable. The network performs bounded search over policy space and verifies results cryptographically, so the mechanisms governing markets can evolve without changing the chain. Everything is open: evaluate the protocol against the whitepaper, clone the repos, and prototype.

Read the docs View GitHub

Everything you need to point a client at Lineage, in one place: the base URLs by node class, the current network status, and how to stand up your own stack.

Network statusA managed public mainnet and testnet are being ported and will be announced here soon. Until then, point a client at the base URLs below, or run your own mempool / storage / miner stack locally. The route names and JSON contracts are identical either way.

Mempoolhttps://mempool.lineage.toTransactions, balances, supply, and mempool metadata.
Storagehttps://storage.lineage.toFull blockchain history and block reads.
Minerhttps://miner.lineage.toOperator-facing status where a release exposes it.

Pick an HTTP client, point it at the public base URL for your node class, and call the documented routes. Subsystems are exposed on separate hosts: mempool calls use the mempool host, storage reads use the storage host, and so on. A minimal connectivity check is a read-only call such as fetch_balance.

bash

# Read-only connectivity check against the mempool host
curl -sS -X POST "https://mempool.lineage.to/fetch_balance" \
  -H "Content-Type: application/json" \
  -H "x-cache-id: 0123456789abcdef0123456789abcdef" \
  -d '["<address-1>"]'

# Example success envelope
{
  "id": "45v340cd2f8c4782a5b058832565afb1",
  "status": "Success",
  "reason": "Balance successfully fetched",
  "route":  "fetch_balance",
  "content": {
    "total": { "tokens": 5463669, "items": {} },
    "address_list": {
      "<address>": [
        { "out_point": { "t_hash": "g9182e1e2a55b0ef36f1183602d74e63", "n": 0 },
          "value": { "Token": 5463669 } }
      ]
    }
  }
}

The public HTTP API is organised by node class. Each subsystem is documented route by route, with full request and response JSON, including the standard error envelope.

https://mempool.lineage.to

Mempool API

Transactions, balances, supply, and mempool metadata: the write and query path for clients.

POSTfetch_balance
POSTcreate_transactions
POSTtotal_supply
POSTcreate_item_asset

Mempool reference

https://storage.lineage.to

Storage API

Full blockchain history. After blocks are mined and validated, they are persisted for long-term read access.

POSTlatest_block
POSTblock_by_num
POSTblockchain_entry

Storage reference

https://miner.lineage.to

Miner API

Operator-facing HTTP where a release exposes it, a small surface compared to mempool and storage.

GETinfo

Miner reference

Three official clients wrap the same API: wallet creation, key management, asset issuance, two-way payments, and chain reads. Configure each with a mempool base URL, a storage base URL, and a passphrase for local key encryption.

JavaScript / TypeScript

sdk-js

The client for browser and Node apps and wallets: create a wallet, issue items and assets, run two-way payments, send and receive. Drop-in for web front-ends and Valence servers.

lineage-foundation/sdk-js

Python

sdk-python

The client for backends, data tooling, and automation: key management, balance and supply reads, transaction construction, and two-way flows, the same surface as sdk-js, idiomatic for Python services and notebooks.

lineage-foundation/sdk-python

PHP

sdk-php

The client for server-side web stacks: wallet creation, asset issuance, payments, and chain reads from within PHP applications and CMS integrations.

lineage-foundation/sdk-php

Evaluate the protocol

Read Lineage: The Living Economy, the full technical and economic specification archived on Zenodo, alongside the concepts in the docs to understand how bounded policy search and cryptographic verification fit together.

Clone the repos

Every repository is open for review, issues, and contributions. The code that ships with the project lives on the Lineage Foundation GitHub organisation.

Prototype against the API

Start with small, read-only calls from the storage or mempool sections of the reference to confirm connectivity, then move on to transactions. Each endpoint page documents the exact request and response contract.

Specification and research questions live in the Fremen Forum (hosted on Discourse). Implementation questions belong in the repo issue trackers on GitHub.

Fremen Forum

Specification and research discussion for the protocol and its mechanisms.

Research & forum

Issue trackers

Implementation questions, bugs, and contributions on the open repositories.

Open GitHub repos

The protocol, the reference deployment, and the documentation are all open. Pick up the docs or jump straight into the source.

Read the docs Browse GitHub

Build on Lineage

Endpoints & network status

Talk to a node in minutes

Three node subsystems