token standard hell

The problem with token standards in a multi-chain world is that there are several of them, they don't interoperate natively, and every new chain that launches adds another surface where the question 'which standard does this token use here' has a non-obvious answer. LayerZero's OFT standard, Hyperlane's HypERC20 standard, native ERC-20s with bridge wrappers, canonical versus non-canonical representations — the same asset can exist as different token types on different chains depending on the path it took to get there. Asset issuers making decisions about where to deploy their token are making simultaneous commitments about bridge security, liquidity fragmentation, and which standard to build around. Those decisions compose with each other in ways that aren't always clear at decision time.

What the Hyperlane standard offered was a different way to think about what 'the token' is. HypERC20 and HypERC20Collateral put the messaging and settlement logic inside the token contract itself, rather than layering a bridge on top of a token that didn't know about cross-chain operations. The result was a cleaner mental model for teams deploying across multiple chains: the token knew how to move itself. The tradeoff was the one that runs through all of this space — the team had to commit to the Hyperlane standard at the moment of deployment, and the liquidity and tooling that came with that commitment was only as deep as Hyperlane's ecosystem.