B

BRIDGEHOLD x TORQUE

Prove liquidity sticks after the bridge. Let Torque run the incentives.

BridgeHold is a reference growth loop: your product emits two Torque custom events (bridge + daily hold snapshot). Torque turns those streams into leaderboards, raffles, rebates, gifts, and distributor payouts- with sybil-aware, measurable participation instead of one-off airdrops.

We showcase five concrete narratives - sticky TVL, anti-dump rules, cohort campaigns, consumer seasons, and referral economics - all fed by the same integration you can demo in the simulator with live ingest.

LeaderboardsRafflesRebatesGiftsDistributors
View use casesOpen simulatorRun auto demoHow it works

Why BridgeHold stands out

Five growth stories, one Torque integration

BridgeHold makes explicit what you measure (hold depth, patience, cohorts, seasons, partner outcomes) and how Torque consumes it- custom_events in, incentives and distributors out.

  • 01

    Sticky TVL & liquidity depth

    Depth that survives after the bridge is what protocols actually monetize.

    Torque leaderboards and rebate tiers read streakDays, meetsThreshold, and balance so incentives track sustained depth, not a single deposit spike.

    Deep dive
  • 02

    Anti-dump & cooling-off rules

    Pay for patience, not for hit-and-run exits.

    Raffles, gifts, and gated rewards use meetsThreshold and streakDays so Torque only pays wallets that behaved through your cooling window.

    Deep dive
  • 03

    Cohorts & route-specific growth

    Same integration, different partner stories per chain.

    Torque SQL filters on route and amount so each cohort gets its own leaderboard, raffle pot, or distributor budget from one ingest stream.

    Deep dive
  • 04

    Gaming & consumer surfaces

    The loop works even when users never say DeFi out loud.

    Torque gifts and competitions consume the same custom_events: eligibility is provable, seasonal resets are just campaign epochs in Torque.

    Deep dive
  • 05

    Referral & distributor loops

    Pay partners when referred users actually stick.

    Torque distributors and incentive programs can key off referred-wallet snapshot streaks, aligning growth spend with measured hold behavior.

    Deep dive

Read the full use-case playbook ->

Torque in production

How we use Torque - not generic, not hand-wavy

BridgeHold's Next.js API routes call the same ingest URL your production worker would. When TORQUE_INGEST_API_KEY is set, every bridge and daily tick attempts a real POST …/events with your Torque custom event names. The simulator, live demo, and leaderboard all exercise that path so you can verify live custom_events end-to-end.

Fire events from simulatorRun scripted demo
Data flow
  1. User / indexer
  2. BridgeHold APIs
  3. Torque ingest
  4. Leaderboards · Raffles · Rebates · Gifts · Distributors

Configure campaigns and SQL with the Torque MCP- BridgeHold focuses on emitting consistent custom_events your rules can trust.

Bridge completed

bridge_hold_completed

Env override: TORQUE_EVENT_BRIDGE

  • userPubkey
  • timestamp
  • amount
  • sourceChain
  • destChain
  • txHash (mock in demo)

Daily snapshot

bridge_hold_daily_snapshot

Env override: TORQUE_EVENT_SNAPSHOT

  • userPubkey
  • timestamp
  • dayIndex
  • balance
  • meetsThreshold
  • streakDays
  • bridgedAmount
  • sourceChain
  • destChain

Programmable retention layer

Torque gives teams leaderboards, rebates, raffles, and gifts on top of live activity - so growth loops are measurable, not theoretical.

  • $5B+Volume routed through Torque-powered incentives
  • 1,400+Campaigns launched on the platform
  • $10M+Rewards distributed to participants
  • Sybil-awarePrimitives designed for real retention, not bot farms

Teams like Raydium, Axiom, and WLFI use Torque to tie acquisition, retention, and velocity to real participation.

Flow

Built-in growth loop

BridgeHold is intentionally narrow: it emits the custom events your Torque SQL expects, then gets out of the way. Wire your keys once and every simulator tick behaves like production traffic.

Read the full flow
  1. STEP 01

    Bridge in

    Record a bridge_hold_completed-style event with route, notional, and wallet - same payload you will use with Torque ingest.

  2. STEP 02

    Prove the hold

    Post daily bridge_hold_daily_snapshot events with balance, meetsThreshold, and streakDays so campaigns grade real behavior.

  3. STEP 03

    Run incentives

    Use Torque primitives - leaderboards, raffles, rebates, gifts - driven by MCP or API so rewards follow live custom_events.

Build with Torque

Wire Torque the same way in demo and prod

BridgeHold connects the simulator, live demo scripts, and leaderboard to the same ingest path your production worker uses. With TORQUE_INGEST_API_KEY in .env.local, bridges and daily ticks send real custom_events so campaigns in Torque see live hold depth, streaks, and routes - not UI-only demos.

Use the MCP quickstart to configure projects and campaigns; follow @torqueprotocol on X for Torque product updates.

Explore

Each section has its own page.