What Aura OmniMesh is
Aura OmniMesh is a protocol and a free app for direct exchange between people who are physically near each other. Each device publishes short signed intents — an offer (“I teach guitar”) or a need (“I need help moving”) — and a small AI model running on the phone itself matches them into closed rings of three to seven participants.
Everything a marketplace normally needs a company for — identity, matching, trust, history — is done by the devices themselves, cryptographically. The result is an exchange network that keeps working where money, banks, or the internet do not.
Why it exists
Direct barter usually fails for a mathematical reason: the person who has what you need rarely needs what you have. Economists call it the double coincidence of wants. Rings solve it: A teaches B, B lends to C, C supplies A — the loop closes even though no pair matches directly.
The second reason is independence. Every existing marketplace runs on servers and accounts — a company that can go offline, censor listings, raise fees, or harvest data. OmniMesh removes the middleman as an architectural fact, not as a promise: there is simply no server to trust, subpoena, or shut down.
How it works
- Identity is a key, not an account.On first launch the device generates an Ed25519 keypair. The private key never leaves the device. No registration, no e-mail, no phone number — your key is your identity.
- Intents are signed text.You publish offers and needs as short sentences. A multilingual language model running on the phone converts each one into a semantic vector, so matching works across languages.
- Devices gossip a shared log.Nearby phones exchange signed operation logs over Bluetooth LE, Wi-Fi Direct, or a shared local network. The log is a CRDT: order-independent and partition-tolerant, so every device converges to the same state without a coordinator.
- Everything is verified, nothing is assumed.Each operation is checked: signature, authorship, protocol rules. A valid signature under the wrong key is still rejected — only an intent’s owner can change its status. Reputation is never accepted from the network; each device recomputes it locally from signed completed exchanges.
- A matcher searches for closed loops.The device scans the local graph of offers and needs for rings of 3–7 participants. The search is deterministic: the same data produces the same rings on every phone.
- The ring locks, people exchange, history is signed.Each participant locks their step; when all steps are locked the ring is confirmed. People meet, exchange, and mark fulfilment. Every stage is a signed operation — withdrawing visibly breaks the ring for everyone.
What it solves
- Exchange when money is weak or absent — inflation, cash shortages, unbanked communities.
- Marketplaces without fees, accounts, or servers — nothing to pay, nobody to register with.
- Working fully offline — disasters, blackouts, remote areas, festivals, ships, camps.
- Privacy by construction — nothing leaves the device except what you explicitly publish to nearby peers.
- Multilateral matching — the loops that two-person barter mathematically cannot close.
Who it is for
- Neighbourhoods, villages, and mutual-aid networks that want a local exchange board with no operator.
- Coworkings, campuses, conferences, and festivals — dense rooms full of complementary skills.
- Communities in disaster or blackout zones, where independence from infrastructure is the point.
- People who refuse to hand a company their trade history in exchange for a matching service.
- Researchers and developers of peer-to-peer systems — the protocol and code are open on GitHub.
Design principles
- Local-first. Your data lives in an embedded database on your device. The signed log is the source of truth; deleting the app deletes the data.
- Zero collection. No analytics, no telemetry, no accounts. There is no company backend to send anything to.
- Fail-closed. Whatever cannot be verified is rejected — never guessed, never assumed.
- Determinism. Every device computes identical matches from identical data; correctness does not depend on who runs the code.
- Honesty about limits. The protocol documents what it does not do, in plain language, below.
What it is not
- Not a payment system: no tokens, no balances, no custody. Version 1 is pure barter of goods, services, and time.
- Not global: range is bounded by radio and local networks. It is a neighbourhood-scale network by design.
- Not Sybil-proof: anyone can create a key. Reputation is earned from completed rings, never granted.
- iOS and Android do not pair directly over the air (platform APIs differ); cross-OS traffic goes through a local network bridge.
Frequently asked
Is it free?
Yes — free and open source, with no ads and nothing sold. There are no servers to fund, so there is nothing to monetise.
Which languages does matching understand?
The on-device model is multilingual: an offer written in one language can match a need written in another. English and Russian are validated today; the model family covers dozens of languages.
Can I build something else on the protocol?
Yes. The layers — transport, signed CRDT log, semantic matcher — are separable, and the source code is public on GitHub under the project repository.