When was the shutdown decision made?
Publish the decision date and the timeline of user communications, including XP updates and builder outreach.
Find your first interaction. Put your days on the record.
Ask for an explanation that lasts longer than the roadmap.
Preparing your PNG…
This draft stays private until you choose to publish it. Your export includes transaction links, dates, calculation details, your words, and chosen sources.
Screenshots stay on your device and go into the downloaded file. They are not uploaded to this site. Check them for private information before sharing the pack.
They counted their losses. Let’s put our time on the record.
Loading the shared ledger
Each voluntarily added wallet counts once. We add its whole days since the earliest transaction we could verify, up to the wind-down notice on 6 October 2026. The endpoint stays fixed as more people join. This is combined wallet age, not active time or a verified measure of time stolen. Several wallets may belong to one person. Partial histories can miss older activity.
Find your receipt to add your days ↗
The ledger starts with us. Add the first receipt and make your voice count.
| Wallet | First interaction | Days | Your voice |
|---|
No wallet needed to speak up. Your message won’t change the days total. Start with what you expected, what happened, and the answer you need.
Reactions are anonymous browser signals. “Helpful receipt” is a reader’s opinion, not verification.
Transaction history is checked. Wallet ownership and personal experiences are not verified. Participation is optional; searching or opening an X draft never adds you automatically.
Follow an answer. Keep a dated record. Come back for the next development.
Following and read state are saved on this browser. New community voices are personal accounts, not reviewed updates.
Trust went in. The wind-down came out. If you no longer trust Luca Netz or Pudgy Penguins, put your experience on the record—and keep the receipts.
Back the questions you want answered. These are anonymous browser signals, not a count of distinct people.
Publish the decision date and the timeline of user communications, including XP updates and builder outreach.
Identify the official wording on rewards and explain what happens to XP and badge records.
Separate chain revenue, Portal or app fees, operating costs, and recipients. Company losses don’t describe every user’s cost.
Compare dated outreach and commitments with the shutdown decision and the migration support actually provided.
Publish the original commitments, what was cancelled or transferred, and the current status.
Clarify responsibility for funding, the token decision, public communications, and the wind-down.
Clarify route deadlines, unsupported assets, pending transactions and the availability of support.