If a legacy integration names a supported destination chain, RenBridge enabled only the asset routes and token deployments available in that release; the application still had to accept the exact output token on that chain. For a Bitcoin route, the input was native BTC on Bitcoin and the output was renBTC on a host chain, not native Bitcoin inside the application. A supported chain name alone could not make every asset usable by every app there.
Chain support identified routes and deployed tokens
A supported chain offered a destination for particular source assets, with gateway and token contracts deployed for those routes. In a RenBridge integration, the network list showed where a selected asset could arrive. Code that handed a deposit to RenBridge still needed to know which wrapped token would arrive before deciding what the application could accept.
The deployment documentation lists gateway contracts separately from the token contracts representing assets on host chains. Ethereum, Polygon, Avalanche, and BNB Chain appeared as historical destinations, but their presence did not promise every asset on every chain. renBTC, renBCH, renZEC, and renDOGE represented different source assets. Their similar names did not establish identical deployment coverage: the relevant gateway and token had to exist for the asset and destination in the release being examined.
The gateway produced a token that the app had to accept
The route took a supported source asset and destination details, then produced the corresponding wrapped asset. On a BTC route, a user sent native BTC on Bitcoin. RenVM authorized the mint after the deposit was processed; the host chain’s gateway verified that authorization and minted renBTC through its associated token contract. Burning the wrapped token was the reverse leg for releasing the source asset. Neither step made the destination application accept renBTC automatically.
Suppose an engineer sees Polygon in an old supported-network list and passes a Bitcoin deposit into an app’s “BTC” flow. The route might deliver renBTC on Polygon, while the app’s deposit function accepts a different token contract. The bridge transaction can succeed and the application call can still fail. A matching ticker, wallet address format, or chain name cannot settle compatibility; the destination chain and token contract address must match what the app’s code accepts.
Application logic sets the final boundary. It may receive the minted token directly or handle a later transfer, but it must recognize that token and make the intended contract call. The integrator also selects the correct chain, supplies destination details, and funds the transactions on the networks involved.
Release and network details define the legacy boundary
The historical release and operating network determine what an old support claim meant. Read the application’s chain identifier alongside its gateway lookup, token address, recipient, and call path. Those details show whether the code expected a direct mint into an application contract or a token transfer followed by a separate action. They also expose assumptions hidden by a short “supported networks” list.
The 2022 sunset notice matters when interpreting a RenBridge shutdown-era integration: a contract that remains deployed proves a historical address existed, not that the original service still operates. Describe the integration as a supported source input, a specific wrapped output on a named chain, and an application call that accepts that output. Those separate requirements explain both what chain support enabled and where it stopped.