Technical whitepaper · v0.3

The trust layer for autonomous financial agents.

Proof of Method connects a versioned method, a risk policy, an execution receipt and an independent attestation. The goal is to prove the process that governed an action without exposing strategy, accounts or keys.

Status: SWTK is in active design and is planned for launch after testnet validation, independent audit and legal review. No token has been issued, no production contract address has been announced and no sale is open.

The research problem

Make a method auditable without exposing the data it needs to protect.

Result tables, alerts and votes are easy to publish but hard to place in context. Proof of Method aims for a chain of verifiable elements: a method version, an input commitment, an outcome, a review and a decision. The registry does not attest that a strategy is profitable; it only makes it possible to verify that a declared process existed at a point in time and was not silently rewritten later.

Market thesis

Agents can already communicate and pay. Their accountability layer is still missing.

A2A and MCP standardise agent interaction, x402 their HTTP payments, and ERC-8004 their identity and validation. SwissTokint targets a narrower gap: method and risk evidence for agents operating in high-consequence financial environments.

75.41M

x402 transactions / 30 days

Activity reported by the official x402 site when reviewed on 27 July 2026; dynamic data.

22,000

x402 sellers / 30 days

An observable base for an initial model, not a SwissTokint customer count.

3 registries

ERC-8004

Identity, reputation and validation; verifier incentives remain protocol-specific.

4.20 / 5

niche score

Top internal score versus bot access, signal marketplaces and distributed compute.

Proposed architecture

Public commitments, private data and independent verification.

  1. 01

    Versioned commitment

    The producer publishes a hash of a rule, its parameters, data policy and versioned code or document.

  2. 02

    Execution receipt

    A test, simulation or strategy event produces a time-stamped receipt tied to the committed version, without publishing secrets or accounts.

  3. 03

    Review attestation

    An independent reviewer can sign a bounded conclusion: format consistency, partial reproducibility or observed limitations.

  4. 04

    Portable verification

    An application or person reconstructs the chain and checks commitments without relying on a proprietary dashboard.

Assurance levels

Each level states exactly what it proves — and what it does not.

L0

Signed receipt

The signer issued this receipt at a given time.

Does not guarantee that its content is true.

L1

Anchored commitment

The receipt existed before anchoring and has not changed.

Does not assess method quality.

L2

Independent attestation

A third party reviewed a published, bounded claim.

Does not predict future performance.

L3

Enhanced assurance

Replay, a TEE or a ZK proof verifies a specific property.

Does not remove every operational risk.

Privacy by design

Prove eligibility or integrity without publishing identity and sensitive detail.

The first version must not store identities, balances, exchange keys or proprietary parameters. Data stays offchain; only hashes and signed attestations may be published. A later research phase will assess zero-knowledge proofs where a member needs to prove voting eligibility without publicly linking a wallet to a vote.

What the protocol does not claim to do

Explicit limits protect both the public and technical credibility.

  • Predict markets or guarantee a strategy’s performance.
  • Hold funds, execute orders for others or automate copy trading.
  • Turn membership activity into a financial right or purchasable influence.
  • Create a new blockchain where interoperable standards can address the need.

Two-instrument economy

Payment stays stable. SWTK secures verifiable work.

A subscription or API call does not need a volatile token. Stablecoins fund services; SWTK is designed as a portable, challengeable bond among independent reviewers, proof producers and challengers.

API, receipts and storage

Stablecoin / conventional payment

Readable pricing and simple access.

Verification work

Stablecoin

Compensation for measurable service.

Verifier identity

SWTK bond

Sybil cost and portable accountability.

Claim or challenge

SWTK bond

Limit spam and expose provable faults.

SWTK token · in development

SWTK is designed as the security bond of the Proof of Method network.

Launching SWTK is part of the SwissTokint roadmap. The token will create economic accountability for reviewers, high-assurance claim producers and challengers. It will not replace stable payments, buy governance rights in the association or promise financial performance.

01

Observable utility

A live service, external users and a measurable reason why a transferable asset improves security or access.

02

No financial right

No dividend, revenue share, buyback expectation or value promise. The token cannot become an investment substitute.

