Follow puts Kill Switch on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
UnknownThe project has a contract, but HEY does not count its calls yet: a token joins the watch once it takes calls in a thirty-day window, and any contract the project’s own sources name is watched. Unknown, not zero.
Contracts
Fact1 contract on record for code changes; latest change 15 days ago: Deployed a new contract: 0x9c83…2570.Source
Token market · context
Market data insufficientToken verified
Same name, different contract: 1 other published project uses the name Kill Switch and the ticker $KS. This page: its site kill-switch.site names 0xf4f7…51a0. Kill Switch: its site kill-switch.site names a different contract than 0x3d7b…3206. HEY does not say which is the real one — only what each project’s own sources name.
Not yet known
Unknown9 gaps: Repositories (no source), Releases (no source), Official docs (no source), Official site changes (not enough yet), Verified source (not enough yet), Contract interface (not enough yet), Current market (not enough yet), Market history (not enough yet), Supply distribution (not enough yet). No repository the project claims as its own.
“Active” by the activity rule: 1 meaningful event in the last 30 days, the newest 2026-10-03.
SourceHEY holds no repository, changelog or feed it can read for this project; the status rests on building events it counted from the chain or from corroborated sources.ReadRecordsDeployed a new contract: 0x9c83…2570What HEY derivedHEY’s activity rule reads the counted events as “Active”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Token verified: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedToken verified: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Market data insufficient.
Market data insufficient: HEY holds no market reading for the token.
Source1 reading from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Market data insufficient”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Market figures are context only and never change activity status. Methodology
Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 9 weeks before HEY began reading this project’s sources — not yet read, not zero.
Questions HEY can answer about Kill Switch — as of 2026-10-18
Is Kill Switch still being built?
DerivedActive: 1 meaningful event in 30 days; latest ship 15 days ago.Evidence →
What did Kill Switch ship last?
FactDeployed a new contract: 0x9c83…2570 — New contract, 15 days ago.Evidence →
Is 0xf4f7568A3abEfC7378D701DeD7366BF43Cb751A0 Kill Switch’s own contract?
FactToken verified: The project’s own site names this contract.Details →
What does HEY not know about Kill Switch?
Unknown9 gaps: Repositories (no source), Releases (no source), Official docs (no source), +6 more. No repository the project claims as its own.Details →
Build timeline
Deployed a new contract: 0xd658…cf06
New contract · Source verified
The account that launched Kill Switch’s token deployed 0xd658…cf06 on 2026-10-03. Read from the chain; the creating transaction is the evidence.