Contribution revenue share network.
Etheraio records verified computing contributions and allocates eligible settled net revenue. Work records, purchased AI usage credits and cash allocations have separate accounting. Financial features show their current provider and verification status.
Verified work is the allocation basis
Tasks remain signed by participating nodes and checked by the existing farm. Only a unique accepted receipt adds weight. The same result, renamed copies, failed work, idle time and self-reported hardware usage do not create additional contributions. Weights are fixed accounting units, not measured FLOPS, electricity or proof of equal scientific value.
All supported sectors use the existing acceptance rules. Missing verifiers or licensed training inputs remain unavailable. No system can guarantee novel science, medicine safety, game quality or continuous 100% utilization.
Income and the split
Only verified, earned and reconciled settled network income qualifies: research sales, AI services already delivered, games, software and licensing. Deduct tax, payment fees, refunds, operating costs and prior commitments first. Then 99% of that net amount forms the contributor pool and 1% is retained by the owner. Every source needs its own trusted settlement adapter. Unused prepaid customer AI Credits, projected sales and crypto mined directly for contributors are excluded. No new source is treated as funded just because a model generates a result.
Settlement snapshots
At a funded settlement, each participant receives their unallocated accepted weight divided by all unallocated verified weight on the network, multiplied by that round’s contributor pool. Work participates once, then is marked allocated. Pending contribution weight does not expire. If there is no settled income, work stays pending. If there is no work, income stays unallocated.
Amounts are recorded as exact millionths of a pound; deterministic remainder allocation conserves the entire pool. A future payment provider can pay whole pennies while retaining smaller remainders. Already recorded allocations cannot be diluted by later contributors. Withdrawing money will not change completed rounds or make old work eligible again. This is compensation accounting for completed contributions, not a perpetual ownership share of all future revenue.
Receipts and trust
Each accepted work digest, income import and settlement links to the previous SHA-256 event hash. SQLite transactions keep a round and its allocations together. Source results and income references are deduplicated. Participants can save receipts and checkpoints.
The service controls verification and storage. A privileged operator could replace its history. Exported checkpoints help detect changes; they do not stop an operator rewriting an entire database. Accounting and financial receipts must persist. They cannot safely be deleted as temporary files every few seconds.
Withdrawal and activation
The deployment exposes read-only revenue summaries and personal receipts. It accepts no client-provided settlement, paid status or cash-balance override. Billing reports the current payment-provider and withdrawal checks. A provisional share is not withdrawable. Refund and dispute reserves must be resolved before a production settlement is recognized; later adjustments require a linked accounting event.
UK legal review
Non-transferable work records do not, by themselves, establish a regulatory exemption. Profit or income sharing can constitute regulated arrangements depending on its rights and operation. A qualified UK adviser must determine the actual structure and contributor terms before public financial activation. FCA guidance on collective investment schemes.
These notes describe the contribution model. They create no ownership interest, guaranteed income or FCA clearance. Historical account records are preserved separately.
RESEARCH-FUNDED CONTRIBUTIONS
Research sales fund cash allocations
Participating devices complete verified jobs, save receipts and maintain an auditable allocation history. Its funding is earned, settled net income. Research results remain unpriced until a sale is verified and its money settles. Creating a report or improving a simulation cannot itself create cash funding.
99% of settled net research-sale proceeds goes to the contributor pool after tax, fees, refunds, operating deductions and prior commitments; 1% goes to the owner. Other eligible earned revenue uses the same existing rule. A funded round divides its pool by each contributor’s share of all unallocated verified weight on the network. Work participates once, and a later withdrawal does not re-use that work or change the completed round.
For example, £100 of verified settled net research income funds a £99 contributor pool. 10% of that round’s accepted weight receives a £9.90 allocation before any later withdrawal costs. This illustration is not an earnings prediction. No income leaves work pending; no work leaves funding pending.
Recorded funding totals are accounting receipts, not a live bank balance or a traded asset price. Cash settlement and withdrawal execution still require verified provider connections, reviewed terms and funded end-to-end checks.
BILLING AND WITHDRAWAL POLICY · 2 NOVEMBER 2026
Payment providers and the automation fee
Etheraio’s additional withdrawal automation fee is 0.5% of the gross amount requested, capped at £1, on top of the separately disclosed provider withdrawal cost. The fee includes any applicable tax and rounds to the nearest penny; half a penny rounds up. The preview shows one combined fee and the net payment, with an expandable breakdown of Stripe costs and the capped Etheraio fee. Both come from the same funded gross earnings amount; no new purchase is required to withdraw. No automation fee is earned on a failed withdrawal.
100% of the net automation fee, after applicable tax, returns to the contributor pool. It is recorded only after a successful payout is confirmed and is funded into the next eligible allocation once. It is not subject to an additional 1% owner deduction. The network-income rule remains 99% of settled net income for contributors and 1% for the owner. A provider fee already deducted from research income is not charged again as a withdrawal fee.
For example, a £100 withdrawal with a separately quoted £0.35 provider cost has a £0.50 automation fee and pays the user £99.15. The £0.35 is an illustration, not a provider rate or a promise of the lowest fee. The quote must use the account’s checked pricing, including any disclosed account costs, currency conversion and limits. Provider costs differ by account, route, country and payout method.
Stripe, PayPal and Square
Stripe Connect uses recipient accounts with provider-hosted identity and bank verification. Etheraio collects customer payments and controls allocation timing; it remains responsible for its Stripe payment obligations, refunds, disputes and applicable negative balances. A normal Stripe merchant payout is not a transfer to an arbitrary contributor.
PayPal checkout and PayPal Business Payouts are separate capabilities. Payouts requires PayPal approval and a funded PayPal balance. PayPal charges its sender; any agreed reimbursement deducted from a contributor’s allocation must be clearly shown in the withdrawal quote. Do not describe that as a fee charged directly by PayPal to its recipient. Square can accept merchant payments; its Payouts API reports merchant bank settlements and is not enabled here as a third-party contributor withdrawal route.
Capped combined transaction fee
AI purchases and contributor withdrawals show one combined fee, deducted from the same transaction funds: actual provider costs plus Etheraio’s 0.5% automation fee, capped at £1 for the Etheraio component. No fixed 5p is added. Provider costs are outside the £1 cap. The breakdown remains available before confirmation and on the receipt. Customer purchase totals include payment processing; no card-specific surcharge or automatic bank topup is used. Historical receipts retain their accepted policy. Purchase automation fees remain reserved against tax and refunds before they can fund contributor allocations.
AI Credits and token billing
Purchased AI Credits are a separate, non-transferable usage balance, separate from contributor cash. £1 of verified settled funds after applicable tax and actual purchase-processing costs creates 1 AI Credit under the proposed purchase policy. Unused customer credit balances are not research proceeds and cannot fund contributor withdrawals. No payment-method surcharge is added to consumer card or PayPal checkout. Purchase pricing and fee treatment must pass the applicable consumer and provider review before activation.
The proposed standard token tariff is 50% of GPT-6.1 Sol’s published standard API price checked on 2 November 2026: USD1 per million input tokens and USD5 per million output tokens, compared with USD2 and USD10. A checked GBP conversion and the resulting AI Credit price must be displayed and retained with each request. This compares API token prices, not ChatGPT subscription allowances or output quality. It does not mean Etheraio runs the OpenAI model.
A trusted server reserves a bounded maximum cost before assigning work and charges only accepted usage receipts. Failed requests return their reserved credits once. Signed miner reports alone cannot change money balances. Provider events and settlements are rechecked, identified uniquely and reconciled; a checkout return URL is not proof of payment.
Mine payment validation
The protected Mine payment worker verifies the private receipt chain, exact amounts, accepted fees and unique provider references for purchases and withdrawals. AI suggestions and participant reports cannot mark a bank payment as complete. Payment keys and bank details remain outside mining devices. Stripe must confirm actual settlement or payout; the linked receipt history is not independent blockchain consensus.
The owner can reconcile recorded contributor funding with the actual Stripe payments balance and the separate Financial account. Customer prepaid balances, tax reserves and pending payment commitments are protected. Financial account funds are not counted as revenue and cannot cover a Connect payout until a separately checked transfer makes them available. No automatic bank topup is started.
Automation and payment security
Automatic withdrawals are opt-in, with a saved recipient, minimum balance and maximum total fee. Only funded allocated earnings may be paid. The protected coordinator performs payment requests; mining devices may supply checked work and reconciliation evidence but receive no payment keys, card numbers or bank details. An uncertain or timed-out payout keeps its funds reserved until the provider outcome is checked, preventing a retry from paying twice.
Card, bank and identity details are entered in the provider’s secure interface. Etheraio stores the provider reference and the minimum receipt and status information needed for accounting. Financial records are durable, access-controlled records; they are not deleted as temporary mining files. Recent authentication is required for financial settings and withdrawal authorisation.
Current activation state
Availability is reported by the current checks on the Billing page. Stripe Checkout requires its protected connection, signed callbacks, reviewed purchase terms, active tax registration and a tested online AI service. Contributor payouts additionally require reviewed contribution terms, provider-verified recipients, current fee and tax settings, a successful payout test and funded allocations. Treasury funding uses a separate checked connection. Unused prepaid AI Credits and unsold research cannot fund a withdrawal. Nothing in this whitepaper establishes an FCA exemption or an independently reviewed legal right to revenue.
References: Stripe Connect · PayPal Payouts fees · Square Payouts API · OpenAI API pricing · Billing and withdrawal controls.
AI tool connections
Etheraio offers separately authorized external MCP connectors at AI plugins. Each user connects their own provider account. Provider plans, charges and permissions are separate. Every tool action requires review of its provider and exact arguments; reads can also disclose data to the provider. External outputs are untrusted and excluded from shared mine training by default. Plugin credentials are protected per account and never supplied to inference workers. Private owner research is not attached automatically. Money movement and credential access use dedicated reviewed workflows, rather than arbitrary AI tools. Connecting a Stripe plugin does not enable Etheraio checkout, Treasury funding or bank withdrawals.
Owner-share withdrawals
The recorded owner share is 1% of eligible verified settled net business income. The owner can request withdrawal of available owner earnings with no Etheraio automation fee. Provider charges are deducted from the same owner funds. This does not permit withdrawal of the contributor pool, customer prepayments, tax reserves or unavailable Financial account funds. Existing provider checks and bank timing apply.
DIGIDASH NETWORK AUTOMATION · PREPARED UPDATE
DigiDash Broadband Share and DigiDash Grid
DigiDash Broadband Share is the authorised upstream-sharing service. DigiDash Grid is the paired hub network for approved public local services. Its first desktop adapter serves a public guide over an existing local link, using HTTPS and signed peer identities. A radio interface, driver, antenna placement and measured end-to-end path determine reach and usable speed. Installing software alone does not extend radio coverage.
The public hub’s payload cache is bounded in RAM and expires after five seconds. A small encrypted identity and selected configuration persist for reconnecting. Account records, payment obligations, accepted contributions and private research require their own durable protected storage.
DigiDash Network Units (DNU) represent independently accepted network payload delivery: one DNU per GiB. Idle time, speed tests and retries create no units. DNU are contribution measurements, separate from purchased sector credits and funded cash allocations. The first hub adapter’s local counters do not issue DNU or cash; an independently checked delivery-and-accounting connection is required.
Only fresh, checked service offers may reserve customers against a shared physical-device budget after primary AI use. New limits or removed roles are rechecked before admission. Service interruption closes the reservation and returns unused credits to that same sector. Offline hub networking cannot confirm a Stripe payment or make a bank withdrawal.
Protected sales and account automation
Sales, customer-credit funding, cash allocation and payout automation use authenticated provider callbacks and the protected ledger. Mining devices can receive only their permitted public tasks and scoped service evidence. Password hashes, verification and reset secrets, email-provider credentials, bank details and payment signing keys are excluded from public hub replication. Accounts and financial state remain with protected services.
Prepaid credit returns
Future purchases made under the disclosed 7 November 2026 credit policy have no voluntary cash redemption. Failed AI requests and undelivered prepaid service restore eligible unused credits to that same product balance. Statutory refunds, provider disputes and the terms accepted for earlier purchases remain preserved; a legally due cash refund is not forcibly replaced with credits.
These components are prepared in source. Public broadband, internet gateways, game-server offers and contributor withdrawals remain subject to actual service capacity, provider readiness and their own release checks.
