Silverhand Buys 0.5.0
GitHub releaseSource-backed
Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.
Everything since 0.2.0: 0.3.0, 0.4.0 and 0.5.0. 0.5.0 · 🚨 DEV SELL: when the token's creator (the Pons deployer, the Flap or pool token's creator) sells, the post is marked DEV SELL and its wallet line says how much of the creator's bag went and what they still hold. Dev sells… Show allShow less
- Everything since 0.2.0: 0.3.0, 0.4.0 and 0.5.0. 0.5.0
- 🚨 DEV SELL: when the token's creator (the Pons deployer, the Flap or pool token's creator) sells, the post is marked DEV SELL and its wallet line says how much of the creator's bag went and what they still hold. Dev sells are posted in every chat of the token, also with sells off and under the chat's minimum, and never merged into other sells. A sale through a router or a trading bot counts: it is told by the creator's own Transfer in that transaction. Pool and Flap tokens cost no extra request (their Transfers are read anyway)…
Record ship:b7e6486d… · HEY counts it as building; it does not judge the release’s quality.
Release, read from the team’s GitHub · no deployment linked
- What it names
- The team’s release names it: “Silverhand Buys 0.5.0” (v0.5.0).
- Stage
- A release is code the team published; HEY has not observed it deployed unless a link below says so.
- Reported by
- Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
- Release and deployment
- Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
- Activity
- No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
- When
- The source dates it 2026-10-18 23:52 UTC; HEY first knew on 2026-10-19.
- Not known
- HEY does not hold the commit the release was cut from.
- HEY has not observed a deployment of this change.
- Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
Evidence: ship record
A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.