Applicant

The Bitcoin Corporation Ltd

Inventor

Richard Boase

Date of Preparation

2 March 2026

Title of Invention

Decentralized Dividend Distribution by Competitive Application-Layer Mining Nodes Using a Tripartite Identity, Payment, and Compliance Protocol Stack

Critical Distinction — Application-Layer Miners vs. Blockchain Base-Layer Miners

This patent describes $402 Proof of Indexing miners, which are application-layer network participants (software agents performing useful indexing work), and NOT blockchain base-layer miners (BSV/Bitcoin miners who validate and confirm transactions). Throughout this specification, the term "miner" refers exclusively to application-layer $402 miners unless explicitly qualified as "blockchain miner" or "BSV miner." $402 miners INITIATE dividend payments by constructing blockchain transactions. BSV miners SETTLE those transactions on the underlying blockchain. These are distinct roles operating at different layers of the system architecture.

Field of the Invention

The present invention relates to systems and methods for decentralized, censorship-resistant distribution of financial dividends to token holders by competitive application-layer mining nodes, wherein the dividend computation and distribution work constitutes verifiable indexing work under a Proof of Indexing consensus mechanism, and wherein recipient identity resolution, payment delivery, and compliance verification are performed using three integrated protocol layers mapped to HTTP status codes 401, 402, and 403. More particularly, the invention concerns a network of competing software agents (application-layer miners) that independently compute dividend entitlements from on-chain token holder records, resolve each holder's payout address via a blockchain-based identity protocol, evaluate each holder's eligibility via a programmable securities compliance protocol, construct and broadcast blockchain payment transactions delivering proportional dividends, and earn mining rewards for performing this distribution work — producing redundant, censorship-resistant financial distribution as an emergent property of economic competition among distribution nodes.

Background of the Invention

Problem Statement

Financial dividend distribution — the process by which revenue generated by an asset is proportionally distributed to the asset's owners — is one of the most centralized processes in modern finance. Despite advances in blockchain technology, distributed computing, and decentralized finance, dividend distribution remains dependent on chains of centralized intermediaries. The following six problems describe the current state of the art:

1. Centralized Dividend Distribution — Traditional dividend distribution relies on centralized intermediaries: registrars, transfer agents, banks, and clearing houses. A publicly listed company distributes dividends through a chain comprising: the company's board (declaration), the transfer agent (record-keeping), the Depository Trust Company or equivalent central securities depository (settlement), banks (payment processing), and broker-dealers (delivery to beneficial owners). If any intermediary in this chain fails, is compromised, or is compelled by a government to withhold payments, dividends stop. There is no mechanism for dividend distribution to continue autonomously when a single distribution node is destroyed, sanctioned, or disconnected. The entire chain depends on every link remaining operational and willing to process the distribution.

2. No Redundancy in Financial Distribution — Content delivery networks provide redundancy for serving web content: if one CDN node fails, another serves the same content. Video streaming services replicate content across hundreds of edge servers to ensure availability. Yet no equivalent redundancy model exists for financial distributions. If a company's transfer agent goes offline, there is no automatic failover. If a government sanctions a transfer agent, dividends for all clients of that agent are frozen. Dividends are not served by competing nodes that can independently take over when one fails. Financial distribution has zero redundancy — it is a single-threaded process through a chain of monopoly intermediaries.

3. No Economic Incentive for Distribution Service — In traditional finance, dividend distribution is a cost center. Companies pay intermediaries to distribute funds: transfer agent fees, bank processing fees, clearing house fees. There is no mechanism by which the act of distributing dividends is itself economically incentivized work that distribution nodes compete to perform. Nobody races to distribute dividends faster or more reliably, because distribution is a contracted service, not a competitive market. Distribution quality and reliability are determined by contractual service agreements with monopoly providers, not by competitive market dynamics among independent service providers.

4. Identity Resolution Decoupled from Payment — Knowing WHO is owed dividends (identity) and DELIVERING the payment (settlement) are handled by separate, disconnected systems. Share registries maintained by transfer agents record ownership. Banks process payment instructions received from transfer agents. Broker-dealers maintain beneficial ownership records that differ from the registry's legal ownership records. These systems communicate through batch files, SWIFT messages, and proprietary APIs with no shared data model or protocol. There is no integrated system where identity resolution (determining who is owed), compliance verification (determining who is eligible), and payment delivery (actually paying) occur within a single protocol stack using shared on-chain state that any participant can independently verify.

5. Compliance as Blocking Gate Rather Than Enabling Layer — Securities compliance (KYC, jurisdiction checks, accreditation requirements, holding period restrictions) is enforced by centralized intermediaries who can arbitrarily block distributions. When a dividend is withheld due to compliance concerns, the holder typically receives a generic notification with minimal explanation. There is no system where compliance conditions are programmatically evaluated by any node in the network, producing machine-readable results that either enable or explain the denial of a distribution, without requiring trust in a single compliance authority. Compliance is an opaque, centralized blocking gate rather than a transparent, distributed enabling layer.

6. No Proof of Distribution Work — When a financial intermediary claims to have distributed dividends, there is no independently verifiable proof that the work was performed correctly. Settlement confirmation exists on payment rails (ACH confirmations, wire transfer receipts), but these confirm only that a payment was made — not that the payment amount was correctly computed from holder records, that all eligible holders were included, that compliance conditions were properly evaluated, or that the distribution was free from error or manipulation. There is no mechanism to cryptographically bind the distribution computation (who is owed what, based on what holdings, checked against what conditions) to a proof-of-work commitment that can be verified by independent peers.

Prior Art Limitations

Traditional transfer agents (Computershare, Link Group, Equiniti, AST Financial): These centralized entities maintain shareholder registries and process dividend distributions under contractual arrangements with issuers. They represent single points of failure — if the transfer agent is sanctioned, compromised, or goes offline, distributions halt. Their compliance processes are opaque and proprietary. No redundancy mechanism exists.

DeFi yield distribution protocols (Compound, Aave, Uniswap fee distribution, Sushi MasterChef contracts): These smart-contract-based systems distribute yield to liquidity providers on a single blockchain. They lack cross-chain capability, have no identity layer (addresses are pseudonymous), have no compliance gating beyond simple address whitelists, and are limited to the single blockchain on which the smart contract is deployed. They also distribute yield from protocol operations (lending interest, trading fees), not dividends from external revenue sources.