03

Separate governance

Association votes remain one eligible member, one vote. Token ownership does not create power over the association.

04

Controls before distribution

Jurisdiction-by-jurisdiction legal opinion, AML/sanctions analysis, contract audit, conflict policy and complete risk documentation.

Target specification v0.3

A capped, auditable bond asset separated from service fees.

These parameters are the published design model. They will be tested on a valueless network before the production contract is deployed. Every material change will be versioned, justified and announced before launch.

Current phase
Active design

Receipt protocol, SDKs and bond mechanics are under development.

Primary function
Security bond

Locked to accept a mandate, publish a claim or open a challenge.

Target network
EVM L2 to be confirmed

Designed for compatibility with EAS, ERC-8004, EIP-712 and ERC-1271.

Proposed maximum supply
1,000,000,000 SWTK

Modelling cap with no discretionary mint function after deployment.

Service fees
Stablecoins / currency

API access does not force token purchases and remains priced in a stable unit.

Community presale
10% maximum

Up to 100,000,000 SWTK reserved for public participants under terms still subject to approval.

Funding objective
CHF 750k–2.5M

Indicative soft and hard caps, with a CHF 2M central target; no price or funds accepted before compliant documentation.

Public availability
After controls

No date, contract address or subscription before security and legal approval.

Economic lifecycle

Lock, verify, challenge and settle under public rules.

  1. 01

    Bounded mandate

    A request states the expected evidence, deadline, assurance level and minimum bond.

  2. 02

    Bond locked

    The reviewer or claimant locks SWTK in a non-custodial vault for the mandate duration.

  3. 03

    Attestation issued

    The work produces a signed attestation describing exactly what was reviewed and its limits.

  4. 04

    Challenge window

    A challenger may submit contradictory evidence with a separate bond to limit spam.

  5. 05

    Traceable settlement

    The bond is returned, rewarded or penalised after documented fault findings and an appeal process.

Provisional distribution model

A capped supply reserving 10% for structured public participation.

The model below is an economic planning case. The community presale is proposed but not open: price, eligible countries, payment safeguards and exact rights will only be published after legal and security approval.

38%

Network security and verification

Declining programme over 10 years

17%

Ecosystem, pilots and public goods

Verifiable milestones over 8 years

15%

Protocol treasury

8 years with a 24-month initial delay

12%

Initial contributors

4 years with a 12-month cliff

8%

Community and testnet

Contribution proofs and anti-Sybil controls

10%

Public community presale

10% at launch, then 90% linearly over 18 months

Risks and controls

The whitepaper also publishes failure scenarios.

Regulatory classification

Swiss and target-market legal opinions, AML/sanctions, tax analysis and separate disclosure before any offer.

Contract or key failure

Tests, fuzzing, external audit, multisignature, timelock, bond caps and a documented pause procedure.

Collusion or Sybil identities

Tiered bonds, portable reputation, declared conflicts, reviewer diversity and mandate rotation.

Abusive challenges

Challenger bond, bounded windows, standardised evidence, reasoned outcomes and appeal.

Volatility and liquidity

Stablecoin-priced fees, mandate bond caps and no price or return promise.

Data leakage

Sensitive data offchain, salted commitments, minimum disclosure and metadata review.

Launch roadmap

Build the network and its controls before making SWTK transferable.

  1. 0–3 months

    Specification, SDK and verifier

    A reproducible local proof with no sensitive data.

  2. 3–6 months

    Testnet anchoring and three pilot bots

    50,000 receipts and published costs.

  3. 6–9 months

    EAS, ERC-8004 and external reviewers

    100 reviews and ten synthetic disputes.

  4. 9–12 months

    x402 API and regulatory file

    Measurable service, legal classification, regulatory whitepaper and sale terms.

  5. 12–15 months

    Structured community presale

    Issuing entity, KYC/AML, geographic restrictions, safeguarded funds and documented soft cap.

  6. 15–18 months

    SWTK contracts, audit and valueless testnet

    Five reviewers, dispute exercises and a public audit report.

  7. 18–24 months

    Controlled public launch

    Legal, security, governance, contracts and launch disclosures approved.