FiveTape/API Docs
DocsRuntimeStrategyBuild Plan
Search docs
Terminal
Navigation
OverviewRuntimeDistributionToken FlywheelBuild Plan
Search docs
Get started
Getting started
FiveTape docsRuntime
Product model
DistributionToken FlywheelBuild Plan
Scope
This document stays focused on the FiveTape runtime, token design, and rollout path.
Docs / Getting started

FiveTape docs

Technical documentation for the FiveTape BTC 5m runtime, token model, and rollout.

Updated Mar 19, 2026FiveTapeTrading AgentToken Model

Overview

FiveTape is a public board for a single-market BTC 5m runtime. The terminal exposes runtime state, trades, and realized PnL. This document covers the runtime structure, token model, and deployment path.

The runtime is designed to keep execution observable and deployment-ready. The token layer sits on top of that board, with a fixed percentage of realized net trading profits allocated back into the treasury and product.

Market
Polymarket BTC 5m
Single-market runtime with one public board and one execution loop.
Execution
Market-fed execution
Real market windows, book-driven entries, tracked fills, and realized PnL accounting.
Surface
/terminal + /docs
Public runtime terminal plus product and integration documentation.
Deployment
Live-ready path
Final deployment path: fund the account and switch the execution connector.

Runtime

The runtime uses real Polymarket BTC 5m windows, book-aware entries, tracked fills, realized PnL accounting, and a public terminal for state visibility.

market: polymarket btc 5m
decision: adaptive-hybrid signal + execution gates
execution: market-fed books, tracked fills, realized pnl
surface: /terminal for state, /docs for architecture
end-state: fund the account and switch the execution connector

The public terminal is the operational surface. The docs route defines the supporting product, token, and integration model.

Distribution

The token layer is there to amplify the runtime, not replace it. Distribution should sit close to the trading board so users can move directly from public performance to ownership, gated access, and community participation.

FiveTape needs launch tooling, fee routing, treasury accounting, and a clean discovery surface. Those pieces should be treated as product plumbing around the runtime instead of the story of the page itself.

What the product needs
Token launch and treasury routing
Fee-share and partner configuration
Analytics and revenue accounting
Community distribution surfaces
Premium access controls
Why that matters for FiveTape
The runtime stays the center of the product.
Revenue can route directly into the treasury.
The token supports retention instead of being decorative.
Community growth feeds back into runtime improvement.

Token Flywheel

Token policy
The token is designed to reinforce the runtime. Distribution, fee share, and a fixed percentage of realized net trading profits feed treasury growth, token support, and continued runtime improvement.
1. Token launch

Launch the FiveTape token with explicit fee-share and treasury routing.

2. Profit allocation

Route a fixed percentage of realized net trading profits into the token side of the product: treasury growth, token support, community incentives, and future token utility programs.

3. Treasury allocation

Route creator fee share and partner fee share into a FiveTape treasury wallet that funds infrastructure, captures, model improvement, and community rewards.

4. Distribution

Use the token surface, public board, and gated community entry points for distribution and user acquisition.

5. Token utility

Use the token for access and coordination: gated signal rooms, advanced board views, leaderboard rights, research drops, strategy voting, and community-funded feature bounties.

6. Reinvestment

Reinvest distribution and treasury growth into captures, execution quality, and model development.

public board + token distribution
-> token fees
-> fixed share of realized net trading profits
-> fivetape treasury
-> more captures, research, execution modeling
-> stronger public board
-> stronger reason to hold / use the token

Build Plan

  1. 1Document the runtime, token model, treasury wallet structure, and profit-allocation policy.
  2. 2Build the token launch helper for metadata, fee-share configuration, partner configuration, and post-launch analytics.
  3. 3Add token-aware product surfaces to FiveTape, including terminal perks, gated community routes, and treasury accounting.
  4. 4Allocate treasury revenue and a fixed percentage of realized net profits back into token support, captures, execution modeling, and later live-capital expansion.
FiveTape runtime
  -> public /terminal board
  -> /docs architecture route
  -> token launch helper
  -> fee-share + partner config
  -> treasury accounting
  -> gated community / premium surfaces
  -> reinvestment into the trading agent