Pluto 🚢

Building @Harbor_DEX

[Pluto 🚢 @pluto_hbr]

Any “click trading” platform has an API that can be reverse engineered. There is virtually no way to prevent anyone from interacting with any Defi system in an automated way. Also the airdrop is 100% being farmed. They released publicly with $1b/day volume immediately. How is that kind of distribution possible without any real ramp up?

[Pluto 🚢 @pluto_hbr]

I found this thread to be pretty interesting. Because at the time we evaluated TSS Shock and other similar disclosures, a 3rd-party cryptographer we spoke to assured us it would take 1000s of keygen attempts to pop a private key. We also determined that many failed keygen attempts would arouse suspicion. It’s almost like this thread was an attempt to legitimize their node’s “issues” (where really each failed keygen was an attempt to extract the key) or otherwise gaslight devs into thinking it was a network issue.

[Pluto 🚢 @pluto_hbr]

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.

[Pluto 🚢 @pluto_hbr]

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.

[Pluto 🚢 @pluto_hbr]

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.

[Pluto 🚢 @pluto_hbr]

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. https://t.co/WQNnfWwCvV

[Pluto 🚢 @pluto_hbr]

It’s been brought to my attention that the NEAR mpc setup was open-sourced in late 2025. When I initially evaluated the protocol it was not. It’s still effectively a multi-sig, like Wormhole. My main point is that NEAR’s play was all about price execution at the expense of decentralization, nothing to do with risk management IMO. Pool-based designs are going away for other reasons.

[Pluto 🚢 @pluto_hbr]

@zacodil All the inventory held by MM on NEAR Intents are in a closed source multi-sig. Really poor taste to use exploits to champion your own less-secure, less-decentralized product. Also, your AI slop summary of the root cause is patently false (it’s not attention logic-related).

[Graham Ferguson @grahamfergs]

All crypto conferences should be held in Miami.

[Pluto 🚢 @pluto_hbr]

@alexfacelesslbs Alright well you’re being dramatic. Conference vibe was A5 wagyu lit my guy. Better luck next time and choose better events.

[Pluto 🚢 @pluto_hbr]

@BooneW @THORChain It’s on the website

[Pluto 🚢 @pluto_hbr]

I am pleased to announce a tender offer to acquire @THORChain.
1/2 cash 1/2 stock.
Offer expires EOD.

[THORChain @THORChain]

Nothing stops this train.

[Pluto 🚢 @pluto_hbr]

The ADR process was probably my favorite contribution I made to the THORChain protocol. Formalized governance processes benefit all.

[THORChain @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.

https://t.co/MsFDM4lrkH

[nicolas, 30 ans @nic_carter]

Sat down with @pluto_hbr for @OnTheBrinkCIV to talk KelpDAO, deep security in DeFi, Aave, LayerZero, Thorchain, Harbor, and where DeFi goes from here

https://t.co/kLwZRYHizh

[Pluto 🚢 @pluto_hbr]

@iotov92 Just to set the record straight: TC is very much alive and well. To think that myself or any others could destroy it sells it short. I never traded or shorted RUNE. And I was publicly against the schemes / features that you're probably referring to.

[Pluto 🚢 @pluto_hbr]

Proud of the team. Long road ahead. We’re confident in our design and ready to scale. 🤝

[Harbor 🚢 @Harbor_DEX]

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!
🚢

[Pluto 🚢 @pluto_hbr]

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.

[Pluto 🚢 @pluto_hbr]

@hosseeb Really well said. Blunt, positive. Your perspective cuts through the hysteria of this week and shows why leadership matters a lot in this space.

[Pluto 🚢 @pluto_hbr]

@familiarcow Nice work!