Router Protocol Shutdown: September 30 Target Reached, Treasury Burn Still Needs Execution Verification
Router Protocol reaches the date it selected for completing its orderly wind-down: September 30, 2026 The project previously said all remaining operations would cease by this date and that it would permanently burn: 303,333,198 ROUTE held in treasury. At this reports publication cutoff, WikiBit has not identified sufficiently authoritative evidence confirming:the final burn transaction;every Router service has stopped;every integrator/relayer endpoint is offline. The correct status is therefore: Shutdown Target Today / Execution Verification Pending rather than automatically declaring the wind-down fully executed.Why Router is closing Router attributed the decision to long-term commercial pressure rather than one new exploit. The project described:persistent Web3 liquidity scarcity;capital shifting toward sectors such as AI;compressed cross-chain bridge fees;infrastructure operating costs;demand concentrating on fewer chains. It said efforts over the prior year to:commercialize technology;license technology;form partnerships;sell/acquire the business; did not produce a sustainable outcome.More than four years of cross-chain infrastructure Router built cross-chain infrastructure including:Router Nitro;messaging/execution tools;integrations across multiple networks;an earlier standalone Router Chain. The shutdown therefore creates both:token-holder risk;infrastructure dependency risk for developers.The 303,333,198 ROUTE burn Router says it will permanently destroy: 303,333,198 ROUTE held in treasury. This amount is roughly 30% of the approximately one-billion maximum-supply figure cited in project reporting. But the burn must be understood correctly.Treasury burn is not holder compensation The treasury-held tokens were not necessarily circulating in the market. Burning them:does
