When a lock expires on Robinhood Chain.

The short answer: nothing automatic. No transfer fires, no tokens move, no notification goes out. The unlock date simply changes what the HoodLock contract on Robinhood Chain will allow.

Mechanically, at the unlock date

Before the date, a withdrawal transaction reverts. After it, the same transaction succeeds, but only if the lock owner sends it. The tokens sit in the contract indefinitely until someone actively claims them, and no other address can take them at any point. There is no expiry deadline and no risk of the position being swept.

This matters more than it sounds. An expired lock is not an event; it's a change in permission. Plenty of locks stay unclaimed for months past their date simply because nobody got around to it.

What it means if you hold the token

An approaching unlock on a large LP position is a real risk window: from that date, the liquidity can be withdrawn. It doesn't mean it will be. What you're looking at is the removal of a guarantee, not the arrival of a sell.

What it means if you're the team

An unlock date is a communication event whether or not you treat it as one. Holders can see it coming. That's the entire point of a public lock, so the choice is between explaining it in advance or letting people draw conclusions.

The strongest move is to extend before the date arrives rather than after. On HoodLock unlock times are extend-only, so an extension is permanent, visible, and cannot later be walked back. Extending a week early reads as a plan; extending a week late reads as a reaction.

Why extending beats re-locking

Withdrawing at expiry and creating a fresh lock produces the same end state but a worse record: for the period between the two transactions, the liquidity was genuinely unlocked, and the new lock has no history. An extension keeps one continuous position with a visible chain of commitments. More on lock duration strategy.

Locks that should never expire together

If the team allocation and the LP lock share an unlock date, that date becomes a supply cliff — liquidity becomes withdrawable at the same moment a large token allocation becomes sellable. Team allocations belong in a vesting schedule that releases gradually, which removes the cliff entirely rather than scheduling it.

Tracking unlocks

Every HoodLock position has a permanent proof page showing its status and unlock date, readable without a wallet, and the explore page lists every lock on Robinhood Chain with its current state. A lock that has already been withdrawn shows as withdrawn — historical proof, not present protection, which is a distinction worth checking before you rely on a link someone sends you.

Common questions

Do tokens unlock automatically when a lock expires?

No. Nothing moves on its own. The unlock date only changes what the contract permits — the lock owner still has to send a withdrawal transaction, and the tokens stay in the contract until they do.

Can anyone else claim the tokens after a lock expires?

No. Withdrawal is restricted to the lock owner regardless of how much time has passed. There is no deadline to claim and no way for another address to take the position.

Should I sell if a project's liquidity lock is about to expire?

An expiring lock removes a guarantee rather than causing a sale. Look at how much of the pool it covers, whether the team has extended locks before, and whether they say anything as the date approaches.

Is extending a lock better than re-locking?

Yes. Withdrawing and creating a new lock leaves a genuine gap where the liquidity was unlocked, and the new position has no history. An extension keeps one continuous lock with a visible record of commitments.

Keep reading

• How long should you lock liquidity?
• What is a liquidity lock?
• How to set up token vesting
• Lock expiry in the app