75.41M
x402 transactions / 30 days
Activity reported by the official x402 site when reviewed on 27 July 2026; dynamic data.
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.
SwissTokint
07
Open risk infrastructure
Research · governance · community
The research problem
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
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
Activity reported by the official x402 site when reviewed on 27 July 2026; dynamic data.
22,000
An observable base for an initial model, not a SwissTokint customer count.
3 registries
Identity, reputation and validation; verifier incentives remain protocol-specific.
4.20 / 5
Top internal score versus bot access, signal marketplaces and distributed compute.
Proposed architecture
01
The producer publishes a hash of a rule, its parameters, data policy and versioned code or document.
02
A test, simulation or strategy event produces a time-stamped receipt tied to the committed version, without publishing secrets or accounts.
03
An independent reviewer can sign a bounded conclusion: format consistency, partial reproducibility or observed limitations.
04
An application or person reconstructs the chain and checks commitments without relying on a proprietary dashboard.
Assurance levels
L0
The signer issued this receipt at a given time.
Does not guarantee that its content is true.
L1
The receipt existed before anchoring and has not changed.
Does not assess method quality.
L2
A third party reviewed a published, bounded claim.
Does not predict future performance.
L3
Replay, a TEE or a ZK proof verifies a specific property.
Does not remove every operational risk.
Privacy by design
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
Two-instrument economy
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.
Stablecoin / conventional payment
Readable pricing and simple access.
Stablecoin
Compensation for measurable service.
SWTK bond
Sybil cost and portable accountability.
SWTK bond
Limit spam and expose provable faults.
SWTK token · in development
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
A live service, external users and a measurable reason why a transferable asset improves security or access.
02
No dividend, revenue share, buyback expectation or value promise. The token cannot become an investment substitute.
03
Association votes remain one eligible member, one vote. Token ownership does not create power over the association.
04
Jurisdiction-by-jurisdiction legal opinion, AML/sanctions analysis, contract audit, conflict policy and complete risk documentation.
Target specification v0.3
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.
Receipt protocol, SDKs and bond mechanics are under development.
Locked to accept a mandate, publish a claim or open a challenge.
Designed for compatibility with EAS, ERC-8004, EIP-712 and ERC-1271.
Modelling cap with no discretionary mint function after deployment.
API access does not force token purchases and remains priced in a stable unit.
Up to 100,000,000 SWTK reserved for public participants under terms still subject to approval.
Indicative soft and hard caps, with a CHF 2M central target; no price or funds accepted before compliant documentation.
No date, contract address or subscription before security and legal approval.
Economic lifecycle
01
A request states the expected evidence, deadline, assurance level and minimum bond.
02
The reviewer or claimant locks SWTK in a non-custodial vault for the mandate duration.
03
The work produces a signed attestation describing exactly what was reviewed and its limits.
04
A challenger may submit contradictory evidence with a separate bond to limit spam.
05
The bond is returned, rewarded or penalised after documented fault findings and an appeal process.
Provisional distribution model
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%
Declining programme over 10 years
17%
Verifiable milestones over 8 years
15%
8 years with a 24-month initial delay
12%
4 years with a 12-month cliff
8%
Contribution proofs and anti-Sybil controls
10%
10% at launch, then 90% linearly over 18 months
Risks and controls
Swiss and target-market legal opinions, AML/sanctions, tax analysis and separate disclosure before any offer.
Tests, fuzzing, external audit, multisignature, timelock, bond caps and a documented pause procedure.
Tiered bonds, portable reputation, declared conflicts, reviewer diversity and mandate rotation.
Challenger bond, bounded windows, standardised evidence, reasoned outcomes and appeal.
Stablecoin-priced fees, mandate bond caps and no price or return promise.
Sensitive data offchain, salted commitments, minimum disclosure and metadata review.
Launch roadmap
0–3 months
A reproducible local proof with no sensitive data.
3–6 months
50,000 receipts and published costs.
6–9 months
100 reviews and ten synthetic disputes.
9–12 months
Measurable service, legal classification, regulatory whitepaper and sale terms.
12–15 months
Issuing entity, KYC/AML, geographic restrictions, safeguarded funds and documented soft cap.
15–18 months
Five reviewers, dispute exercises and a public audit report.
18–24 months
Legal, security, governance, contracts and launch disclosures approved.
Standards to evaluate
An open-source, tokenless infrastructure for onchain or offchain attestations; a candidate for registry interoperability.
An emerging standard for agent identity, reputation and validation requests.
An HTTP-native payment protocol for services and agents; a candidate for stablecoin fees.
An open protocol for opaque agents to collaborate without exposing internal state.
A precedent for bonding and slashing nodes and bots that provide security work.
The current open-source core for reproducible risk rules, published under the MIT licence.