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.
SwissTokint
08
Open risk infrastructure
Research · governance · community
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
Non-negotiable conditions before public launch.
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
- Primary function
- Security bond
- Target network
- EVM L2 to be confirmed
- Proposed maximum supply
- 1,000,000,000 SWTK
- Service fees
- Stablecoins / currency
- Community presale
- 10% maximum
- Funding objective
- CHF 750k–2.5M
- Public availability
- After controls
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
Lock, verify, challenge and settle under public rules.
01
Bounded mandate
A request states the expected evidence, deadline, assurance level and minimum bond.
02
Bond locked
The reviewer or claimant locks SWTK in a non-custodial vault for the mandate duration.
03
Attestation issued
The work produces a signed attestation describing exactly what was reviewed and its limits.
04
Challenge window
A challenger may submit contradictory evidence with a separate bond to limit spam.
05
Traceable settlement
The bond is returned, rewarded or penalised after documented fault findings and an appeal process.
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.
Launch roadmap
Build the network and its controls before making SWTK transferable.
0–3 months
01Specification, SDK and verifier
A reproducible local proof with no sensitive data.
3–6 months
02Testnet anchoring and three pilot bots
50,000 receipts and published costs.
6–9 months
03EAS, ERC-8004 and external reviewers
100 reviews and ten synthetic disputes.
9–12 months
04x402 API and regulatory file
Measurable service, legal classification, regulatory whitepaper and sale terms.
12–15 months
05Structured community presale
Issuing entity, KYC/AML, geographic restrictions, safeguarded funds and documented soft cap.
15–18 months
06SWTK contracts, audit and valueless testnet
Five reviewers, dispute exercises and a public audit report.
18–24 months
07Controlled public launch
Legal, security, governance, contracts and launch disclosures approved.
Technical whitepaper · v0.3
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.