Skip to main content
AVOID.NET
← AVOID.NET

Entity Graph

Browse extracted entities, relationships, and potential duplicates.

Total entities
29,475
Relationships
32,557
Potential duplicates
0

Entities

↯
Second alleged violent home invasion robbery in France; victim bound and threatened until ~$110,000 in crypto was surrendered.(2026-04-20:m1llionz-richmilly666)event
c8afbc63
↯
First alleged violent home invasion robbery in France; five attackers reportedly stole ~7.2 BTC (~$557,000); victims reportedly hospitalized.(2026-04-17:m1llionz-richmilly666)event
2835c85f
□
M1llionz (RichMilly666)organization
af89c6d9
◎
sideswap.iodomain
dd9c9adb
◎
blog.liquid.netdomain
2923518b
◎
bitcoin.frdomain
13b7c7ef
↯
Liquid Network resumes controlled block production at 12:26 UTC. Peg-in and peg-out operations remain suspended. Adam Back states Blockstream will cover the 1:1 L-BTC to BTC peg.(2026-09-10:sideswap)event
7a239bf9
↯
SideSwap publicly acknowledges two operational failures (an online authorization key with automatic same-block payouts, and no size/velocity/origin checks) and returns its approximately 4 BTC peg-out fee to the federation.(2026-09:sideswap)event
a7867aaa
↯
At block 965,950, 3,400 BTC is returned to the Liquid federation peg wallet by the actors. Approximately 598.5 BTC is retained.(2026-09-07:sideswap)event
650756ff
↯
At approximately 14:28 UTC, 3,996 BTC exits the Liquid federation reserve in a single transaction through SideSwap's PAK, collapsing reserves from ~4,205 BTC to ~202 BTC. Liquid Network halts transaction processing.(2026-09-06:sideswap)event
7ab87369
◎
cmfchile.cldomain
bf0c4dbb
↯
CMF issued a public notice reiterating that Orionx and its activities are not supervised by the Commission and that it is not overseeing any wind-down plan.(2026-09-08:orionx)event
91257a4f
↯
CMF confirms it is not supervising Orionx's closure or restitution process. Tether does not respond to media requests for comment.(2026-09-07:orionx)event
0e46c945
↯
Orionx suspends customer withdrawals and announces permanent closure of operations.(2026-09-03:orionx)event
c28a4f6f
↯
Orionx files criminal complaints against co-founders Roberto Zibert and Joaquin Diaz, alleging misappropriation of customer assets between 2018 and 2021. Both deny the allegations.(2026-09-02:orionx)event
dc77fa94
↯
Orionx COO Thomas Mac Millan identifies a significant mismatch between internal system balances and assets held in custody wallets.(2026-08-27:orionx)event
08c5f1ff
↯
Chile's CMF rejected Orionx's application for enrollment and authorization under the Fintech Law (Oficio Ord. N°104672), citing failure to provide audited financials and required client-protection collateral. Orionx said it would appeal.(2026-06-19:orionx)event
fc7434fc
↯
Tether announces it led Orionx's Series A funding round to accelerate digital asset adoption in Latin America.(2025-06-03:orionx)event
ced505e2
↯
Bitfinex made a strategic investment in Orionx (exact date in 2023 not confirmed in publicly available English-language sources).(2023-01-01:orionx)event
8084a720
↯
Alleged period of unauthorized asset transfers ends, per the criminal complaint. The complaint separately references transfer activity extending into 2021-2022.(2021-12-31:orionx)event
b70256b6
↯
Alleged period of unauthorized asset transfers from Orionx custody wallets begins, according to the criminal complaint filed by Orionx in September 2026. These are allegations; no court finding has been made.(2018-01-01:orionx)event
2137253d
□
Orionxorganization
3763ab30
◎
blog.jamestsetsekas.comdomain
e3942467
↯
Liquid Network resumes block production at approximately 12:26 UTC, initially without user transactions. Peg-in and peg-out operations remain suspended pending full reserve recovery.(2026-09-10:blockstream-liquid-network)event
b58390d2
↯
Blockstream releases Elements v23.3.4 emergency patch. Adam Back states the LBTC 1:1 peg 'will be covered.' Blockstream publicly rejects the bounty demand, stating it will not pay a ransom.(2026-09-09:blockstream-liquid-network)event
f5dfba96
↯
Attackers escalate demands, requesting a 10% bounty paid from Blockstream's corporate reserves, threatening permanent 15% loss for L-BTC holders if refused.(2026-09-08:blockstream-liquid-network)event
07965c50
↯
At approximately 16:09:25 UTC, attackers return 3,400 BTC to the Liquid Federation peg wallet, retaining approximately 598.5 BTC as a self-declared bounty.(2026-09-07:blockstream-liquid-network)event
417a4fc1
↯
At approximately 20:25 UTC, Blockstream disables bridge nodes and halts new peg operations after detecting the exploit.(2026-09-06:blockstream-liquid-network)event
90415866
↯
Vulnerability fix merged into the Elements main branch — four days before the exploit.(2026-09-02:blockstream-liquid-network)event
fe27204c
↯
Fix for the rangeproof verification cache-key collision vulnerability committed to the Elements open-source repository.(2026-08-03:blockstream-liquid-network)event
de6bb6d2
↯
Elements v23.3.3 released — the version running on federation nodes at the time of the exploit, predating the fix for the rangeproof cache vulnerability.(2026-04-13:blockstream-liquid-network)event
6d00e39b
◎
blockstream.comdomain
75133811
↯
Attackers began preparatory activity on the Liquid Network, conducting test transactions and seeding the range proof cache with 68 identical range proofs across 14 hours.(2026-09-04:liquid-network-blockstream)event
43f02341
↯
Liquid blockchain went live at 1:29 UTC with 23 founding federation members.(2018-09-27:liquid-network-blockstream)event
532881b1
↯
Blockstream publicly announced Liquid Network.(2018-10-10:liquid-network-blockstream)event
f94673a0
□
Liquid Network (Blockstream)organization
a404bc6e
↯
Blockstream publicly rejected the attackers' demand for a 10% bounty from company funds, characterizing the retention of 598.5 BTC as theft rather than responsible disclosure and stating 'We will not pay.'(2026-09-11:liquid-network-blockstream)event
ef12c893
↯
Liquid Network resumed block production at 12:26 UTC in a controlled mode. Peg-in and peg-out operations remained suspended. Blockstream CEO Adam Back publicly pledged that the L-BTC to BTC 1:1 peg would be maintained and covered.(2026-09-10:liquid-network-blockstream)event
f7849cee
↯
Elements software version 23.3.4 released with a patch hardening range proof cache keys against concatenation collisions.(2026-09-09:liquid-network-blockstream)event
cd2df547
↯
Security experts including Ledger CTO Charles Guillemet publicly rejected the white hat framing, characterizing the retained $47M as extortion. Bloomberg published analysis on systemic sidechain vulnerabilities exposed by the incident.(2026-09-08:liquid-network-blockstream)event
56c4244b
↯
Blockstream deployed an emergency patch to bridge nodes. Attackers returned approximately 3,400 BTC (~$270M, 85% of drained funds) to the federation multisig at 16:09 UTC. Approximately 598.5 BTC (~$47M) was withheld as a self-declared bounty.(2026-09-07:liquid-network-blockstream)event
a36a679c
↯
At 13:53 UTC (Liquid block 4,050,336), attackers minted approximately 4,000 unbacked L-BTC by exploiting a range proof cache collision in the Elements software. At 14:28 UTC, the federation processed a 3,996 BTC peg-out via SideSwap, draining approximately $320 million from the reserve. The Liquid Network was paused and bridge nodes disabled. Attackers posted an OP_RETURN message: 'we are whitehats. contact us on chain.'(2026-09-06:liquid-network-blockstream)event
32c07c63
↯
The vulnerability fix commit was merged into the Elements main branch. No production federation nodes had been updated to include the fix.(2026-09-02:liquid-network-blockstream)event
0a6bf2b2
↯
A fix for the rangeproof cache bug was publicly committed to the Elements GitHub repository with a descriptive commit title identifying the vulnerable code path.(2026-09-01:liquid-network-blockstream)event
2d6e7573
□
Liquid Network / Blockstreamorganization
64fa5580
↯
STONK reports an additional 21.91% intraday gain. Phishing domains including claim-stonkfun.xyz and stonkfun-proposal.xyz flagged by security services as active threats.(2026-09-10:stonk)event
4105e584
Data refreshes within about 10 minutes · All metrics derived from Supabase