LBLockbox
Docs / Prefilled links

Prefilled links

Send someone a Lockbox link with the token, the amount and the date already filled in. They connect, check it and sign. There is no API key, no SDK and nothing to deploy, because it is a URL.

Who this is for

Anyone standing where the decision to lock actually gets made. A launchpad's post-deploy screen, a deployer tool, a bot that posts when a pool is created, a Telegram message to a team that just launched. The gap between "we should lock that" and actually doing it is where most locks are lost, and a prefilled link closes it.

Locking tokens

Point at https://lock-box.xyz/ with any of these.

ParameterWhat it does
chain4663 for Robinhood Chain, 5042 for Arc. Set this first: every other value names a contract on one specific chain.
tokenThe ERC-20 to lock.
amountIn whole tokens, as a person would type it. Not base units.
untilA date, as YYYY-MM-DD or a unix timestamp in seconds. Everything unlocks at once on that day.
cliffDays before anything can be claimed. Use instead of a date.
vestDays of linear vesting after the cliff. Omit it, or pass 0, for a straight timelock.

Lock 5,000,000 of a token until the end of June 2027:

https://lock-box.xyz/?chain=4663
  &token=0xDA0d76Fcc35da5A5809037e5eE619EB31c5CEB8e
  &amount=5000000
  &until=2027-06-30

A one year cliff and two years of vesting after it:

https://lock-box.xyz/?chain=4663
  &token=0xDA0d76Fcc35da5A5809037e5eE619EB31c5CEB8e
  &amount=5000000&cliff=365&vest=730

Locking a liquidity position

Point at https://lock-box.xyz/positions with collection (the position NFT contract, normally Uniswap's v4 position manager), id (the position id) and either until or days.

https://lock-box.xyz/positions?chain=4663
  &collection=0x58daec3116aae6D93017bAAea7749052E8a04fA7
  &id=2993364&days=365

What a link cannot do

It cannot set the beneficiary, and it never will. A link that chose who receives the tokens would be a phishing tool: send someone a "lock your liquidity" link that quietly names your own address, and a careless user locks their supply to you, irreversibly, with the interface showing exactly what they asked for. Locks always default to the connected wallet, and anyone locking for someone else types that address in themselves.

Nothing in a link is trusted beyond being a suggestion. Every value is validated as though it had been typed, a date in the past is ignored rather than used, and the form is fully editable before anyone signs. A bad link produces a form on its defaults, not a bad lock.

Building something that should hand people a lock? Tell us what you need and we will add the parameters. The contract addresses are public and the contracts are ownerless, so you can also skip this entirely and call them directly.