Check Vesting Dates Before You Bridge a Token

Before bridging a vesting token, check whether the destination balance will stay locked and which contract controls its release. A bridge can move a token or create a destination-chain representation without moving the vesting contract or its schedule.

The key question is whether you are transferring tokens you can use now or a claim that remains subject to the original release terms.

Bridges commonly lock or burn tokens on one chain and release or mint a corresponding representation on another, though designs vary. If the tokens are held in a vesting contract, you may not be able to transfer them directly; the bridge may support only the freely transferable balance. Some systems instead bridge a receipt or claim whose rights depend on separate contract rules.

For a Manta-specific route, the fuller manta bridge guide covers the transfer details this overview only touches. Whatever the route, a matching ticker or token name on the destination chain does not establish that the same vesting terms apply.

Does bridging change when my tokens unlock?

It depends on how the token and vesting contracts are designed. If the original vesting contract keeps custody, its release schedule may continue on the source chain while the bridge handles only transferable tokens. If the project has built cross-chain vesting, the destination contract may instead check messages or release instructions tied to the original schedule.

Check the schedule’s start date, cliff (the point before which nothing unlocks), release intervals and beneficiary address. Then verify whether those terms apply to the destination token or only to the source-chain allocation. A bridge transfer by itself is not proof that a lock has ended or that a destination balance is claimable.

What should I check before sending?

Use the project’s official token and vesting documentation, then compare it with the bridge’s supported-token list and the relevant contract details. Before confirming, check:

• Whether the bridge accepts the exact token contract, rather than a token with the same ticker.
• Whether the balance you want to send is transferable or still held by a vesting contract.
• Which token contract and balance will appear on the destination chain, and whether they are locked.
• Whether the vesting schedule keeps its original dates, restarts, or requires a separate claim.

Also account for the source-chain transaction fee, any bridge fee and the cost of a destination transaction if claiming or moving the received tokens requires one. Fees and processing times depend on the route and network conditions, so review the quoted amount and status before proceeding. If the contracts do not clearly explain what happens to the vesting rights, pause and ask the project for the specific contract addresses and release rules.

Can I use the tokens as soon as they arrive?

Only if the destination balance is transferable and the project’s rules allow it. A bridge may deliver a wrapped or separately issued token that trades differently from the original, or it may deliver a locked position that cannot be sold or moved until its release conditions are met. Check the destination contract and wallet balance rather than relying on a completed-transfer notice.

For most holders, the safer choice is to bridge only after confirming that the exact allocation is supported and how its release date is enforced. If the goal is simply to wait for an unlock, keeping the allocation in the vesting contract may be clearer than moving it across chains.