Sign offline
A full public-key address signs a portable instruction locally with Ed25519. A valid signature establishes which key authorized the bytes; it does not establish funds or settlement.
ECHO PAY · NEARBY
Echo Nearby
Internet optional.
A protocol people can carry. A decision only you make.
Echo Nearby is an open protocol in development. The signed object can travel by QR, file or copied packet, and anyone with a compatible verifier can check its signature. Apps are optional clients. Start here with test credits; no settlement service is connected.
$MME · MONEY MUSK ECHO
Our planned official token. Target launch: November 11, 2026. This is a plan, not a live token announcement. No verified mint or contract address is published here yet. A name or ticker alone does not identify the authentic token.
Echo Nearby currently uses test credits, not $MME. These demonstrations do not transfer real value, promise redemption or establish a conversion rate. Token creation alone will not enable payments: a separately reviewed settlement integration is still required.
YOUR INTENT · YOUR SIGNATURE
Use Echo Nearby here
Request, authorize and compare signed test intents on this page. Every valid intent remains Pending Sync.
Export your signed objects before switching tools. Switching discards the temporary signing key and unfinished work.
Loading the local tools. You can also open the standalone view below.
For offline reload, open the standalone tools on each device and choose Prepare offline copy before disconnecting. This surrounding website is not cached by that step. Protocol controls currently use English.
Open rules. Independent verification.
The payment intent and its rules outlive any one app. The public specification, independent TypeScript and Rust verifiers, and hostile test vectors let others build compatible clients. Signing proves which key authorized the bytes. Identity, authority and settlement need their own evidence.
Optional native companion
Native Bluetooth reference app · physical-device validation pending
The web protocol tools above need no App Store installation. This separate iPhone reference explores direct Bluetooth permission exchange. It requires Xcode signing and installation on both phones; it does not yet exchange the portable payment intents above.
Get the iPhone companion sourceExplore the original local-balance demo
This separate demonstration uses simulated discovery, local test balances and its own signed format. Its authority cap and publication log are not connected to the portable intents above. Opening it initializes its older local demo state.
How a nearby payment travels
Queue with a cryptographic id
The new protocol derives its payment ID from the complete canonical intent. Retained and exported objects stay Pending Sync. Their signatures make changes detectable.
Carry the same signed object
The reference client displays QR codes and accepts QR images, exported files and copied packets. Load and prepare the verifier before going offline. Scanning never approves a payment.
Confirm through an authoritative rail
A future settlement adapter must independently check funds, authority, expiry and conflicting spends. This draft has no settlement connection; every verified intent remains pending.
Four questions, online or off
Inspect the signed evidence and keep its limits visible before relying on an intent.
Who signed it?
The full signing key. Confirm who controls that key separately.
Who receives it?
The full signed recipient key, compared with an independently confirmed address.
When was it made?
The payer's claimed issue time. A signature does not make the device clock trustworthy.
Is it finalized?
The portable protocol tools always say Pending Sync. A disconnected submission may have an unknown outcome; only authoritative evidence can resolve it.
Why offline changes everything
Three pillars of sovereignty
The internet can disappear. Networks fail, banks go offline, servers go down. But your identity, your signature, and your device are still with you. That is the whole idea — the network only synchronizes a reality you already own.
I am my Echo ID.
Not a phone number, not a bank account, not an email. A key only you hold.
I sign my own payments.
Not a server, not a bank, not an API. Your device authorizes value — no one else can.
The network helps. It doesn't control.
If the internet exists, great. If it doesn't, life continues. Reality reconciles later.
People own their identity. People authorize their value. Networks only synchronize reality.
Honest sharp edges
Offline means pending, never settled
An offline payment is a signed promise, not a finalized transfer. Echo Nearby never claims otherwise — the status stays Pending Sync until the ledger confirms it. Real settlement guarantees come at sync time, not before.
Global double-spend protection needs a real ledger
Disconnected devices cannot know all competing spends. A chosen ledger must serialize valid admissions atomically. Payer-supplied timestamps cannot decide priority. The existing browser balances are a local simulation.
Transport support must be demonstrated
QR and file transfer are implemented in the new client. NFC and local-network adapters are future work. The separate native Bluetooth permission companion still needs physical-device validation.
Balances are demo Echo Credits
These are test credits, not money. Connecting a payment rail requires a separately reviewed settlement, custody, recovery and conflict-handling design.
Keep evidence; distinguish publication from settlement
The new client retains signed public intents locally and keeps temporary test keys only in memory. Its packets are readable by carriers. The older demo publication log is unverified; a hash and amount do not prove settlement.