Skip to content

Build with us

FOAF is a credit-graph protocol for community-scale mutual credit. The first application built on it, GrowOperative, is in soft launch in Crawford Bay, BC. The protocol's eventual home is Radix Babylon. The architectural picture across the tracks below sits behind one shared mission: building infrastructure for resilient distributed networks that let communities trade real value with each other without depending on fiat exchange.

The project is at the stage where adding the right person changes the rate at which the whole thing happens. We are looking for collaborators who can see the shape of all the tracks, even if they only contribute to one.

What we are building

Three concurrent tracks. Each has its own scope, role profile, and recruiting page.

The Hyperlane bridge

Deploy a warp route between Ethereum and Radix Babylon and bring FOAF onto Radix as a Scrypto resource. Required before anything else on Radix can use FOAF. Smaller in scope than the other two tracks and likely the first to ship.

See Bringing FOAF to Radix.

The Scrypto protocol stack

Staking (vFOAF and rFOAF), RHEO accrual and consumption, threshold-tier governance, treasury. The full on-chain protocol layer that activates in Phase 3. Senior Scrypto work that intentionally exploits Radix's resource model instead of porting Ethereum patterns.

See Building the FOAF protocol stack on Radix.

The peer-to-peer architecture

Move the credit graph from a centralized Rails database to a peer-to-peer model where bilateral state lives between the parties involved. The chain carries anchors, tokens, and governance, not the credit graph itself. The longest-horizon track and the one most important for what FOAF actually is at scale.

See The peer-to-peer architecture.

What is shared across all three

  • Compensation is FOAF allocation with vesting from the 16% team-and-advisors pool. Tokens are the primary compensation. A cash retainer can be part of the package for engagements that need one, but only once the seed round closes.
  • Public attribution in the project's documentation and any released materials.
  • Asynchronous work, reasonable communication cadence, no application form. The first conversation is always a conversation.
  • A working relationship with the Foundation founder. Decisions get made in the same conversation rather than queued behind hierarchy.
  • Continuing involvement welcome but not required. Clean engagements that end when a track ships are fine.

How to start

Each track has its own page describing scope and what's expected. If one fits, reach out via the contact on the Foundation site or through the Radix community channels where this is being discussed. If you read more than one and want to talk about combining roles, that's also fine.