Search content
Sort by
Showing 20 of 29 results by sad-error
Are the hashes in the release notes correct?
I get
I get
Code:
C:\Users\...\Downloads>certutil -hashfile v2.0.6-passport.bin md5
MD5 hash of v2.0.6-passport.bin:
93f87f44d2635339926c41e151ff5de7
CertUtil: -hashfile command completed successfully.
MD5 hash of v2.0.6-passport.bin:
93f87f44d2635339926c41e151ff5de7
CertUtil: -hashfile command completed successfully.
Code:
C:\Users\...\Downloads>certutil -hashfile v2.0.6-passport.bin sha256
SHA256 hash of v2.0.6-passport.bin:
1aee526cfcd28d262c00b74740adb0e75dbe89de9e81fe6f6896d88c6163cb72
CertUtil: -hashfile command completed successfully.
SHA256 hash of v2.0.6-passport.bin:
1aee526cfcd28d262c00b74740adb0e75dbe89de9e81fe6f6896d88c6163cb72
CertUtil: -hashfile command completed successfully.
Any ideas why I'd be getting a "memory allocation failed" exception when signing a transaction imported from the qr code - importing from the sd card works fine.
That usually happens when the PSBT you're trying to sign is quite large/complex. What version firmware are you running? If less than v2.0.6, please update to that as we've made quite a few quality of life improvements in it.
We're also about to release a beta for v2.0.7 that has a completely reworked transaction parsing memory approach that will allow for signing *much* larger transactions via QR, but we do still recommend microSD for larger transactions as the process is much faster and easier that way.
it's 2.0.6. Yes, the psbt is likely quite big as it's 3/6 multisig.
Any ideas why I'd be getting a "memory allocation failed" exception when signing a transaction imported from the qr code - importing from the sd card works fine.
Traceback looks something like this
Traceback looks something like this
Code:
File "flows/flow.py", line 139, in run File "flows/sign_psdbt_qr_flow.py", line 95 in show_signed_transaction MemoryError: memory allocation failed, allocating 5859 bytes
Do we know if $199 is the total price, or just the cost to reserve one?
I got an email after ordering that when it's ready to ship I can add the Q1 to my cart and then add my reservation as a "discount." And it appears no shipping or sales tax is charged yet.
I got an email after ordering that when it's ready to ship I can add the Q1 to my cart and then add my reservation as a "discount." And it appears no shipping or sales tax is charged yet.
I remember them mentioning that $199 is the full price in their podcast for now, but it will probably go up once it's out of preorders.
they can't be really backed up offline or by hand writing....
why not? sure it's a bit long and inconvenient but surely nothing is preventing you from writing it out by hand?
Cryptosteel cassette, whose original design this is ripping off, has nothing written on it at all.
https://cryptodeeptech.ru/lattice-attack/
https://cryptodeeptech.ru/twist-attack/
https://github.com/demining/CryptoDeepTools
My opinion, I believe this software attacksafe/CryptoDeepTools , I think this is creating for scam by referencing other research breaks ECDSA for made the scam happen.
attacksafe create for sale(SCAM) who contact them
maybe can possibility to scam, be careful.
noway to use that tools(all) for break
Hello. You don't have to worry, there are no viruses in AttackSafe/LatticaAttack/CryptoDeepTools. Verified in Kaspersky Internet Security. Proof! https://cryptodeeptech.ru/doc/Kaspersky-Internet-Security/CRYPTODEEPTECH.gifhttps://cryptodeeptech.ru/twist-attack/
https://github.com/demining/CryptoDeepTools
My opinion, I believe this software attacksafe/CryptoDeepTools , I think this is creating for scam by referencing other research breaks ECDSA for made the scam happen.
attacksafe create for sale(SCAM) who contact them
maybe can possibility to scam, be careful.
noway to use that tools(all) for break
https://cryptodeeptech.ru/doc/Kaspersky-Internet-Security/CRYPTODEEPTECH.gif
Scam doesn't always mean a software contain virus/malware. If you want to convince @riceberryrice, you need to bring better argument.
I don't understand why we are still talking about this - the tool, even if it's not malicious and works as expected - does not actually do anything because there's no attack surface.
At least in the EU apple is forced to switch to usb-c. Weather their shitty lightning through usb-c implementation will actually support data transfer on these devices - probably not because earning money through licencing lightning is too good of a deal for them - is a thing you should take up with apple.
Dream on and read the latest news about that iPhone topic.They are planning to introduce payment charges fee and verification for this special cables, so you won't be able to use your universal usb-c type cable
I'm pretty sure this won't fly at all in the EU.
Quote
Note that I am not a fan of iPhone at all, just trying to provide evidence that billions of people wont be able to use new coldcard device without paying extra money for new cable and new batteries.
ok to play the devil's advocate - you get the usb-c cable with the coldcard. What good does it do with your lightning port iphone exactly?
I guess iPhone users are screwed than and they can't use new coldcard wallet, but I guess that is nothing...''only'' around billion people use iPhone devices right now... especially in North America.
At least in the EU iphone is forced to switch to usbc. Weather their shitty lightning usb-c implementation will actually support data transfer is a thing you should take up with apple.
This is old news and a complete non-issue. For what it's worth, as far as I'm aware most (if not all) wallets use rfc 6979 to decide on the value of k, which means that as far as we know 
the randomness completely depends on the randomness of the private key and therefore your mnemonic.
the randomness completely depends on the randomness of the private key and therefore your mnemonic.Oh I see... you are one of those guys who is going to ''save the planet'' by paying more money for chargers and cables, sorry but I won't fall for that scam 
no, I just don't like useless parts that end up in the trash. But you do you. 🤷♂️
Electrum often crashes for me too, on my desktop. It happens right after broadcasting a transaction from a hardware wallet, and I've reproduced it with different versions on different (Linux) systems.
When it crashes, the transaction may or may not have been sent right before it crashed.
When it crashes, the transaction may or may not have been sent right before it crashed.
I've never had it crash on desktop, personally, but the mobile app was a complete disaster for me. The desktop electrum app does have some quirks with multisig that made me switch to sparrow, though.
Please try Electrum on desktop first, then come back here and tell us what you've experienced.
It's even better if you visit the Electrum child board and follow the discussions there.
In the meantime, try to interpret what LoyceV is saying about which is better between Electrum and Blue Wallet.
It's even better if you visit the Electrum child board and follow the discussions there.
In the meantime, try to interpret what LoyceV is saying about which is better between Electrum and Blue Wallet.
I've been using electrum on desktop pretty much ever since it first came out, it's an excellent wallet - on desktop.
They started doing similar strategies like smartphones that don't ship chargers in package anymore, and I can't find information if microSD cards are included or not.
I don't know any other wallet that don't ship with USB cable and I hope this won't be the new trend, but I guess everyone has some old cable from smartphones.
I don't know any other wallet that don't ship with USB cable and I hope this won't be the new trend, but I guess everyone has some old cable from smartphones.
I could not disagree more. Most of people already have those, probably, and even if not I don't see why you could not buy these separately. Imho there's no need to endlessly litter the planet with these.
If he can 1) prove in court he is Satoshi with this and 2) then he has the 'proof' to make the Bitcoin Devs make a 'fork' to get all Satoshi's coin 3) Well, BTC as such is 'toast' IMHO at that point. Remember it is a 'Jury' Trial..so if he can 'convince' them of the above it will be 'quite' the sh*tshow then.
Imho I don't think any of these matter at all. The only thing that matters is if he can claim copyright for bitcoin's source code - which if granted would set an extremely dangerous precedent when it comes to other open source software. Which is why I am 100% certain it won't happen.
I don't think it's true that bitcoiners don't like meeting face to face. There are weekly meetups in the city I live in - however from my personal experience with these, it's just a giant circlejerk, there's no added value from those conversations. Every meaningful discussion happens online, imho.
My second question, Electurm or Blue Wallet, which one you think is better?
For me personally electrum never really worked as expected on android - it was constantly crashing at the most inconvenient places. That said, even if it worked great I think bluewallet is much, much more polished and a better user experience - and it's available on ios as well, which electrum is not.
You need to very careful with address reuse using your set up. Whenever you spend from an address, then the three individual public keys for that address are revealed in the transaction data. If someone was to then compromise a single one of your paired back ups, they would have all the information required to spend any other coins on that address.
I'd also be quite uncomfortable about the wallet files on your PC, depending on your set up. If your wallet files are simply on an online computer then that is not very safe, since you are relying on the secrecy of your wallet descriptor/public keys not to reduce an attacker to only needing 1-of-3 of your back ups to compromise your wallet.
I'd also be quite uncomfortable about the wallet files on your PC, depending on your set up. If your wallet files are simply on an online computer then that is not very safe, since you are relying on the secrecy of your wallet descriptor/public keys not to reduce an attacker to only needing 1-of-3 of your back ups to compromise your wallet.
you are absolutely correct on all counts.