Sign offline
Your Echo ID signs the payment locally with Ed25519. No network is needed to authorize value — the signature is real the instant it's made.
ECHO PAY · NEARBY
Echo Nearby
Internet optional.
Your money shouldn't wait for a signal.
Pay nearby with your Echo ID even when the network is gone. The payment is signed on the spot, queued on your device, and synced the moment you're back online — with an honest double-spend safeguard, because a promise made offline only becomes a settlement on the ledger.
Standing up the mesh…
How a nearby payment travels
Queue with a cryptographic id
The signed payment is stored on the device with a unique echo_0X_… id and a status of Pending Sync. It cannot be silently altered — the id is derived from the signature itself.
Transfer over the mesh
Nearby, the signed packet hands off to the recipient's Echo, who immediately sees 'Received — pending network confirmation.' Both devices can be fully offline.
Reconcile on the ledger
When either device reconnects, the queue syncs. The ledger is the single arbiter: the first payment a balance can cover finalizes; a later one that would overspend it is rejected.
Four questions, online or off
Every Echo Nearby payment can always answer the same four questions — so you understand exactly where your money stands, even before it reaches the network.
Who signed it?
The payer's Echo ID, backed by a verifiable Ed25519 signature.
Who receives it?
The payee's Echo ID — a public label, never an account number.
When was it made?
The moment it was signed, recorded on the queued payment.
Is it finalized?
Pending Sync, Finalized, or Rejected — never ambiguous.
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.
Double-spend is prevented at sync, first-write-wins
A device offline cannot know a balance was already committed elsewhere. On reconnection the queue reconciles in creation order — the first payment finalizes, and any later payment that would overspend the same balance is rejected with a clear reason.
True Bluetooth peer discovery needs a native app
The Web Bluetooth API is central-only — a browser can talk to a hardware peripheral, but two phones running a website cannot advertise to each other. The 'nearby' discovery here is simulated so the experience is visible; the signing, queue, and sync are all real.
Balances are demo Echo Credits
The value here is demo credits, not money. But the mechanism — ID-addressed, signed offline, reconciled on a ledger — is real, and a live settlement rail swaps in later without touching the offline model.
The queue is yours, the network log is opaque
Your keys, balances, and pending queue live only on this device (Law 1) and survive a reload — nothing is uploaded. When a payment finalizes, only an opaque head crosses to the shared network log: proof a settlement happened and for how much, never who paid whom.