Trade Bangers

Technical reference

Clear rails.
Clear claims.

A concise reference for where Trade Bangers stores state, which interactions settle through contracts, and which live products rely on signatures and verified offchain records.

Architecture

Onchain and offchain.

Live · Onchain

Contract-settled systems

Token deployment, prediction markets, raises, escrow, refunds, subscriptions, receipt NFTs, and associated fee rules.

Live · Offchain

Signed application systems

Talent, Resources, Gifting, Super Thanks, shortlists, teaching records, moderation, receipts, and public recognition.

Offchain records are file-backed for the current product stage. Important writes use canonical content hashes and wallet signatures where implemented. Public visibility may also depend on receiver decisions or verifier moderation.

Networks

Chain coverage

NetworkUsesEnvironment
BaseTokenize deployments, Clanker integration, Predict USDC marketsMainnet and Base Sepolia testing
ApeChainRaises, escrow, subscriptions, receipt NFTs, supported gifting referencesMainnet
ApeChain CurtisPredict experimental factories and onchain asset verificationTestnet
OffchainTalent, Resources, Gifting, Super Thanks, gigs, bounties, reputation, receiptsSigned/file-backed application state

Fees

Documented defaults

  • TokenizeFixed 1% platform fee with configurable creator fee from 0–4%, routed according to the launch configuration.
  • PredictUSDC market mechanics with creator fee from 0–4% where supported by the deployed market version.
  • Raises1% platform fee accrued by the contract and released only after successful completion.
  • Subscriptions1% platform fee enforced by the onchain receipt contract for contract-routed plan payments.
  • Offchain productsNo contract fee is implied by an offchain record; the underlying wallet transfer or external payment rail may have its own costs.

Contracts

Sources of truth

Deployment addresses must be read from the repository deployment JSON rather than copied into new static prose:

  • Predictcontracts/deployment.json and the product catalog APIs expose current mainnet/testnet factory references.
  • Raisescontracts/escrow-raises-deployment.json records the deployed escrow-raise system.
  • Subscriptionscontracts/subscriptions-deployment.json records the receipt-contract deployment.
  • Dreamweaverscontracts/dreamweavers-soulbound-deployment.json records the mascot soulbound deployment.
Verify before transacting. Networks and addresses can change after migrations. The app configuration and deployment records take precedence over screenshots or copied addresses.

Public interfaces

API families

  • Commands and content/api/command, /api/resolve-post, Tokenize discovery, Predict builder drafts, chat, and share previews.
  • SubscriptionsPublic plans and approvals plus authenticated plan administration and scanner synchronization.
  • People and reputationProfiles, builders, vouches, scores, Talent profiles, claims, shortlists, and stored profile media.
  • ResourcesTutors, resources, resource batches, series, collections, curators, engagement, notices, reports, and administration.
  • Work marketsGigs, orders, bounties, applications, and signed status updates.
  • RecognitionSuper Thanks, payment receipts, patron nominations, requests, and receiver decisions.
  • Onchain indexOwnership, asset verification, index status, and authenticated synchronization.

Integrations

Connected surfaces

  • ClankerBase token deployment, launch configuration, creator rewards, vaults, airdrops, and related launch helpers.
  • Privy and GlyphWallet and account connections across supported public surfaces.
  • Base App / XMTPGuided token and prediction commands plus optional announcements in configured chats.
  • Farcaster / NeynarCast resolution and command/reply infrastructure; public UI status remains explicit when paused.
  • Social and article providersX, Bluesky, Farcaster, TikTok, Medium, Substack, and recognized fallback providers with capability-specific availability.
  • Grok fallbackOptional server-side public URL metadata extraction when a native resolver cannot supply usable content.

Status vocabulary

Consistent labels

  • Live · OnchainA public product whose defining settlement or receipt behavior is available through deployed contracts.
  • Live · OffchainA public, usable product relying on signed records, stored data, verification, or moderation rather than contract settlement.
  • BetaA working product flow still carrying beta-level operational or interface expectations.
  • ShowcaseBrowsable creative assets and references, not presented as a transaction product.
  • PlannedRoadmap direction that must not be described as available.
  • PausedImplemented or previously exposed functionality intentionally unavailable.

Security boundaries

Operational expectations

  • Wallet signaturesMutating offchain records bind normalized content and timestamps to the expected signer.
  • Operator secretsAdministrative command and plan routes require the configured bearer/header secret where enabled.
  • Rate limitsCommand, chat, media, receipt, profile, tutor, gig, and bounty routes apply bounded request limits.
  • URL safetyResource previews validate public destinations and reject private network hosts.
  • Private dataSensitive contact fields remain private or encrypted rather than appearing in public payloads.
  • Audit statusExperimental contracts and beta products must not be represented as audited production systems unless that status changes in repository evidence.