So, your token is being sent to a new blockchain…

Far from an elaborate crypto scam, the decision to carry out this process, known as a "token migration" or "token swap," has become increasingly popular among blockchain projects. Notably, two of the top 25 cryptocurrencies trading globally - Tron and EOS - are in the midst of such a transition, and at least two more top 30 tokens are expected to soon follow suit.

With millions – even billions – of dollars worth of tokens involved in each migration, the stakes are high. But despite this, the blockchain industry remains largely uninformed on token migrations and their implications. In a sampling of experts, CoinDesk found that even industry leaders were sometimes unable to answer basic questions about the process.

Nonetheless, much about token migrations can be discerned from those pioneering the shifts. For those who have undergone such transitions, they often represent a difficult but necessary step in realizing their project's vision.

For Shawn Wilkinson, founder of decentralized storage startup Storj, which started its token migration in 2017, the rewards simply outweighed the risks.

He told CoinDesk:

But why would a project need to complete a token migration in the first place?

Often, the shifts are carried out by projects that begin by using the ethereum blockchain to raise money and distribute their tokens. The tokens distributed at this phase typically act as "placeholders" for those that will eventually be used when the project is live.

One benefit of this strategy is that traders don't have to lock up this capital. Rather, they're able to exchange these placeholder tokens on exchanges while they develop their technologies.

Therefore, a "token migration" has come to describe the process by which token holders' balances are transmitted from their ethereum wallets to a given project's new compatible wallets. After the switch, tokens have effectively "moved" from one blockchain to another.

However, it's important to note that token migrations are not exclusively linked to live blockchain launches, and also take place when projects merely shift from one protocol to another.

For example, Storj's token migration was prompted by its decision to move from a bitcoin-based protocol to ethereum due to scalability issues.

"We became increasingly aware that if we didn't do [the token migration], the consequences would be pretty big," Wilkinson said.

For users and investors, the degree of their involvement in the token migration process varies - typically according to where they store their tokens.

For those who store their tokens on exchanges, it is unlikely that they will have to take any steps to participate in the migration. Major exchange Binance, for example, says it handles "all technical requirements" of the process for the EOS, Tron, ICON and Ontology migrations.

San Francisco-based exchange Kraken also aims to reduce the difficulty of the process.

"We pause funding ahead of the transition, swap all the old coins for new and when we resume funding, all the old balances are for the new coins," Kraken co-founder and CEO Jesse Powell explained. "It's really as simple as that."

However, users who store their tokens in wallets may need to initiate the process manually.

More specifically, they must undergo token registration, also called "mapping," in order to send their tokens from the previous blockchain to the new network.

In practice, this process typically entails generating a project-specific key (for example, an EOS key) and sending tokens to it from the key address where the tokens were initially stored after purchase, prior to the mainnet launch (for example, an ethereum key).

Projects typically implement cut-off periods by which users must swap their tokens. In projects such as EOS, these are 'hard' deadlines after which tokens on the old blockchain will be "frozen" and inaccessible to users.

Other projects allow for open-ended migration.

But despite exchanges' efforts to simplify token migrations, risk is not entirely diminished.

"I don't think there's any perfect way to do a token migration," Wilkinson said. "It's always a pain, it's always miserable, and there's always, not a small chance, a very hefty chance, that you could screw things up."

Dialogue with their communities is one way projects can mitigate a (thus far) common problem: a lack of awareness amongst token holders.

According to Wilkinson, despite initiating Storj's token migration in 2017, users are still migrating their tokens one year on. Storj has continued to support its token migration, but for projects with hard token freeze deadlines, token holders stand to lose their money if they are unaware of the migration process.

Perhaps the most significant risk associated with token migrations is that they are not "trustless" processes.

Instead, users must place their trust in those in charge of the project to implement the shift according to plan. However, because token migrations are relatively novel, there is often no blueprint for their execution.

For this reason, Wilkinson said, "A lot of the stuff around the [Storj] migration we built from scratch."

Though these risks are no small matter, they are not unexpected for such "bleeding edge" technologies, he added.

As for what projects currently undertaking token migrations should keep in mind, Wilkinson concluded:

Eggs via Shutterstock