Use cases
Where BridgeHold + Torque win together
Each block ties a concrete growth problem to Torque primitives fed by the same two custom events BridgeHold emits. Every story maps to fields you can filter and score in Torque.
- 01
Sticky TVL & liquidity depth
Depth that survives after the bridge is what protocols actually monetize.
Snapshot events encode whether balances stay above your minimums across simulated or real indexer ticks. That turns one-time TVL spikes into a time series you can threshold, tier, and reward - aligned with MM pools, lending utilization, or LP health programs.
How Torque uses it
Torque leaderboards and rebate tiers read streakDays, meetsThreshold, and balance so incentives track sustained depth, not a single deposit spike.
- 02
Anti-dump & cooling-off rules
Pay for patience, not for hit-and-run exits.
When balance drops below min or streak breaks, your SQL sees it on the next bridge_hold_daily_snapshot. You can require N qualifying days before raffle tickets count, slash weights after early dumps, or run recovery bonuses when users climb back - all from the same two custom events.
How Torque uses it
Raffles, gifts, and gated rewards use meetsThreshold and streakDays so Torque only pays wallets that behaved through your cooling window.
- 03
Cohorts & route-specific growth
Same integration, different partner stories per chain.
bridge_hold_completed carries sourceChain, destChain, bridgedAmount, and wallet. Snapshot rows add daily truth. Segment Base arrivals vs Arbitrum whales, run parallel prize pools, or co-market with an L2 - without forking your stack.
How Torque uses it
Torque SQL filters on route and amount so each cohort gets its own leaderboard, raffle pot, or distributor budget from one ingest stream.
- 04
Gaming & consumer surfaces
The loop works even when users never say DeFi out loud.
Treat a bridge (or deposit) as capital committed to the experience and snapshots as ongoing eligibility. Season passes, ranked seasons, and fair drops inherit the same meetsThreshold and streak signals - BridgeHold is the reference spine.
How Torque uses it
Torque gifts and competitions consume the same custom_events: eligibility is provable, seasonal resets are just campaign epochs in Torque.
- 05
Referral & distributor loops
Pay partners when referred users actually stick.
First bridge attributes acquisition; snapshots prove retention. Distributor IDs or referral tags (in your production payload) combine with streaks so rev share or bounties unlock on qualifying days - not only on the first transfer.
How Torque uses it
Torque distributors and incentive programs can key off referred-wallet snapshot streaks, aligning growth spend with measured hold behavior.