How TimeLock Works: What Actually Happens to Your Crypto

1

Your crypto travels to a vault, not to us

When you press lock, your crypto is sent to a digital vault on the Ethereum network. We never receive it and can never touch it. The vault is a small computer program that runs on its own, with no one behind the counter.
2

The vault writes down three things

Who locked it (your wallet's address), exactly what was locked, and the date it is allowed to leave. That note is saved on the blockchain, a public ledger that nobody can edit or delete afterwards. Not us, not even the people who run the network.
3

Ask early, and it checks the note

Try to withdraw before your date and the vault does exactly one thing: it compares today's date with the date on your note. Too early? It refuses. There is no manager to convince, no support line, no override button anywhere in the system.
4

On the date, the door opens

From your unlock date onwards, that same check passes. The vault hands the exact crypto you locked back to the exact wallet that locked it, and it can never give it to anyone else. Withdrawing is free.

1

Locking creates an on-chain record

Your deposit goes to a smart contract on Ethereum mainnet, not to a company wallet. The contract stores a lock entry with four fields: your address, the token, the amount, and your unlock timestamp. From that moment the record lives on the blockchain, not on our servers.
2

The rules were frozen at deployment

The contract is immutable and non-upgradeable. Nobody can change the code, add an early exit, or redirect funds later. The exact code you can read on Etherscan today is the code that will run in ten years.
3

Every withdrawal runs the same three checks

Are you the wallet that made the lock? Is it still unwithdrawn? Is the current block time past your unlock time? Fail any one and the transaction reverts. Pass all three and nothing can stop it: withdrawals can never be paused, and no admin key can touch locked funds.
4

You never depend on this website

The site just formats transactions for your wallet to sign. Every lock and withdrawal is a public transaction anyone can inspect, and if this site ever went offline you could view your locks and withdraw straight from the verified contract on Etherscan. A one-time 0.5% fee at deposit; withdrawing is free.

1

Deposit: lockNative() or lockToken()

ETH enters through payable lockNative() (bare receive() reverts); ERC-20s through lockToken() via transferFrom against an allowlisted set. The 0.5% fee is skimmed at deposit and a lock struct {owner, token, amount, unlockTime, withdrawn} is written to storage.
2

Immutable bytecode, no proxy

A single plain contract: no delegatecall, no upgrade path, no proxy pattern. The deployed bytecode is final, so the invariants you audit today hold for the life of the contract.
3

withdraw(uint256): three requires, nothing else

lock.owner == msg.sender, !lock.withdrawn, block.timestamp >= unlockTime. Effects before interactions, nonReentrant, and principal only ever transfers to msg.sender. No other selector moves user funds. pause() gates deposits only and auto-expires after 30 days.
4

Minimal, timelocked admin surface

The owner is a multisig, and admin ops (token allowlist, role rotations) sit behind 48-hour timelocks. None of them can reach locked principal. Diff the bytecode and read the ABI at 0x571B…794c; confirming no early-exit path exists beats anything this page can claim.

What actually happens to your crypto.