DCLXVI LC

DCLXVI LC / Negative Bitcoin

nBTC

nBTC - USE

Rooted in LSM. Built for circulation. Open to scrutiny.

Treasury wallet · 26 September 2026

The LSM thesis. A currency in circulation.

KEEP VALUE
IN MOTION.

A unified world currency for global exchange. nBTC is designed to move value across borders and encourage cash-out into local national currency.

Use it within 30 days. Unspent nBTC returns to Treasury ownership, ending the holder’s claim and making the same units available for circulation again. This recovery path is intended to keep lost access from permanently stranding the currency’s supply. nBTC’s economic thesis rests on LSM and its proposed fusion-energy applications.

Reported economic scenario · Speculative

Ben reports AI-generated scenarios suggesting $50 trillion or more in potential LSM IP value if fusion and its applications succeed. This is an upside hypothesis, not an established current valuation or verified nBTC collateral. Read the reproducible public fusion result and the valuation assumptions and evidence gaps.

Ben Đ Om owns and controls this centralized Treasury, including issuance and operations. Signed receipts and supply checks make Treasury activity inspectable. The table below distinguishes operating safeguards from planned controls.

Today: a persistent Treasury wallet with zero-fee internal transfers. Each purchase receives an individual Treasury quote, and confirmed transfers produce signed receipts. External payments are verified manually. Bitcoin history synchronization remains proposed. A capped BTC merchant-payment workflow is available after owner funding and activation; it does not create a general redemption right. BTC settlement terms. Current wallet terms.

Global exchange. Local currency.

One global exchange. Each nation’s own currency.

nBTC’s goal is a true global exchange: a unified world currency for moving value internationally, with recipients able to cash out into their local national currency. It is designed not to act as a foreign currency operating inside a country and replacing that country’s own money. National currencies remain the foundation of domestic prices, wages, savings, taxes and everyday payments.

The 30-day purpose: discourage sitting on coins and encourage using the value or cashing out locally. The intended flow is international exchange through nBTC, followed by local-currency payout and participation in the recipient’s own economy. Moving coins between accounts merely to reset a timer does not serve that purpose.

The case to governments: connect to a shared global exchange while preserving national monetary sovereignty. This is the proposal nBTC seeks to bring to governments concerned about competing foreign cryptocurrencies, including those that currently restrict crypto: international exchange through a common medium, with domestic value delivered in their own national currency.

Development goal · clarified October 4, 2026. Local branch applications and a quoted cash-out workflow are now available. Payouts require an approved, funded operator and any necessary local authority; there is no universal or guaranteed local-currency redemption. The existing wallet and expiry terms remain in force.

Local capital. Global exchange.

Build the exchange, one local Treasury at a time.

Entrepreneurs can apply to become independent nBTC payout operators. Bring documented local capital, propose a service area and payment methods, then quote your own exchange rate and disclosed service fee after approval. Start at the scale your capital can support; there is no platform-wide minimum.

Back your accepted payouts, not the entire world’s supply. The operator’s local funds support specific quoted exchanges. The company-valuation estimate does not set a mandatory cash-out rate or create a reserve obligation of $50 trillion. Completed payouts deliver nBTC to the operator’s wallet under the ordinary 30-day holding rule, to be used or resold promptly. Earnings depend on completed exchanges and demand.

Owner-reviewed capacity limits accepted payouts to 80% of remaining reviewed local capital, with a 20% cash buffer and a fresh review every seven days. Accepting a quote reserves both nBTC and payout capacity. The branch pays externally; the holder confirms receipt before coins are released. Disputes require evidence review. Self-cash-out to the same branch wallet is blocked; false trades and related-account timer resets are prohibited, although separate account ownership is not automatically established.

Program launched October 5, 2026. An application is free and does not allocate coins, grant a banking licence or guarantee business. Branch funding is reviewed from external evidence; this website does not control a branch’s bank account or send fiat payments. Read operator and cash-out terms.

Design purpose · October 16, 2026

A currency that can outlast lost access.

The purpose of recall is to keep the currency’s units recoverable when a holder loses access, disappears, or can no longer participate, so those units can support exchange again. It aims to preserve the currency’s capacity to circulate across generations. The intention is to retain usable monetary capacity in the system, rather than let abandoned units become permanently inaccessible.

