@ColeTU Newly generated seedphrases on mk3s still have some bits of entropy even with the improper rng. Sorry if you’ve clarified but are these tests gauging newly created mk3 seedphrases with low entropy plus a passphrase or an already comprised seedphrase plus a passphrase?
@0_3_BTC@Trezor It is inconvenient but at the moment you still can use more words. For example you could use the first 4 letters of 10 words with 9 spaces. Thats 10 words of entropy with just 49 character limits.
@chordateX@w_s_bitcoin Just for minimum 50 character limit passphrases. Obviously on wallets with larger passphrase limits you would just add to the passphrase.
@chordateX@w_s_bitcoin Hm this is what I just looked into. Diceware entropy for 7 completely random words would get around 90 bits of entropy. Anyway one could increase this, Ideally above 128 bits?
@chordateX@w_s_bitcoin Depends on how low the seedphrase entropy is tho right? If the seedphrase entropy is so low then the attack can be focused on the single passphrase which I imagine could be brute forced eventually.
@Dantoshi If I go from model T to safe 7 do the additional security features apply with a wallet retrieval or would I have to generate a new seed phrase?
I am urging engineers who are in the Bitcoin ecosystem, use @OpenRouter or @opencode to use @Kimi_Moonshot K3 on any software you run which interacts with bitcoin in any way internally and any public repos you use.
Other models CAN find issues, but K3 will one shot full vulnerability reports to get an extra set of eyes for security checks.
Some of it will be slop/overstated/wrong, but I've been scanning open source repos and finding things I'll be passing along to maintainers.
Kimi K3 came out as open weights on Monday, and I don't think that is a coincidence as it relates to the COLDCARD issues unfolding.