THE FEDERATION / WHAT WE'RE BUILDING

A foundation for
finance on-chain.

Bringing finance on-chain takes intelligence, accountable decisions, clear governance, and financial mechanisms people can examine.

These are the foundations of the Federation's work on Solana. Explore the systems, their current stage, and the evidence behind them as the project develops.

For builders & businesses: find your starting point →

THE COMMON FOUNDATION

Research. Specifications. A public record.

Research examines Solana DeFi, market structure, and mechanism design. Published specifications make proposals available for scrutiny. The record and corrections log preserve commitments and changes.

THE WORK, SYSTEM BY SYSTEM

Purpose you can understand.
Progress you can examine.

Account, Alliance and swap status updated .
Other projects retain their own dated evidence; follow each source for its published position.

COMMAND / PUBLIC DASHBOARDLive, read-only

Command Deck

See your public wallet data in one place.

Enter a public Solana wallet address to view supported balances, reference prices and current-mint lock records. Device-local missions sit alongside the dashboard. Address lookup does not prove wallet ownership. The deck does not sign transactions or open staking or lending.

Next documented gate
Existing approved accounts can use email-code sign-in. Public registration and the expanded protected member dashboard remain closed pending acceptance. Google sign-in is deferred.
Open the Command Deck → · Read the data and privacy limits →
COMMUNITY / PROJECT TEAMSPublic introduction · member build in review

Federation Alliance

Bring a project, a challenge or a useful idea.

Explore proposed creative, research and builder formats, prepare a project introduction, and use the private request intake. The community sandbox is a demonstration; it does not create membership, invitations or scores. Public team enrollment and competition entries are not open.

Next documented gate
Complete protected member and owner journeys, verify hosted recovery and routine backups, finish accessibility checks, then review the exact release scope. A project proposal does not approve a match.
Explore the Alliance → · Read challenge briefs and founder steps → · Existing-account sign-in →
TOOLS / SOLANA QUOTESLive quote preview · trading closed

Galactic Swap

Compare SOL, GFOF and native USDC quotes beside Federation tools.

The public preview offers reviewed SOL, GFOF and native USDC pairs on Solana without requiring a wallet. Route availability varies by pair and amount. It does not submit or sign trades, and no Federation referral fee is configured or collected. Quoted costs and minimums are provider-reported, not an executable transaction review.

Next documented gate
Verify referral and recipient accounts, build transaction and fee validation, prove mobile wallet and confirmation behavior, and complete separately approved bounded tests before any trading release.
Open Galactic Swap →
AUTOMATION / REVIEW THE FOUNDATIONSPublic demonstrations

Federation Automation Lab

Try the ideas before live services are proposed.

Explore reviewed hints for fictional missions, synthetic event replay and a declared agent-permission example. These demonstrations do not subscribe to live events, send alerts, verify agent records, enforce permissions or award mission progress. The optional Dossier AI selector is prepared but disabled.

Next documented gate
Prove reader value, authenticated evidence and operating limits before separately authorized live services.
Explore the labelled demonstrations →
OPERATIONS / REVIEWED INVESTIGATIONReleased manual tool

Operations Assistant

Bring site checks and release evidence into one report.

The operator-run report checks the Federation's three public homepages and their Command Deck links, then compares Command and Dossier publication metadata with independently supplied approved revisions. It prioritizes availability investigations and marks stale or missing evidence. Reviewed rules supply the report; no AI model, automatic repair, scheduled monitoring or message is activated. Passing checks do not establish security or sign-in acceptance.

Next documented gate
Review authenticated evidence and an explicit operating scope before proposing scheduled checks or notifications.
Read the released change → · Read the operator guide →
WATCHTOWER / ON-CHAIN OBSERVATIONPilot preparation

Watchtower

Investigate changes with dated evidence and explicit limits.

A controlled observation pilot is being prepared for the current GFOF mint and three published Streamflow lock accounts. Intake and verification components are tested, but live monitoring is not activated. This narrow scope does not cover every holder transfer or trade, and a candidate observation does not prove a sale, ownership change, lock effect or safety. No public alerts are active.

Next documented gate
Complete private setup and a controlled acceptance test before proposing ongoing monitoring.
Explore the labelled event-replay demonstration → · Read the published lock records →
01 / INTELLIGENCEPublic beta

Dossier

Make on-chain intelligence answerable to evidence.

The read-only Token Structure Lens accepts a Solana mint and reports mint controls and up to 20 largest token accounts with source slots and explicit unknowns. Its free plain-language guide highlights missing evidence and partial coverage, with reviewed explanations tied to source fields and slots. No AI model, account or upload is used by the guide. Lens can time out on some mints and does not prove ownership, bundles, sales or safety. Dossier's separate Program 01 convergence alerts are retired and intake is closed. Its measured verdict, original methodology, forecast record and corrections remain public.

Next documented gate
Improve coverage of slower mints and reader comprehension while tracking provider cost. Program 01's measurement outcome is already published.
Try the Solana beta → · Read the Program 01 verdict →
02 / CAPITAL ACCOUNTABILITYPublic experiment

Federation Capital Command

Put the reasoning on record before the outcome.

FCC develops a public protocol for registering, challenging, and scoring consequential capital judgments. Its latest recorded Epoch 2 outcome is SHORTAGE_EVENT. No capital is deployed and no rerun is authorized.

Next documented gate
Complete the recorded prerequisites and obtain a new, separately recorded authorization for a rerun.
Examine the FCC protocol and record →
03 / GOVERNANCEAdvisory deployment

Federation Council

Give holder preferences a public place in the process.

The published governance specification describes an advisory deployment on Realms. Its scope assigns no control over the treasury, repository, website, or token.