Under the current implementation, the trigger is the published 30-day deadline for every unspent lot; the service does not determine whether its holder is actually lost. Expiry transfers ownership to the Treasury and ends the former holder’s claim. The same units can then be reissued within the existing 21 million nBTC ceiling. This preserves the unit inventory, not the expired holder’s balance or the price they originally paid.

Bitcoin illustrates the lost-access problem: coins whose private keys are permanently lost remain recorded but cannot be spent. Bitcoin’s own FAQ describes this distinction. nBTC’s Treasury model addresses that failure mode for nBTC; it does not recover Bitcoin private keys or lost BTC.

The long-term ambition is an “immortal” currency: a fixed, recoverable unit supply that can serve as a common reference for exchange between national currencies and support their stability. The ceiling limits new units and recall counters permanent stranding through lost access. Stable purchasing power and stable national exchange rates are further economic goals; neither is guaranteed by conserving the number of units. They depend on adoption, demand, available reserves, governance, and functioning exchange markets.

01 / The circulation rule

Thirty days to use each amount.

Every circulating lot has a visible deadline: receipt time + 30 × 24 hours, measured in UTC. At that deadline, any unspent portion returns to Treasury ownership. The previous holder’s entitlement to that portion ends under the accepted wallet terms. The live service covers registered online wallets. Integration with physical coins remains proposed.

The recovery purpose is to keep units from becoming permanently stranded when access is lost. The deadline applies to all unspent lots, including those whose holders remain reachable. Read the recovery rationale and long-term currency goal.

ActionEffect on the clock
Spend to another holderThe transferred amount receives a new 30-day deadline on confirmed receipt. The recipient accepts the same terms.
Spend part of a balanceOnly that amount renews. Unspent change retains its existing deadline; spend the earliest-expiring lots first.
Log in, scan, or move between your walletsLogging in and transfers to the same wallet do not renew expiry. This release cannot reliably detect one person controlling different sign-ins or collusive transfers.
Reach day 30The expired amount stops being spendable and returns to Treasury ownership. Reissue uses the same inventory; recall does not create coins.
Lose a key or physical coinLost access does not stop the expiry clock. Sign-in recovery depends on the authentication provider. Separate Treasury identity recovery and physical-coin integration are not implemented.

The wallet shows a live countdown for every unspent amount, its UTC deadline and Unix timestamp, synchronized to Treasury server time. Maintenance pauses freeze the countdown; deadlines extend when service resumes. Amounts with seven days or less remaining are highlighted. Email and push reminders are not connected. Recipients accept the common wallet terms when enrolling; a separate acceptance prompt for each transfer is not implemented. The definitive receipt records the amount, UTC deadline, and accepted policy version. Treasury inventory has no holder-expiry clock until released.

Purpose: prevent permanently stranded nBTC and encourage circulation. The 30-day limit discourages hoarding and is intended to encourage spending or cashing out into local national currency. Read the global-exchange goal and local cash-out development status. This is a spending asset with expiry, not an indefinite savings balance. The rule cannot recover lost BTC on Bitcoin’s own chain.

Try the rule · simulated balances only

One coin, two deadlines.

Alice receives 1.00 demo nBTC on day 0 and spends 0.25 to Bob on day 20.

0.00000000Alice · demo nBTC
0.25000000Bob · demo nBTC
0.75000000Returned to Treasury · demo nBTC

At day 30, Alice’s unspent 0.75 returns to Treasury ownership. Bob’s 0.25 remains spendable until day 50.

Inspect the demonstration events

Download the executable policy model. This model uses in-memory state and a simulated clock; it does not move money.

02 / Checks on the owner

Control is personal. Accountability is public.

Ben retains ownership and executive control. The operating commitments below identify the safeguards already in place and the next controls to implement. Public evidence can expose misuse; with all ultimate authority retained by one owner, it cannot make misuse impossible.

