How to Manage Locked Allocations and Vesting Across Wallets

To manage locked allocations across wallets you need three things in one place: a complete list of the wallets holding them, the vesting schedule attached to each allocation, and a calendar of the dates those allocations unlock or become claimable. Almost every failure comes from having one or two of those, but not all three.

Why locked allocations get mismanaged

• They are invisible in a balance. A tracker that shows total value without separating locked from liquid tells you a number you cannot act on.
• The schedule lives somewhere else. Usually a term sheet, a PDF, or a founder's memory.
• The wallets multiply. A deal wallet here, a claims wallet there, a personal wallet used once at 2am.
• Cliffs are lumpy. A cliff means nothing happens for months, and then something significant happens on one specific day. That is the day people miss.

A system that works

1. Enumerate every wallet, once, properly

Write down every address that holds or will receive an allocation. Include the ones you used once. This list is the foundation, and no tool can build it for you, because nothing on chain knows which addresses are yours.

2. Separate liquid from locked, always

Your portfolio view should never show a single blended number. Liquid value and locked value behave differently and answer different questions.

3. Attach the schedule to the allocation, not to a document

Cliff date, vesting start, vesting end, release frequency, and claim mechanism. If this lives in a PDF, it will be wrong within a quarter.

4. Put every date on one calendar

Unlocks, cliffs, claim windows, and distribution dates across every deal and every wallet. This is the artifact that actually prevents missed deadlines.

5. If capital is pooled, track member-level positions

When a syndicate holds a locked allocation, each member owns a pro-rata slice of something that is not yet liquid. Calculating that by hand at distribution time is how allocation errors happen.

What this looks like in Cryptool

Cryptool tracks vesting schedules and upcoming claims alongside total value and profit and loss, across every wallet and chain, non-custodially. For pooled capital, it calculates member allocations pro-rata, tracks individual positions inside a pooled wallet, and runs distribution workflows, so the locked slice each member owns is a tracked number rather than a quarterly calculation.

The Action Calendar collects the dates: funding rounds, vesting, claim windows, and syndicate milestones in one overview, so a cliff is something you see coming rather than something you discover.

What Cryptool does not do

Worth stating plainly, because you will find out anyway:

• Fundraising is chain-limited. Portfolio tracking and fund administration cover all chains and all wallet providers. Raises themselves currently run on BNB Chain, Ethereum, and MultiversX only.
• NFTs. Cryptool does not track NFT portfolios yet.
• Tax reporting. Not available yet. Use a dedicated tool such as Koinly or CoinTracker and treat Cryptool as the upstream source of transactions.
• KYC and automated compliance. Cryptool is not a compliance product. It gives you the audit trail and reporting, not the legal workflow.
• Automatic wallet detection. You add the wallets you want to track. Nothing is discovered for you.

Common questions

How do I track vesting across multiple wallets?

Enumerate the wallets, attach each allocation's schedule to the allocation itself rather than a document, keep locked value separate from liquid value, and put every unlock and claim date on a single calendar.

Why does my portfolio value look wrong?

Usually because locked allocations are being counted as liquid. A vested but unclaimed token and a freely tradable one are not the same asset for any decision you are about to make.

How do syndicates split a locked allocation?

Pro-rata against each member's contribution to the pool. The arithmetic is simple. The failure mode is doing it manually, in a spreadsheet, months after the deal, from a wallet list that is missing an address.