Exchange Ave

The engine
behind every
network

Five systems that every Exchange Ave network inherits on day one. Together they make nodes interoperable without making them identical — a community brings its own culture, rules, and language and the engine handles the rest.

MEMBER SURFACE ea.exchange · node interfaces · partner clients ENGINE SYSTEMS SYS 01 Identity SovID · credentials attestation · standing SYS 02 Offers goods · skills · time ʻike · availability SYS 03 Geography ahupuaʻa zones proximity matching SYS 04 Ledger logged exchanges verification · audit SYS 05 Reciprocity tokens · recognition unlocks · benefits GOVERNANCE NODE GOVERNANCE · LOCAL RULES · DATA HELD IN PLACE each network configures categories, limits, tokens, and visibility for itself

Scroll sideways to see the whole diagram

The five systems

01

Identity & profile management

A person's standing in the network belongs to them, travels with them, and is vouched for by people who actually know them.

  • · Self-sovereign identity (DID / SovID)
  • · Verifiable credentials for skills and roles
  • · Community attestation rather than platform scoring
  • · Reputation history that survives leaving a node
  • · Tiered visibility on every field
02

Offer & inventory builder

Anything a community can circulate can be listed — including the things marketplaces have no field for.

  • · Goods, services, skills, time, teaching, land access
  • · Categories defined per network, in its own language
  • · Quantity, seasonality, and availability windows
  • · Photos, audio, and moʻolelo attached to an offer
  • · Needs posted as first-class listings, not afterthoughts
03

Geographic offer listing

Circulation stays close to home before it travels. Discovery is shaped by place, not by a bidding system.

  • · Location-aware discovery within ahupuaʻa-shaped zones
  • · Distance-based matching with local-first ranking
  • · Regional rollup for island, city, and nation views
  • · Corridor routing when two networks open a trade route
  • · Precise location never exposed without consent
04

Tokenized exchange logger

Every completed exchange leaves a record the community can inspect. This is what makes reciprocity legible at scale.

  • · Tamper-evident transaction ledger
  • · Two-sided confirmation before an exchange closes
  • · Network-specific tokens and units of account
  • · Full audit trail for stewards and funders
  • · Aggregate figures publishable, records held locally
05

Reciprocity & incentive system

Recognition tuned by each network, so the behaviour it rewards is the behaviour that community actually values.

  • · Activity-based recognition and standing
  • · Milestone unlocks for deeper participation
  • · Community benefits funded by circulation, not fees
  • · Steward tooling for setting and adjusting weights
  • · No leaderboards by default — reciprocity, not competition

Interoperability contract

The five systems expose the same contracts to every client. That is the whole reason a Puerto Rico node and a Hawaiʻi node can trade without either adopting the other's interface.

See the ecosystem map

What a member
actually does

What a member actually experiences, and which system is carrying each step.

STEP 01

Establish identity

Join through a network that already knows you, or apply and be attested by members. Runs on SYS 01.

STEP 02

Name what you have and what you need

List surplus, skills, hours, and equipment. Post the needs too — a need is an offer to receive. Runs on SYS 02.

STEP 03

Discover locally

See what is moving in your zone first, then your region, then any corridor your network has opened. Runs on SYS 03.

STEP 04

Exchange and log it

Agree terms, meet, complete. Both sides confirm and the exchange enters the ledger. Runs on SYS 04.

STEP 05

Standing grows, access opens

Consistent reciprocity opens deeper participation — stewardship roles, larger exchanges, corridor access. Runs on SYS 05.

Hands packing a care parcel on a kitchen table: a cardboard box lined with newspaper holding dried fish, paʻakai, seed packets and a handwritten note
A corridor in practice — surplus travelling to someone who left
Take the app tour Open the app

Running your
own node

Most networks run on the app and never touch the engine directly. Nations and organisations with their own stack can implement the contracts instead and federate as a peer.

The engine is the standard; the app is one implementation of it. If your community already has identity infrastructure, land records, or a member registry, those become the source of truth for the systems they cover and the engine fills in the rest.

Talk to us about federating