ƒxyzƒxyz Network

Technical Documentation

Deep dive into ƒxyz Network's technical implementation

Technical Documentation

Current Implementation Status

Phase 1: Retroactive Allocation (Active)

Timeline: Q4 2025
Status: In Development

We are currently implementing a retroactive token distribution system for early contributors:

  • Token Type: Normal Solana Token-2022 (public balances)
  • Allocation: 20% of total supply
  • Extensions: NonTransferable + MetadataPointer
  • Distribution: Merkle tree-based claim system
  • Vesting: 6-month cliff, 24-month linear vesting

Mainnet Configuration

All production systems now operate on Solana mainnet-beta:

  • Network: mainnet-beta
  • RPC: Configured via NEXT_PUBLIC_SOLANA_RPC_URL
  • Explorers: Solana Explorer, Solscan
  • Programs: Deployed to mainnet addresses

Membership System

NFT-Based Membership

Members receive non-transferable Token-2022 NFTs with:

  • Extensions: NonTransferable, MetadataPointer
  • Network: Solana mainnet-beta
  • Minting: Automated via GraphQL mutations
  • Verification: On-chain balance checks

Privacy-Aware Proofs

Membership proofs can be generated with privacy controls:

  • Public Personas: Visible in proofs with full details
  • Private Personas: Counted but details hidden
  • Auto-Sync: Proofs update when persona visibility changes

Identity System

Personas & DIDs

Each member can have multiple personas (identities):

  • Default Persona: Auto-created on signup
  • Additional Personas: User-created with custom names
  • DIDs: Decentralized Identifiers for each persona
  • Privacy: Per-persona visibility controls

FIBO Identity Switching

UI component for switching between personas:

  • Context Provider: FiboProvider for global identity state
  • Switcher UI: FiboIdentitySwitcher component
  • GraphQL: Integrated with Neo4j queries
  • Real-time: Live updates on persona changes

Token Economics

Multi-Token System

ƒ(xyz) = (wF × FLR) + (wJ × JLE) + (wH × HOW)

Where:
- wF (Florin weight) = 0.333333333
- wJ (Joule weight) = 0.333333333
- wH (HoW weight) = 0.333333334

Token Allocations

Total supply: 100,000,000 ƒ(xyz)

  • P (Retroactive): 20,000,000 (20%)
  • E (Ecosystem): 70,000,000 (70%)
  • T (Team): 10,000,000 (10%)

Graph Database

Neo4j Schema

Key node types:

  • Member: Network members
  • Persona: Member identities
  • Organization: Companies, DAOs, groups
  • Contribution: Work done by members
  • MembershipProof: Privacy-aware proofs

Constraints

  • One DID per Member (enforced at DB level)
  • Unique wallet addresses
  • Unique persona names per member

API Architecture

GraphQL Layer

Type-safe GraphQL API with:

  • Schema: Generated from TypeScript types
  • Resolvers: Modular resolver architecture
  • Auth: JWT-based with Privy integration
  • Subscriptions: Real-time updates via WebSocket

Key Mutations

mutation IssueMembership {
  issueMembership {
    id
    membershipNFTMint
    status
  }
}

mutation MintMyMembership {
  mintMyMembership {
    membershipNFTMint
    transactionSignature
  }
}

mutation BootstrapUser {
  bootstrapUser {
    member {
      id
    }
    persona {
      id
      did
    }
  }
}

Testing

Test Coverage

  • Unit Tests: Jest for utilities and services
  • Integration Tests: GraphQL resolver testing
  • E2E Tests: Playwright for full user flows
  • Blockchain: Devnet testing for Token-2022

CI/CD

Automated testing on:

  • Pull requests
  • Main branch commits
  • Production deployments

Security

Authentication

  • Privy v3: Embedded wallet and authentication
  • Guest Mode: Available for testing
  • JWT Tokens: Secure API access
  • Wallet Connection: Solana wallet adapters

Best Practices

  • Environment variable isolation
  • CORS configuration
  • Rate limiting
  • Input validation
  • SQL injection prevention
  • XSS protection

Performance

Optimizations

  • React 19 Compiler: Automatic optimization
  • Next.js 16: App Router with streaming
  • Code Splitting: Automatic with Next.js
  • Image Optimization: Next.js Image component
  • Font Optimization: Next/font integration

Monitoring

  • Server-side logging with structured logs
  • Client-side error tracking
  • Performance metrics
  • Database query optimization

Development Workflow

Package Manager

Always use pnpm - NOT npm or yarn:

pnpm install
pnpm dev
pnpm build

Monorepo Structure

Turborepo-powered monorepo with:

  • apps/: Applications (app, web, api, docs)
  • packages/: Shared packages (auth, solana, neo4j, etc.)
  • scripts/: Utility scripts
  • tests/: E2E test suites

Commands

# Development
pnpm dev                    # Start all apps
pnpm dev --filter app       # Start specific app

# Build
pnpm build                  # Build all packages
pnpm build --filter web     # Build specific package

# Test
pnpm test                   # Run all tests
pnpm test:e2e              # Run E2E tests
pnpm test:integration      # Run integration tests

# Linting
pnpm lint                   # Check all files
pnpm lint:fix              # Fix issues

Deployment

Platforms

  • Frontend: Vercel / Coolify
  • API: Coolify / Docker
  • Database: Neo4j AuraDB / Self-hosted
  • Blockchain: Solana mainnet-beta

Environment Variables

Required for production:

  • NEO4J_URI, NEO4J_USER, NEO4J_PASSWORD
  • PRIVY_APP_ID, PRIVY_APP_SECRET
  • NEXT_PUBLIC_SOLANA_RPC_URL
  • NEXT_PUBLIC_GRAPHQL_URL

Resources