NA

NAS

Nebulas

Unresolved

Late-2024 code is real, static sites remain online, and backend failures may be temporary; a dead-project verdict would be premature.

Checked-channel clock

591complete dayssince the latest checked project commit · through 11 Jul 2026This is not a project-wide silence date.
AssessmentUnresolved

Evidence conflicts or is incomplete

Clock interval591 days

Native timestamp precision

Overall confidencelow

Minimum of identity, timestamp and coverage

Policy2026-07-11.1

Reviewed as of 11 Jul 2026

Concise conclusion

Late-2024 code is real, static sites remain online, and backend failures may be temporary; a dead-project verdict would be premature.

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

01

Strongest supporting evidence

3 cited facts

02

Strongest counterevidence

Leading hypothesis attacked
C1

Multiple official web surfaces remain online and late-2024 maintenance is much newer than the project's old communication feeds.

Official website leadlive · redirected

03

Channel ledger

Separate clocks; separate failure modes
ChannelStatusLast verified activityEvidence
Codenebulasio/wiki default branchsilent26 Nov 2024591 complete daysOpen source ↗A genuine late-2024 project commit; all repositories and branches remain to be enumerated.
WebsiteNebulas official web surfacesreachable unverified freshnessUnresolvedunknownOpen source ↗Multiple static surfaces returned HTTP 200, while an explorer data endpoint returned 502.
NetworkExplorer and mainnet APIunresolvedUnresolvedunknownOpen source ↗Backend failure and timeout do not prove the chain stopped; independent node checks are required.
CommunityX, Telegram and Chinese channelsnot exhaustively checkedUnresolvedunknownOpen source ↗Communication histories were not completely enumerated.

04

Alternative explanations

  • A1The explorer/API failure may be temporary, geographic or edge-network related.
  • A2The chain may still produce blocks even if public infrastructure is broken.

05

Unresolved unknowns

  • U1Current chain height, timestamp and independent validator count are unresolved.
  • U2Official X, Telegram and Chinese-language histories remain incomplete.

Highest-value next checks

What would most reduce uncertainty?

  1. Query multiple independent Nebulas nodes and record current chain height and validator activity.
  2. Enumerate all organization repositories and official communication channels.