Trust and compliance

Compliance by architecture.

SILS is designed so the chain holds proofs, not people. Identity checks happen off chain with regulated partners, who keep the records and the legal duty. The chain stores commitments. Regulated institutions get the disclosure the law requires. Everyone else gets a proof.

In development This page describes design intent. It is not legal advice. Controls marked Planned do not exist yet.

Design rules

Seven rules that shape every component.

These rules come from the Revolution Network design SILS builds on.1 SILS adopts them as its own. They are design rules, not certifications.

  1. No personal data on chain."No PII, KYC data, or payment detail on chain. Ever." Identity documents stay with regulated identity partners.
  2. Commitments only.Per identity, the chain holds one facet root, one reputation pointer and per-settlement nullifiers. Commitments are designed so a hash alone links to no one.
  3. Prove, do not store.A merchant checks a proof that a fact holds, such as age.over.21. It never receives the document behind it.
  4. Selective disclosure for auditors.A payer can generate a viewing proof that reveals one specified payment to an auditor, a regulator or an accountant, without revealing the rest.
  5. Three disclosure tiers.Full signed disclosure to regulated relying institutions. Zero-knowledge facets to merchants and other verifiers. Issuer-held records for lawful requests.
  6. Every verification is logged.Method, result, time and issuer are recorded so relying institutions can meet their recordkeeping duties. A yes or no proof alone does not meet those duties, so SILS does not present it as if it did.
  7. Every off-chain service signs its outputs.Each service keeps audit logs with the input hash and policy version, and its keys can be rotated and replaced.
In developmentViewing proofs are in development and follow the SILS Proof beta.

Who is responsible

The legal duty stays with regulated parties.

SILS separates the legal role from the technical role. A regulated party owns customer due diligence, recordkeeping and liability. SILS proves, links and logs.

PartyRoleHolds identity records
Regulated identity partnerPerforms customer due diligence. Keeps records for the required retention period. Answers lawful requests. Revokes credentials.Yes
Relying institutionRuns its own CIP and AML program. Decides whether to accept a SILS credential.Its own
SILSVerification provider. Issues proofs, binds agents to owners, logs every verification.No. Logs only.
MerchantChecks proofs.No
Not a regulated institution.SILS is not a regulated financial institution. An institution that uses SILS credentials keeps responsibility for its own program. Regulated issuers can join the issuer set so reliance can apply where the law permits.

Verification levels

Permissions follow verification.

Every agent traces to a verified parent. The parent's level decides what its agents can do. Verification runs off chain through identity data partners.2

LevelWhat is verifiedWhat it unlocksStatus
L1 BasicEmail and device bound. Uniqueness only. L1 proves a unique human. It is not identity verification.Testing and sandbox agents. No commerce facets.In development
L2 VerifiedGovernment identity checked against data partnershuman.verified, agent creation for commerce, age and jurisdiction facets, standard settlementIn development
L3 EnhancedKYC and AML screening completedAccredited investor facets, settlement linked to tokenized assetsIn development
L3 EntityLegal entity verified with an authorized signatoryMerchant agents, bonded reputation poolsIn development

KYC for people. KYB for businesses. Know Your Agent for agents. Agents are children of a verified parent, have no transfer function, expire unless re-verified and cannot create agents. Credentials expire at the earlier of document expiry or 12 months.

Regulatory posture

Design intent, with the rules it answers to.

Each row states what SILS is designed to do and the rule behind it. SILS Proof hides the payer from the merchant. It does not hide the payer from the regulated party that onboarded them. SILS does not claim its proofs remove any compliance duty.

TopicDesign intentBasis
Sanctions screeningScreen against OFAC lists at onboarding, at funding and at withdrawal. Expose a sanctions.clear facet to counterparties.OFAC guidance for the virtual currency industry, Oct 2021, names KYC, screening and transaction monitoring as controls.5
Travel RuleOriginator and beneficiary data stays with licensed counterparties and is shared under the Travel Rule. SILS is designed with an IVMS101 data hook for VASP to VASP settlement, and proof of control for self-hosted wallets on EU transfers above EUR 1,000.FATF threshold USD or EUR 1,000.6, 7 U.S. threshold $3,000 under 31 CFR 1010.410(f).8 EU Transfer of Funds Regulation from Dec 30, 2024, with no general threshold.9 Self-hosted wallet verification above EUR 1,000 under Regulation (EU) 2023/1113, Art. 14(5) and 16(2).20
Payment stablecoinsSettle in permitted payment stablecoins once the GENIUS Act rules take effect. SILS does not issue a stablecoin or pay yield.GENIUS Act enacted Jul 18, 2025. Effective on the earlier of Jan 18, 2027 or 120 days after final regulations.10, 11
Hashed identifiersKeep linkable hashes off chain. Salts stay off chain and can be deleted.EDPB Guidelines 02/2025: hashes with identifiers can still be personal data. Where erasure cannot be guaranteed, store no personal data on chain.12
SILS ScoreSILS Score is commercial reputation for agents and merchant entities, never the human. It is shown only as a threshold proof. It is not a consumer report and not a credit score. Counsel review precedes release.Revolution Network design scope.4 Definition of consumer report, 15 U.S.C. 1681a.13
Custody and rampsNon-custodial by design. Fiat on and off ramps through licensed providers chosen after legal review.Revolution Network design.1 Regulatory classification of SILS is under review with counsel.14 SILS does not claim to be a regulated institution and does not claim that any institution may rely on it.
Transaction screeningScreen transactions at the payment facilitator and at bridge-in through a blockchain analytics partner. Direct exposure to a sanctioned address blocks. Attenuated exposure is risk-scored and reviewed. Owner screening at onboarding is not transaction screening. PlannedOFAC guidance names transaction monitoring as a control.5
Customer identificationDesigned to fit within a bank's own Customer Identification Program as a verification method that program permits. SILS credentials are not a substitute for that program.31 CFR 1020.220.19 Interagency FAQs on verifiable digital credentials under CIP, Sep 2026.18 Counsel to confirm.
Know Your AgentEvery agent carries a signed, scoped, expiring mandate from an accountable owner. Mandates map to AP2 and other agent payment formats.Revolution Network design.1
EU digital identityAccept EU Digital Identity Wallet credentials as root documents once regulated acceptance applies. PlannedRegulation (EU) 2024/1183 (eIDAS 2).21
Not legal advice.This section describes design intent. Participants are responsible for their own obligations in their own jurisdictions.