Staking reward systems (Ethereum PoS rewards, Cosmos staking, Polkadot nominated proof-of-stake): These systems distribute rewards to validators for securing the network. They do not distribute dividends from external revenue sources to shareholders. The rewards are inflationary (newly minted tokens), not distributive (revenue from operations). They serve a fundamentally different purpose.

Payment channel networks (Lightning Network, Raiden): These reduce payment costs and increase throughput for individual transactions. They address payment efficiency but do not solve the problems of identity resolution, compliance verification, competitive distribution, or proof-of-distribution-work. A payment channel can deliver a dividend, but it cannot determine who should receive one, whether they are eligible, or prove that the computation was correct.

The $402 Protocol (The Bitcoin Corporation Ltd, Patent Application filed): The $402 protocol defines the application-layer mining network and Proof of Indexing consensus mechanism. $402 miners perform useful indexing work (content scanning, token verification, content serving) and earn $402 tokens. However, the $402 protocol as previously claimed does not extend to using this mining network for competitive dividend distribution, nor does it claim the tripartite integration of identity resolution ($401), payment delivery ($402), and compliance verification ($403) in a single dividend distribution event.

The HTTP Status Code Tokenization Suite (The Bitcoin Corporation Ltd, Patent Application filed): The suite defines the three integrated protocol layers ($401, $402, $403) and their cross-layer resolution sequence. However, the suite as previously claimed does not describe the use of these three layers in a competitive, decentralized dividend distribution system where multiple application-layer miners race to serve dividend batches.

No existing system combines: competitive application-layer mining for dividend distribution; economic incentives producing distribution redundancy; identity resolution via a blockchain-based identity protocol; compliance verification via a programmable securities protocol; payment delivery via a mining network; proof-of-distribution-work via Proof of Indexing; and censorship-resistant financial distribution as an emergent property of economic competition.

Summary of the Invention

The present invention provides a system and method for decentralized dividend distribution ("the Distribution Engine") comprising:

(a) Competitive distribution mining — $402 Proof of Indexing miners (application-layer network participants that run the clawminerd daemon or equivalent software) compete to compute and distribute dividend payments to token holders. These are NOT blockchain base-layer miners: they are software agents that perform useful indexing work at the application layer. The dividend computation and delivery constitutes verifiable indexing work that earns Proof of Indexing mining rewards. Multiple miners independently compute the same dividend batch, producing redundancy: if any miner fails, is destroyed, or is disconnected, other miners serve the same dividends without interruption. The competitive model ensures that dividend distribution quality emerges from market dynamics rather than from contractual arrangements with monopoly intermediaries.

(b) Tripartite protocol resolution for each dividend event — Each dividend distribution event requires resolution across three integrated protocol layers, all previously defined in the HTTP Status Code Tokenization Suite and extended in the present invention for dividend distribution:

The $401 Identity Layer resolves WHO is owed dividends: querying on-chain identity chains (root inscriptions and strand inscriptions) to determine verified payout addresses for each token holder. The $401 layer provides portable, self-sovereign, multi-provider identity that the miner queries to determine where each holder's dividend should be sent.
The $402 Commerce Layer delivers the payment: the application-layer mining network constructs and broadcasts blockchain transactions paying each eligible holder their proportional share. The $402 miner — NOT the BSV blockchain miner — builds the transaction. The BSV blockchain miner subsequently validates and confirms it.
The $403 Securities Layer gates eligibility: programmatically evaluating compliance conditions (KYC level, jurisdiction, accreditation status, holding period, transfer lock) against each holder before authorizing distribution. The $403 condition engine produces per-condition machine-readable results, transforming compliance from an opaque blocking gate into a navigable enabling layer.

(c) Revenue-to-dividend pipeline — Revenue generated by tokenized assets (micropayments from web traffic via HTTP 402 responses, token sales, secondary market transaction fees, content serving fees) accumulates in an on-chain dividend pool. The pool is transparent and auditable by any network participant — its balance, transaction history, and accumulation rate are publicly observable on the blockchain. When distribution is triggered (per-epoch timer, per-threshold amount, or on-demand by authorized party), miners race to serve the batch.

(d) Distribution work as Proof of Indexing — The computational work of dividend distribution — enumerating holders, resolving identities, checking compliance, computing proportional shares, constructing payment transactions — is classified as verifiable indexing work under the Proof of Indexing consensus mechanism. This work is committed to the miner's work commitment Merkle root alongside other indexing tasks (content scanning, token verification, content serving). Distribution work thus earns $402 mining tokens in addition to any distribution service fee, creating a dual-incentive model for performing distribution work.

(e) Redundancy through economic competition — Because distribution work is profitable (service fees + Proof of Indexing rewards), multiple miners independently attempt to serve each dividend batch. The first miner to successfully broadcast valid distribution transactions to the BSV blockchain earns the service fee. Failed or slow miners' work is not wasted — their independent computation serves as verification of the winning miner's work, because any peer can compare the losing miners' computed distributions against the winning transaction. This competitive model produces censorship-resistant financial distribution: destroying one node does not interrupt dividends, because competing nodes were already computing and preparing to serve the same batch.

(f) Machine-readable compliance resolution — When a holder is ineligible for a dividend (insufficient KYC level, prohibited jurisdiction, unexpired holding period, insufficient accreditation), the system produces a machine-readable explanation specifying which conditions were unsatisfied and what the holder must do to become eligible. Withheld dividends are held in a time-locked on-chain escrow until conditions are satisfied or a configurable expiry period elapses, at which point they are redistributed to eligible holders. No dividends are permanently lost.

Detailed Description of the Invention

1. System Architecture

The Distribution Engine operates at two distinct layers of the system architecture. Understanding the separation between these layers is essential to understanding the invention.

1.1 Application Layer — $402 Mining Network

The $402 mining network comprises a plurality of application-layer mining nodes ("$402 miners"). Each $402 miner is a software agent — a daemon process (the clawminerd daemon or equivalent) running on commodity hardware — that performs useful indexing work. $402 miners are NOT blockchain miners. They do not validate blockchain transactions, they do not compete to find block hashes, and they do not earn block rewards from the underlying blockchain.

$402 miners perform the following categories of work:

