Time Farm News

ChronoTech — Path Forward: Consolidating to Ethereum
Following our 22 April incident update, the team has made a final decision on remediation. We are publishing it now so the community has the same information our exchange partners do.
Where we stand right now
• The compromised BNB Chain TIME contract has been isolated. The fraudulent tokens cannot leak across networks — TimeBridge is decommissioned and there is no live path between chains.
• Trading has been suspended on exchanges in coordination with our listing partners. This is deliberate and temporary, intended to prevent the fraudulent BSC tokens from being arbitraged out into honest order books while we execute the consolidation.
• TIME supply on Ethereum was never affected by the exploit and remains untouched.
The decision: retire BSC and Polygon TIME, consolidate on Ethereum
We have decided not to rebuild a cross-chain bridge for TIME and not to maintain TIME deployments outside Ethereum. Instead:
• The BNB Chain and Polygon TIME contracts are being retired permanently. The fraudulent 519,000 TIME on BSC, the legitimate BSC-side balances, and the Polygon-side balances are all on contracts we will no longer support.
• TIME continues as a single-chain Ethereum-native asset at its original contract: 0x485d17A6f1B8780392d53D64751824253011A260 .
• Total supply returns to the original 710,110 TIME — the figure on every historical tokenomics document since launch. The exploit-inflated BSC supply is excluded from circulating and total supply going forward.
• Legitimate BSC and Polygon TIME holders (i.e. holders whose balances pre-date the exploit and were not part of the attacker flow) will be made whole on Ethereum on a 1:1 basis through a snapshot-and-claim process. Snapshot blocks and the claim portal will be published in a follow-up announcement.
Why this path
A bridge rebuild and continued multi-chain deployment were on the table, and we drafted full specs for both. We chose against them. The honest read is that multi-chain TIME is not load-bearing for the product roadmap — LaborX, the AI-agent execution layer, and any future product surface can settle on a single chain. Retiring the BSC and Polygon contracts removes the entire class of vulnerability that was exploited on 22 April. One contract, one chain, one supply number that ties out.
Trading resumption
Trading will resume on partner exchanges once:
1. The Ethereum contract is confirmed by listing teams as the single canonical TIME contract.
2. The BSC and Polygon TIME tickers are delisted or migrated by each venue.
3. The snapshot-and-claim process is live for legitimate BSC and Polygon holders.
We are working through this with each exchange directly. We will not give a date we cannot keep — the resumption window will be named in this channel only once it is confirmed by venues.
What this does and does not change
• Total supply: unchanged at 710,112 TIME.
• Contract on Ethereum: unchanged.
• Holders on Ethereum: no action required.
• Holders on BSC and Polygon: do not trade or move your TIME. Wait for the snapshot announcement. Any movement of legitimate BSC or Polygon TIME after the respective snapshot block will not be eligible for the Ethereum claim.
• Exchanges: paused, coordinated, will resume on the schedule above.
Next update
When ready, we will publish:
• The snapshot blocks on BSC and Polygon.
• The eligibility criteria distinguishing legitimate holders from attacker flow.
• The Ethereum claim portal URL.
• The list of partner exchanges resuming trading.
These will be released as each piece is confirmed, rather than bundled to a deadline. We would rather publish less and have it be accurate than publish on schedule and have to walk it back.
Thank you for your patience. The decision to consolidate to Ethereum rather than rebuild the bridge or maintain multi-chain deployments is a hard one, but it is the cleanest possible answer to the question “is TIME safe to hold?” going forward. One chain, one contract, one supply number.
— ChronoTech team

1❤92🤯17👌9🔥7👾7

19.9K views09:33