how crypt works.
Two people put money into a lockbox on Stellar. A bot watches an API. If the API stays down past the limit, the money goes to the subscriber. If it stays up, the money goes to the provider. Nobody decides — the contract does, based on what the bot saw.
sign in
One message that proves you control your wallet address. No transaction, no fee.
deposit
One transaction per side. Locks your USDC into a lockbox contract on Stellar testnet.
watch
After both sides deposit, no more wallet prompts. The contract handles payout.
Calls the API at the interval the provider chose (every 15s, 60s, 5min, etc.) with a 5-second timeout.
If it answers normally — log a healthy check, reset the failure counter.
If it errors or times out — log a failed check, increment the counter.
When the counter hits the failure limit (3 by default), the contract pays the subscriber both deposits — automatically.
The amounts are locked into the contract at deposit time. The contract only knows two addresses — the provider's payout wallet and the subscriber's payout wallet. We can decide which one wins, but we can't change either address or take a cut.
Today we run the API check ourselves — you have to trust we report honestly. Next we'll have multiple independent checkers agreeing before a payout triggers. After that, a math-based proof that the checkers agreed, verified by the contract itself. The goal: nobody — us included — can decide who gets paid. The math does.