Gate before authority expands
A new specification, security review, and recorded authorization.
Read the current governance scope →
04 / LENDING PRODUCTPrivate prototype

Borrower-protective lending

Build a bounded supply-and-borrow market with accountable interest and risk rules.

A private Solana program has completed local synthetic-token tests for supply, borrowing, collected-interest settlement, several supplier withdrawals, and a final exit with one funded supplier. The borrower-protective liquidation design remains unresolved and unimplemented in this program. No public lending market, real-fund route or independent audit is live.

Next documented gate
Prove multi-supplier exits and later deposits, integrate default and loss rules, settle and implement liquidation, then obtain independent security and legal review before any separately authorized public release.
See the build status →

This overview describes the shared vision and published stages. It does not represent an integrated financial service or a commitment to launch dates.

FINANCIAL PRODUCT / BUILD STATUS

Real lending work.
Clear release gates.

Private build snapshot · 24 September 2026
Not a customer-facing market

The Federation is developing a bounded Solana lending program for supplying tokens and borrowing against collateral. The current prototype runs with synthetic tokens in a local validator. This is engineering progress, not a deployed lending service. The code and runtime reports are private, so the results below are self-reported and not yet independently reproducible by visitors.

LOCAL CHECKS PASSED

Supply and draw

Private local flows have moved synthetic tokens into market cash and out to a borrower, with recorded supplier shares, collateral and principal.

TWO LOCAL CYCLES PASSED

Interest and settlement

Two private local cycles collected borrower interest before paying suppliers and reserve, then cleared recorded liabilities. The second settlement used a supplier's reduced share balance after two withdrawals between periods. These are synthetic-token tests, not public lending activity.

BOUNDED FLOWS PASSED

Supplier withdrawals and exit

In one local test, a supplier withdrew all 1.2 million synthetic units of available cash while a loan remained open; repayment and settlement still completed. In another, a supplier withdrew 500,000 and then 250,000 units after payout, followed by a second full settlement. Separately, a market with one funded supplier completed payout and returned its remaining 1 million synthetic units at terminal exit. These are different test paths, not one continuous market history.

OPEN ENGINEERING

Later deposits and multi-supplier exit

Deposits at market creation have been exercised. Deposits after a paid period, withdrawals after the second payout, and a terminal exit with multiple funded suppliers have not passed a complete local flow. The prototype also has a fixed, operator-approved cohort of up to 16 borrowers and 16 suppliers.

OPEN ENGINEERING

Default and loss

Research records a reserve and proportional supplier-loss direction for this bounded prototype. It is not an integrated on-chain default or loss path. A non-paying borrower, reserve exhaustion, supplier claim changes and recoveries still need end-to-end proof.

DESIGN UNDER REVIEW

Liquidation and price data

The published liquidation specification has an unresolved trigger conflict. Oracle failure handling, borrower notification, emergency behavior, partial-fill limits and liquidator economics still need final rules and adversarial tests. No borrower-protective liquidation mechanism is live.

RELEASE GATE

Independent scrutiny and operations

Before any real-fund proposal: complete stressed and failure-case testing, examine reserve economics and operating coverage, obtain independent security and appropriate legal review, build a public interface, and record separate release authorization. No customer deposits or yields are available.

The Lending Lab is an educational simulation. Its example parameters are not live market terms, and using it does not supply, borrow, earn, or hold $GFOF.

BUILDERS · BUSINESSES · RESEARCHERS

Bring your expertise.
Help shape what comes next.

Get to know the Federation as we build. Choose a starting point, examine the work, and bring a specific question to the conversation.

01 / BUILDERS

Review a mechanism

Examine a design assumption, model a failure scenario, or propose a test that could improve the specification.

Start hereBorrower-protective liquidation →Open questions include oracle outages, grace periods, and liquidator incentives.

Prepare a technical review

Use these headings to frame your contribution:

  1. Reference: specification version and section.
  2. Scenario: the conditions or assumptions you are testing.
  3. Finding: expected behavior, failure mode, and supporting calculation or evidence.
  4. Next step: a proposed change or test, including its trade-offs.

02 / BUSINESSES

Bring a real use case

Describe a financial workflow that is difficult today and what moving it on-chain would need to improve.

Start hereCurrent scope and development gates →Use the published stages to frame an exploratory conversation.

Prepare a use-case brief

A useful brief can be just four points:

  1. Workflow: who needs to do what, and where the process breaks down.
  2. Outcome: what a better result would look like and how you would measure it.
  3. Constraints: privacy, permissions, settlement, reporting, or integration needs.
  4. Question: which Federation project relates to the problem and what you want to explore.

03 / RESEARCHERS

Challenge the evidence

Test whether a public claim is supported. Bring a reproducible observation, a counterexample, or a better way to measure it.

Start hereThe Federation's public record →Read the original claim alongside its sources and recorded corrections.

Prepare an evidence review

Make the observation easy for someone else to check:

  1. Claim: quote the relevant passage and link to its source.
  2. Evidence: identify the data, date, method, and limitations.
  3. Result: explain what supports or contradicts the claim.
  4. Reproduction: provide the steps or public references needed to check it.

Start the conversation

Introduce your question in the Federation's public Telegram community. Include the relevant source and a short summary so others can follow your reasoning.

Share only information suitable for a public discussion. These are discussion guides; formal proposals and protocol challenges follow their published procedures.

Open Telegram community ↗

STAY CONNECTED

Follow the work as it develops.

Explore the research, follow the public record, and get to know the thinking behind the Federation.

New to the ideas? Explore First Contact, our interactive introduction to money, choices, and trust.