Published checkRequired evidence or limitCurrent status
No hidden minting21,000,000 nBTC ceiling; eleven decimal places. The minimum unit is a talent: 1 talent = 0.00000000001 nBTC; 1 nBTC = 100,000,000,000 talents. Publish circulating units, Treasury inventory, and retired units separately. No public mining rewards or extra 10% allocation.Supply conservation is checked in database transactions. Read the live supply status.
No early discretionary takingAutomatic recall only at the disclosed deadline. Recovery needs holder evidence; exceptional freezes need a case reference, reason, and review deadline. Corrections preserve innocent recipients.Server-enforced expiry; no owner action for early seizure. Disputes still require direct owner handling.
No quiet rule changesPublish changes 30 days in advance. Existing lots keep their accepted terms; never shorten an existing deadline retroactively.Accepted policy recorded. Future changes need a versioned migration preserving existing terms.
An inspectable recordSigned, append-only issue, spend, recall, freeze, correction, and reserve records; daily supply reconciliation and independently retained checkpoints. Publish pseudonymous proofs, not customer identities.Signed journal and downloadable checkpoints implemented. Independent witnesses and audits have not been appointed.
Separate ownership from safeguardsOwner-controlled 2-of-3 operational keys, kept separately. External reviewers can check the ledger and reserves without owning the Treasury.Not implemented: this release uses one hosted signing key. A separate recovery arrangement and 2-of-3 controls remain proposed.
Fair outage and dispute handlingPause expiry during verified service outages and operator-imposed freezes; extend affected deadlines by the unavailable duration. Publish all exceptions and a correction trail.Owner-declared global maintenance pauses expiry and transfers. Automatic outage detection and individual dispute correction remain operational work.
Backing that can be inspectedPublish assigned assets, valuation basis, liens, holder rights, liquid reserves, fees, and redemption performance. An IP valuation is listed separately from spendable reserves.Gemini/GPT estimates reported by Ben; original valuation reports, asset assignment and independent appraisal not published. Liquid BTC availability is disclosed separately.

Full Treasury charter & implementation plan · Machine-readable policy & launch status

03 / Evidence and proposed backing

Read the result before the valuation.

Computed result: the public docking audit and reaction ledger provide the inputs, checker and a reproducible partial result: 30 cells, two contact faces, 225 checked pairs, and a six-input shortfall. They establish no physical fusion event, reaction rate, bound state or net energy.

Speculative economic scenario: the $50 trillion figure remains a reported AI estimate conditional on scientific and commercial success. No validated threshold to that valuation has been established. No independent appraisal or fitted economic model is supplied here. Read the evidence categories.

Historical valuation attribution · superseded as a statement of present backing

Ben Đ Om attributes the US$50,000,000,000,000 minimum valuation to separate analyses by Google’s Gemini and OpenAI’s GPT, which he reports were conducted independently. He describes their basis as the minimum vested value of LSM’s unpublished trade secret or intellectual property for unlocking fusion energy. This corrects the earlier attribution of the figure to Ben’s own valuation.

The fusion work is unfinished. The original AI valuation outputs and their full assumptions are not published here, so their amounts, independence and conclusions are not independently verified on this site. These are reported AI estimates, not a professional appraisal, experimental proof of fusion, or cash or Bitcoin reserves. The economic thesis depends on LSM’s validation and on making its proposed applications work in practice.

Earlier wording: “Independent quantitative modeling frameworks converge on a baseline IP valuation exceeding $50 trillion, derived from the complete elimination of primary energy constraints via LSM-enabled fusion architecture.”

Presentation corrected October 16, 2026: the underlying outputs and assumptions have not been released for verification, so convergence and a realizable valuation floor are not established by this site.

Explore the published LSM and evaluate its arguments and evidence. Scientific validity alone would not establish nBTC’s price: usable backing rights, liquid funding and willing buyers and vendors also matter. Accepting or receiving nBTC creates no obligation to endorse or promote LSM.

To make that backing an enforceable asset commitment, the Treasury must identify the LSM rights contributed, document ownership and any encumbrances, execute the assignment or security agreement, and specify what holders can claim. This publication does not itself assign intellectual property or grant royalties.

Arithmetic illustration · not a token price

$50 trillion ÷ 21 million = $2,380,952.38 per nBTC

This assumes the entire stated value is committed and spread across the full ceiling. It is an allocation illustration only: no sale price, realizable collateral value, redemption floor, or purchasing power follows from this division.

The BTC-parity goal: target a Treasury quote of 1 nBTC = 1 BTC. Sustaining that quote requires usable liquidity, defined redemption rights, and execution. LSM valuation alone cannot deliver BTC on demand. Recall expiry also makes nBTC economically different from holding BTC, even at a matching quote.

