Applications

The protocol's first proof is a business.

A coalition rewards application runs today for malls, districts, business parks, airports and campuses — in points and local currency, on the payment rails each market already uses. The protocol makes what it proved portable.

Deployment is compliance-led: region by region, framework-first.

One strategy, two speeds.

One strategy, two speeds. The application runs wherever an operator does — the United States, Europe, the Middle East, Asia — in points and local currency, on the payment rails each market already uses, under each market's existing rules. The protocol activates region by region, as frameworks for digital settlement are ready. Where a framework is still forming, the application operates and the protocol follows it.

The applicationPoints and local currencyPayment railsExisting rulesOperating todayThe protocolFramework readyRegion activatedCoalition settles on-chainPortable.
The application
  1. Points and local currency
  2. Payment rails
  3. Existing rules
  4. Operating today
The protocol
  1. Framework ready
  2. Region activated
  3. Coalition settles on-chain

Both lanes converge on one outcome: Portable.

Earn. Back. Settle.

Earn

A qualifying purchase, shift, visit or action is validated by the operator. The commitment is recorded with its coalition, its source, the oracle price at that moment and a unique receipt hash; once written, the amount cannot be reduced.

Back

The issuing coalition's obligations are counted against stablecoin it holds in escrow. A health factor is recalculated on every change: issue at 1.5×, warning at 1.1×, settlement paused below 1.0×, insurance fund below 0.8×.

Settle

Conversion batches settle against that escrow, inside that coalition. Cross-coalition redemption is explicit and fee-bearing. Regional settlement can pause one region while others continue.

The same three steps the application performs today on its own ledger, made portable.

One program for a whole place.

Malls and town centres

purchases, visits, events · receipt, card, presence

Business parks and districts

tenant-staff arrivals, purchases, participation · employer record, card, address

Airports

purchases, parking, lounge use · boarding pass, receipt, card

Hotels and campuses

stays, dining, attendance · property system, campus card

Employers

wellness, tenure, training, commuting · payroll system, attestation

Transit and civic

rides, recycling, participation · tap, sensor, address

Events earn. Standing defines who. Everything else is configuration.

Reference application

The application that proved it.

A coalition rewards platform for malls, districts, business parks, airports and campuses. It operates today in points and local currency and is the protocol's first and reference application.

  • Operating today
  • Points and local currency
  • Existing payment rails
Visit the application →

Everything a builder needs.

  1. STEP 1

    Read the interfaces

    Versioned ABIs and the published interface set, per release.

  2. STEP 2

    Deploy against the testnet

    The Polygon Amoy registry and reference deployment scripts.

  3. STEP 3

    Register a coalition

    When the framework in your region is ready.

Versioned ABIs

For every layer, published per release.

Interface set

The published contract interfaces the layers expose.

Testnet registry

Deployed addresses for Polygon Amoy.

Deployment scripts

Reference scripts for Polygon Amoy.

Built for the people who run places — and the people who build for them.

Operators of places

Malls, districts, airports, campuses, employers.

Loyalty and rewards software companies

Run your product on a settlement layer you don't have to own.

Payment and fintech platforms

Settle rewards beside the payments you already move.

Coalition anchors

Fund the escrow, set the rules, invite the participants.

Any operator, in any market, can build on what we proved.