Abrham Bunaro

Compliance oracle

InternalTeam

An internal Fairway service that answers a compliance question about a participant with a response anyone can verify, because the payload is signed with Ed25519.

The problem

On-chain finance needs compliance signals that a counterparty or a contract can check independently, without trusting whoever relayed them.

How it works

A client asks for a subject's compliance status. The service runs its checks, returns the status with an expiry, and signs the payload with an Ed25519 key.

Whoever receives the response verifies the signature against the service's public key before acting on it.

Request, check, signed response, verification
  1. Client to Compliance oracle: Ask for a subject's compliance status
  2. Compliance oracle: Run the checks
  3. Compliance oracle to Client: Status, expiry and an Ed25519 signature
  4. Client to Verifier: Pass the signed response along
  5. Verifier: Verify the signature with the oracle's public key

What I worked on

  • Contributed to the API endpoints that produce and verify the signed responses.
  • Supported branded wallet configuration and the mobile deep-link callback flow that hands a result back to the app.

Security notes

  • This page is deliberately high level. It contains no endpoints, schemas, customer names or code from the internal repository.
  • A signed response proves who issued it and that it was not altered; the expiry limits how long a stale answer can be replayed.
  • I can go further in conversation, within what Fairway allows.

Where it stands

Internal product work. The closest public code is the attestation and signature routes in the Rayls hackathon prototype listed below.

KYC attestation soulbound token

Next project

ContraClear

Back to all work