We're giving away a Hogwarts Legacy custom wrapped NVIDIA GeForce RTX 5090 to celebrate its official release with DLSS 5 🪄
To enter:
🟢 Share this post
🟢 Comment #RTXON
Terms and Conditions: nvidia.com/en-us/geforce/con…
> Engineer A from Wallet DevOps downloaded a tampered Homebrew installation in order to install a popular AI coding tool after searching for it on a search engine.
> The attacker soon discovered Wallet DevOps Engineer A had a container deployment permission token on his computer.
"I don't always hold deployer keys to billion-dollar MPC infrastructure on my dev laptop, but when I do, I pipe curl to bash to install agentic coding tools."
Binance @binance Nov 3 Article 29 October Binance Security Incident: Initial Findings and Response Update On 29 October 2026, Binance experienced a serious and highly sophisticated security incident. This should not have happened, and we apologise for the concern, disruption and uncertainty it caused our
The latest TC release 3.18 was done as a private binary (something we had done before when patching crits). There was a long-standing practice that if a node requested, by signing a message with their validator key, devs would send them the validator-key encrypted diff of the security patch. That’s exactly what the malicious node did in this case. It’s possible even that the private release spooked them into speeding up their timeline for the attack. I find this class of attack very interesting. Networks need to be designed maximally defensive, even against their own validators. In this case, a malicious validator can still get the source code for patches and exploit them before the code goes out. I wonder if this puts an end to that practice. It all exists on a spectrum of decentralization. I actually don’t disagree with @jpthor that closed source TSS might be the move from here. Anyone who is saying that’s “the end of the experiment” is either a crypto-anarchistic maxi that lost the plot or an NK hacker astro-turfing protocols into not making sound trade-offs between security and decentralization.
In total, DKLS seems very promising, and seems to have worked out for @vultisig so far. That said, the comparative leap to move THORChain from GG20 tss-lib v1.0 to v3.0 is relatively lean. Just give keygen messages a version flag so that current vaults can continue signing using legacy keyshares, then cutover and deprecate the TC fork once a new keygen is successful. THEN move to DKLS later. IMO that's the safest path to getting TC back up and running ASAP, safely.
Second, the DKLS implementation that supports ECDSA has had a few dozen commits by 2 authors, with the last release dated July 2025. By contrast, Binance's tss-lib implementation that TC inherits from has commits date from last month, with far more contributors and commits. github.com/silence-laborator…
The current working branch that @jpthor is vibe-coding (gitlab.com/thorchain/thornod…) vendors @vultisig's go-wrapper implementation (github.com/vultisig/go-wrapp…). Don't vendor! Import the upstream and keep it to-date. That was our first fatal flaw running a GG20 tss-lib fork for TC. I take full responsibly for not getting us up to at least v2.0.0 at the time, which was largely in my wheelhouse.
Ok, I'm going to go ahead and say it. Silence Labs' DKLS implementation, and Vultisig's go wrapper of it, is not ready for primetime use on @THORChain.
Ever seen "ADR" mentioned in THORChain discussions and wondered what it means?
An ADR, or Architecture Decision Record, is how THORChain proposes and formalises major changes to the protocol. New features, tokenomics updates, chain integrations, fee structures, node incentives. If it changes how THORChain works, it's gone through an ADR.
The process is open. Anyone can draft one, it gets published publicly, the community discusses it, and nodes vote to accept or reject it. No backroom decisions, no unilateral changes. Every significant shift in the protocol's architecture is documented, debated, and recorded permanently.
Recent examples include ADR 021 which established the marketing fund, ADR 023 which introduced reserve burn improvements, and ADR 025 which is currently redirecting the dev fund to a new treasury.
It's like an audit trail of every major decision THORChain has ever made, publicly accessible and permanently on record.
dev.thorchain.org/architectu…
We’re coming up on 3 months since Harbor’s launch. We’re proud to say that our initial rollout phase is complete, and the protocol has performed to the team’s high standards:
100% swap completion rate, 212x week-over-week growth, 74% of quotes won on routes/wallets supported. Furthermore:
* $500k volume processed to-date, next stop: $1M!
* Live in 5 wallets: @THORWallet (as of today!), @THORSwap, @xverse, @orangerockxyz, @wire_wallet.
* 3 more wallets launching very soon, all made possible via @SwapKitPowered .
* Maximum size: $10k, increasing to $20k soon.
* Routes: ETH/BTC and BTC/USDT, with more planned.
* Roadmap: multi-book routing, chains (BNB, Tron), DEX aggregation.
Stay tuned as we continue shipping!
🚢
The prevalence of leverage trading in crypto is a byproduct of how hard it is to buy and sell spot native assets for the average user.
Don’t believe me? Search “Bitcoin” in @phantom wallet. The only options are Long & Short (“Trade BTC Perp”). This isn’t self-custodial, self-sovereign crypto. It’s paper Bitcoin. And it’s allowed various firms to profit at retail’s expense for too long now.
End perp reliance. Stop holding wrapped, bridged equivalents. Improve native trading capabilities in wallets. Buy and hold spot. Don’t let the sharks take your Bitcoin.
We’re building @Harbor_DEX for the next chapter.
We just had a $4.1k BTC<>USDT swap via @THORSwap on @Harbor_DEX. If you take into account Binance’s 10 bps taker fee, the swap was 2 bps cheaper than Binance! We’ll post our explorer soon that transparently surfaces quote, execution and comparable oracle/CEX pricing.
Slowly and deliberately, @Harbor_DEX is increasing its max swap size, validating execution quality at each milestone before moving up.
$5k swap next week?