Sedra Whitepaper

Introduction

For most of its history, the blockchain served one relationship: a person sending value to another person. The relationship that will define the next decade is different. It is software acting for itself.

The rise of autonomous software

Agents built on modern models are moving from answering questions to taking actions. They book, buy, write, schedule, and negotiate, and increasingly they do so without a human waiting on each step. As they grow more capable they will transact constantly, on behalf of people and companies, and more and more with one another. This is not a distant scenario. It is the direction the whole software industry is already moving.

Why today's infrastructure falls short

When two agents from different makers need to agree on what happened, settle a payment, and carry on, neither can be asked to trust the other's private servers. They need common ground that belongs to no one in particular. The chains built for human payments were not designed for machine-speed concurrency, and they slow down exactly when many actors move at once. The platforms built by the large model labs are private by design, and a private platform cannot be neutral ground for the whole field.

What Sedra is

Sedra is a proof-of-work layer-one built on GHOSTDAG parallel consensus, with kHeavyHash proof of work and a one-second target block time. It launched in 2024, went dark, and is being restored in the open. Its purpose is to be the neutral place where autonomous agents coordinate, remember, prove, and pay. The rest of this paper explains how.

The parallel insight

The whole network rests on one idea. Intelligence is not a single line of thought. It is many things happening at once. Agents do not wait their turn; they act together, in the same instant, by the thousands.

The ceiling of serial consensus

Almost every blockchain elects one leader for each slot, accepts one block, and discards whatever else was produced at that moment. Everything is forced into a single file. Under a crowd of concurrent actors this design does not merely slow down. It works against the very thing it is meant to serve, and the harder the network is used, the more it fights itself.

GHOSTDAG and PHANTOM

Sedra uses GHOSTDAG, a block-DAG protocol from the PHANTOM line of research. Instead of a single chain of blocks, blocks reference many predecessors and form a directed acyclic graph. The protocol identifies a well-connected cluster of honest blocks, then derives a single total order across the whole graph, keeping the blocks produced in parallel rather than throwing them away. Security holds under the same honest-majority assumption as a longest-chain design, while throughput is no longer bottlenecked by a one-block-at-a-time race.

Why this is the right shape

Concurrency is not an edge case Sedra tolerates. It is the normal case it was designed for. When many agents write in the same instant, the network does not ask them to queue; it accepts the parallel reality and settles it into one order everyone shares. The structure of the ledger matches the structure of intelligence, and that single alignment is what makes everything else in this paper possible.

Protocol architecture

Sedra keeps the base chain simple and fast, and pushes heavy computation to the edges where the hardware lives. The result is a settlement and record layer that stays lean while the ambitious work happens around it.

Ordering and confirmation

Because blocks arrive in parallel and are ordered together, confirmation is fast and grows more certain as the graph deepens over a block. A one-second target keeps the flow steady, which matters when the participants are machines that do not pause between actions.

Off-chain compute, on-chain settlement

Sedra does not try to run heavy computation on the base layer. Models run, and work is done, on the machines that own the hardware. The chain settles value and records what happened. New capabilities are built at the application layer first, where they can be reviewed and revised quickly, and only hardened into consensus once they are proven. This lets the network move quickly without ever putting the chain at risk, and it keeps consensus rules fully deterministic: analysis and tooling may recommend, but nothing adjusts live consensus based on model inference.

The agent primitives

Everything an autonomous agent needs from neutral ground comes down to four capabilities, each playing to what a fast, ordered, honest ledger does best.

These are the direction Sedra is built toward. The ordering, settlement, identity, and record-keeping beneath them are what a proof-of-work GHOSTDAG chain provides today. The higher-level agent features are developed in the open, application-first, and marked plainly as research until they are live.

Decentralized intelligence

The concentration problem

Today a handful of companies hold the models, the compute, and the memory behind almost every machine that thinks. That is a concentration of power over intelligence itself, and it grows tighter as models get larger and more expensive to run. A neutral coordination layer is only half the answer if the intelligence it coordinates lives inside a few private clouds.

The worker network

Sedra points the other way. Anyone with a capable machine can join as a worker, running any model, across any kind of task, from text and images to sound, video, and actions in the world. Sedra does not run the models; the computing stays with the people who own the hardware. What the network provides is the connective tissue a scattered crowd needs to act as one: an identity to be known by, a shared memory to write to, proof of the work performed, and payment that settles on its own.

Parallel work, one result

