Illustrative. Not a forecast or offer.
Keep BTC.
Stay
Liquid.
Set your LTV ceiling, buffer floor, and stress response once — then simulate it in Shadow Mode before any capital moves.
Modeled. Non-custodial. Not investment advice.
Example only. Actual results depend on your inputs and market conditions.
BTC stays yours. Cashflow follows explicit rules, not yield targets.
You set max leverage and reserve minimums. The rehearsal refuses unsafe receipt steps.
Breakwater surfaces modeled liquidation pressure early; it does not guarantee liquidation avoidance.
The Problem
Holders and treasuries shouldn't live inside DeFi screens.
Fragmented wrappers, manual rebalancing, liquidation anxiety. TIDE replaces the spreadsheet with a policy engine — for individuals and teams.
Core shift
You set the rules. Shadow Mode rehearses the playbook.
Cashflow target, risk ceiling, buffer floor — defined once. Live execution remains gated behind wallet signing, audit, and mainnet controls.
Cashflow band, not fixed yield
A survivable range tied to real collateral, not a marketing number.
Buffer as first-class policy
Reserves are modeled in policy and anchored on Sui testnet before any live rollout.
Pre-liquidation stress response
Breakwater flags de-risking early and keeps the policy response visible before liquidation pressure compounds.
Plain-language audit trail
Every action logged as a readable treasury decision. Zero DeFi jargon.
Shadow Mode
Simulate before you commit.
Full treasury simulation against real market scenarios. See exactly how your policy performs — before a single sat moves.
Your policy, four stress regimes
Input BTC amount, cashflow target, max LTV, and buffer minimum. TIDE runs it through calm, trending, stressed, and emergency scenarios.
- Modeled payout range under the scenarios you configure
- Breakwater triggers and de-risk timeline
- Buffer runway at 30 / 90 / 180 day horizons
- Full action log in plain treasury language
Scenario A — Protection priority
Simulated
Survivable payout
$820–$1,020
Breakwater trigger
−22% drawdown
Buffer runway
114 days
Reduced exposure — volatility breached safe corridor.
Rebuilt buffer — cashflow window reopened.
Held borrowing paused — stress mode still active.
Architecture
Three layers. Zero black boxes.
A constrained policy engine — not a yield optimizer. Every decision bound by your policy, visible in the log.
No hidden strategies. No opaque rebalancing. Policy-driven behavior you can audit line by line.
Policy Engine
LTV ceiling, buffer floor, venue caps, emergency rules — enforced on every cycle, no exceptions.
Breakwater
Detects stress early. Flags slowing exposure, suspending cashflow, and pausing borrowing before forced liquidation risk compounds.
Action Log
Every move in plain language: what changed, why, and which policy rule triggered it.
Modes
Operating modes, not yield labels.
Harbor models income within policy. Breakwater activates when protection overrides profit.
Harbor targets cashflow. Breakwater protects.
Model cashflow when conditions allow. Shift to defense before manual intervention becomes urgent.
Policy-modeled cashflow
Explicit stress response
Auditable log
Harbor
Steady cashflow within your LTV and buffer constraints. Default state.
Breakwater
Auto de-risk: reduces exposure, pauses cashflow under stress.
Verified readout
Data source, stress assumptions, and next action stay visible before any guided rollout.
Public alpha
Public alpha users review the simulator first. Live execution stays gated.
Infrastructure
Rehearsed on Sui. Venue-adaptive by design.
Fast testnet proof, wallet-signed receipts, future native-BTC rail path. Sui is where we start; venue-adaptive live execution stays gated as BTCfi matures.
Clear UX from simulation to guided rollout.
Clear wallet prompts, testnet receipts, and future sponsorship paths. Sui gives the proof flow room to become simpler without hiding what is being signed today.
Hashi is tracked as a future native-BTC rail candidate. The current V1 positive proof loop uses seeded Sui BTCfi rail profiles: Scallop, NAVI, Suilend, and Bucket. AlphaLend remains seeded coverage, not a positive proof run.
Sui supports sponsored transaction paths. The current Overflow proof flow uses wallet-signed testnet gas unless sponsorship is explicitly enabled for that session.
Rail profiles model Sui venue choices before signing. The current proof pack does not claim routed swap execution.
Treasury state lives in owned Sui objects — policy actions don't queue behind unrelated traffic.
Shadow-first GTM
Future native BTC rail
Policy-driven cashflow
Sub-second finality
Route rehearsal
Action receipts
Latest verified testnet rehearsal.
This receipt pack verifies the Sui testnet policy and receipt loop, not live execution, cashflow outcomes, or mainnet capital movement.
Harbor / Scallop / conservative stress
Testnet verified
Proof run commit
ebba040
Generated
2026-05-07 04:33 UTC
Policy anchor tx
2tbh2bRt…JgXYvv
Policy object
0x0b96b64e…69b5f0f
Mint tx
E9VxM52H…GFCHZd
Receipt object
0xbf44cded…4b19011
Rail-pack digest 0xf5feb3cd…40bb68e
· Package + admin-cap documented in onchain_mvp_proof_pack.md
· Regenerate with npm run proof:testnet
· Judge demo (Sui Overflow 2026) →
FAQ
Straight answers only.
What TIDE can and cannot do. No fog.
No. It models a survivable cashflow range based on your policy and real collateral dynamics. Simulated, never promised.
Yield apps chase APY. TIDE enforces constraints: LTV ceilings, buffer floors, venue limits, auto stress response. Survivable cashflow, not maximum return.
See exactly how the policy behaves under stress before any capital is at risk. Trust earned, not assumed.
Drawdowns, volatility spikes, liquidity drops, or any threshold you define. It models slowing exposure and pausing cashflow; any live action remains wallet-signed and gated.
Not for Shadow Mode — it's pure simulation, no signing. For guided testnet proof receipts you connect a Sui wallet (Sui Wallet, Phantom, Nightly, or any WalletStandard extension). Teams keep custody with their own wallet or custody provider; Hashi remains a queued native-BTC rail candidate, not part of the current V1 proof rails.
Not yet. The on-chain policy engine runs on Sui testnet for proof receipts. Full third-party audit is a prerequisite for mainnet — Shadow Mode lets you evaluate behavior without capital in the meantime.
TIDE has a configured read-only Pyth BTC/USD path for Sui testnet and labels freshness/confidence before making any live-oracle claim. Lending-market context is shown as rail-profile or read-only evidence unless a proof artifact captures a live read-back.
In the current Overflow proof flow, TIDE records policy and receipt evidence on Sui testnet and does not custody or move mainnet funds. Future live deployments keep protocol positions under the operator wallet, with TIDE preparing policy and proof payloads rather than holding assets.
Try it now
60 seconds to your first simulation.
BTC amount, cashflow target, risk limits → full behavior log. No wallet. No capital. No commitment.