Protocols
Current protocol and integration layers across Solana, GraphQL, REST, graph storage, and archived lineage interfaces.
This page documents the current protocol layers that matter in the live ƒxyz stack. It intentionally separates:
- current integration surfaces
- storage/query protocols
- historical lineage concepts
Current Protocol Layers
| Layer | Current role |
|---|---|
| Solana Token-2022 | on-chain token and certificate primitives |
| GraphQL | canonical application API |
| REST | task-oriented route families |
| Bolt + Cypher | Neo4j graph transport and query layer |
| SSE / streaming | Fixie and live-response patterns |
Solana Token-2022
Solana Token-2022 underpins:
- Florin
- membership certificate flows
- related on-chain token state
The docs should describe Token-2022 as a core primitive, not as a speculative add-on.
API Protocols
GraphQL
The canonical application endpoint is:
https://api.fxyz.network/api/graphqlGraphQL is used for:
- identity
- onboarding
- network graph
- membership state
- portfolio and other app-linked data surfaces
REST
The task-oriented REST base is:
https://api.fxyz.network/apiIt covers:
- Bridge routes
- Fixie routes
- Solana routes
- documents
- prices / FX / health
Graph Storage Protocols
Neo4j remains the graph store, with:
- Bolt as the transport protocol
- Cypher as the graph query language
These are internal implementation primitives, but they matter when explaining graph-native behavior and tooling.
Historical Lineage
FIX and older bridge/exchange protocol work belongs to the project lineage, not to the current public product surface.
If you are reading this to understand the current stack, prioritize GraphQL, REST, Token-2022, Neo4j, and app-facing streaming. Read FIX and older exchange protocol work as archive lineage.