Atomic Ownership Blockchains
Overview
Atomic Ownership Blockchains (AOB) are a type of blockchain architecture in which each atomic digital object is recorded on its own independent blockchain. As a multi-blockchain system, every blockchain represents the complete state and ownership history of exactly one indivisible (“atomic”) object. When the ownership of each atomic object is well-defined, the global state of the entire system is also well-defined.
AOB is designed to achieve a level of decentralization and security higher than that of Bitcoin-style public blockchains, while offering scalability limited only by hardware constraints.[1]
Problems in Bitcoin-style Public Blockchains
AOB is proposed partly to address decentralization and security limitations inherent in Proof-of-Work cryptocurrencies such as Bitcoin.
In Bitcoin, the miner who appends the next block temporarily holds excessive authority, which constitutes a form of centralization. Users cannot independently finalize payments; each transaction must be approved by miners, often incentivized through additional fees or “bribes.” Although block producers frequently rotate, this results only in fluid centralization, not true decentralization.
Because decentralization is insufficient, Bitcoin-style systems remain vulnerable to 51% attacks and cannot fundamentally resist double-spending. Arguments that economic incentives deter attacks are considered weak:[1]
- Attackers can rent hash power at acceptable cost; block rewards partially offset expenses.
- A double-spend may not trigger market panic if unnoticed by the public.
- Attackers can profit by shorting Bitcoin before executing the attack.
- Attack motivation may be non-economic (e.g., demonstration attacks such as the Monero attack in August 2025), and states controlling large shares of hash power may also launch attacks.
Therefore, building monetary security purely on economic assumptions is insufficient, and Bitcoin’s economic foundation is not robust.[1]
Technical Architecture
Atomic Ownership Blockchains describe a system built from many micro-blockchains, each representing a single atomic object. This enables decentralized circulation, cryptographic-level security, and open-ended scalability.[1]
Public-Domain Private Blockchains
Each micro-blockchain in AOB is a public-domain private blockchain:
- publicly readable,
- privately writable—only the blockchain’s current owner may append blocks.
To transfer ownership, the owner appends a block specifying the recipient’s public key. The recipient becomes the new owner and may append subsequent blocks. No consensus algorithm or privileged role is required; blockchains circulate freely among users.
Since each blockchain corresponds to an indivisible asset (e.g., a digital banknote), the global asset distribution (ledger) is determined by the set of terminal blocks across all blockchains.[1]
Decentralization
AOB extends Bitcoin’s decentralization by removing privileged actors such as miners. All participants have equal rights; users can authorize payments independently without requiring approval from any external party. This realizes a fully decentralized, non-hierarchical system.[1]
Security
AOB inherits Bitcoin’s cryptographic safety while additionally achieving resistance to Sybil attacks and double-spending without relying on economic assumptions.
Sybil Resistance
Sybil attacks influence voting-based systems. AOB employs no voting, thus Sybil attacks are inapplicable.[1]
Double-Spend Resistance
AOB uses several mechanisms to prevent double-spending at the cryptographic level:
Punishment of Attackers
Because each blockchain is writable only by its owner, all forks originate from the same individual. Any fork is therefore direct evidence of malicious behavior. Nodes may blacklist the attacker and invalidate the attacker’s assets. If account creation requires fees, the attacker also loses the account cost, ensuring economically negative expected returns.[1]
Selecting the Valid Fork
Conflicting blocks are resolved by the first-broadcast-wins rule.
- If the attacker broadcasts conflicting blocks far apart in time, the entire network will agree on the order (implicit consensus).
- If the interval is short, recipients reject the payment due to insufficient confirmation time.
Given an estimated network broadcast time t₀:
- A third-party node, after receiving a payment and observing no conflicting block within 2·t₀, can accept it safely.
- A payment recipient may wait 4·t₀ to ensure all nodes have also observed the block and applied the same rule.[1]
Collusion
If an attacker A sends two conflicting blocks privately to colluding parties B and C without public broadcast:
- When B or C later attempts to pay honest nodes and must broadcast the blockchain, A is exposed and blacklisted.
- The first broadcast among the conflicting blocks is accepted.
- Recipients may adopt an additional safeguard: if the previous transfer occurred while they were online but they did not observe a broadcast, they may reject the blockchain.[1]
Network Partition
In a rare scenario where a network partition occurs immediately after the attacker broadcasts the first block and the attacker broadcasts a second conflicting block to a disjoint region:
- Probability is extremely low; generally not actionable.
- For high-value payments, recipients may extend the waiting period beyond the maximum plausible partition duration plus 3·t₀.
- Users may test connectivity to major websites to verify they are in the larger network region.
Even in theoretical edge cases, discrepancies affect only a single atomic object, not the global system. Since expected attacker profit is negative, such attacks rarely occur in practice.[1]
Scalability
AOB scales without upper bound by increasing the number of blockchains. When blockchain count becomes extremely large, network broadcast load increases; several strategies mitigate this:[1]
Grouping
Blockchains may be partitioned into groups. Nodes subscribe only to selected groups, and broadcast traffic occurs only within the relevant group. Increasing the number of groups improves performance linearly.
Speedy Channels
Inspired by the Lightning Network, users may create Speedy channels—themselves a form of AOB—where participants deposit several AOB banknotes and exchange payment statements off-chain without broadcasting, as long as each transfer stays within the deposited balance.
Stablecoins
Fiat-pegged stablecoins require a centralized entity because fiat is centralized. AOB instead enables a decentralized asset whose value is stable relative to computational effort.
AOB can implement non-competitive Proof-of-Work minting:
- any user who performs a hash collision of a specified difficulty may mint a banknote,
- the denomination is proportional to the difficulty,
- when market value rises, higher profit margin incentivizes minting,
- unlike Bitcoin, producing more notes merely requires more computation without competition.
Thus, the currency stabilizes relative to the total amount of hashing work. Short-term stability reflects electricity prices, while in the long term, hardware progress causes it to depreciate against them.[1]
Applications
AOB can be used for cryptocurrencies, stablecoins, fiat-denominated digital instruments, virtual currencies, metaverse assets, NFTs, real-world asset (RWA) tokens, commercial vouchers, financial notes, commodity traceability, and more.
For other Cryptos
AOB can also provide banknote functions for other cryptocurrencies to achieve higher decentralization, security, and performance.[2]
For example, to transfer Bitcoin to an AOB banknote, the steps are as follows:[2]
1. Create an AOB banknote with the face value set to the amount of Bitcoin to be transferred in, and generate the banknote’s ID.
2. From a Bitcoin wallet, transfer the same amount of Bitcoin to an address that can be uniquely mapped to the banknote ID created in Step 1. Because this address is not a valid Bitcoin wallet address, the transferred Bitcoin cannot be spent again on the Bitcoin network.
3. After the UTXO from Step 2 is validly recorded on the Bitcoin public blockchain, add a block to the banknote created in Step 1 and write this UTXO into the block. This proves that the banknote is fully backed by the corresponding amount of Bitcoin. Afterwards, the banknote can be paid to others by adding blocks according to AOB’s rules.
It should be noted that after the transfer is completed, forks may still occur at earlier positions on the Bitcoin public chain. Such forks can only be handled according to Bitcoin’s own principles. Therefore, if a 51% attack occurs at an earlier position and causes the UTXO transferred to AOB to no longer be on the main chain, the AOB banknote will lose its full Bitcoin backing.[2]
If Bitcoin adds the appropriate adaptation functionality, it will also be possible to transfer Bitcoin from an AOB banknote back to the Bitcoin public chain. The steps are as follows:[2]
1. The current owner of the banknote adds a block to the AOB banknote to destroy it. In the destruction block, a valid Bitcoin wallet address is written. Once destroyed, the banknote can no longer be used. At the same time, a temporary UTXO is generated and broadcast to the Bitcoin network.
2. Bitcoin miners should monitor the AOB network. After confirming all blocks of this banknote from its creation to its destruction according to AOB’s rules, they make a judgment on this temporary UTXO when adding a block.
3. Subsequent block adders make the same judgment. When R% of the blocks among m consecutive blocks judge the temporary UTXO as valid, the temporary UTXO can be converted into a formal UTXO, allowing the amount recorded on the banknote to be paid to the Bitcoin wallet address specified in the destruction block.
Global Collaboration
The pioneers of AOB seek to collaborate with companies worldwide, serving as technical advisors to guide partners in developing blockchain projects that achieve the highest degree of decentralization, cryptographic-level security, and unlimited scalability.
Contact: [email protected]
Resources
Published paper: Achieving Greater Decentralization with Atomic Ownership Blockchains
Unpublished preprint: Migrating Bitcoin to AOB for Enhanced Security
Two interactive demos:
Testnet (supports banknote-style payment and speedy-channel payment across devices on real netwrok) -- video
References
This article "Atomic Ownership Blockchains" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Atomic Ownership Blockchains. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