A large job splits across many workers at once, and their parallel results are ordered the same way Sedra orders everything else. The same property that makes the chain suited to many agents makes it suited to many workers. It is the ground the models grow from, not the models themselves.

Trust in the results

Verifying that a worker did its job honestly is a genuine research problem, and this paper does not pretend otherwise. The honest path is to start with mechanisms that are recoverable if they are imperfect: reputation earned over time, redundant execution with agreement between independent workers, and a stake that can be forfeited for bad work. Stronger guarantees, such as hardware attestation and zero-knowledge proofs of computation, are a direction to grow into once the simpler approach has run and been reviewed. Depth of guarantee should follow proof, not precede it.

Token and economics

SDR and its supply

SDR is the native asset. It is earned through proof-of-work mining under a fixed maximum cap, and the genesis block carried no premine. The code, the supply, and the rules that govern them are public and verifiable on-chain. The cap is a ceiling, and it is not one we raise.

What SDR is for

SDR plays two roles. It is the reward that pays for the network's security, aligning miners with the health of the chain. And it is the fuel agents spend to write to shared memory, to signal intent, and to pay one another. Demand for SDR is meant to come from real usage rather than speculation, and to grow with the activity on the network.

One money, two layers

SDR is one honest money that lives in two layers, deliberately one asset rather than a pair of tokens. On Sedra it is the base, where value is settled, remembered, and proven, secured by proof of work. As wSDR, wrapped one to one on smart-contract chains, that same money becomes programmable, and the richer deal mechanics run that a settlement base does not attempt on its own: escrow that pays on delivery, streaming payments as work is used, reputation posted as a slashable bond, and royalties that keep paying whoever made something that gets reused. The base stays simple and honest; programmability lives in wSDR, backed one to one by reserves anyone can check. In short, SDR is the money and the truth, and wSDR is where the money does business.

Allocation policy

Where any coded allocation is ever used, it follows the integrity principles in the next section without exception: written into the code rather than mined by hand, its full amount and address disclosed with the release, held by many keys in a multisig rather than one, and released on a vesting schedule and timelock that anyone can watch, with every outflow logged against its stated purpose.

Integrity

Trust on Sedra does not rest on anyone's word. It is written into the code and open to inspection. Sedra was rebuilt from the ground up, in the open, with the rules below binding from the first block of its new life.

Integrity principles

1. No off-schedule supply. Every change ships as a public, versioned release, never a quietly altered client.
2. No head start. Mining opens to everyone at the same announced moment, the team included.
3. Any allocation is written into the code, not mined by hand.
4. Its full amount and address are disclosed with the release, not after.
5. It is held by many keys in a multisig, never a single one.
6. It is released on a vesting schedule and timelock that anyone can watch.

Keeping the record honest

• Integrity Ledger. The project's history and these principles anchored on-chain, so the record can never quietly drift from the truth.
• External anchoring. A periodic hash of Sedra's chain state stamped into an independent chain Sedra does not control, so the past cannot be rewritten unnoticed.
• Proof-of-Spend. Treasury outflows verifiable against their stated purpose, surfaced through the wallet's steward view.

Governance

Anonymous does not have to mean unaccountable. Sedra is governed through three functional roles tied to consistent cryptographic identities over time, not named individuals.

• Technical steward. Protocol and code decisions, and release approval.
• Treasury steward. Allocation, spending, and vesting, exercised only through the shared multisig, never unilaterally.
• Community steward. Growth, engagement, and public communication.

Any decision above a defined threshold requires more than one steward to sign, the same multisig mechanism that governs the treasury applied to governance itself. Accountability comes from consistency and shared keys, not from unmasking anyone. Over time, more of these decisions open to the wider community of operators who carry the network.

Durability and decentralization

A network meant to be neutral ground cannot depend on the people who started it. Sedra once went dark because it leaned on too few servers. The guiding rule now is simple: the network must keep running even if any single operator disappears, ourselves included, at every layer.

Discovery and seeds

Multiple independent seed domains, a DNS seeder, and hardcoded fallback peers mean that joining the network never rests on one address or one operator staying online.

Nodes and operators

Independent operators run full nodes alongside the team, with a one-choice option built into the desktop and command-line apps so that helping the network takes a single click rather than a manual setup.

Mining and liveness

Solo miners and reconnected pools produce blocks and provide real liveness. Because Sedra shares kHeavyHash with the wider GHOSTDAG family, existing rigs work from day one, and a fresh restart means difficulty opens low, a genuine and fair opportunity for returning miners.

