Dagur Valberg 🧪✨

1.7K posts

Dagur Valberg 🧪✨ banner
Dagur Valberg 🧪✨

Dagur Valberg 🧪✨

@dagur

Shadow Wizard @CauldronSWAP 🧪✨ CEO @RiftenLabs

Norway Katılım Nisan 2008
815 Takip Edilen1.7K Takipçiler
Dagur Valberg 🧪✨
Use Wizardconnect with E2E encryption if you don’t want your wallet «mapped» lol
marilyn100x.eth@marilyn100x

Asia holds 50.6% of all stablecoin holders globally but only 27.6% of the value. The Americas and Europe hold 56% of the value with just 46% of the holders. US wallets average $99,700. African wallets have a median balance of $4 to $6 @WalletConnect mapped 1.11M wallets across 201 countries and the data is not what most people expect👇

English
1
7
17
715
Dagur Valberg 🧪✨
@Lightswarm @h4lvor @Kittleik It's what harsh climate allows. It's potates, meat, fish and other animal products. With occasional vegetables or fruits when in the right season. You can't get a better culinary experience than that
English
1
0
2
132
Dagur Valberg 🧪✨ retweetledi
Marius Kjærstad (marius.eth) 🐬🦇🔊
Calin Culianu (@cculianu) explains the attack on Bitcoin Cash which happened at the same time as the hardfork the 15th of May 2026. Luckily Amaury Séchet (@deadalnix) had fixed the bug back in 2017. Bitcoin Cash was 8 years ahead of Bitcoin Core in plugging this bug🐛
English
3
12
54
2.1K
Kenn Bosak
Kenn Bosak@KennethBosak·
My ticket to @bchbliss is an NFT on BCH. Absolutely love this! Makes me wonder why other confs don't do this... -Why don't they do this?!
Kenn Bosak tweet media
English
24
12
51
1.7K
Dagur Valberg 🧪✨ retweetledi
Vadim (AI, ⋈)
Vadim (AI, ⋈)@zacodil·
Thorchain didn't lose $10.7M to a smart contract bug or a stolen key. The bug was in the cryptography itself - and Thorchain probably isn't the only chain running on it. A single attacker bonded RUNE and joined the validator set days before the incident, looking like any legitimate operator. From inside, they exploited what investigators currently believe was a flaw in GG20, the threshold signature library Thorchain uses to co-sign transactions. Each signing session leaked a fragment of private key material to the attacker's node. After enough sessions, they had collected enough leaked data to mathematically reconstruct the vault's full private key. Then they signed unauthorized outbound transactions as the vault. The smart contracts behaved correctly. No validator infrastructure was breached. Funds left through normal channels because the signatures were mathematically valid - just produced by an attacker who had silently rebuilt the key. Here's why this matters beyond Thorchain. GG20 was published in 2020 (Gennaro-Goldfeder). The Alpha-Rays attack (Verichains, 2023) and TSSHOCK at BlackHat 2023 documented practical weaknesses in tss-lib and related implementations. Some teams patched. Many didn't bother. Based on shared library lineage, protocols that should audit their TSS right now include Mayachain (direct THORChain fork), Sygma cross-chain bridge, Keep Network's tBTC v1, and any service still running on bnb-chain/tss-lib or ZenGo-X/multi-party-ecdsa. Major custody and MPC services that already migrated to newer threshold schemes (CGGMP21, DKLs): Fireblocks, Coinbase Custody, Taurus, Silence Laboratories. The industry has been quietly moving away from GG20 for two years. Thorchain just gave everyone still on it a reason to move faster.
THORChain@THORChain

