Simple Layer One · Option X

Sovereign Intent Mesh for real-world commerce

Offline-first p2p transactions with zero gas friction, instant local execution, and deterministic EVM finality on Polygon. No chain switching. No RPC management.

View Live EVM Proof Build with Connect

Zero-Chain UX Local mesh execution Linked-Tip notary

Live proof

Polygon Amoy Linked-Tip Notary

Intent Ledger tips are notarized on-chain without making EVM the execution parent. Public Amoy artifacts from ADR-0096 smoke.

Polygon Amoy Testnet Live contract verified

Notary contract: 0x7F78…5346 ↗
Tip sequence: #5
Active state root (tip): 0xb81ac66f4199d517e95980f0b422d0ce69853600f9f549d84b0d17349a1f799f

Anchored sequence proofs

Seq #1 · Genesis anchor 0xb8a635b2… ↗
Seq #2 · Linked tip continuity 0xed949c65… ↗
Seq #3 · Merkle Lab v1 (honest intent root) 0xd3d6f0cb… ↗
Seq #4 · Relayer daemon flush 0x0e9a7679… ↗
Seq #5 · POS SDK E2E 0x1c9de27c… ↗

Deploy tx: 0xde1570a7… ↗ · ADR-0096 · Merkle Lab v1 · Lab cadence N=64 / T=15m · Next live seal via Field Lab (seq=6)

Field Lab · Amoy

Interactive POS terminal

Sign a coffee intent on-device, ingest via Relayer Daemon, anchor the Merkle tip on Polygon Amoy, then clear through the vault notary gate — Intent hash → Batch Root → Polygonscan → Vault Decision.

Checkout Amoy · Slice 2C POS

Coffee intent

$2.50

SKU FIELD-COFFEE · 2_500_000 uunits

Device: —
Relayer: http://127.0.0.1:8787

1. Device Local idle
2. Relayer Ingest idle
3. On-Chain Anchor idle
4. Vault Clearing idle

Live path needs Relayer Daemon (?relayer=). UX walkthrough without chain: ?demo=1 ·

Most apps blur identity, permission, and money into one login button.

SL1 keeps them separate so each step can be checked.

Passkey, not a shared password.

You approve access with the device you already trust. The site learns who you are — not how to impersonate you later.

Permission

Every action has a reason.

Purchases, payouts, and sensitive changes leave a trail: who approved what, for which app, and when.

Wallet

Balances stay with you.

Rewards and receipts on the protocol ledger live here. Crypto and bank balances live in linked providers.

How it works

Three steps apps and people can actually follow.

01 Ask Your app opens SL1 Connect

02 Approve User confirms with a device passkey

03 Return Your app gets a one-time proof

For developers

Built for real integrations, not demo logins.

SL1 Connect uses short authorize links, audience-bound proofs, and a registry of known clients so redirects stay predictable.

Connect Passkey sign-in Identity proof for your domain

Policy Checks before money moves Clear allow / deny decisions

Wallet Portable balances Receipts and rewards in one place

Settlement Recorded state changes Auditable after the fact

SL1 Identity

Who you are — not where your money is custodied.

Your passkey controls this identity. USDC, BTC, and other instruments live in linked providers such as Meanly Vault — not inside the protocol node.

Identity

loading

syncing

reading /api/identity/summary

Protocol SL -- Native SL1 ledger balance on this identity.

Linked providers

none

Checking provider attachments …

Providers own instruments. The protocol only lists what you have linked.

Link Meanly Vault

Passkeys

-- active

Add or rotate passkeys without giving custody to a marketplace.

Protocol activity

0 receipts

Syncing identity history --

For builders

Ship apps and dapps on SL1 Connect — not on our login page.

Connect is a protocol primitive: passkey approval, short authorize links, audience-bound proofs. Run your own issuer, or use the public reference host only while you prototype.

SL1 Connect

Protocol primitive for builders — attach your app via authorize links and audience-bound proofs.

Read Connect spec