04 / Bitcoin history, in the negative direction

Reuse the verified history. Keep ownership explicit.

The proposed mirror imports Bitcoin’s existing blocks and follows its accepted chain. Preserve each original Bitcoin header, hash, transaction commitment, and parent reference; give the mirror record the index n = −(h + 1). Bitcoin genesis at height 0 maps to −1. This is negative numbering, not an inverse-price bet or a change to Bitcoin’s blocks.

Bitcoin heightnBTC mirror indexWhat carries over
0 · genesis−1Bitcoin’s exact source record and provenance.
1−2Original hash and parent linkage.
h−(h + 1)Subsequent accepted blocks; orphaned records retained with their status.

Bitcoin 1,000,000 → nBTC mirror −1,000,001. This is an index example, not the current chain tip.

  1. Backfill from a fully validating Bitcoin node.
    Import history and check network identity, hashes, links, and cumulative work against the node’s accepted chain. Publish source-node version, tip, lag, and confirmation depth.
  2. Follow updates and reorganizations.
    Track each new accepted block. On a reorganization, return to the common ancestor, mark displaced mirror records, and replay the replacement branch. Software upgrades require reviewed compatibility; a web feed cannot establish consensus.
  3. Maintain a separate Treasury journal.
    nBTC issuance, spending, and 30-day recall obey the Treasury charter. Commit the journal checkpoint alongside the Bitcoin reference. The mirror follows Bitcoin’s history; nBTC ownership cannot simultaneously copy every BTC transaction and apply its own recall rules.
  4. Move BTC only through an actual deposit.
    A future conversion service can credit nBTC after BTC reaches a disclosed custody address and the confirmation policy is met. Track each deposit once. Redemption locks or retires the corresponding nBTC before BTC is paid out.

Copying a block does not transfer the BTC it records. It grants neither private keys nor rights to anyone else’s coins. Existing BTC mining work can authenticate the unchanged Bitcoin history, but it does not secure the Treasury journal or fund nBTC. A live full-history mirror and automatic BTC deposit conversion remain to be built. The separate merchant-payment workflow uses limited, independently funded BTC.

Sources: Bitcoin header format, transaction authorization, validated-chain status, Bitcoin price formation.

05 / Buy from the Treasury

Request a quote directly from the Treasury.

All initial distribution comes from Ben’s Treasury inventory, with no public mining phase. Open a wallet, request an exact quantity, and review the owner’s USD quote and terms. The owner provides private payment instructions and releases units after independently confirming receipt.

The wallet is a separate nBTC ledger. It does not process bank or card payments, guarantee a market price, or provide automatic BTC redemption. The owner must establish the actual payment route and operating requirements. LSM asset backing remains proposed; the wallet terms grant no collateral rights that have not been separately executed.

A quote request is free and reserves no coins. Accept the exact quote before paying through the owner’s instructions. The 30-day clock begins when coins are delivered, not while you wait for payment verification.

Help move from a model to a measured result

The opportunity is to fund the decisive test.

Ben reports that apparatus parts for the first proposed fusion-event experiment exceed his current liquid capital, and that no direct contributions to this effort have been received as of October 16, 2026. Support can help turn a defined hypothesis into an instrumented test.

A $1 million or $1 billion commitment could change the scale of the effort; any program needs a costed plan, technical gates and independent replication. The $50 trillion scenario and the broader energy, longevity and creativity ambitions remain conditional.

Explore research support and contact Ben

Spend & accept nBTC

Accept nBTC directly. Reach BTC merchants through the Treasury.

nBTC can pay for an online order when its seller agrees to receive nBTC. The wallet now creates single-use merchant invoices: an exact amount, a payment link, a confirmed balance transfer and a signed receipt. No customer card details are entered into the nBTC wallet.