Content indexing: Scanning the web for tokenized content (URLs containing the $address prefix), verifying token metadata, cataloguing token markets.
Content serving: Serving gated content to paying users, processing micropayments, maintaining ticket stamp chains.
Token verification: Validating token transfers, updating market state, relaying peer-to-peer messages.
Dividend distribution (the subject of this invention): Enumerating token holders, resolving identities, evaluating compliance, computing proportional dividends, constructing and broadcasting payment transactions.

Each $402 miner has access to the full state required for dividend distribution:

The token holder registry: On-chain records showing which addresses hold which tokens, in what quantities, and since when.
The $401 identity chains: On-chain root inscriptions and strand inscriptions for each holder, providing verified payout addresses and identity metadata.
The $403 compliance conditions: Configurable rules specifying KYC levels, jurisdictions, accreditation requirements, holding periods, and transfer locks.
The dividend pool balances: On-chain balances showing accumulated revenue available for distribution.

$402 miners communicate with each other via a libp2p-based peer-to-peer gossip network using Noise encryption, Yamux multiplexing, and GossipSub message propagation. The gossip network propagates distribution triggers, work commitments, and block announcements.

1.2 Settlement Layer — BSV Blockchain

The BSV blockchain is the settlement layer. BSV miners (blockchain base-layer miners) validate and confirm transactions through the Bitcoin proof-of-work consensus mechanism. BSV miners have no knowledge of the $402 protocol, the $401 identity layer, or the $403 compliance layer. They do not know that a particular transaction is a dividend distribution. They simply validate that the transaction is properly formed, that inputs are unspent, that signatures are valid, and that sufficient transaction fees are included.

The critical architectural relationship is: $402 miners INITIATE dividend payments by constructing and broadcasting BSV transactions. BSV miners SETTLE those transactions by including them in confirmed blocks. The $402 miner decides WHO gets paid and HOW MUCH. The BSV miner confirms that the payment transaction is valid and permanent.

1.3 Protocol Layer Interactions

The three protocol layers ($401, $402, $403) interact within each $402 miner during the dividend distribution process:

Protocol Layer	HTTP Code	Role in Dividend Distribution	Data Source
$401 Identity	401	Resolves holder payout addresses	On-chain identity chains
$402 Commerce	402	Constructs and broadcasts payment transactions	Mining network + BSV blockchain
$403 Securities	403	Evaluates compliance conditions per holder	On-chain compliance records

Each dividend distribution event triggers a sequential resolution across all three layers for each token holder. The $402 miner performs this resolution independently — it does not need to contact any centralized authority, any intermediary, or any other miner to complete the resolution. This independence is what enables competitive, redundant distribution.

2. The Dividend Distribution Cycle

The dividend distribution cycle operates as follows:

2.1 Revenue Accumulation

Revenue from tokenized assets accumulates in an on-chain dividend pool. Sources of revenue include:

HTTP 402 micropayments: Visitors to $402-gated web resources pay micropayments to access content. A configurable percentage of each micropayment flows to the dividend pool.
Token sales: Primary sales of content tokens generate revenue, a portion of which flows to the dividend pool.
Secondary market fees: When tokens are traded on secondary markets, a small transaction fee (configurable by the token issuer) flows to the dividend pool.
Content serving fees: When $402 miners serve gated content to paying users, a portion of the serving fee flows to the dividend pool.

The dividend pool is a blockchain address whose balance is publicly observable. Any network participant can query the pool balance at any time and independently verify the revenue accumulation. The pool's transaction history provides a complete, immutable audit trail of all revenue received.

2.2 Distribution Trigger

Distribution is triggered by one of three mechanisms:

Epoch timer: A configurable time interval (e.g., every 24 hours, every 7 days, every 30 days) triggers automatic distribution. The epoch timer is enforced by the protocol — when the current block timestamp exceeds the last distribution timestamp plus the epoch interval, the trigger activates.
Threshold amount: When the dividend pool balance exceeds a configurable threshold (e.g., 1 BSV, 10 BSV, 100 BSV), distribution is triggered automatically. This ensures distributions are economically meaningful relative to the transaction costs of processing them.
Manual trigger: An authorized party (the token issuer or a designated administrator with a $401 identity of sufficient strength) can trigger distribution on demand.

Distribution triggers are propagated through the $402 gossip network. When any miner detects a trigger condition, it announces the trigger to connected peers. All miners receiving the announcement independently verify the trigger condition against on-chain state before beginning distribution work.

2.3 Competitive Distribution Process

Upon detecting and verifying a distribution trigger, each competing $402 miner independently performs the following steps:

Step 1 — Holder Enumeration: The miner enumerates all current holders of the relevant token by scanning on-chain records. For each holder, the miner records: the holder's blockchain address, the number of tokens held, the timestamp of acquisition (for holding period calculation), and any relevant metadata.

Step 2 — Identity Resolution ($401 Query): For each holder, the miner queries the $401 identity layer to resolve the holder's payout address. The miner looks up the holder's $401 root inscription and reads the payTo field, which specifies the BSV address to which dividends should be sent. If the holder's blockchain address (the address holding the tokens) differs from their $401 payTo address, dividends are sent to the payTo address — the holder controls where dividends are delivered by updating their $401 root inscription.

If a holder has no $401 identity chain, or if their $401 identity is revoked or expired, the miner flags that holder's dividend for escrow (see Section 8).

Step 3 — Compliance Evaluation ($403 Query): For each holder, the miner evaluates all active $403 compliance conditions attached to the token. The compliance evaluation is described in detail in Section 4.

Step 4 — Proportional Share Computation: For each eligible holder (a holder who has passed both identity resolution and compliance evaluation), the miner computes the proportional dividend share:

holderDividend = (holderTokens / totalEligibleTokens) * dividendPoolBalance * (1 - serviceFeeRate)

Where:

holderTokens is the number of tokens held by the holder
totalEligibleTokens is the sum of tokens held by all eligible holders
dividendPoolBalance is the current balance of the dividend pool
serviceFeeRate is the configurable fee retained by the miner for performing distribution work

Note that the denominator is totalEligibleTokens, not totalTokens. Tokens held by ineligible holders (those failing compliance) are excluded from the proportional calculation. This means eligible holders receive a larger share when some holders are ineligible — they are not penalized for other holders' non-compliance.

Step 5 — Transaction Construction: The miner constructs a BSV transaction (or minimal batch of transactions, if the number of recipients exceeds the practical transaction size limit) with the following structure:

