GE

GEIST

Geist Finance

Explicitly ceased

Geist publicly said it would not reopen after the Multichain loss; a generic page at the old domain does not reverse that closure.

Cessation clock

1,092–1,093complete dayssince the official closure announcement · through 11 Jul 2026
AssessmentExplicitly ceased

Cessation supported by a primary source

Clock interval1,092–1,093 days

Source gives a date, so a range is preserved

Overall confidencehigh

Minimum of identity, timestamp and coverage

Policy2026-07-11.1

Reviewed as of 11 Jul 2026

Concise conclusion

Geist publicly said it would not reopen after the Multichain loss; a generic page at the old domain does not reverse that closure.

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

01

Strongest supporting evidence

3 cited facts
01

The official Geist Finance X account announced on 14 July 2023 that the protocol would not reopen after Multichain's loss became unrecoverable.

02

Strongest counterevidence

Leading hypothesis attacked
C1

Withdraw-and-repay-only contracts may remain usable, and a current page exists at the old domain; neither establishes protocol reactivation or original-team control.

03

Channel ledger

Separate clocks; separate failure modes
ChannelStatusLast verified activityEvidence
CommunicationOfficial @GeistFinance X accountceased14 Jul 20231,093 complete daysOpen source ↗The official thread stated the protocol would not reopen after Multichain confirmed funds would not be recovered.
Codegeist-finance visible repositoriessilent15 May 20221,518 complete daysOpen source ↗Last official default-branch commit found.
Websitegeist.financeidentity uncertainUnresolvedunknownOpen source ↗The current page describes the protocol as inactive but includes generic recent SEO content; original-team ownership is unverified.

04

Alternative explanations

  • A1The current domain may be maintained by a third party or for informational/SEO purposes.

05

Unresolved unknowns

  • U1Current domain ownership continuity with the former team remains unverified.

Highest-value next checks

What would most reduce uncertainty?

  1. Verify domain ownership lineage and archive the complete official shutdown thread.