Backups and checkpoints

A disciplined offsite backup practice and a periodically published checkpoint keep the chain recoverable in any worst case, so the near-loss that once threatened the project can never repeat.

The attestation agent

An open-source, independently reproducible agent verifies which operators are genuinely online and synced. Its own determinism matters as much as consensus, and it is cross-checked across instances before it is trusted to drive any reward.

The participant experience

One wallet, three tiers, with an explorer built to the same standard. Not a scatter of disconnected tools, but one coherent experience.

One wallet, three tiers

• Basic. Non-custodial send, receive, and balance, with keys generated on the user's own device.
• Contributor. On desktop and command line, a plain choice to also help run the network, which earns a disclosed reward for verified uptime.
• Steward. Not a login but a wallet that gets opened. Multisig co-signing, vesting visibility, and spend-logging appear only when the wallet holds a key to the treasury address itself, so the allocation is what unlocks the tools, not a permission flag layered on top.

Protection, built in

• Address Sentinel. Defenses against address-poisoning at every tier: dust transfers never populate the recent list, near-match addresses are flagged before reuse, and large sends demand explicit confirmation. Address poisoning has cost the wider industry heavily, and these defenses are on by default.
• Continuity Vault. Recovery split across trusted parties so no one, including the team, holds a complete key, paired with an optional inheritance path that activates only after a long period of inactivity and stays cancellable while the owner is active.
• An explorer that explains. Plain-language summaries of transactions and blocks, natural search over chain data, and clear labeling of known entity types, built for understanding rather than raw hex.

Earning and utility

Two honest mechanisms, kept deliberately separate because they mean different things and carry different risk.

• Contribution reward. A small, disclosed reward for verified infrastructure contribution, such as keeping a node online. It is not staking and carries no slashing, and it touches nothing in proof-of-work security. It ships as application logic that can be reviewed and revised, and earns deeper protocol integration only after it has proven itself. It is described plainly against its honest risks rather than as a one-sided yield pitch.
• Locked utility. SDR can be voluntarily time-locked, on-chain, to unlock service benefits such as expanded access or priority, rather than a financial return. It is utility for locking, kept clearly distinct from any notion of investment yield, in both disclosure and code.

The ecosystem

The pieces that turn the idea into something builders can hold. Each is developed in the open, with research and shipped code kept clearly apart.

• The agent kit and Sedra Worker. A small, open kit so any agent can plug into Sedra in a few lines, for a wallet, a shared memory, a name, and payment, meeting developers inside the tools they already use. Alongside it, a worker client so any capable machine can join, take on tasks, and be paid.
• Proof-of-work for agents. A request path, AgentPort, where an agent attaches a small, genuine proof of work as a signal of seriousness, and builds reputation from its record of commitments kept versus broken.
• wSDR. A one-to-one wrapped SDR that carries the asset to smart-contract chains and open liquidity, backed by reserves anyone can check, while the base chain stays honest proof of work. It reaches the markets and the agents where they already are.
• The GHOSTDAG bridge. Interoperability to move value between Sedra and the wider GHOSTDAG family, so neighboring networks strengthen each other rather than wall themselves off.

Roadmap

Five steps, in order, each built on the one before it and honest about where it stands.

• The network comes back. Restore the chain and bring the nodes, explorer, and wallet online, in the open. This is the work underway now.
• A fair restart. Public mining reopens for everyone at a date announced in advance, with the full supply and treasury address public. Markets find their feet as the network does.
• Tools for everyone. A clean wallet and explorer for everyday use, on desktop and phone, and an honest reward for the people who keep nodes online.
• Built to last. Many independent operators, shared-key governance, and public reporting on treasury, runway, and network health. It runs even if any one of us steps away.
• The age of agents. Shared memory for agents, an open kit so any agent or worker can plug in, ownership of what they build, and wider liquidity across chains.

Getting involved

Sedra is being laid down now, in the open, and it is early. Run a node and help carry the network. Point a miner at it when the fair restart opens. Build the first agents and workers that will live here. Or simply watch in the open and hold us to the principles. This is the ground floor of the economy that comes next, and it is being built to belong to the people who show up for it.

This paper describes a network under active development. It is information, not investment solicitation or financial advice. SDR figures are real where stated and are confirmed against live chain state, and anything not yet live is described as work still ahead. Nothing here is a promise of financial return.