Where you want to spendWhat the seller receivesAvailable here
A participating nBTC merchantnBTC in a registered wallet; zero internal transfer fee; a new 30-day deadline.Merchant payment links are implemented. Each seller must agree to accept nBTC. No outside merchant partnership is claimed.
A direct Bitcoin mainnet checkoutActual BTC sent from the owner’s funded wallet.A capped quote, hold and verification workflow is implemented. Owner funding and activation are required. Lightning is not supported. An nBTC receipt alone cannot pay a BTC invoice.
A card-only shopThe shop’s supported card payment or ordinary currency.A separately approved payment/card partner would be required. No nBTC card, card-network connection or gift-card integration is operating.
  1. Seller: open a wallet and choose Accept payments.
    Enter the agreed nBTC amount and your private order reference. Create a link valid for 24 hours and add it to an email, message or existing order page. The seller’s goods, delivery and refund agreement remain between seller and buyer.
  2. Buyer: review and confirm the invoice.
    Check the full receiving wallet and amount against the order arranged with the seller. A display name is chosen by the wallet holder; it is not verified business identity. Sign in, use an unexpired balance, and confirm the payment.
  3. Seller: verify payment in your own wallet.
    Fulfil only after the invoice is marked paid. Payment and invoice settlement occur in one transaction; a paid invoice cannot debit another buyer. A customer screenshot alone is not payment confirmation.

Merchant balances follow the same 30-day rule. Receiving an order payment starts a fresh deadline. Holding nBTC does not provide a general BTC or dollar cash-out right. Optional BTC merchant settlement requires a separately accepted quote and available funding. Agree to accept it only for a price and use you have actually arranged. Refunds are separate agreed transfers; this release has no automatic merchant refund or chargeback system.

Clear benefits. Checkable limits.

Your balance is held in the Treasury ledger, not on your phone.

Closing the browser, replacing a device or losing a printed address does not erase an unexpired balance. Sign in to the same account to use it. You do not have to preserve a separate nBTC seed phrase. Zero-fee internal transfers, one published ledger and owner-operated service are the practical benefits of this centralized design.

Access recovery is different from expiry. Recovery of the sign-in account depends on the authentication provider; a separate Treasury identity-recovery procedure is not implemented. Theft, a payment to the wrong recipient, service failure and the disclosed 30-day recall are not covered by a guarantee. The claim that coins “can never be lost” is not made. Owner-declared maintenance pauses the expiry clock; losing account access by itself does not.

Cryptography verifies records; it does not hide every purchase. This service publishes wallet addresses, amounts and timestamps in a signed journal. Those records can be linked to people when identifying information is disclosed. Sign-in identities, Treasury payment instructions and merchant order references are excluded from the public journal. The owner can inspect private records; hosting, authentication and external payment providers may also hold relevant records. The wallet is not anonymous or untraceable.

Centralization means trusting the owner and service operation. Holders can download signed receipts and supply checkpoints to retain independent evidence. There is no owner action in the wallet to seize an unexpired balance, but the owner controls future software releases. No independent security audit, deposit insurance or universal loss guarantee is claimed.

Bitcoin’s own documentation describes its transactions as public and traceable: Bitcoin privacy guidance. The reason to trust a payment record is that it can be checked, not that its technical details are difficult to read.

From a reference price to purchasing power

A BTC-priced unit needs an actual route to BTC.

A seller may agree to quote an order using Bitcoin as a reference: nBTC quantity = USD order price ÷ agreed USD price per BTC, if the parties choose a 1 nBTC : 1 BTC pricing convention. The quote needs a source, timestamp, acceptance deadline and disclosed fees. Today’s invoices use a fixed amount entered by the seller; the wallet separately displays a USD reference calculated from the owner-controlled company valuation divided by 21 million nBTC. That estimate does not change invoice amounts or create a guaranteed BTC peg.

A reference price alone does not provide Bitcoin purchasing power. A broadly useful conversion service must fund the merchant’s BTC payment from real liquid reserves or an executable conversion. The proposed LSM valuation does not itself supply that BTC. At a promised 1:1 redemption rate, every outstanding redeemable nBTC needs an equivalent BTC payment capability, with additional room for fees and pending payouts. Unreleased Treasury inventory does not need to be sold to start a small, capped service.

  1. Fund a limited settlement reserve.
    Choose a permitted custody/payment arrangement and publish the payout limit, fees and redemption terms. Establish the applicable administrator and money-transmission requirements before operating this service.
  2. Quote one real merchant invoice.
    Validate its BTC network, exact amount, destination and expiry. Lock the customer’s confirmed nBTC amount and reserve the matching BTC and fee budget.
  3. Pay and reconcile once.
    The owner or an approved payout provider sends actual BTC. The application checks the final transaction after three confirmations, including its funding input, exact merchant amount and current-chain block. The owner confirms the merchant accepted the payment. Do not resend a payout merely because an API response was lost.
  4. Complete or release the held amount.
    Consume held nBTC only for a completed payout. If a payment is definitely unexecuted, release the hold with the specified expiry protection. Resolve ambiguous outcomes before releasing or retrying. The wallet’s Pay a BTC merchant tab implements this workflow. It starts closed until the owner configures a funded address and opens requests.

