<lordx3nu:matrix.org> Kimi breakdown of the range proof bug that drained liquid btc last night (4000 total btc): gist.github.com/1440000bytes/211ac92dd4433bb1a2e674bf0ff7db2e

<ofrnxmr:xmr.mx> Bug B — ambiguous key encoding (introduced by the fix itself): the fix ("Fix caching bug in rangeproof caching", c26d719c29, PR #1561 — authored 2026-08-03 per its git author date) computes the key as a salted hash over the raw concatenation proof ‖ commitment ‖ asset-generator ‖ scriptPubKey with no length [... too long, see mrelay.p2pool.observer/e/u5PRragLOVR0OVpk ]

<ofrnxmr:xmr.mx> [... more lines follow, see mrelay.p2pool.observer/e/u5PRragLOVR0OVpk ]

<thomasbuilds:matrix.org> plotwist: it was the dev lmao

<jpk68:matrix.org> Blockstream has been obsessively shilling their 'Jade' hardware wallet devices, ever since Coldcard the coldcard incident, of course presenting them as a safer alternative

<jpk68:matrix.org> It will be fun to see how the mental gymnastics go from there (I know the bug is unrelated to private keys)

<ofrnxmr:xmr.mx> @thomasbuilds:matrix.org: I think thats where i would suspect

<slowbeardigger:matrix.org> Like snex said in a podcast

<slowbeardigger:matrix.org> “Get coldcarded”

<rbrunner7> From that Kimi breakdown, towards the end: "he fix was authored 2026-08-03 and sat unmerged for ~4 weeks, then was public, clearly titled, and easily diffable for 3–5 days pre-attack ("Fix caching bug in rangeproof caching") — effectively a published exploit recipe. "

<ofrnxmr> Inside job

<ofrnxmr> As unreleased code, the person had to know that the "core" team was running it

<ofrnxmr> The half of the network that halted /rejected it, was running release software

<jpk68:matrix.org> In that case, why would they publicly release info pertaning to how the exploit could be pulled off, before doing it themselves?

<ofrnxmr> wdym? They did do it themself

<jpk68:matrix.org> > was public, clearly titled, and easily diffable for 3–5 days pre-attack

<ofrnxmr> it was public for a month

<jpk68:matrix.org> Would it not be easier, if this was indeed an inside job, to only release that info after exploiting the network?

<ofrnxmr> For a month

<ofrnxmr> Release what info? It was an i merged pr for a month

<jpk68:matrix.org> I don't see how that changes anything

<ofrnxmr> Unmerged*

<ofrnxmr> 5 days after merge, once core /50% of network was running it, they swept the platform

<jpk68:matrix.org> By "release info", I mean publicly submit the PR

<ofrnxmr> I dont mean the author was the attacker

<jpk68:matrix.org> One would think that, if this was found internally first and they wanted to exploit it, they would do so before submitting the PR.

<ofrnxmr> how could you exploit something that isnt live?

<ofrnxmr> Tje exploit was only possibly once thatcode was merged

<jpk68:matrix.org> I'm retarded, nevermind

<ofrnxmr> It was never released. It was merged, and core ran it

<ofrnxmr> And core seems to have controlled over half of the network, and likely the majority of the endpoints used by wallets and other service providers

<slowbeardigger:matrix.org> They got coldcarded xD

<thomasbuilds:matrix.org> > Kept 598.5 BTC for himself. About 15%. "Sending most back" was literal.

<thomasbuilds:matrix.org> Was the dev(s) 100%

<slowbeardigger:matrix.org> yep

<thomasbuilds:matrix.org> They just wanted money and obviously didn't want to kill the project

<thomasbuilds:matrix.org> So that's the move they did lol

<ofrnxmr:xmr.mx> so does that mean they are going to dump it into zcash now?

<ofrnxmr:xmr.mx> or are those coins considered clean?

<thomasbuilds:matrix.org> I never heard of this blockchain before but seems like there are bitcoin core contributors in it?

<ofrnxmr:xmr.mx> i guess it matters on the users jurisdiction, bcuz it doesnt matter what blockstream says, if the espionage is illegal, then the feds will be looking to trace them

<ofrnxmr:xmr.mx> its not a lockchain

<ofrnxmr:xmr.mx> its a sidechain iirc, like lightning, but custodial

<thomasbuilds:matrix.org> Well bitcoin guys like XMR more than ZEC > <@ofrnxmr:xmr.mx> so does that mean they are going to dump it into zcash now?

<ofrnxmr:xmr.mx> adam back / blockstream product.. again, iirc

<thomasbuilds:matrix.org> ?

<jbabb:cypherstack.com> ZEC started as a BTC fork before they abandoned the bitcoin core they started with

<jbabb:cypherstack.com> iirc

<jbabb:cypherstack.com> just a codebase fork tho, not a blockchain fork like bitcoin cash. now ofc their software's in rust

<thomasbuilds:matrix.org> The ZEC pump was market pricing in that 😂

<ofrnxmr:xmr.mx> @jbabb:cypherstack.com: only one of the nodes, the reference node is still c++

<jpk68:matrix.org> The repo was archived recently

<ofrnxmr:xmr.mx> oh damn eh. rip

<jbabb:cypherstack.com> I thought also zebra, the first rust client, was or is also on the way to being archived

<jbabb:cypherstack.com> (I thought wrong)

<ufo808:matrix.org> just opened my view-only wallet and received ~0.12 xmr and it looks like from mining, someone used my wallet for mining by mistake? how is that possible

<ufo808:matrix.org> mrelay.p2pool.observer/m/matrix.org/xfBqFExHitoiJNJfyvgJdYZL.png (image.png)

<ufo808:matrix.org> trying to scan main wallet to see if it's real...

<ufo808:matrix.org> oh sorry wrong chat

ufo808: maybe change from a tx you made?

<ufo808:matrix.org> UkoeHB: oh yea, it might be, it would actually explain everything

<ufo808:matrix.org> you might be right, thanks

<ufo808:matrix.org> oh but hm, I didn't do any transactions 11 days ago... anyways I'm still re-syncing with a different node nad from height 1, let's see

<ofrnxmr:xmr.mx> you can just sync from before the first tx that you see in the view wallet

<ofrnxmr:xmr.mx> remote node sync from block 1 is over 30gb

<ufo808:matrix.org> that's why it's so confusing, because I did it exactly, synced from 3744800 multiple times, both wallets

<ufo808:matrix.org> 3744801 is the height of 0.12.. tx

<ofrnxmr:xmr.mx> did you sync the spend wallet?

<ofrnxmr:xmr.mx> come to #monero-support:monero.social if you think this will drag on

<ufo808:matrix.org> @ofrnxmr:xmr.mx: yes