CryptoSlate
Allium says data delivery is operating normally across Snowflake, Databricks and BigQuery after it identified unauthorized access to certain systems on Oct. 25. But historical backfills remain underway, and passing checks on one warehouse does not confirm recovery across the others.
Why it matters
Raw and enriched tables for 18 named chains, including Ethereum, Solana, Bitcoin, Base and Arbitrum, passed Allium's completeness and freshness checks on Snowflake and Databricks. Hyperliquid remains under validation. Backfills for the affected period continue for other chains and for all chains on BigQuery.
Allium says some verified_until timestamps may look stale as automated re-verification is restored, and that the lag does not indicate missing data. Users should distinguish that timestamp issue from the historical backfills that are still in progress.
Market impact
For teams using Allium in research, reconciliation or product infrastructure, the relevant check is the specific warehouse, chain and historical window they rely on. The Oct. 28 update marks normal delivery, not a blanket confirmation that every historical record is complete.
Allium's recovery instructions call for replacing existing API keys and setting a new password, with multi-factor authentication recommended. New uploads and access to previously uploaded data remain temporarily disabled, limiting queries that depend on uploaded tables. Completion of the remaining backfills and validation will determine when historical coverage is fully restored.
Frequently asked questions
-
Does normal data delivery mean Allium has completed historical recovery?
No. Allium says historical backfills remain in progress, including for other chains and for all chains on BigQuery.
-
Which chains passed Allium's checks on Snowflake and Databricks?
Raw and enriched tables for 18 named chains passed completeness and freshness checks on those platforms. The update names Ethereum, Solana, Bitcoin, Base and Arbitrum among them.
-
Why might an Allium verified_until timestamp look stale?
Allium attributes the lag to automated re-verification being restored. It says the timestamp lag does not indicate missing data.
-
What credential changes does Allium recommend after the incident?
The recovery instructions call for replacing existing API keys and setting a new password. Allium also recommends multi-factor authentication.
-
Which Allium features remain restricted during recovery?
New uploads and access to previously uploaded data are temporarily disabled, preventing queries that depend on uploaded tables.
CoinDesk
Crypto Capital Venture
WuBlockchain
TheBlock
CoinTelegraph
Lookonchain