Barkskin on nostr

Recent Notes

If the code is open source, yes. I'd do what everyone else is doing and have Kimi K3 review it.

Over the years i told people about btc and to get some, and that these top three hww are the ones to choose from. I'm pretty grateful they ignored me.

CC was not fully opensource i read?
Just kind of flabbergasted so many of us from levels from full tech knowledge to non had the cc as one of the the top hww, but no one in vijf years saw the entropy flaw or even seemed to have looked. Big lesson, harsh for the ones that lost their savings.
I feel somewhat left at the mercy of the goodwill of the other when it comes to technical stuff as code. WOT here on nostr could have helpt i'm guessing. I did not! I hope something changes here so non-coders somehow can verify that coders verify the coder etc etc that they verified the wallet that they feel comftebale to tell to folks 'yes , that one's good to get'

note1dthvy...

Barkskin @Barkskin 1785948497

That language i don't understand. Not sure if you meant you did/can any hww or also the cc?
My question on checking the code/firmware i'm asking, is if one would recognize that the entropy was not as it should have been or if any other code is corrupted. Even if this firmware is offered via the official hww's website/app.

Barkskin

@Barkskin 1785930171

#asknostr #cc
Who here actually knows how to check and verify the code on a hww?

Not that i will believe you or maybe your a scamming/bot, but who here dares say they can and did the verifying?

🇵🇸 whoever loves Digit · 4d

If you mean checking for issues like the coldcard RNG issue, I don't think it's humanly possible to have absolute verification for projects this complex. The goal is instead to have way more time spent analyzing the code than writing it. If 100 people spend 100 hours each looking at code that took...

Derek Ross · 5d

Real talk time. I've watched NVK attack devs, contributors, and competitors for years. I've also met him a few times in person, had a good time, and gave him a few 🤙🏼 and 🫂. If I'm being hon...

Barkskin @Barkskin 1785929924

Love and strength to those what have been hurt.
Good you say what you said. I somehow have been trusting, but who ,what and why? You seem like a kind brother here online. I made assumptions you know how to code. My foolishness is that I think when i see a review on the top wallet i 'ass u me' they know code and checked it. Same as with nostr. My doubt is growing on btc, for i can maybe dice or pull words out of a hat, but what if i know nothing about verifying chips/softwares etc to be sound.. I am curious, Can you yourself - if you wanted- check code on wallets firmware to see if the entropy is solid?

Derek Ross · 4d

If the code is open source, yes. I'd do what everyone else is doing and have Kimi K3 review it.

BTC_P2P · 1w

Does anyone know if these provide true randomness? Hardening and I have questions. nostr:nevent1qqswad0ppwukrz6vja6urtvd27gv4zfplwvfz3lun8rstjezkupfwxszyqkxt9q8ykalzzlmhaftwmzpvpn4g3qjvnms057eesww4wr...

Barkskin @Barkskin 1785694195

Need to always pull them out with the same hand and between the samen fingers, shake and roll the hat or whatever cup that's holding them the same amount of time and ... Well, to be honest I don't know 😊 Might be a trillion less change out of te many one in a trillions ., but it seems to me an option...

Telluride · 6d

Or randomize how you pull em and add some entropy… this conv is silly.

Noshole · 1w

Finally got a chance to wear the new dress last night https://i.nostr.build/JNLBCdpBFl7QQkll.jpg

Barkskin @Barkskin 1785693802

Crazy-funny stoner and beautiful. Nice combo. If you got a man tell him he's a lucky one.

Telluride · 1w

Its complex and beyond my ability to explain that part to you. Google it up or use your favored LLM to ELI5 and expand your knowledge on this. It’s important to understand the basics. 🧡👊...

Barkskin @Barkskin 1785693415

Got this

Barkskin @Barkskin · 1w

Barkskin

@Barkskin 1785693318

Got this
#BIP39 #Checksum Summary
What Is It?
The checksum is a built-in error-detection code that ensures your recovery phrase is valid. It sits inside the final word of your seed phrase.

How It Works
Step Process
1 Generate entropy (128 bits for 12 words, 256 bits for 24 words)
2 Apply SHA-256 hash to the entropy
3 Take first 4 bits (12 words) or 8 bits (24 words) of hash = checksum
4 Append checksum bits to end of entropy
5 Split total bits into groups of 11 → each group = one word index (0-2047)
Why You Can't Choose the Last Word Freely
The last word contains the checksum bits. These bits are mathematically determined by SHA-256 of your first words (entropy). Change any word earlier in the phrase → checksum changes → last word must change too.

Why It Exists
Without a checksum:

Typos go undetected
You could silently create a different wallet
Your backup appears valid but fails when restoring
With checksum:

Invalid phrases are rejected immediately
Hardware wallets only accept valid last words
Restoring with a typo fails fast
Analogy
Like an IBAN number: the last digits are a control number. One wrong digit = invalid account. Same principle in BIP39.

Formula (Simple)
checksum = first (ENT/33) bits of SHA256(entropy)
valid_phrase = entropy + checksum → split into 11-bit chunks → map to words

Bottom line: Checksum = fingerprint of your entropy. Ensures you didn't make mistakes. Last word isn't yours to pick—it's locked by math.

1❤️1