Governance and transparency

THOR coordinates buyer requirements and commercial delivery alongside a contributor network. Accountability means making both delivery decisions and the use of funds inspectable, while protecting customer material.

Operating responsibilities

Commercial responsibility, production, verification and network administration are distinct roles. Buyer agreements need to identify the contracting entity and its delivery obligations; contributor guidance needs to identify who assigns work, reviews it and resolves disputes.

What THOR is explains the group's intended scope.

Rules and changes

Contributors should know which task specification and acceptance criteria apply to their work, who can change the rules and how a disputed judgement is reviewed.

Participation explains qualification and whitelist review. From brief to delivery explains the terms published before work starts. Changes should preserve a clear record of the requirements under which work was assigned.

Financial transparency

The confirmed emissions-funding plan uses a disclosed multisig. Its dashboard will publish:

• Wallet configuration: the wallet address, signers' public addresses and signing threshold.
• Funding and balance: emissions received and the current balance.
• Spending: every outgoing transaction.

The revenue dashboard also describes the contract reserve and confirmed customer-funded SN112 alpha buyback policy. Reporting should distinguish intended allocations from completed transactions and reconcile transfers without counting them as new revenue. Economics explains the purpose of each flow.

Evidence without exposing customer data

THOR will publish task descriptions, eligibility rules, budgets and progress, with evidence connecting each miner payment to completed, evaluated work. Sensitive source data and submissions remain restricted to authorised participants.

Data rights and access explains the permissions boundary, including authorised sample review. Delivery evidence and project-specific access permissions support accountability while protecting customer material.

Payment records and duplicate protection

Track the unit's quality result, the buyer's acceptance decision and its payment record separately. An earned reward, an approved transfer and a confirmed on-chain transfer are distinct states. Their records let reviewers reconcile each payment with evaluated work and prevent duplicate payouts.

Unit and submission hashes identify repeated content. Repeated submissions receive no additional payout, and a correction replaces the prior submission. Content identified as an unauthorised copy is flagged and excluded from payout. Commissioned cross-checks are separate, budgeted assignments: qualifying workers can each earn payment while the buyer receives one delivered record for the source unit.

Worker earnings remain attached to the worker account through operator UID changes. Public reporting can show the relevant delivery and payment evidence while private review uses the authorised source material.

Neutrality and disclosure

Relevant ownership interests, commercial relationships and conflicts should be disclosed. Openness should help participants inspect who sets the rules, who can access data and who benefits from decisions.

Operating details

The multisig model and disclosure commitments are confirmed plans. Published wallet configuration and transaction records establish implementation status. The following details are not specified here:

• Decision-makers: the contracting entity and authorities for admission, removal, scoring changes and validator administration.
• Wallet authority: actual signer addresses, the threshold value, spending permissions and reserve limits.
• Buyback policy: allocation rules, execution arrangements and control or use of purchased alpha.
• Reporting ownership: who reconciles records, corrects errors and publishes updates, and on what cadence.

The applicable operating policies establish these decision rights, spending permissions and reporting responsibilities.