Fletcher

FLTC and other blockchains

A learning page. Which other blockchains could FLTC reach, how that works, what it would cost a small token, and what can go wrong. Nothing here is a plan or a promise, and it isn't a reason to buy.

Where things stand today 13 Oct 2026

FLTC lives only on NEAR: fltc-af549c.launchpad.justhoot.near. There is no official FLTC on any other chain. People on other chains can already pay for FLTC through Intents, but the token itself stays on NEAR. That is covered on Buying FLTC from another chain, so this page doesn't repeat it.

1. Two ways to be "on" another chain

A token is just a record in one contract on one chain. "Moving" it to another chain never really moves it. One of these happens instead:

One important detail: FLTC's 0.1% fee, burn and holder share are written into the NEAR contract. A wrapped copy on another chain is a plain token there. Trades of the copy would not run FLTC's fee rules. Only trades on NEAR do.

2. The options, one by one

RouteReachesFor FLTC today
NEAR Intents (JustHoot Fast Intents)Pay from 15+ chainsWorks now. FLTC stays on NEAR. Details
Omni BridgeEthereum, Base, Arbitrum, Polygon, BNB Chain, Solana, Bitcoin, Zcash, and more in its SDKTechnically possible, not set up. No FLTC copy exists (checked 11 Oct 2026).
Aurora (NEAR's EVM)Ethereum-style apps running on NEARPossible in principle, not set up. Little reason without a pool there.
Rainbow Bridge (original)Ethereum, AuroraRetired. Replaced by Omni Bridge.
Wormhole, other bridgesMany chainsNot a direct route for NEP-141 tokens like FLTC. Wormhole works as a part inside Omni Bridge.

Omni Bridge

Omni Bridge is NEAR's official bridge and the successor to the Rainbow Bridge. Going out from NEAR, it uses Chain Signatures: a network of NEAR validators jointly signs the transaction on the other chain (this is called MPC, multi-party computation). Coming back to NEAR, it checks the other chain with a light client (Ethereum, Bitcoin, Zcash) or with Wormhole messages (Solana, Base, Arbitrum, Polygon, BNB).

For a token that starts on NEAR, putting a copy on another chain takes four steps in the bridge tools: log the token's details on NEAR, wait for a proof, deploy the copy on the other chain, then "bind" it back on NEAR. Anyone with the know-how could run those steps; it doesn't need permission from NEAR. But a copy with no pool and no holders is just an empty contract.

Aurora

Aurora is an Ethereum-compatible chain that runs on top of NEAR, so wallets like MetaMask and Ethereum-style apps can use it. Aurora has its own built-in link for NEAR tokens, separate from the bridges to other chains: anyone can ask Aurora's engine contract (aurora) to create an ERC-20 twin of a NEAR token. Sending FLTC to Aurora would then lock it on NEAR and mint the twin; sending it back burns the twin and releases the FLTC. These moves happen inside NEAR in one transaction, not through an outside bridge. To show the right name and logo in apps, the token's details also have to be submitted to the Aurora team.

Aurora's activity in meme tokens is small, and there's no FLTC pool there, so a twin would have nothing to trade against. Fee rules still wouldn't apply to trades of the twin.

Rainbow Bridge

The original Rainbow Bridge (NEAR, Ethereum, Aurora) was archived in 2025, and new deposits stopped. Its job now belongs to Omni Bridge. If someone tells you to "use the Rainbow Bridge" for FLTC, that's out of date.

Wormhole and other bridges

Wormhole is a large messaging network between chains. NEAR tokens don't go through Wormhole's own token portal; instead Omni Bridge uses Wormhole as one of its checking systems. Other bridges and "cross-chain" services mostly support big tokens like USDC, ETH or NEAR, not small launchpad tokens.

3. What a small token would actually need

  • A pool on the new chain. A copy can only be traded if someone puts both the copy and another coin into a trading pool there. That money is split away from the NEAR pool.
  • Gas on two chains. Deploying and bridging costs fees on NEAR and on the other chain. On Ethereum mainnet that can be noticeable; on Base, Arbitrum or Solana it's usually small.
  • Listings and trust. Wallets and price sites won't show the copy as "FLTC" until they verify it. Until then it looks like any unknown token, which is exactly what scams look like too.
  • Upkeep. Someone has to watch the bridge, answer questions and keep the official addresses list current.

4. Risks, with real examples

  • Bridges get hacked, and the losses are big. Ronin bridge (March 2022, about $624M), Wormhole (February 2022, about $326M, later replaced by its backer Jump), Nomad bridge (August 2022, about $190M) and Multichain (July 2023, about $126M) are well-known cases, using rekt.news figures. Closer to home, NEAR Intents had an incident on 30 Sept – 1 Oct 2026, listed at about $3.87M (see the note). If a bridge's locked tokens are stolen, every wrapped copy can become worthless.
  • Fake wrapped tokens. Anyone can create a token called "FLTC" on any chain in minutes. The name means nothing; only the contract address does. Check an address.
  • Split liquidity. Spreading a small pool across chains makes every pool thinner, so prices jump more and trades get worse for everyone.
  • The fee rules don't travel. As explained above, trades of a copy elsewhere wouldn't feed FLTC's burn or holder share.

5. My honest take

For a small community token, Intents already gives people on other chains a way in, while FLTC and its rules stay on NEAR in one place. Making copies on other chains would add cost, split the pool, add bridge risk and open the door to confusion with fakes. So I'm not planning it. If that ever changes, I'll explain why here first and list the exact official address of any copy.

Sources

Last checked 13 October 2026.