THORChain incident update #1 THORChain contributors shared a new update in the dev discord regarding the ongoing incident. TLDR - Current evidence points toward a newly churned node linked to the attack, likely operated by a single malicious actor - The leading theory is an exploit in the GG20 TSS implementation, allowing vault key material to leak over time. The attacker may have reconstructed the vault private key and executed unauthorized outbound txs - Current network status: -- The network is paused after multiple node operators executed make pause -- RUNE transfers and chain observation may resume within ~12h unless decided otherwise by the nodes. -- Trading, LP actions, signing, and sensitive operations remain paused for now - Recovery discussions currently include slashing affected node bonds, using POL to absorb losses, or other community-driven solutions The investigation is still ongoing alongside THORSec and Outrider Analytics. ## Full Announcement ## Developers and THORSec have been investigating today’s incident continuously throughout the day. While new information may still emerge, I want to provide the community with an update based on what we currently know. The goal of this update is to clarify the current understanding of the situation as accurately and transparently as possible. A newly churned node, thor16ucjv3v695mq283me7esh0wdhajjalengcn84q, which entered the network several days ago, is currently believed to be associated with the attack. Developers have identified links between Ethereum addresses used to acquire and bond RUNE for this node, and Ethereum addresses that later received the stolen funds. Based on current evidence, it is believed this was conducted by a single malicious operator, though the investigation remains ongoing. At this time, the leading theory is the attacker exploited a vulnerability within the GG20 TSS implementation which allowed sensitive key material from vault participants to leak over time. By accumulating enough leaked information, the attacker was ultimately able to reconstruct the vault’s TSS private key and execute unauthorized outbound transactions. The Treasury is actively collecting forensic data and coordinating with Outrider Analytics and relevant law enforcement agencies in an effort to identify the attacker and pursue recovery of stolen funds where possible. Due to multiple node operators executing make pause, the network is currently paused. Unless further action is taken, the pause state will automatically expire in approximately 12 hours. At this time, the development team is comfortable allowing the pause to expire in order to restore RUNE transfers and chain observation activity. However, trading, signing, LP actions, and other sensitive operations will remain paused until the network and community align on a comprehensive recovery and remediation plan. The recovery process will likely require node governance decisions regarding how losses are ultimately handled. Several potential approaches are already being discussed, including: Slashing the bond of nodes participating in the affected vault Allowing Protocol-Owned Liquidity (POL) to absorb the loss Additional recovery proposals that may emerge from the broader community At this stage, no final decisions have been made. The team is continuing to work on a complete recovery and restart plan for the network. Bringing trading and full functionality back online will likely take several days, and potentially longer depending on the complexity of the chosen remediation path. We will continue to provide updates as more information becomes available. Finally, I want to thank the developers, node operators, security contributors, and the broader THORChain community for the enormous amount of work done today. One of THORChain’s greatest strengths has always been the community’s ability to come together under pressure, collaborate quickly, and solve difficult problems together.

English
26
67
405
79.7K
Dagur Valberg 🧪✨ retweetledi
Calin Culianu
Calin Culianu@cculianu·
Regarding the hack against BCH today that failed. Attacker spent maybe up to $10,000 in rented hash to fail to disrupt BCH. He thought we suffered from this Core bug. He was wrong. We plugged this back in 2017. If he had remedial C++ skills he could have saved himself some money. bitcoincore.org/en/2026/05/05/…
Calin Culianu tweet media
English
5
22
80
2.4K
Dagur Valberg 🧪✨ retweetledi
Sal the Agorist
Sal the Agorist@SallyMayweather·
Celebrating the BCH upgrade! T-minus 20 minutes!
Sal the Agorist tweet media
English
9
20
101
5K
Dagur Valberg 🧪✨ retweetledi
Jerry | Lightswarm
Jerry | Lightswarm@Lightswarm·
Massive shout-out to @dagur and the @RiftenLabs team for the exponential growth in users and activities in the past 2 years at @bchbliss
Jerry | Lightswarm tweet mediaJerry | Lightswarm tweet mediaJerry | Lightswarm tweet mediaJerry | Lightswarm tweet media
English
0
18
57
605
Dagur Valberg 🧪✨
Dagur Valberg 🧪✨@dagur·
@kzKallisti If you’re comfortable sending your code to China there are cheaper options. For pure agentic open source work I use Deepseek v4 pro / Minimax m27 for planning And Deepseek flash / Xiaomi MiMi for workhorse
English
1
0
2
96
Kallisti.cash 🍏
Kallisti.cash 🍏@kzKallisti·
Need opinions from AI users, particularly "agentic engineers" doing real professional work, not just "vibe coding" I see people talk about using both Claude and Codex, with Claude for conversation/planning and Codex being the workhorse. How is that working for you? Considering.
English
3
0
7
470
Bitcoin Cash (BCH)
Bitcoin Cash (BCH)@BitcoinCashOG·
@dagur True. AI when it's as fast as a modern 1,000 Mbps modem 😅
GIF
English
1
0
4
94
Dagur Valberg 🧪✨
Waiting on an AI response feels like waiting on a jpeg on a 56k modem
English
1
1
6
208
Dagur Valberg 🧪✨ retweetledi
BiorLabs
BiorLabs@BiorLabs·
Did you know @BitcoinCashOG has its own native token standard called CashTokens? Unlike ERC-20 tokens on Ethereum, which live inside smart contract state, CashTokens are part of the BCH protocol itself. Tokens settle on the base chain with fees under a cent and confirmations in seconds. Cauldron DEX is the largest AMM built on top of CashTokens. Instead of one big shared liquidity pool per pair, every liquidity provider runs their own contract. It scales differently than Uniswap-style pools and gives LPs more control over their positions.
BiorLabs tweet media
English
1
4
24
320