Your keys stay yours.
stackme has no unilateral power to move your funds. You authorize the transaction; the protocol holds the position.
Drag the price. Watch it hold.
Bitcoin falls.
Your protection has a plan.
Explore an illustrative Bitcoin drop and see how the three-layer Safety Rail is designed to respond within limits you set. This simulation does not use live account data or create real receipts.
You keep the keys. The limits stay yours.stackme has no unilateral power to move your funds — real rail actions require authority you signed.
Illustrative position interactive simulation
Safety Buffer
53%
action thresholdhealthy range
Bitcoin price$84,760
← drag to crash the price
L1
Sentinel repayRepaid from your USDC balance, inside your signed cap.
armedL2
Bounded unwindUnwound one small slice — the taxable disposal disclosed.
armedL3
On-chain BackstopModels the on-chain path intended to remain available through an app outage.
armedRail Record · samplenot on-chain
No sample event yet. Drag the price down to explore the sequence.
The market · outside
$84,760
0%
A calm starting point.
This illustration shows how the three-layer Safety Rail is designed to respond in bounded steps. Actual outcomes depend on market and protocol conditions.
Illustrative buffer · monitoredProtection before panic.
Layer by layer.
Bitcoin-backed liquidity, bounded protection designed to keep working through an outage, and evidence for each real intervention. Best-effort by construction, never a guarantee.
45 sec · AI narration, generated with ElevenLabs
3layers of best-effort protection
1human owner at the root of authority
Meaningful actionsdesigned to be attributable and receipted
Noplatform custody in the product architecture
Why stackme
Finance should feel quiet because the hard parts are handled.
We remove complexity without hiding responsibility. The experience is simple; the authority, evidence, and disclosures stay visible.
Designed for the worst day.
Repay from balance, model a bounded unwind when needed, then use an on-chain path intended to remain available through an outage.
Meaningful actions are designed to leave a receipt.
Signed, timestamped records make it possible to check what happened, who authorized it, and whether the system did what it said.
Your AI, under a mandate.
Planned agents can watch, simulate, and act only inside signed limits. No authority without a mandate; consequential actions are designed to be receipted.
The Safety Rail
Protection that does not disappear when the app does.
The Safety Rail is designed to escalate deliberately: begin with the least disruptive action, preserve explicit user limits, and retain an on-chain final layer.
01
Sentinel repay
Uses available USDC inside the exact cap you approved.
02
Unwind
Sells only a bounded collateral slice, with the likely taxable disposal disclosed.
03
On-chain Backstop
The design uses an on-chain path intended to remain executable even if stackme is offline.
Best-effort protection, not insurance or a guarantee.
Guardian MandateKeep my Safety Buffer above 50%
Signed by you
L1
Repay from balanceWeekly cap enforced
FirstL2
Bounded unwindTax disclosure attached
If neededL3
On-chain BackstopOn-chain execution path
Independent path The mandate is designed to reject actions outside these signed bounds.
Trust you can check
The Rail Record is how the promise becomes falsifiable.
At launch, a public, de-identified record is intended to show when protection fired, what layer acted, and the outcome - including misses. Marketing should never outrun evidence.
- Signed and timestamped entries
- Outcomes visible, including failures
- No balances or identity exposed
- Verifiable without trusting stackme's interface
Public proof surfaceRail Record
Illustrative entriesIllustrative protected value$13,490 designed for independent verification
L1
Balance repayPosition restored
$1,240L2
Partial unwindBuffer protected
$3,350L3
On-chain BackstopKeeper confirmed
$8,900 Entries include outcomes, including failures.signed - timestamped - shareable
The governed-agent direction
Useful autonomy without invisible authority.
The planned Agent Gateway extends the same authority model to Claude, GPT, and other agents: human-signed limits, policy checks before action, and a receipt after every consequential tool call.
readwatchsimulaterepaycooloff
Talk with us about agent access mandate evaluation
principal verified-human:emily
agent personal-assistant
request repay 1200 USDC
scope repay
weekly_cap 2500 USDC
policy PASS
receipt queued after confirmation
Inside the signed boundary
How it works
From Bitcoin to usable cash, without surrendering the relationship.
Connect without a seed phrase
A passkey creates your account. Familiar login, explicit ownership, no recovery phrase to hide under a mattress.
Choose a borrow before a sale
Deposit Bitcoin collateral and borrow USDC through a direct-to-protocol transaction. No stackme lending balance sheet.
Set the protection you want
Arm a Guardian Mandate, see the exact caps, and keep a clear record of each recorded intervention.
Verify the story
Receipts and the Rail Record turn safety from a claim into evidence you can inspect and share.
Proof status
Confidence should have a boundary.
stackme is pre-launch. The protected-borrow path has been demonstrated in controlled fork testing; independent receipt verification and mainnet launch remain explicit gates.
Bounded protection path
A mandate-constrained repay has fired under simulated price stress on a fork, with a receipt produced.
Independent receipt check
The current mission is verification by a real non-founder, non-agent participant.
Mainnet availability
No public mainnet launch is claimed. Product imagery and figures on this page are illustrative.
stackmeEarly accessKeep your future.
Keep your future.
Borrow with proof.
Join the founding group helping turn a protected borrow from a controlled proof into independently verified, production-ready infrastructure.
Request early access No spam. No rate bait. Just product access and proof.