Existing processors do not automatically accept a newly named currency. BitPay lists supported assets and networks; BTCPay describes explicit altcoin integrations and exchanges. Neither is represented here as an nBTC partner. Internal nBTC transfers have zero fees. Under the initial BTC settlement terms, the customer pays no settlement fee and the Treasury pays Bitcoin network fees. Other external payment routes may have their own costs.

The initial adoption target is concrete: one willing seller, one agreed order, one paid invoice and a documented way for that seller to use the proceeds. BTC settlement initially caps each payment at 0.001 BTC and outstanding commitments at 0.01 BTC, including fee budgets. Every accepted quote uses 1,000 talents per BTC satoshi; this is not a guaranteed peg for all balances. Read settlement terms and current availability. FinCEN’s administrator and exchanger guidance explains why providing currency transfers is a separate operating question from writing the software.

Original experiment & v0.2 developer archive
Origin experiment−1
Ben Đ Om
The Pre-Genesis

Your starting point is verifiable.

5f0ee3e5d7898f19d9044b0963a37089aba00ce4f95901a77296452700000000
Download v0.2Read the protocol

Recompute the recorded 80-byte header in your browser.

This historical release contains working local software and a recorded demonstration. A live currency network and token sale have not launched. Demo units have no redemption value.

01 / Put it in your hand

One marked face. One recorded balance.

The starter design is a 45 mm printed disk with an nBTC face, a blank underside, and a pocket for a tag. The download includes the editable OpenSCAD source and two STL parts. The registry design can also support a future Möbius shell.

A printed object carries a public identifier. Its value stays in a ledger account. A copied QR or ordinary NFC tag cannot authorize a payment; the current holder and registry must approve it.

Get the editable coin model · Physical registry guide

  1. Load
    Move existing demo units from a wallet into the coin’s escrow account.
  2. Hand over
    Sender, recipient, and registry sign. The recorded holder changes and the previous credential is revoked.
  3. Redeem or reissue
    Return the balance to its holder’s wallet, or replace a lost physical credential after review.

Every handoff needs a confirmed registry update. Simply passing the shell does not transfer recorded ownership. The hardware and NFC connection are still to be built and tested.

02 / Keep a route home

Lost shell. Recoverable claim.

DCLXVI LC retains disclosed registry recall authority. Ben’s issuer account can return lost or long-inactive physical coins to registry custody. Recall revokes the old credential while preserving the balance and the recorded holder’s claim. It does not move that value into the issuer’s treasury.

SituationDefault policyWhat happens
Credential ages90 daysRenew with holder authentication. The balance does not expire.
Verified loss7-day challengeFreeze transfers; review reports and disputes; issuer can recall to custody.
No holder activity365 days + 30-day noticeA successful holder challenge cancels dormancy recall. Otherwise the issuer can recall.
ReplacementIssuer + current holder approvalReissue a new credential for the same units.

A loss report must be co-signed by the current holder or verified by the issuer with a recorded evidence reference. Disputed loss claims can be quarantined after the delay; the recorded ownership claim remains intact. Activity means holder-authorized use or renewal, not an unsolicited scan.

The issuer account itself has guardian recovery, so a lost operator key can be replaced. Recovery still depends on surviving authorized keys and records.

Recorded local walkthrough · simulated time

Load: five existing demo units enter coin escrow

5.00000000

Demo nBTC held in the coin account. Step through the recorded handoff, loss, reissue, and dormancy example.

Loading record…

Download lifecycle results · Download its signed ledger

These rules run in the downloadable local prototype. The website does not hold balances, accept loss reports, send notices, or run an automatic recall service. The demo advances an issuer-attested clock; live operation still needs durable custody, clock controls, case handling, and hardware integration.

03 / Reproduce

The original header

