divingjohn's comments | Ecency

DiscoverWavesCommunities

@divingjohn

46

Resource Credits

Available

Used

Created

2024-12-31 04:13

RSS Feed

Comments

Blog Posts Comments Communities Wallet

divingjohn

4M

RE: LeoThread 2026-05-18 01-06

$RUNE to Valhalla

$ 0.000

0

divingjohn

4M

RE: LeoThread 2026-05-18 01-06

Continuing to build and resolving the chaos that arises is the only viable path forward Gratitude for the wider community, key contributors, and developers for their hard work and resilience Building the

$ 0.000

0

divingjohn

4M

RE: LeoThread 2026-05-18 01-06

There is broad agreement on the importance of continuing to build, which is why lively discussions are happening everywhere; the shared goal is the best possible outcome

divingjohn

4M

RE: LeoThread 2026-05-18 01-06

A community of builders and visionaries — not perfect, but with the mindset needed to construct such an important protocol The incident might have been preventable, but final conclusions require the team

divingjohn

4M

RE: LeoThread 2026-05-18 01-06

That's why the protocol is the cockroach of crypto It persists regardless of outrage or calls for its demise, adapts, patches flaws, and returns stronger, refusing to be captured or put down

divingjohn

4M

RE: LeoThread 2026-05-18 01-06

While many critics and attention-seekers spread FUD, pile on criticism, or gloat over setbacks, core teams and contributors are focused on what matters and already deep into fixing issues and moving forward

divingjohn

4M

RE: LeoThread 2026-05-18 01-06

Resilience — that's what stands out about THORChain and its community, because it matters

divingjohn

4M

RE: LeoThread 2026-05-13 15-05

Development and releases will proceed in stages

divingjohn

4M

RE: LeoThread 2026-05-13 15-05

"remind me tomorrow to pay the 10 USDC bill" "set up a weekly $100 DCA into BTC" "withdraw my tornado cash deposit in one month" "if vitalik tweets about his girlfriend,

divingjohn

4M

RE: LeoThread 2026-05-13 15-05

Second — the agent will enable bespoke, just-in-time UIs around chain data of interest: prices, charts, positions — anything can be shown as simple widget-like cards. Third — scheduling examples:

divingjohn

4M

RE: LeoThread 2026-05-13 15-05

The agent will be trained on essentially every DeFi transaction: sends, swaps, bridging, lending, saving, LPing, staking, privacy — anything. It will demystify on-chain activity and make it straightforward.

divingjohn

4M

RE: LeoThread 2026-05-13 15-05

It literally can't — with 2-of-2 fast vaults, every transaction must be confirmed by the user. As a result, this is an extremely safe wallet to build an agent around.

divingjohn

4M

RE: LeoThread 2026-05-13 15-05

First — powered by MPC technology supporting 30+ chains in a multi-party wallet. That architecture means an agent cannot complete a transaction on its own. Not "won't" Not "shouldn't"

divingjohn

4M

RE: LeoThread 2026-05-13 15-05

What's the plan? The approach rests on three pillars: Agent-first transaction construction Highly customizable, bespoke widgets Agent scheduling

divingjohn

4M

RE: LeoThread 2026-05-13 15-05

End-game wallet releasing in stages, with more features arriving progressively. Crew in formation 🫡

divingjohn

4M

RE: LeoThread 2026-04-19 04-29

A whitelist mechanism will be deployed in the next few days so new multisig accounts initially go to a pending state requiring manual addition to the Squad list Further updates will be shared as these

divingjohn

4M

RE: LeoThread 2026-04-19 04-29

— A banner alerting users to this attack — An alert on any multisig never interacted with before

divingjohn

4M

RE: LeoThread 2026-04-19 04-29

— If legitimacy is uncertain, verify with the team before taking action — Set Squads accounts as default to pin them at the top of the Squad list via the Squad list options UI updates deploying in the

divingjohn

4M

RE: LeoThread 2026-04-19 04-29

— Do not interact with any multisig that was not created or added by the team — Do not rely on matching only the first and last characters of an address; always verify the full address against internal

divingjohn

4M

RE: LeoThread 2026-04-19 04-29

Impact: None if there is no interaction. This is not a protocol vulnerability. Attackers cannot access funds, execute transactions, or modify existing multisigs. It is a UI-level social engineering attempt.