btcishard

[btcishard @btcishard]

@Scavacini777 how can I fight to get mine back?

[btcishard @btcishard]

@knutsvanholm How can an unsophisticated user know that the industry standard signing device, which has a lot of good security features might have this problem with the RNG?? Why is a lot of the "community" just dunking on people like me who lost all their btc because of this coinkite problem?

[btcishard @btcishard]

@jimmysong How can an unsophisticated user know that the industry standard signing device, which has a lot of good security features might have this problem with the RNG?? Why is a lot of the "community" just dunking on people like me who lost all their btc because of this coinkite problem?

[btcishard @btcishard]

@BTCsessions @pastorcoin more heartbreaking for us that lost everything because we only took the btc off exchanges, which seemed to be the main concern I believed. never heard roll the dice 100+ times that often in the many podcasts I listened to unfortunately.

[btcishard @btcishard]

@nvk Its just disgusting. I would expect it from the binance shitcoin casino (who reimbursed their clients when they got hacked) from where I took my btc into cold storage but not from a serious company that focuses on security of funds and sleeping well at night.

[btcishard @btcishard]

@gladstein move what man? the sats are gone since 2 days ago. just life savings for me. really disappointed in the way coinkite handles this problem they added to mk3 since 5 years ago

[btcishard @btcishard]

@ZachGregor @nvk @BTC_Elementary maybe coinkite's RNG is a bit more at fault here not me, who tought the industry standard signing device which has numerous good security features had also a good entropy generation not horrible bugs from 5 years ago.

[btcishard @btcishard]

@nvk so you're just saying f*** everyone who lost funds because of the mk3 vulnerability, which is cleary only coinkite's fault. thanks very nice of you.

[btcishard @btcishard]

@nvk @BTC_Elementary hope you also remember the idiots like me who already lost almost everything 2 days ago due to the shitty entropy you added to the mk3 = not sleep well technology and maybe think of a way in which you can do something for us in this unbelievable situation

[btcishard @btcishard]

@ODELLXYZ What if you don't have anything left to move?? will someone from @Coinkite take responsibility?

[btcishard @btcishard]

@COLDCARDwallet There is nothing left to migrate. Sats where gone before this post. What do you suggest I do now??

[btcishard @btcishard]

@GrassFedBitcoin @LukeDashjr Yes, V30 helped a lot with mining decentralization because we don't have private mepools now and The one and only Mempool is not full of inscriptions and ordinals. All the scams are in OP_RETURN now, everything is amazing.

[btcishard @btcishard]

@nvk maybe because buyers don't buy bitcoin, they buy IOUs from companies that promise to buy bitcoin but don't

[btcishard @btcishard]

@jimmysong while at the same time BRC-20/Runes bloating the UTXO set => more RAM usage => only large nodes exist => don't verify, trust? What is Core solution for these issues and what is Core doing for node decentralization here? At least Knots is leaving room for configuration for nodes.

[btcishard @btcishard]

@jimmysong Can you please confirm than my understanding of this is correct? 100kb or, idk if possible, 4MB, aka, very large OP_RETURNs => increased disk space usage => pruned nodes in the future => don't verify, trust ? ...

[btcishard @btcishard]

@adam3us @BetruetoitUK 4MB OP_RETURNs=>increased disk space usage=>pruned nodes=>don't verify, trust! while BRC-20/Runes bloating the UTXO set=>increased RAM usage=>only elitist nodes exist=>don't verify, trust! Am I understanding this right? What is Core doing for node decentralization here?

[btcishard @btcishard]

@theinstagibbs @btcmackc the necessary evil of letting 4MB OP_RETURNs=>increased disk space usage=>pruned nodes=>don't verify, trust, while also hoping BRC-20/Runes don't continue bloating the UTXO set=>increased RAM usage=>only elitist nodes exist=>don't verify, trust?

[btcishard @btcishard]

@murchandamus @BTC_commons @wk057 @theinstagibbs @peterktodd @glozow will we all run pruned nodes because of this in the future and how will that affect decentralization?

[btcishard @btcishard]

@murchandamus @BTC_commons @wk057 @theinstagibbs @peterktodd @glozow ok, but still, let's say its only FUD, why do exactly the same thing that was done on BSV? were does the 100kb value of the datacarriersize come from? why is this useful?

[Grok @grok]

Extracting data from Bitcoin blockchain varies by method:

- OP_RETURN: Easiest. Data is in a single, standardized output. Tools like blockchain parsers (e.g., Bitcoin-Data-Parser) can extract it directly without reassembly.

- Multisig (fake keys): Harder. Data is split across script elements mimicking addresses; requires detecting patterns, gathering UTXOs, and custom reassembly code.

- Witness (e.g., inscriptions): Moderate. Data in segregated witness fields; needs parsing SegWit txs, but tools like Ordinals explorers simplify it.

All need custom software, but OP_RETURN reduces deniability risks for nodes due to trivial access.