PO

POE

Po.et

Possibly silent

Its final official update promised a roadmap the following week; no later publication appeared, code had already stopped, and the domain is gone.

Checked-channel clock

2,058complete dayssince the last verified official communication · through 11 Jul 2026This is not a project-wide silence date.
AssessmentPossibly silent

Strong lead; incomplete coverage

Clock interval2,058 days

Native timestamp precision

Overall confidencemedium

Minimum of identity, timestamp and coverage

Policy2026-07-11.1

Reviewed as of 11 Jul 2026

Concise conclusion

Its final official update promised a roadmap the following week; no later publication appeared, code had already stopped, and the domain is gone.

“Ghosted” is editorial shorthand only. The formal assessment is possibly silent, scoped to the channels and dates shown below.

01

Strongest supporting evidence

3 cited facts
01

The final item in the official Medium RSS was published 20 November 2020 at 17:30:50 UTC and promised a new roadmap and partnership the following week.

Official Po.et Mediumaccess blocked · 403
02

The latest default-branch project commit found across visible official non-fork repositories was recorded in February 2020.

02

Strongest counterevidence

Leading hypothesis attacked
C1

The final official post did not announce closure; it claimed a migration and partnership were imminent, so a private acquisition or unlinked rebrand remains possible.

Official Po.et Mediumaccess blocked · 403

03

Channel ledger

Separate clocks; separate failure modes
ChannelStatusLast verified activityEvidence
CommunicationOfficial Po.et Medium publicationsilent20 Nov 20202,058 complete daysOpen source ↗The official RSS feed contains no later item; X and Telegram remain incomplete.
Codepoetapp official non-fork repositoriessilent18 Feb 20202,335 complete daysOpen source ↗Latest default-branch project commit found across visible official non-fork repositories.
Websitepo.et and former explorerinaccessibleUnresolvedunknownOpen source ↗The domains did not resolve during review; DNS failure cannot date the last update.
X@_poetprojectnot exhaustively checkedUnresolvedunknownOpen source ↗Complete account history was not available, so the displayed clock is not asserted as the final possible message.

04

Alternative explanations

  • A1A private acquisition or unlinked successor may exist.
  • A2Open-source Po.et code can survive independently of the original team.

05

Unresolved unknowns

  • U1The complete @_poetproject X and Telegram histories were not available.
  • U2No first-party closure notice or verified successor was found.

Highest-value next checks

What would most reduce uncertainty?

  1. Obtain the complete X account archive by stable account ID and an authorized Telegram export.
  2. Search BTC Inc. corporate announcements and late-November 2020 archives for the promised roadmap.