Token Lock-Up Agreement: Document and Monitor It

A token lock-up agreement records when specified digital tokens cannot be transferred, sold, pledged, or otherwise used, and when those restrictions end. To document and monitor one, define the parties, token amounts, wallets, dates, and release conditions precisely, then track on-chain activity and keep a reliable record of any changes. This is general operational guidance, not legal, tax, or investment advice; have qualified counsel review the agreement and the applicable rules before signing.

What You’ll Need

• The parties’ legal names and contact details, plus the identity and authority of each signer.
• The token name and network, contract address where applicable, quantities, and the wallet addresses holding or controlling the tokens.
• A written schedule stating the lock-up start, duration, any vesting or release dates, and the conditions for each release.
• A secure way to retain the signed agreement and related records, and access to a reliable blockchain explorer or monitoring tool for the relevant network.
• Legal and technical reviewers who can check the wording, token details, wallet control, and any relevant local requirements.

Step-by-Step

1. Identify the parties and their roles. State who is providing, receiving, holding, or administering the tokens. Include full legal names, entity details where relevant, notice addresses, and each person’s capacity to sign. If a custodian, multisignature group, or other service controls the wallet, name its role and responsibilities rather than assuming the token holder has direct control.
2. Describe the locked tokens unambiguously. Specify the token’s full name, blockchain network, and contract address if it has one. State the quantity and denomination, and clarify whether the amount is fixed or may change through splits, migrations, redenominations, or other token events. Avoid identifying an asset only by ticker symbol: different tokens can share a symbol. Attach a schedule if there are several allocations.
3. Identify the relevant wallets and control arrangements. Record each address and the network it belongs to. Verify addresses independently before including them; a typo can point to an unrelated wallet. Explain who controls the keys, whether the wallet is single-signature or multisignature, who can approve transactions, and what happens if a key or signer becomes unavailable. Never place seed phrases or private keys in the agreement or ordinary records.
4. Set clear restrictions and dates. List prohibited actions explicitly, such as transferring, selling, pledging, lending, or moving tokens to another address. Define the start time and end time with a time zone, not just a date if timing matters. If there is a cliff, gradual vesting, or staged unlock, give a table with each release date and amount, and specify how rounding or leftover units are handled.
5. Write release and exception rules. State exactly what permits an unlock: a date, delivery milestone, written consent, or another verifiable event. Name who confirms the condition, what evidence is required, and how much notice is needed. Explain any permitted transfers, such as a move to a replacement wallet or custodian, and require advance written approval and a recorded destination. Define how amendments, early termination, disputes, and breaches are handled, subject to legal review.
6. Confirm the agreement matches the technical setup. Check that the stated balance and addresses match the relevant network records at an agreed reference time. If a smart contract enforces the lock, have a qualified technical reviewer verify its address, functions, release schedule, and administrative controls. A written promise alone may not prevent a wallet controller from transferring tokens; conversely, an on-chain mechanism may not reflect every obligation in the written agreement.
7. Sign, preserve, and circulate the final version. Use a signing method accepted by the parties and retain the fully executed agreement, schedules, approvals, and any technical verification. Give each party the same final copy. Record the document’s version, effective date, and any attachments, so a draft cannot be mistaken for the binding version.
8. Create a monitoring record and cadence. Assign a named person to check the relevant wallets and schedule, for example weekly or around each release date. Record the check date, network, address, balance, transaction history reviewed, and result. Use alerts for outgoing transfers where available, but verify alerts against the network itself. Keep transaction hashes, explorer links, approval messages, and balance snapshots with the monitoring log.
9. Reconcile every change and release. Before a scheduled unlock, confirm the trigger, amount, destination, and required approvals against the agreement. Afterward, record the transaction hash, time, quantity, remaining locked balance, and updated schedule. Treat wallet changes, token migrations, chain changes, or lost access as events requiring documented review and, where needed, a signed amendment—not informal edits to the monitoring sheet.

Common Mistakes

• Using a token ticker without the network and contract address, or copying a wallet address without independent verification.
• Writing “locked until the end of the year” without an exact date, time zone, release amount, or explanation of staged vesting.
• Assuming a signed agreement technically blocks transfers. Unless a suitable mechanism enforces the restriction, the wallet controller may still be able to move tokens.
• Failing to say whether restrictions cover indirect transfers, custodians, replacement wallets, or changes in control.
• Keeping only screenshots. They can help document a check, but transaction hashes and independently verifiable network records are more useful for reconciling activity.
• Making schedule changes in chat or a spreadsheet without obtaining the approvals and signed amendment the agreement requires.

Tips

• Use a schedule that can be checked mechanically: one row per wallet and release event, with quantity, date, trigger, and evidence required.
• Keep the signed contract, monitoring log, approvals, and transaction records in access-controlled storage with backups. Limit access to sensitive operational information.
• Separate observation from approval: the person who monitors activity should not be assumed to have authority to authorize an unlock.
• Set reminders before each release and a separate follow-up check after it. Record “no change” checks too, so there is a continuous history.
• Have counsel review enforceability and governing-law provisions, and have a technical reviewer assess any on-chain lock. Do not treat either review as a substitute for the other.

Troubleshooting

The balance or address does not match. Recheck the network, token contract, decimals, and address character by character. Compare the balance at a specified block or timestamp, and document any discrepancy before changing the agreement or schedule.

A transfer occurs during the lock-up. Preserve the transaction hash, timestamp, wallet records, alerts, and relevant communications. Notify the designated parties through the agreement’s notice process, pause any further release if authorized, and consult counsel about the contractual response. Do not assume a transfer can be reversed.

A release condition is unclear or disputed. Do not release tokens based on an informal interpretation. Follow the agreement’s dispute or approval process, request the specified evidence, and obtain written direction from the authorized parties or qualified counsel.

A signer or key is unavailable. Follow the documented recovery, replacement-signer, or custodian procedure. Do not share or request private keys through email or chat. If no procedure exists, seek legal and technical advice before moving tokens or changing access controls.

An alert fails or the monitoring service is unavailable. Check the wallet directly using an independent source for the correct network, save the outage details, and resume checks as soon as possible. Add a backup reviewer or monitoring method and document any gap rather than implying continuous monitoring.

Frequently Asked Questions

Does a token lock-up agreement stop a transfer on-chain?
Not by itself in every arrangement. A contract can create obligations, but technical prevention generally requires an appropriate on-chain control or custody setup. Confirm the distinction with legal and technical reviewers.

What should a lock-up schedule include?
Include each wallet, token identifier, amount, restriction period, release date or trigger, approval requirement, and evidence of completion. Define time zone and how partial or rounded amounts are treated.

How often should locked wallets be checked?
Set a cadence that fits the agreement’s risk and release timetable. Check more frequently near unlocks or after a reported incident, and record the date and evidence for every review.

Can tokens be moved to a new wallet?
Only if the agreement permits it or the required written approval is obtained. Record the old and new addresses, verification, approvals, transaction hash, and updated monitoring details.

What records should be kept?
Retain the executed agreement and amendments, schedules, approvals, wallet and balance checks, alerts, transaction hashes, and notices. Store them securely and follow applicable retention requirements.

Related

• Bose SoundLink Max: Is It $25 Off?
• AI Provider Usage Dashboard Doesn’t Match Invoice
• AI Networking: How It Supports Large Language Models