Inputs: One or more UTXOs from the dividend pool address, authorized by the pool's spending conditions.
Outputs: One output per eligible holder, each paying holderDividend to the holder's resolved $401 payTo address.
Service fee output: One output paying the service fee to the miner's own address.
Escrow output: One output paying withheld dividends (for ineligible holders) to the time-locked escrow address.
OP_RETURN output: A data output containing distribution metadata (see Section 5).

Step 6 — Signing and Broadcasting: The miner signs the transaction using its own cryptographic keys (which are authorized as signers on the dividend pool's spending conditions) and broadcasts the signed transaction to the BSV peer-to-peer network.

Step 7 — Settlement: BSV miners (blockchain base-layer miners) receive the broadcast transaction, validate its structure and signatures, and include it in a confirmed block. Upon confirmation, the dividend distribution is settled and immutable.

2.4 Competition Resolution

Multiple $402 miners independently perform Steps 1-6 simultaneously. Because they are all reading the same on-chain state (the same holder registry, the same $401 identity chains, the same $403 compliance conditions, the same dividend pool balance), they should all compute the same distribution (subject to minor differences in the exact block at which they snapshot the state).

The first miner to broadcast a valid distribution transaction that is confirmed on the BSV blockchain "wins" — that miner earns the service fee. Other miners' transactions, if they attempt to spend the same dividend pool UTXOs, are rejected as double-spends by the BSV network. This is the normal operation of blockchain consensus: only one transaction can spend a given UTXO.

The losing miners' computational work is not wasted. Their independent computation of the same distribution serves two purposes:

Verification: Any peer can compare the losing miners' computed distributions against the winning transaction to verify that the winning miner computed dividends correctly.
Readiness: If the winning miner's transaction had been invalid or if the winning miner had been offline, the next-fastest miner would have won instead. The existence of multiple miners computing the same distribution in parallel provides implicit redundancy.

3. Identity Resolution ($401 Integration)

The $401 identity layer is defined in the HTTP Status Code Tokenization Suite (Patent Application filed by The Bitcoin Corporation Ltd). The Distribution Engine integrates with $401 as follows:

3.1 Holder-to-Payout-Address Resolution

Each token holder's on-chain identity is anchored by a $401 root inscription containing a payTo field:

{
  "p": "401",
  "op": "root",
  "v": "1.0",
  "payTo": "<BSV payout address>",
  "ts": "<ISO 8601 timestamp>"
}

The payTo field is the canonical destination for dividend payments. When a $402 miner computes a dividend distribution, it resolves each holder's payout address by:

Looking up the holder's blockchain address in the $401 identity index.
Finding the corresponding $401 root inscription.
Reading the payTo field from the root inscription.
Using the payTo address as the output destination in the dividend payment transaction.

This resolution ensures that holders can direct their dividends to any BSV address of their choosing, independent of the address that holds their tokens. A holder may hold tokens at one address and receive dividends at another, providing operational flexibility and security isolation.

3.2 Identity Updates

Holders can update their payout address at any time by issuing a $401 Update operation, which creates a new on-chain inscription:

{
  "p": "401",
  "op": "update",
  "v": "1.0",
  "root": "<root inscription transaction identifier>",
  "payTo": "<new BSV payout address>",
  "ts": "<ISO 8601 timestamp>"
}

$402 miners pick up payout address changes on the next distribution cycle. The miner always uses the most recent payTo address associated with the holder's $401 root inscription as of the distribution snapshot block.

3.3 Identity Absence and Revocation

If a holder has no $401 identity chain (no root inscription linked to their blockchain address), the miner cannot resolve a payout address. In this case, the holder's dividend is withheld to escrow. The holder can subsequently create a $401 identity chain, and any miner can then release the escrowed dividend.

If a holder's $401 identity has been revoked (via the $401 Revoke operation), the identity is no longer valid. The holder's dividend is withheld to escrow until the holder creates a new valid identity.

3.4 Identity Caching

$402 miners cache resolved identities to avoid redundant on-chain queries. The cache is periodically refreshed from on-chain state. The refresh interval is configurable per miner, with a recommended default of refreshing at the start of each distribution cycle to ensure current payout addresses are used.

4. Compliance Gating ($403 Integration)

The $403 securities layer is defined in the HTTP Status Code Tokenization Suite (Patent Application filed by The Bitcoin Corporation Ltd). The Distribution Engine integrates with $403 to gate dividend eligibility.

4.1 Per-Holder Compliance Evaluation

Before distributing a dividend to each holder, the $402 miner evaluates all active $403 compliance conditions attached to the relevant token. The following conditions are evaluated:

Condition 1 — KYC Level: Does the holder's $401 identity meet the minimum verification level required by the token's compliance configuration? The miner queries the holder's $401 identity chain and determines the identity strength level using the type-gated classification system (Level 1: Basic OAuth, Level 2: Verified with human participation, Level 3: Strong with economic/social commitment, Level 4: Sovereign with biometric KYC). If the holder's identity strength is below the minimum required level, this condition is unsatisfied.

Condition 2 — Jurisdiction: Is the holder in a permitted jurisdiction? The miner determines the holder's jurisdiction from their $401 identity metadata (if available) or from jurisdiction attestations in their identity strands. If the holder's jurisdiction is on the token's prohibited jurisdictions list, or if the holder is not on the permitted jurisdictions list (depending on configuration mode — blacklist or whitelist), this condition is unsatisfied.

Condition 3 — Accreditation: Is the holder an accredited investor? If the token requires accredited investor status (as defined by the applicable securities regulation for the token's jurisdiction), the miner checks the holder's $401 identity chain for an accreditation attestation strand. If no valid, unexpired accreditation attestation is found, this condition is unsatisfied.

Condition 4 — Holding Period: Has the holder held tokens for the minimum required period? The miner checks the holder's acquisition timestamp (recorded on-chain when the tokens were transferred to the holder's address) against the current block timestamp. If the elapsed holding period is less than the minimum required, this condition is unsatisfied.

Condition 5 — Transfer Lock: Are the holder's tokens currently transfer-locked? If a transfer lock is active on the token (e.g., during a lock-up period following issuance), this condition is unsatisfied for all holders. Transfer locks are distinct from holding periods: a transfer lock applies to the token itself, while a holding period applies to each holder individually based on their acquisition time.

4.2 Machine-Readable Compliance Results

Each condition evaluation produces a machine-readable result with the following structure:

{
  "condition": "kyc_level",
  "required": 2,
  "actual": 1,
  "satisfied": false,
  "reason": "Holder identity strength level 1 (Basic OAuth) does not meet minimum required level 2 (Verified). Holder must complete identity verification with a self-attestation, identity document, camera verification, or video verification provider.",
  "remediation": "Complete $401 Level 2 verification at path401.com/verify"
}

Each condition result specifies:

Which condition was evaluated
What was required
What the holder's actual status is
Whether the condition was satisfied (boolean)
A human-readable reason explaining the result
A machine-readable remediation action (if unsatisfied)

The complete compliance evaluation for each holder comprises an array of per-condition results plus an overall eligibility determination:

{
  "holder": "<holder address>",
  "token": "<token identifier>",
  "eligible": false,
  "conditions": [
    { "condition": "kyc_level", "satisfied": false, "reason": "..." },
    { "condition": "jurisdiction", "satisfied": true, "reason": "..." },
    { "condition": "accreditation", "satisfied": true, "reason": "..." },
    { "condition": "holding_period", "satisfied": true, "reason": "..." },
    { "condition": "transfer_lock", "satisfied": true, "reason": "..." }
  ],
  "action": "escrow",
  "escrow_expiry": "<ISO 8601 timestamp>"
}

If ANY condition is unsatisfied, the holder is ineligible and their dividend is routed to escrow. The machine-readable results enable automated systems (wallets, agent software, compliance dashboards) to display precisely what the holder must do to become eligible.

4.3 Independent Compliance Verification

A critical property of the system is that any $402 miner can independently evaluate the same compliance conditions and verify another miner's compliance decisions. All compliance inputs are on-chain: the holder's $401 identity chain, the token's $403 compliance configuration, the holder's acquisition timestamp, and the jurisdiction/accreditation metadata. No off-chain data or proprietary databases are required. This enables trustless verification of compliance decisions — if a miner incorrectly flags a holder as eligible (or ineligible), any peer can detect the error by performing the same evaluation against the same on-chain state.

5. Payment Construction and Settlement ($402 Layer)

5.1 Transaction Structure

The $402 miner constructs a BSV transaction paying all eligible holders in a single transaction (or minimal batch of transactions if the number of outputs exceeds the practical limit). The transaction structure is:

Inputs:

One or more UTXOs from the dividend pool address. The spending conditions on these UTXOs are configured to authorize any $402 miner with a valid Proof of Indexing work commitment to spend them for distribution purposes.

Outputs:

One output per eligible holder: amount = holderDividend, destination = holder's resolved $401 payTo address. Outputs below the dust threshold (the minimum viable UTXO size on the BSV network) are aggregated and carried forward to the next distribution cycle.
One service fee output: amount = totalDistributed * serviceFeeRate, destination = miner's own address.
One escrow output (if any holders are ineligible): amount = sum of withheld dividends, destination = time-locked escrow address (see Section 8).
One OP_RETURN data output containing distribution metadata.

5.2 Distribution Metadata (OP_RETURN)

The OP_RETURN output contains a structured data payload recording the distribution event:

{
  "p": "$402",
  "op": "distribute",
  "v": "1.0",
  "token": "<token identifier>",
  "epoch": "<distribution epoch number>",
  "totalDistributed": "<total amount distributed>",
  "totalEscrowed": "<total amount escrowed>",
  "recipients": "<number of eligible recipients>",
  "escrowed": "<number of ineligible holders>",
  "merkleRoot": "<Merkle root of individual distributions>",
  "poolBalanceBefore": "<dividend pool balance before distribution>",
  "poolBalanceAfter": "<dividend pool balance after distribution>",
  "miner": "<miner $401 identity root>",
  "ts": "<ISO 8601 timestamp>"
}

The merkleRoot field is a SHA-256 Merkle root computed from the individual distribution records (one leaf per holder, containing: holder address, payout address, token amount held, dividend amount, compliance result). This Merkle root enables compact verification: a verifier can request individual distribution records from the miner and verify them against the Merkle root without needing the complete list.

5.3 Settlement Process

Upon construction and signing, the $402 miner broadcasts the transaction to the BSV peer-to-peer network. BSV miners (blockchain base-layer miners) receive the transaction, validate its structure:

All inputs reference valid, unspent UTXOs
All signatures are valid
The transaction fee is sufficient
The total output value does not exceed the total input value

BSV miners include the valid transaction in a block. Upon block confirmation, the dividend distribution is settled and immutable. The BSV miners have no knowledge that this transaction represents a dividend distribution — to them, it is simply a valid transaction moving funds from one set of addresses to another.

The $402 miner monitors the BSV blockchain for confirmation of its distribution transaction. Upon confirmation, the miner records the distribution event as completed and includes it in its Proof of Indexing work commitment.

6. Distribution Work as Proof of Indexing

The Proof of Indexing consensus mechanism, defined in the $402 protocol, binds useful data-indexing work to proof-of-work mining challenges. The present invention extends Proof of Indexing to encompass dividend distribution work.

6.1 Distribution Work Items

The computational work of dividend distribution comprises the following verifiable work items:

Holder enumeration: Scanning on-chain records to enumerate all holders of the relevant token. Work item identifier: hash of (token ID + snapshot block height + holder count).
Identity resolution: Querying $401 identity chains to resolve each holder's payout address. Work item identifier: hash of (holder address + resolved payTo address + $401 root txid).
Compliance evaluation: Evaluating $403 compliance conditions for each holder. Work item identifier: hash of (holder address + per-condition results array).
Share computation: Computing proportional dividend shares for each eligible holder. Work item identifier: hash of (holder address + tokens held + dividend amount + total eligible tokens).
Transaction construction: Building the BSV payment transaction. Work item identifier: hash of (transaction ID + output count + total distributed).

Each work item is independently verifiable: a peer can request the work item data from the miner and recompute the identifier to confirm correctness.

6.2 Distribution Work Commitment

The work item identifiers are sorted and combined into a SHA-256 Merkle root — the distribution work commitment. This is a 32-byte value cryptographically binding the distribution work to a Merkle tree that peers can partially or fully verify.

The distribution work commitment is included in the miner's overall work commitment alongside other indexing work (content scanning, token verification, content serving). The overall work commitment is a Merkle root computed from all work commitments (distribution + other indexing) performed since the last mining cycle.

6.3 Mining Challenge Integration

The overall work commitment is included in the Proof of Indexing mining challenge:

challenge = previousTransactionId || workCommitment || destinationAddress || nonce

The miner iterates nonces until SHA256(SHA256(challenge)) produces a hash value below the current difficulty target. A valid solution is submitted to the $402 smart contract on the BSV blockchain, which verifies the work commitment and mints $402 tokens to the miner's address.

A miner that performs dividend distribution work AND finds a valid PoI solution earns from both:

Distribution service fee: Earned from the dividend distribution transaction itself.
$402 mining reward: Earned from the Proof of Indexing block containing the distribution work commitment.

This dual-incentive model makes distribution work more profitable than other forms of indexing work (all else being equal), attracting more miners to perform distribution work and increasing the redundancy and reliability of dividend distribution.

6.4 Peer Verification of Distribution Work

Peers can verify distribution work by requesting individual work items from the miner and checking them against the Merkle tree. A verifying peer can:

Request the distribution work commitment Merkle root.
Request any subset of work item leaves.
Verify the Merkle proof for each requested leaf.
Independently recompute the work item identifier (e.g., re-resolve a holder's $401 identity and verify the result matches).
If any discrepancy is found, flag the miner's work commitment as invalid.

This verification mechanism ensures that miners cannot earn Proof of Indexing rewards for distribution work they did not actually perform, or for distributions they computed incorrectly.

7. Redundancy and Censorship Resistance

The competitive distribution model produces censorship-resistant financial distribution as an emergent property of economic incentives.

7.1 Multi-Miner Redundancy

When a distribution trigger fires, multiple $402 miners independently compute the same dividend batch. Each miner performs the full computation independently: holder enumeration, identity resolution, compliance evaluation, share computation, and transaction construction. Each miner produces a distribution transaction that, if broadcast first, would be the valid distribution.

If Miner A broadcasts first and its transaction is confirmed, Miners B, C, and D's transactions are superseded. But if Miner A is offline, destroyed, or refuses to broadcast, Miner B's transaction is confirmed instead. If Miner B also fails, Miner C takes over. The distribution succeeds as long as at least one miner in the network is operational and willing to perform the work.

7.2 Economic Guarantee of Redundancy

The number of miners competing to serve any given distribution is not fixed — it is determined by economic incentive. Miners perform distribution work when it is profitable: when the service fee plus the expected PoI mining reward exceeds the miner's operational cost (computation, bandwidth, electricity).

As the value of distributions increases (larger dividend pools, higher-value tokens), the profitability of distribution work increases, attracting more miners. More miners means more redundancy. The system self-scales: high-value distributions attract many competing miners and are therefore the most censorship-resistant.

7.3 Geographic and Jurisdictional Resilience

$402 miners can operate anywhere in the world. There is no requirement for miners to be registered, licensed, or located in any particular jurisdiction. A government shutting down miners in one country does not affect miners in other countries. The distribution continues uninterrupted as long as any miner anywhere in the world is operational.

This geographic distribution provides jurisdictional resilience: no single government can halt dividend distribution by targeting miners within its borders, because miners outside its borders continue serving the same distributions.

7.4 Comparison to Traditional Systems

In traditional finance, dividend distribution depends on a single chain of intermediaries. If the transfer agent (Computershare, Link Group) goes offline, ALL dividends for all its clients halt. There is no automatic failover. The Distribution Engine's competitive model eliminates this single point of failure. The redundancy is not engineered through contractual backup arrangements — it emerges naturally from economic competition.

8. Escrow and Redistribution

8.1 Escrow Mechanism

When a holder fails compliance evaluation (any $403 condition is unsatisfied) or when identity resolution fails (no valid $401 identity chain), the holder's dividend is not discarded. It is routed to a time-locked on-chain escrow.

The escrow is a BSV transaction output with spending conditions that allow:

Release to holder: If the holder satisfies the previously unsatisfied conditions within the escrow period, any $402 miner can construct a release transaction paying the escrowed amount to the holder's resolved $401 payTo address. The miner verifies that the conditions are now satisfied (e.g., the holder has completed $401 Level 2 verification) and releases the escrow.
Redistribution: If the escrow period expires (configurable, e.g., 90 days, 180 days, 365 days) and the holder has not satisfied the conditions, the escrowed amount is returned to the dividend pool and redistributed to eligible holders in the next distribution cycle.

The escrow period, conditions for release, and redistribution rules are configured in the token's $403 compliance configuration and are publicly readable on-chain.

8.2 Escrow Audit Trail

Each escrow event is recorded on-chain via an OP_RETURN inscription:

{
  "p": "$402",
  "op": "escrow",
  "v": "1.0",
  "token": "<token identifier>",
  "holder": "<holder address>",
  "amount": "<escrowed amount>",
  "reason": "<array of unsatisfied conditions>",
  "expiry": "<escrow expiry timestamp>",
  "distributionEpoch": "<epoch number of the distribution that triggered this escrow>",
  "ts": "<ISO 8601 timestamp>"
}

This provides a complete, immutable audit trail of all escrow events, enabling holders to track their escrowed dividends and understand exactly what they need to do to release them.

8.3 No Dividends Lost

A critical design principle of the escrow mechanism is that no dividends are permanently lost. Every unit of revenue entering the dividend pool is eventually distributed to eligible holders — either directly (in the distribution cycle) or via escrow release (when the holder becomes eligible) or via redistribution (when the escrow expires). The only deduction is the distribution service fee paid to the miner that performs the distribution work.

9. Integration with Existing Protocol Stack

The Distribution Engine extends the capabilities of the previously filed patent applications as follows:

9.1 Extension of the $402 Mining Network

The $402 protocol defines a network of application-layer miners performing useful indexing work (content scanning, token verification, content serving) and earning $402 tokens through Proof of Indexing. The Distribution Engine extends this network's capabilities to include financial distribution. The same miners, running the same daemon software, can perform both content-related indexing work and dividend distribution work. The work items from both categories are combined into a single Proof of Indexing work commitment.

9.2 Tripartite Resolution in a Single Event

The HTTP Status Code Tokenization Suite defines the three-layer resolution sequence: $401 (identity) -> $402 (payment) -> $403 (compliance) -> 200 (content delivery). The Distribution Engine uses all three layers in a single atomic distribution event for each holder:

$401 query: Resolve the holder's payout address from their on-chain identity chain.
$403 evaluation: Check the holder's eligibility against all compliance conditions.
$402 payment: Construct and broadcast the payment transaction.

All three layers resolve in sequence for each holder. If any layer fails (no $401 identity, $403 condition unsatisfied), the holder's dividend is escrowed rather than paid. The resolution is performed independently by each competing miner, producing redundant evaluation.

9.3 Economic Consistency with Content Serving

The competitive distribution model follows the same economic logic as competitive content serving (as described in the Autonomous Discovery and Acquisition patent application). In both cases:

Miners race to serve because serving is profitable.
Redundancy emerges from competition, not from engineered infrastructure.
Censorship resistance is a byproduct of economic incentive, not a primary engineering goal.
The number of competing nodes scales with the economic value at stake.

The Distribution Engine applies this proven economic model to financial distribution, a domain previously served exclusively by centralized intermediaries.

Brief Description of Drawings

The following drawings would accompany this application:

Figure 1 — System Architecture: Two-layer diagram showing the $402 mining network (application layer) above and the BSV blockchain (settlement layer) below. $402 miners are shown as nodes in a peer-to-peer gossip network, each with access to $401 identity chains, $403 compliance conditions, and the dividend pool. Arrows show $402 miners constructing and broadcasting transactions downward to the BSV blockchain for settlement. Clear visual separation between the two layers with labels "APPLICATION LAYER — $402 Miners (Initiate)" and "SETTLEMENT LAYER — BSV Miners (Confirm)."

Figure 2 — Dividend Distribution Cycle: Flow diagram showing the complete cycle: Revenue Accumulation (micropayments, token sales, fees) -> Dividend Pool (on-chain, transparent) -> Distribution Trigger (epoch/threshold/manual) -> Miner Competition (multiple miners computing in parallel) -> First Valid Broadcast Wins -> BSV Settlement -> Distribution Complete. Feedback loop showing service fee and PoI reward flowing back to miners.

Figure 3 — Tripartite Resolution for a Single Holder: Sequential diagram showing the three-layer resolution for one holder: $401 Identity Query (resolve payTo address) -> $403 Compliance Check (evaluate KYC, jurisdiction, accreditation, holding period, transfer lock) -> Decision Gate (eligible: pay via $402 / ineligible: route to escrow). Machine-readable results shown at each stage.

Figure 4 — Competitive Mining: Diagram showing multiple miners (A, B, C, D) independently computing the same dividend batch in parallel. All miners read the same on-chain state. Miner B broadcasts first — its transaction is confirmed. Miners A, C, D's transactions are superseded. Miner B earns the service fee. The independent computation by A, C, D provides implicit verification.

Figure 5 — Redundancy Under Failure: Scenario diagram showing: Normal operation (Miners A-D all computing, Miner A wins). Miner A destroyed (Miners B-D still computing, Miner B wins — no interruption). Miners A and B destroyed (Miners C-D still computing, Miner C wins — no interruption). Only total network failure (all miners destroyed) halts distribution.

Figure 6 — Compliance Gating Flow: Per-condition evaluation flowchart. For each of the five conditions (KYC Level, Jurisdiction, Accreditation, Holding Period, Transfer Lock), a diamond decision node produces a machine-readable result (satisfied/unsatisfied + reason + remediation). If ALL satisfied: route to payment. If ANY unsatisfied: route to escrow with complete condition results.

Figure 7 — Distribution Work as Proof of Indexing: Tree diagram showing: individual distribution work items (holder enumeration, identity resolutions, compliance evaluations, share computations, transaction construction) -> work item identifiers -> sorted list -> Merkle tree -> distribution work commitment (root) -> combined with other indexing work commitments -> overall work commitment -> PoI mining challenge -> valid solution -> $402 token reward.

Figure 8 — Revenue-to-Dividend Pipeline: End-to-end flow diagram: Web Visitor pays micropayment via HTTP 402 -> Revenue enters dividend pool -> Pool balance grows transparently -> Distribution trigger fires -> $402 miners compute proportional dividends -> Resolve $401 identities -> Check $403 compliance -> Construct BSV transaction -> Broadcast -> BSV settlement -> Token holders receive proportional dividends. Shows the complete path from web visitor to token holder with no centralized intermediary.

Initial Claims

Note: These claims are provided in sketch form for the purposes of establishing a priority date. Formal claims will be drafted and filed within 12 months in accordance with UKIPO rules.

Claim 1 — Decentralized Dividend Distribution by Competitive Application-Layer Miners

A method of distributing financial dividends to token holders using a network of competing application-layer mining nodes, the method comprising:

(a) accumulating revenue from a tokenized asset in an on-chain dividend pool, the pool being publicly observable and auditable on a blockchain;

(b) upon a distribution trigger, a plurality of application-layer mining nodes independently computing the dividend entitlement for each token holder by enumerating holders from on-chain records and calculating proportional shares based on each holder's token balance relative to the total eligible token supply;

(c) each mining node independently constructing a blockchain transaction paying each eligible holder their proportional dividend from the dividend pool;

(d) the first mining node to successfully broadcast a valid distribution transaction to the underlying blockchain earning a distribution service fee;

wherein the dividend distribution is performed by competing application-layer nodes operating above the blockchain base layer, multiple nodes independently compute the same distribution producing redundancy, and if any node fails the remaining nodes serve the dividends without interruption, producing censorship-resistant financial distribution as an emergent property of economic competition.

Claim 2 — Tripartite Protocol Resolution for Dividend Distribution

A method of distributing dividends to token holders using three integrated protocol layers mapped to HTTP status codes, the method comprising:

(a) resolving each token holder's payout address by querying a first protocol layer ($401) that maintains on-chain identity chains comprising root inscriptions with payout address fields and strand inscriptions linked to verified identity providers;

(b) evaluating each token holder's eligibility by querying a third protocol layer ($403) that programmatically evaluates compliance conditions including one or more of: identity verification level, jurisdiction, accreditation status, holding period, and transfer lock status, producing per-condition machine-readable results;

(c) delivering payment to each eligible holder via a second protocol layer ($402) whose application-layer mining network constructs and broadcasts blockchain payment transactions to the underlying settlement layer;

wherein identity resolution, compliance verification, and payment delivery are performed within a single integrated protocol stack using shared on-chain state, and wherein any mining node in the network can independently perform all three resolution steps without contacting any centralized authority.

Claim 3 — Dividend Distribution Work as Proof of Indexing

A method of earning mining rewards by performing dividend distribution work, the method comprising:

(a) an application-layer mining node performing verifiable distribution work comprising: enumerating token holders from on-chain records, resolving identity records from a blockchain-based identity layer, evaluating compliance conditions from a programmable securities layer, computing proportional dividend shares, and constructing payment transactions;

(b) assigning a cryptographic identifier to each completed work item in the distribution;

(d) including the distribution work commitment in the mining node's overall work commitment for a Proof of Indexing mining cycle alongside other indexing work commitments;

(e) submitting the combined work commitment as part of a proof-of-work mining challenge, the challenge comprising the work commitment and a nonce iterated until the hash meets a difficulty target;

wherein the computational work of dividend distribution constitutes verifiable indexing work that earns mining rewards, and wherein peers can request individual work items and verify the Merkle tree to confirm the distribution was performed correctly.

Claim 4 — Censorship-Resistant Financial Distribution Through Economic Competition

A system for achieving censorship-resistant financial distribution through economic incentive, the system comprising:

(a) a plurality of geographically distributed application-layer mining nodes, each independently capable of computing and delivering dividend payments to token holders without reliance on any centralized intermediary;

(b) an economic incentive mechanism whereby mining nodes earn distribution service fees from the dividend pool and Proof of Indexing mining rewards for performing distribution work;

(c) a competitive distribution model wherein multiple nodes independently compute the same dividend batch from the same on-chain state, the first node to broadcast a valid distribution transaction earning the service fee;

wherein the number of nodes capable of serving any given dividend distribution is determined by economic incentive — nodes perform distribution work when it is profitable — and wherein distribution continues without interruption when any subset of nodes is destroyed, disconnected, or compelled to cease operation, because the remaining nodes independently compute and serve the same distributions motivated by the same economic incentives.

Claim 5 — Machine-Readable Compliance Resolution with Dividend Escrow

A method of handling dividend distributions to token holders who fail compliance verification, the method comprising:

(a) evaluating compliance conditions for each token holder using a programmable condition engine that produces per-condition machine-readable results specifying whether each condition was satisfied and, if not, what specific action is required for remediation;

(b) withholding dividends for non-compliant holders in a time-locked on-chain escrow, the escrow recorded with an immutable audit trail specifying the unsatisfied conditions and the escrow expiry;

(c) releasing escrowed dividends to the holder upon any application-layer mining node verifying that compliance conditions are subsequently satisfied within a configurable escrow period;

(d) redistributing expired escrowed dividends to eligible holders via the dividend pool if conditions remain unsatisfied after the escrow period;

wherein non-compliant holders receive machine-readable guidance on achieving compliance, dividends are neither permanently lost nor indefinitely frozen, and the escrow mechanism is transparent and auditable on-chain.

Claim 6 — Revenue-to-Dividend Pipeline via Application-Layer Mining Network

A system for converting micropayment revenue from a tokenized web resource into proportional dividend payments to token holders, the system comprising:

(a) a revenue collection mechanism receiving micropayments from visitors via HTTP 402 Payment Required responses, the micropayments accumulated from content access fees, token sales, and secondary market transaction fees;

(b) an on-chain dividend pool accumulating collected revenue transparently, the pool balance and transaction history publicly observable on the blockchain;

(c) a distribution trigger that activates when the pool reaches a configurable threshold amount, a configurable time epoch elapses, or an authorized party with a verified on-chain identity requests distribution;

(d) a network of competing application-layer mining nodes that, upon activation, independently compute proportional dividends based on on-chain token holdings, resolve holder identities via a blockchain-based identity protocol, verify compliance via a programmable securities protocol, and broadcast payment transactions to the underlying blockchain;

(e) a settlement layer (blockchain) that confirms the payment transactions through base-layer consensus, the base-layer miners having no knowledge of the dividend distribution semantics;

wherein revenue flows from web visitors through the application-layer mining network to token holders without any centralized intermediary, the mining network provides redundant and competitive distribution service, and the separation between the application layer (which computes and initiates distributions) and the settlement layer (which confirms transactions) ensures that the system leverages blockchain immutability without burdening the base layer with distribution logic.

Abstract

A system and method for decentralized distribution of financial dividends to token holders by competing application-layer mining nodes. Revenue from tokenized assets accumulates in on-chain dividend pools. Upon distribution triggers, multiple mining nodes in a Proof of Indexing network independently compute dividend entitlements by enumerating holders from on-chain records, resolving recipient identities via a blockchain-based identity protocol ($401), evaluating compliance conditions via a programmable securities protocol ($403), and delivering payments via the mining network's payment layer ($402). The first node to broadcast valid distribution transactions to the underlying blockchain earns a service fee; competing nodes' independent computation provides verification and redundancy. The dividend distribution work constitutes verifiable indexing work earning additional mining rewards through a cryptographic work commitment mechanism. If any mining node is destroyed or disconnected, remaining nodes serve the same dividends without interruption, producing censorship-resistant financial distribution as an emergent property of economic competition. Non-compliant holders receive machine-readable compliance guidance and their dividends are escrowed until conditions are met or redistributed upon expiry. The system distinguishes between application-layer miners (which initiate distributions) and blockchain base-layer miners (which settle transactions), operating as complementary layers within a unified architecture.

Document prepared for UKIPO filing. Priority date to be established upon submission. Applicant: The Bitcoin Corporation Ltd Inventor: Richard Boase Date of preparation: 2 March 2026

Get Started

This patent was filed by The Bitcoin Corporation Ltd with the UK Intellectual Property Office. To learn more about the technology described here, visit b0ase.com or press the MoneyButton in the bottom right corner to support this work.

For AI Readers

Intent: Public disclosure of UKIPO patent filing for decentralized dividend distribution via competitive application-layer mining. Core Thesis: Financial dividend distribution can be made redundant, censorship-resistant, and competitive by treating it as Proof of Indexing mining work performed by autonomous software agents using the $401/$402/$403 protocol stack. Key Takeaways:

Competing $402 miners independently compute and distribute dividends, producing redundancy
Tripartite resolution: $401 identity + $402 payment + $403 compliance per dividend event
Distribution work earns Proof of Indexing rewards + service fees (dual incentive)
Machine-readable compliance with time-locked escrow for ineligible holders
Application GB2604496.6 filed with UKIPO on 2 March 2026