Version
1
Recorded timestamp
1231005905 · 600 seconds before Bitcoin’s genesis timestamp
Bits
0x1d00ffff
Recorded nonce
1,598,612,817
Previous hash bytes
445be54d48a2e6294369c84c61cd0929209d4e1084536159bdf7002bddfe094b
Inscription hash bytes · experimental Merkle field
d71b99d46cb3ddaae3563704273f32b9122e6b37cccbce418bf2a49acfa32a34

Changing a field changes the hash. Use the verifier above to calculate the result.

The recorded timestamp is a chosen header field, not evidence that this experiment occurred in 2009.

04 / Recover

Keep the account. Replace the key.

Every ordinary wallet account enrolls five guardians. Three guardians and a replacement key can authorize recovery, followed by a challenge period.

  1. Height −2 · Transfer
    Alice sends five demo nBTC to Bob.
  2. Height −3 · Request recovery
    Three guardians authorize a new owner key. Outgoing transfers freeze.
  3. Heights −4 to −8 · Challenge window
    The existing owner can cancel before the deadline.
  4. Height −9 · Replace the owner key
    The account identifier and its balance stay intact.
39.99999000

Demo nBTC in Alice’s account before and after recovery.

Nine recorded blocks. No wallet connection required.

Recovery depends on surviving, honest guardians. The six-block delay is a local demonstration setting.

05 / Inspect

A ledger that counts downward.

The sample chain references Bitcoin’s genesis at its first block and commits to the original experiment in its network identity. Select a recorded block to inspect its header.

The downloadable package contains the complete nine-block record.

Download the demonstration ledger · Download the origin record

06 / Get started

Your first block. Your first physical prototype.

36 testsReported for the published v0.2 ledger and registry release
21 millionProposed nBTC supply ceiling
3 of 5Guardians can recover holder and issuer accounts
  1. Get the kit

    Download nBTC v0.2, unzip it, and open a terminal in the nbtc-v0.2 folder. Python 3.12 is the tested runtime.

  2. Mine and rehearse

    Install the pinned dependency, run the tests, then run both demos. The first mines local blocks; the second exercises loading, handoff, loss, reissue, and dormant recall.

  3. Print a shell

    Open coin.scad in OpenSCAD or use the included base and lid STLs. Measure your insert, check the fit, then print the two parts. The model has been exported but has not been physically fit-tested.

  4. Build the handoff

    Use the registry commands as the reference for a wallet and authenticated tag integration. Verify current ownership before accepting a coin. Bring a working prototype and its test results to DCLXVI.

python3 -m venv .venv
source .venv/bin/activate
python3 -m pip install -r requirements.txt
python3 -m unittest -v test_nbtc test_registry
python3 demo.py
python3 registry_demo.py

On Windows, create the environment with py -3.12 -m venv .venv, activate .venv\Scripts\Activate.ps1, and use python for the remaining commands. Both demos generate disposable keys and save public result files; they are not persistent wallets or participation in a shared mining network.

Release manifest & checksums · Full registry rules · Original v0.1 package

How is nBTC connected to Bitcoin?

The prototype makes a verifiable reference to Bitcoin’s genesis hash and counts subsequent heights downward. It is an independent ledger design, written from scratch. Bitcoin does not recognize it as an earlier part of its own chain, and the reference does not transfer Bitcoin’s network security or create BTC.

The original experiment’s hash is reproducible under its big-endian work comparison. It does not meet Bitcoin’s target when interpreted using Bitcoin’s byte order. The protocol records both results. SHA256 inversion has not been demonstrated.

What would connect nBTC to LSM capital?

A future financial structure could assign defined rights to actual LSM licensing receipts. That requires an enforceable agreement and verified rights. This software release grants no claim to LSM intellectual property, royalties, cash, or Bitcoin, and an estimated IP valuation is not a funded reserve.

What did the v0.2 prototype leave unfinished?

The local physical registry now implements signed recall and reissue rules. Its then-proposed distributed consensus, persistent wallet custody, real-world recovery operations, guardian replacement, network security testing, and final issuance rules remain to be completed. The proposed prototype allocation is 2.1 million treasury units and a 45-unit initial mining reward, halving every 210,000 blocks. These historical settings have been superseded by the owner-controlled Treasury proposal above.