Concise conclusion
Old code and an inactive listing are strong leads, but public communication histories remain incomplete.
“Ghosted” is editorial shorthand only. The formal assessment is possibly silent, scoped to the channels and dates shown below.
01
Strongest supporting evidence
The checked staking-contract default branch records a last commit on 8 June 2019 at 15:25:46 UTC.
CoinPaprika currently marks BNTY inactive and lists the historical website, X and repository links.
02
Strongest counterevidence
The historical website still responds. That keeps open the possibility of a maintained static service, although it does not establish recent communication.
03
Channel ledger
ChannelStatusLast verified activityEvidence
Codebounty0x/StakingContract default branchsilent8 Jun 20192,589 complete daysOpen source ↗The organization's repository metadata has a later push timestamp, so branch, tag and force-push history need reconciliation.
Websitebounty0x.iostale or unchangedUnresolvedunknownOpen source ↗The page responds and contains historical copy; uptime and copyright text are not publication timestamps.
X@bounty0xnot exhaustively checkedUnresolvedunknownOpen source ↗No complete timeline was available for this review.
04
Alternative explanations
- A1The product may have entered feature-complete maintenance with little public code activity.
- A2Team communication may have moved into a private or unindexed community.
05
Unresolved unknowns
- U1The latest substantive first-party post or community response is unresolved.
- U2The discrepancy between repository pushed_at metadata and the default-branch commit history is unresolved.