Research preview · No live network or real fundsProject status ↗
Protocol / 01

An independent ledger.
A lasting account.

The coin is the foundation. Account continuity and enforceable authority are the reason to build around it.

Independent by architecture.

1soft’s objective is a sovereign Layer 1 with its own genesis, native monetary rules, validator configuration and history. The coin is intended to be part of that ledger—not a token issued by a contract on someone else’s chain.

The development direction reuses established cryptographic and consensus components rather than inventing new primitives for the sake of originality. The application adapter targets CometBFT. Actual communicating-validator execution remains an outstanding acceptance gate.

Today: native application research and local verification. Not today: an operational public chain, public coin issuance or a claim of decentralized security.

Identity is not a device key.

Native account opening uses explicit incoming-key consent and a sponsoring signature. Key rotation preserves the account identifier and history while changing the controlling key and invalidating older agent permissions.

Rotation currently requires the existing key. It is not a lost-key recovery service. Broader portability and recovery ceremonies remain development work.

Permission is part of the monetary rule.

Agent grants specify who may spend, which recipients are permitted, an allowance and an expiry. In the opt-in shared-budget prototype, each agent grant belongs to one owner-authorized parent budget.

Each accepted delegated payment consumes both the individual allowance and the shared remainder, including its native fee. Adding grants does not increase the parent ceiling. Owner-signed activity is outside these agent caps.

A permission ceiling is not escrow: it does not reserve a balance, guarantee future funds or control a payment on a different network.

Verify selected records.

The compact-state experiment lets a client verify selected account, permission, budget or receipt records under an authenticated state commitment. The client checks the requested records, not whichever records a responding server prefers to show.

This avoids sending unrelated ledger records in that response. It does not make the chain anonymous, prove that a snapshot is latest, or establish independently operated validators. Current examples use synthetic committee certificates.

A monetary policy is a commitment.

The coin’s public name, ticker, supply, allocation, security incentives and governance are not finalized. The development denomination, DEV, has no promised value and is not redeemable for dollars.

A market-priced native coin and a dollar-redeemable instrument serve different purposes. Dollar integration would require a separate, substantiated backing and redemption design. Neither reserve backing nor banking access is implied by this website.

A continuing account.
A clearer kind of control.

Read the working paper