Deployed a new contract: 0xfcc7…e1f0
New contractSource-backed
Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.
The account that launched Tokyo Futuro’s token deployed 0xfcc7…e1f0 on 2026-11-02. Read from the chain; the creating transaction is the evidence.
Record ship:b7a75d3f… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.
Contract deployment, recorded on chain · no release names it
- What it names
- A new contract. The chain record names no capability.
- Stage
- A contract on chain. A deployment says nothing about whether anything uses it.
- Reported by
- Recorded on chain. Independently recorded: HEY read it from the chain, not from the team.
- Release and deployment
- Not established: no release text HEY holds names this contract. Timing alone never links a release to a deployment.
- Activity
- 0xfcc7…e1f0 (a contract the project’s deployer put up): 0 calls to its own functions and 0 ERC-20 token calls in 7 days to 2026-11-19. Whether calls succeeded is not measured. Calls come from addresses, not people.
- When
- The source dates it 2026-11-02 17:16 UTC; HEY first knew on 2026-11-03.
- Not known
- No source HEY holds names what this change does.
- Not established: no release text HEY holds names this contract. Timing alone never links a release to a deployment.
- Whether calls succeeded is not measured: failed transactions are not read.
Evidence: ship record
A contract record says what the chain shows about a contract. It is not a safety check, and it does not say who runs the contract.
