Search content
Sort by
Showing 20 of 53 results by Solo6R
You haven't done anything wrong yet, when you have new cold card just create entirely new seeds and move the funds to it and that's it the funds again went back to cold storage.
You can't be 100% sure that any device is free from any kind of malware even the most advanced machines with all the necessary things from government agencies can't stop the remote attack from hackers so think about security of your device. For now you can use the wallet meanwhile not connecting to internet can be a better than always connected to internet.
You can't be 100% sure that any device is free from any kind of malware even the most advanced machines with all the necessary things from government agencies can't stop the remote attack from hackers so think about security of your device. For now you can use the wallet meanwhile not connecting to internet can be a better than always connected to internet.
Alright, Well my new cold card arrives in the next 1-2 hours so I'll just generate a new seed and call it a day. Thanks.
I made a post about my Cold Card quitting on me (replacement on the way), and when it quit working I decided to import my wallet into my older Tangem wallet that I wasn't using anymore. I'm not sure why I did this as I didn't need immediate access to my BTC, I think I just paniced at the thought of not having access to it for the moment? Who knows. Anyways, in order to restore my wallet created on the Cold Card, I of course had to enter my seed phrase into Tangem. That's pretty straight forward and standard for any wallet's recovery process, I know. But what I'm being paranoid about is that Tangem is a phone app. So up until this point I've been completely air gapped with my Cold Card Q, and now I'm not. BitDefender Mobile runs on my phone and I don't do anything crazy with it, but how bad of an idea was it to restore my wallet into Tangem? I know the chances of my seed being "seen" or extracted in the process of typing it in are not 0, but I have to imagine I'm probably ok, right? Am I being too paranoid here or should I just generate a new seed phrase when my new Cold Card Q arrives? I've never put my seed into any digital media. I've got 2 paper backups, and a metal seedplate backup (Keystone Table Plus), so the ONLY time it's ever seen something "electronic" was when I restored it inside the Tangem app. What are your guys thoughts?
And just now received confirmation that my replacement was on the way. No questions asked. I will say that's some top notch support for the industry.
That was quick. Good for you. It's a positive sign that Coldcard decided to send you a replacement device so fast, but it's also a bit worrying. You must have made a compelling case for them not to ask photo/video evidence and have you run through various possible fixes first. I said worrying because it seems they know exactly what happened and that it can't be fixed remotely, and it's also not something new to them. Still, this is the first case I remember seeing on Bitcointalk.Well I sent them photos and the above posted video with the original support ticket, preemptively. Try to save us both some time.
Now that I have a replacement unit on the way, a bit of an off-topic question if I may. Will I need to re-import my wallet into sparrow even if I'm using the same seed? I assume that would be the same XFP as well. I'm planning to just restore the cold card backup file I generated with the previous cold card.
⭐ Merited by DaveF (2)
And just now received confirmation that my replacement was on the way. No questions asked. I will say that's some top notch support for the industry.
That being said I've since learned that ColdCard policy states that they don't make customers send their devices back, so I'll just wait for the new one to arrive and just restore my backup to it. No need to move my BTC anywhere.
That's even better, and it's a good policy. It's safer for the end-user than being forced to send the hardware wallet back, not knowing who will look at it and what could happen. Your problem occurred on Friday. It's now evening hours on Monday. Did someone reply to you from Coldcard's support and what did they say? I have not received a response yet. Support email went out on Friday and they say 1-3 business days for a response. So between today and Wednesday I should hear something. From what I've read from other users in the past, a new unit is shipped out and issues resolved. Not one of them when asked (these are mostly reddit posts I'm reading), has said they were told to ship their broken wallet back, most stating they were told NOT to. Being that it's under warranty still I imagine this process will play out similar, if not identical. I will update here however.
Don't send your coins to a shitty centralized exchange that might find faults with them and say they are "dirty" and that they need to keep them for everyone's sake. Or you could get them back if you do everything they tell you to and send all kinds of documents. If you must move the BTC from your Coldcard, keep them on Sparrow.
Are you confident enough that your computer is safe and malware-free? Do you use if for any purposes where it might catch malware, keyloggers, etc.?
Are you confident enough that your computer is safe and malware-free? Do you use if for any purposes where it might catch malware, keyloggers, etc.?
Nah, I just play (legal, bought) games, run a MWB and BitDefender scan daily. I'm pretty certain the system is clean and secure. That being said I've since learned that ColdCard policy states that they don't make customers send their devices back, so I'll just wait for the new one to arrive and just restore my backup to it. No need to move my BTC anywhere.
⭐ Merited by DireWolfM14 (1)
You would import the current Cold Card wallet's back up seed into a Sparrow hot wallet (i.e. Sparrow on a machine that's connected to the internet.) Then you'll be able to sign a transaction right from Sparrow. Again, you would essentially turn your current Cold Card seed into a hot wallet, but since you're not going to use it again in the future, it's not a big deal.
Right, that's what I was suggesting to begin with. I thought for some reason you were saying not to do that. Instead you're saying make a new wallet in Sparrow after I recover this one, rather than sending it to an exchange. Gotcha. Alright I may do that. Thanks
EDIT: I guess I could import my 24 words + passphrase into Sparrow just long enough to sign a transaction back to an exchange right? I know entering your seed directly onto Sparrow probably isn't the safest thing to do, but if the plan is just to instantly send it off to an exchange to hold it until I get a new HW wallet then it's probably safe enough right?
Or, just use Sparrow on an offline machine to create a cold wallet and send your bitcoin there. Personally I would rather do that than trust a non-custodial exchange wallet, especially if we're talking about a significant amount. When you get your Cold Card back you can use that same seed to restore your Cold Card, and all your bitcoin will be accessible in your new hardware wallet. Since you created the new seed offline it'll be as safe and secure as if you had created a it with hardware wallet, and it'll save you a transaction.
Also, if you're sending the bitcoin from it's current location to a new seed, there's really no reason not to import the current seed into Sparrow. You would basically be turning your current seed into a hot wallet, but again, that will save you one transaction.
But how would I send from my current wallet to a new wallet if I don't have access to the cold card to sign the transaction? That's why I suggested importing the seed into sparrow to get access to it. If I just make a new wallet I can't send to it from my current cold card wallet to sign the transaction....
Green light in the top left remains on, but screen never came back.
Then, it looks like that problem is relevant to MCU/display_controller (I'm not sure whether the devece's display is controlled by MCU or has the build in controller) and I'm afraid that there will be a need to send device to manufacturer to replace it according to their warranty statements. If this will happen I would advocate to move (somehow) your stash to new addresses not related with your SEED on Cold Card Q (before sending device to manufacturer).
It seems like the program becomes corrupted after you flash the Coldcard Q and then it works just fine then suddenly the screen stuck on the black screen it looks like the bootloader issue it can't start because of the corrupted program.
The documentation from Cold Card seems does not have any way to hard reset this wallet and according to them there's no way to reset the pin meaning we can't reprogram this hardware wallet(Their docs doesn't have enough information) after a deep research I found a guide where you need to burn the recovery image for this unit I think this will help to revive this unit.
Check this guide from their github here https://github.com/Coldcard/recovery-images
Take note of recovery images you can download them from this link https://coldcard.com/downloads/recovery
The documentation from Cold Card seems does not have any way to hard reset this wallet and according to them there's no way to reset the pin meaning we can't reprogram this hardware wallet(Their docs doesn't have enough information) after a deep research I found a guide where you need to burn the recovery image for this unit I think this will help to revive this unit.
Check this guide from their github here https://github.com/Coldcard/recovery-images
Take note of recovery images you can download them from this link https://coldcard.com/downloads/recovery
Great, I'm giving it a shot now, although not convinced it's even doing anything. I've imaged it to an SD card and turned the device on with the SD card inserted. It still just does the "verifying...." bit and goes back to black screen with the greenlight in the top left still on. But maybe it's doing something behind that black screen? Here is a video of the behavior: https://streamable.com/eq53hc
Here is a similar problem where a user experienced problems with powering on their Coldcard. According to him, support asked him to send several photos and videos of his hardware wallet not working and eventually sent him a free replacement device. I would suggest to follow the support's instructions and be patient. Don't enter your seed into a hot wallet out of paranoia or "just to see if it works". You'll only lower the security of your bitcoin.
Yeah that issue doe sound quite similar. Bummer that it happened on a Friday, hah. I'll wait to hear back from them on Monday I guess. Cheers.
⭐ Merited by ABCbits (2)
I've been using a Cold Card Q for about a month or two now without issue. Today I upgraded (after verifying) the firmware, and also decided to try a restore from backup (after sending my BTC to another wallet first), since it dawned on me I never actually tested that yet after creating the wallet. Anyways everything went well, the firmware upgrade went smoothly, as did my backup, all good. I sent my BTC stack back to the cold card, and called it a successful..maintinance? Anyways, a couple of hours later I go to turn on the device and it shows the normal "Verifying..." screen but then the screen just goes black, almost like it's off, but it's not because the green light in the top left remains on. I've tried removing the batteries for a minute and powering back on, I've tried powering on with just USB (wall charger, not a PC) power, I've tried with and without an SD card present. I'm not sure what else to do. I've got a support email into Coinkite but I imagine I won't hear back from them until Monday, so figured I'd ask here if anyone had a solution or has heard of this happening, and what the general recourse is like, will they mail me out a new one free of charge or am I gonna get burned here?
⭐ Merited by nc50lc (1)
Yeah I'm using bitcoin core. This didn't seem to solve much. I've specified my onion address via the externalip param and I'm still getting connected to via regular IPv4 addresses. Tried with discover on(1), and off(0).
Have you followed the instructions to add bind=127.0.0.1:8334=onion to your config to prevent clearnet inbound connections?Because onlynet=onion only works in outbound connections like what you've described.
Don't forget to restart Core to apply the new bitcoin.conf settings.
That seems to have done the trick. Thank you. I get a LOT fewer inbound connections now (for obvious reasons), but the ones I get are via the onion network and not an IPv4 connection.
Using Bitcoin Core?
Set the provided args in the third option in this official documentary for Bitcoin Core client: https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md#3-manually-create-a-bitcoin-core-onion-service
Most importantly, the --externalip that you can get from "C:/Tor/tor/hidden_service_directory/hostname" based from the "HiddenServiceDir" that you've set in your torrc file.
Set the provided args in the third option in this official documentary for Bitcoin Core client: https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md#3-manually-create-a-bitcoin-core-onion-service
Most importantly, the --externalip that you can get from "C:/Tor/tor/hidden_service_directory/hostname" based from the "HiddenServiceDir" that you've set in your torrc file.
Yeah I'm using bitcoin core. This didn't seem to solve much. I've specified my onion address via the externalip param and I'm still getting connected to via regular IPv4 addresses. Tried with discover on(1), and off(0)
⭐ Merited by odolvlobo (1)
I've setup a full node and after some reading decided to run it over tor. The problem I'm having is that inbound connections are still over IPv4, whereas the outbound connections are proper tor/onion addresses. I can ofcourse turn off incoming connections with "bind=127.0.0.1" in in my bitcoin.conf file, but that sort of defeats the purpose of running the node to contribute to the network doesn't it? I've tried a slew of configuration settings with bitcoin.conf, and torrc and can't seem to figure this out.
Is it common for folks running their node over tor to accept and connect just to other tor addresses, or do most just connect(outbound) to other tor addresses, but still receive from normal IPv4 addresses?
Bitcoin.conf:
torrc:
Is it common for folks running their node over tor to accept and connect just to other tor addresses, or do most just connect(outbound) to other tor addresses, but still receive from normal IPv4 addresses?
Bitcoin.conf:
Code:
server=1
proxy=127.0.0.1:9050
onion=127.0.0.1:9050
listen=1
listenonion=1
onlynet=onion
torcontrol=127.0.0.1:9051
proxy=127.0.0.1:9050
onion=127.0.0.1:9050
listen=1
listenonion=1
onlynet=onion
torcontrol=127.0.0.1:9051
torrc:
Code:
Log notice file C:\Tor\tor\tor.log
ControlPort 9051
HiddenServiceDir C:/Tor/tor/hidden_service_directory/
HiddenServicePort 8333 127.0.0.1:8333
ControlPort 9051
HiddenServiceDir C:/Tor/tor/hidden_service_directory/
HiddenServicePort 8333 127.0.0.1:8333
After a couple of days of syncing, I've finally got my full node setup on a 1TB SSD. Feels pretty liberating to finally see the green power icon/switch on sparrow instead of the yellow public one. Granted I'm still using a CEX so the anonymity benefits of running a node are mute, it still feels pretty neat to be able to verify my own transactions, and even better I can verify others and help out the network! Aside from the information window with things like connections, block height, etc, etc. Is there any neat bits on Bitcoin Core to look at? Things like how many transactions my node has personally verified or anything?
Anyways, just wanted to share with you guys that I'm doing my part and we've got another full node online! I literally have no one else in my life that would A.) care, or B.) even know what I'm talking about.
Anyways, just wanted to share with you guys that I'm doing my part and we've got another full node online! I literally have no one else in my life that would A.) care, or B.) even know what I'm talking about.
Solo6R, it is great to see that you are only a jr member and already managed to run your one full node, especially when you use CEX and are not benefiting from any anonymity benefits, while many veteran members haven't done it yet. I honestly believe that this should serve as a great motivation for many members, new and old, in the forum.
Congratulations and thank you!
Hah, thanks. I've been DCA'ing into BTC since Dec '23, reading everything I can, and always looking for ways to get involved and/or contribute. Figured since I had an unused 1TB SSD laying around, I may as well give it a shot, and here I am. I have since configured both my node, and sparrow to use Tor/Onion, so I'm making some "progress" here I suppose. I'm not entirely sure what an Electrum server is yet, or how it'll benefit myself, or the network, but reading another reply on here I guess I'm about to head down that rabbithole as well. Cheers and thanks for the kind words!
Aside from the information window with things like connections, block height, etc, etc. Is there any neat bits on Bitcoin Core to look at? Things like how many transactions my node has personally verified or anything?
I would suggest running a full node on Tor instead of clearnet, if possible.Since you are already running full bitcoin node you can also do the same thing for mempool.space explorer, and you will get detailed information about transactions and mempool state.
This is great open source project and you can easily install it with one click or manually:
https://github.com/mempool
Aye, I've since setup tor and have configured both the node, and sparrow to connect through Tor. So I'm well on my way. Thanks!
It's great to have a full node, are you running it from an old computer, a server, a raspberry pi or what?
Sparrow Wallet will allow you to better integrate with hardware wallets.
The wallet will keep syncing so all new blocks will be checked and downloaded, if your internet is slow it will take longer to sync.
Sparrow Wallet will allow you to better integrate with hardware wallets.
The wallet will keep syncing so all new blocks will be checked and downloaded, if your internet is slow it will take longer to sync.
Neither I guess. It's being ran on a new computer (i7-12700k, 64GB DDR4, RTX 4080). I use 2x 2TB NVME's for most of my stuff, but the node is on a 1TB SSD.
After a couple of days of syncing, I've finally got my full node setup on a 1TB SSD. Feels pretty liberating to finally see the green power icon/switch on sparrow instead of the yellow public one. Granted I'm still using a CEX so the anonymity benefits of running a node are mute, it still feels pretty neat to be able to verify my own transactions, and even better I can verify others and help out the network! Aside from the information window with things like connections, block height, etc, etc. Is there any neat bits on Bitcoin Core to look at? Things like how many transactions my node has personally verified or anything?
Anyways, just wanted to share with you guys that I'm doing my part and we've got another full node online! I literally have no one else in my life that would A.) care, or B.) even know what I'm talking about.
Anyways, just wanted to share with you guys that I'm doing my part and we've got another full node online! I literally have no one else in my life that would A.) care, or B.) even know what I'm talking about.