Skip to main content

Flywheel Proof Mechanism

The Believe Flywheel API uses a robust proof system to ensure transparency and auditability for all tokenomic actions. When you register a flywheel and execute pipeline actions, you provide proof data that gets recorded on-chain via memo instructions.

Proof Types Configuration

During flywheel registration, you define the proof types your project will use. Each proof type includes:
  • Type: A unique identifier (e.g., "PRODUCT_BUY", "WATCH_AD", "ENGAGEMENT_REWARD")
  • Description: Human-readable explanation of what this proof type represents

Example Proof Types Definition

Pipeline Proof Data

When creating flywheel pipelines, each pipeline includes:
  • Type: Matches one of your registered proof types
  • Payload: JSON string containing the specific proof data for this operation

Example Pipeline with Proof

Automatic Proof Recording

The Flywheel API automatically:
  1. Generates Proof Hash: Creates a SHA-256 hash of your proof data
  2. Creates Proof Memo: Combines the hash with the original proof data
  3. Prepends to Pipeline: Adds the proof memo as the first action in your pipeline
  4. Records On-Chain: Ensures proof data is permanently recorded on Solana

Generated Proof Structure

Proof Data Best Practices

Essential Fields

Include key information that proves the validity of your action:
  • Unique Identifiers: Transaction IDs, user IDs, session IDs
  • Timestamps: When the triggering event occurred
  • Amounts/Values: Relevant monetary or engagement metrics
  • Context: Platform, device, location if relevant

Example Proof Schemas

Product Purchase

User Engagement

Validation and Compliance

  • Immutable Records: All proof data is permanently recorded on Solana blockchain
  • Audit Trail: Complete history of all flywheel actions with supporting evidence
  • Transparency: Public verification of tokenomic operations
  • Compliance: Detailed records for regulatory requirements

Integration with Flywheel Actions

Proof data flows through the entire flywheel process:
  1. Registration: Define your proof types and schemas
  2. Pipeline Creation: Include proof data with each pipeline
  3. Batch Processing: Multiple pipelines with their proofs processed together
  4. On-Chain Recording: All proof data permanently stored via memos
  5. Verification: Community and auditors can verify all actions
For detailed implementation, see the Flywheel API endpoints.