Security program

Planned controls. None completed yet.

SILS has not completed any audit and holds no SOC 2 report. These are commitments for the path to mainnet.3

ControlCommitmentStatus
Contract auditsIndependent audit of every contract before mainnetPlanned
Circuit auditsProof circuits audited before activation. Zero-knowledge bug classes are well documented.15Planned
Timelock and multisigPrivileged contracts owned by a timelock controlled by a multisigPlanned
Guardian pauseBounded powers. Pauses expire or leave exits openPlanned
Bug bountyPublic program with severity tiers. Terms to be published16Planned
SOC 2Roadmap toward a Type I report, then Type II17Planned

Responsible disclosure

Report a vulnerability.

If you find a security issue in SILS code, contracts, circuits or services, email the security inbox. Include steps to reproduce and the affected component. Please give SILS reasonable time to fix the issue before public disclosure. Do not access other people's data or disrupt service while testing.

Security inbox

security@sils.solutions

A bug bounty with published terms is planned. Until then, reports are acknowledged but not paid.

Status legend

What each label means.

SILS describes what exists and labels what does not. Today no SILS-specific capability is Live.

LabelMeaning
LiveGenerally available in production with real value.
TestnetRunning on a public test network. No real value. Interfaces may change.
In developmentBeing built. Not available to the public.
SpecifiedDesign written down. Build has not started or is at an early stage.
PlannedIntended. Not yet specified in detail. Timing not committed.

"Design intent" describes how a component is meant to work. It is not a shipped control.

Forward-looking statements

Full notice.

[PENDING COUNSEL] Notice text requires counsel approval before launch.

This website contains forward-looking statements, including statements about product development, any proposed corporate transaction, regulatory plans and market opportunity. These statements are based on current expectations and are subject to risks and uncertainties that could cause actual results to differ materially. Any proposed transaction is subject to definitive agreements and conditions and may not close.

Products and features described as Testnet, In development, Specified or Planned are not commercially available. Descriptions of planned functions do not mean an unfinished feature exists. Market figures are third-party estimates with sources and dates. They do not represent company revenue.

SILS is quoted on the OTC market under the ticker SILS. The company is not currently an SEC reporting company. No national exchange listing, listing date or liquidity is assured.

SILS undertakes no obligation to update forward-looking statements, except as required by law.

Read the full forward-looking statements page.

Nothing on this website is an offer to sell or a solicitation of an offer to buy any security or token.

Sources

  1. Revolution Network Whitepaper v2.0, October 2026, draft for review: §2.1, §5.1, §8.6, §8.9.
  2. Revolution Network Whitepaper v2.0, October 2026, draft for review: §6.2.
  3. Revolution Network Whitepaper v2.0, October 2026, draft for review: §13, §13.3.
  4. Revolution Network Whitepaper v2.0, October 2026, draft for review: §8.8, §13.2.
  5. White & Case, "OFAC Sanctions Compliance Guidance for the Virtual Currency Industry," Oct 2021 (secondary summary of OFAC guidance of Oct 15, 2021). whitecase.com
  6. Sidley Austin, "FATF guidance regarding digital asset exchanges," Jul 2019 (secondary). sidley.com
  7. FATF, "Update to Recommendation 16 on payment transparency," Jun 2025. fatf-gafi.org
  8. 31 CFR 1010.410. ecfr.gov
  9. De Nederlandsche Bank, "Transfer of Funds Regulation (TFR)." dnb.nl
  10. Federal Register, "GENIUS Act Regulations on Payment Stablecoin Issuance, Offer, and Sale," NPRM, Aug 18, 2026. federalregister.gov
  11. Tazapay, "The GENIUS Act One Year On," Jul 20, 2026 (secondary). tazapay.com
  12. EDPB, "Guidelines 02/2025 on processing of personal data through blockchain technologies." edpb.europa.eu. Summary of version 2.0 (secondary). ppc.land
  13. 15 U.S.C. 1681a, Fair Credit Reporting Act definitions. law.cornell.edu
  14. FinCEN, FIN-2019-G001, May 9, 2019. fincen.gov
  15. 0xPARC, "zk-bug-tracker." github.com/0xPARC/zk-bug-tracker
  16. Immunefi, "Vulnerability Severity Classification System v2.3." immunefi.com
  17. AICPA, "SOC 2." aicpa-cima.com
  18. Board of Governors of the Federal Reserve System, SR 26-06, "Frequently Asked Questions Regarding the Treatment of Verifiable Digital Credentials Under the Customer Identification Program Rule," Sep 2026. federalreserve.gov. NCUA, same FAQs. ncua.gov
  19. 31 CFR 1020.220, Customer identification program requirements for banks. ecfr.gov
  20. Regulation (EU) 2023/1113 on information accompanying transfers of funds and certain crypto-assets. eur-lex.europa.eu
  21. Regulation (EU) 2024/1183 amending Regulation (EU) No 910/2014 as regards the European Digital Identity Framework. eur-lex.europa.eu