|
For the record... your Bitcoin Core error was caused by corruption in your block database... you'd need to delete the contents of your Bitcoin Core blocks folder and resync Bitcoin Core from scratch.
In any case, I'm glad you managed to get your private key(s) successfully exported and imported into Electrum. As bob123 said, if you want to continue using Electrum, I'd also recommend that you create a new "standard" wallet that has a 12 word backup phrase... it's like the Armory "Root Key", it will enable you to restore/recover your wallet using just the 12 words in case of hardware failure/data loss etc.
|
|
|
|
Probably a dumb question, but anyway. Would it be safe enough to just change my wallet passphrase, then claim the forkcoins, and then change it back?
No. The wallet passphrase is only required if you are needing to unlock a given wallet file. If the attacker has your private keys... they don't need your passphrase at all. By importing your seed/private keys into other (somewhat) untrusted forkcoin wallets to claim these coins... you are potentially exposing your seed/private keys. This is why you are advised to move your bitcoins to a completely new wallet (with a new seed/private keys)... that way, when you import the old seed/private keys into a forkcoin wallet, there is no chance your BTC (obviously the most valuable) can be stolen... because even if the wallet application turns out to be a scam and sends your seed/private keys to scammers, the scammers will only be able to get the low value forkcoins, as your BTC is no longer being controlled by the stolen seed/keys. |
|
|
|
Just FYI, your code is Python 3 compatible only... PK4 = PK1 + str(checksum)[2:10] #I know it looks wierd
If you run that in Python2, it gives a really weird result as the str(checksum)[2:10] is only returning 6 chars instead of 8. Instead of str() on the bytes object, you should probably use the .decode() method... so, a "better" solution might be: # From private key(hex) to Wallet Import Format(WIF)
# Reference: https://medium.freecodecamp.org/how-to-create-a-bitcoin-wallet-address-from-a-private-key-eca3ddd9c05f
# https://docs.python.org/2/library/hashlib.html
import codecs #If not installed: "pip3 install codecs"
import hashlib
# PK0 is a demo private key.
PK0 = "3cd0560f5b27591916c643a0b7aa69d03839380a738d2e912990dcc573715d2c"
PK1 = '80'+ PK0
PK2 = hashlib.sha256(codecs.decode(PK1, 'hex'))
PK3 = hashlib.sha256(PK2.digest())
checksum_bytes = codecs.encode(PK3.digest(), 'hex')[0:8] #get checksum as bytes
checksum = checksum_bytes.decode("utf-8") #convert byte array to string
PK4 = PK1 + checksum
# Define base58
def base58(address_hex):
alphabet = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'
b58_string = ''
# Get the number of leading zeros
leading_zeros = len(address_hex) - len(address_hex.lstrip('0'))
# Convert hex to decimal
address_int = int(address_hex, 16)
# Append digits to the start of string
while address_int > 0:
digit = address_int % 58
digit_char = alphabet[digit]
b58_string = digit_char + b58_string
address_int //= 58
# Add 1 for each 2 leading zeros
ones = leading_zeros // 2
for one in range(ones):
b58_string = '1' + b58_string
return b58_string
WIF = base58(PK4)
print(WIF)
That should work on both Python2 and Python3  |
|
|
|
Connections are being added automatically now. 7 is the highest number that I've seen displayed. Thank you for the help!
Yeah, sometimes it just takes a while for your node to discover (and be discovered by) other peers... Is the sync progress actually increasing now that you have a good number of connections?  |
|
|
|
I have an old i5-3570k with only 8Gigs... Armory works "OK" on my rig (like most things, a little "slow"  ) I don't think you should have any issues with a Ryzen5 2600 and 16 Gigs |
|
|
|
And your friend is 100% sure that they saw this address and the balance within their Coinbase wallet app? It honestly seems like either: - This address was not generated from their coinbase wallet app at all and they actually got it from somewhere else or - They have the wrong seed It's incredibly strange that you have a seed mnemonic that is generating transaction history etc... but is missing one particular address. The only other explanation would be some random bug in the wallet app that generated an address using some unknown derivation path. It's not impossible, given that their app seems to be not showing me some of my transaction history   |
|
|
|
I think it was a mistype... and they meant 11sat  |
|
|
|
open the .txn file using any text editor on your mobile, copy its content then load it on Electrum by clicking the paste button. It worked for me.
That is a very nice (and somewhat undocumented) feature... thanks for sharing!  So I guess the only option is to broadcast it using coinb.in
As above, you can follow khaled0111's tip and just "copy" the raw hex using a text editor on your Android device, and then in Electrum Android, on the "Send" tab... click the "paste" icon... it'll give you a preview of the signed transaction and the option to broadcast |
|
|
|
I asked Coinmama to transfer to Legacy address format and it started with 33TQ, why ? - it was not cash address format, like it should have been right ?
So the address that you attempted to send the BCH to, starts with a "3"? If that is correct, then I am assuming that on the title bar of your Electrum screen, next to the wallet name... it says "[2fa]"... like this:  If that is correct, then unfortunately, you have no real option but to follow the somewhat complicated procedure as shown by nc50lc above... "Electron Cash" does not support Electrum "2fa" wallets as TrustedCoin does not support BCH transactions. The solution is to restore a "disabled" version of your 2fa wallet as outlined above in the first part... this will give you 2 master private keys (the xprv's) and 1 master public key (the xpub)... from that you can reconstruct the wallet as a "normal" multisig wallet in Electron Cash (as outlined above in part 2). |
|
|
|
Attempted addnode and connect commands in the console
Ahhh ok, you asked about bitcoin.conf... the previous example was bitcoin.conf option. In the console, the command syntax is different, it should be: for example: |
|
|
|
I currently have 1 active connection to the bitcoin network. That happened after I dropped my personal firewall.
Is there a way to enter IP addresses for bitcoin nodes into the bitcoin.conf file?
yeah... you can use the addnode command... either with bitcoin-cli, in the console in Bitcoin Core GUI or in the bitcoin.conf file. As per the examples on the bitcoin github: # Use as many addnode= settings as you like to connect to specific peers
addnode=69.164.218.197
addnode=10.0.0.2:8333
|
|
|
|
Armory won't work properly until Bitcoin Core is finished syncing... As for the version of Bitcoin Core required for the old version... I am not 100% sure which version it was that basically "broke" the old versions of Armory. Now, I need to ask, are you wanting to continue using Armory in the future? or are you simply trying to recover funds? If you're just trying to recover funds, you'd be better off just exporting the private keys from Armory and importing into another wallet like Electrum etc. |
|
|
|
By default, Bitcoin Core will download and save the blockchain data to your C: drive (unless you explicitly tell it to store it somewhere else)... currently, this is over 350+ gigs worth of data. Do you have enough free space on your C: drive to hold that data? If not, and your drive is out of space... that is likely the reason for getting the fatal error. Otherwise, have a look in C:\Users\YOURUSERNAME\AppData\Roaming\Bitcoin and look for the "debug.log" file. You can open this in a text editor like Notepad++. Have a look towards the very end of the file and see if there are any "obvious" error messages for why Bitcoin Core is crashing. You can also copy/paste the contents of debug.log to https://pastebin.com/ then click "create new paste"... that will generate a unique URL which you can copy/paste here and we can take a look at your debug file to see what is wrong. |
|
|
|
I`m scared to type the seeds again in to my laptop.
Can I send my coins safely to a ledger s without reopen my electrum wallet?
Why do you need to retype your seeds? Did you delete your Electrum wallet file? If you still have the wallet file, you should be able to open it with Electrum without needing to enter your seed. Then you can simple connect your Nano S to Electrum using the "New/Restore -> Standard wallet -> Use a hardware device"... and send all your coins from your old wallet to an address from your Nano S wallet. |
|
|
|
Hello, i have a very old Bitcon Core Version from 2011 on my Macbook. If i start the Programm everything is empty, but if i check my bitcoin address there is something ;-)
Most likely because your old version is not "synced"... so it's data is out of date. I donīt want to make a mistake. I read something about a wallet.dat but i canīt find this on my macbook? What should i do and is the best advice - update this to the newest version or how can i find my private key? You have several options... but before you start... find your wallet.dat and make a couple of backups! Then your options are: - Install latest version of Bitcoin Core. Let it sync... see coins... be happy! or - Use dumpprivkey command in version of Bitcoin Core you have installed... then import privkey into another wallet... see coins... be happy! But the most important thing is to find the wallet.dat on your macbook and make some backups before your try anything else!!! |
|
|
|
Can I simply download the BCH wallet and replace the wallet.dat with the one in my BTC wallet?
Yes... If you have been using Bitcoin Core, then the wallet.dat from that will be compatible with the BCH "Core" wallet. You'll need to download BitcoinABC or whatever the "core" BCH wallet is these days (given the whole BCHA and BCHN bunfight, it's difficult to know which is the "real" Bitcoin Cash shitcoin  )... then put a copy of your Bitcoin Core wallet.dat into the datadir for the BCH wallet app. Then open the BCH app and let it fully sync. |
|
|
|
I increased the fee to 10 Satoshis in Electrum as per your suggestion.
Unfortunately, that isn't enough now... that message suggesting 10 sats/byte was written hours ago... the fees are always constantly changing. This is why you need to check the current state of the network before setting a fee if speed of confirmation is important to you. Always check here: https://jochen-hoenicke.de/queue/#0,2hand here: https://mempool.space/As you can see, as I type this... to be close to 1meg of the tip you need to be using ~20+ sats/byte:  It's constantly changing, by the time you read this it will probably be different. You keep linking to the address... not the actual transaction... Try this: https://blockchair.com/bitcoin/transaction/63c1fbcd718de7cfcb17aca86c6036ba81bbdd8dea871e1d6579f44efc10173aand this: https://blockchair.com/bitcoin/transaction/fc20da9ca6d90913f8dc0d5b19d0a63b58319def64ad8dab20df803af9324817Why did the balance double to approx $88 from $44.
It's because of the "double spend" caused by using RBF... when you "bump fee", it creates a 2nd transaction that should get confirmed before the 1st transaction... nodes that support RBF should realise it is an RBF and "drop" the 1st from their mempool, but not all nodes do this... So, for a period of time... both of your transactions exist... the wallet sees 2 incoming transactions, and it seems like you're going to get paid twice Of course, as soon as either one of the transactions gets confirmed, the other transaction instantly becomes invalid and will "disappear". EDIT: and now it seems like blockchair has figured out you're doing an RBF ("double spend") and has removed the lower fee transaction... so the balance is showing "correctly" Can the fee be increased multiple times.
Yes, if you don't mark it as "final" when doing the RBF. If you mark it final, it basically turns RBF "off" and you won't be able to bump the fee any more. Why is Armory rated as the best wallet in one list and third best in a second list Which lists? Like a lot of "10 Best XXXXXXX's" type lists, these "ratings" are generally terribly subjective and rated according to whatever criteria the list author decides to use. Their priorities may not align with yours. It's like movie critics etc... just because they love foreign language films in black and white doesn't mean you will... or should. |
|
|
|
Can you try something for me... can you try installing the Mycelium wallet app: https://play.google.com/store/apps/details?id=com.mycelium.wallet and then restoring the seed in that application and check to see what transactions you can see? I've just restored an old Mycelium seed into Coinbase... and it's missing the first couple of transactions from the wallet history. So, it seems that perhaps the Coinbase app might be "broken"? But the last transaction is the one that is shown in the segwit wallet! WTF?! It's like the conbase wallet app contains different wallets with different derivation paths within itself and it exchanges between them from time to time. Yes, that is exactly what the Coinbase wallet does... Like I said, you can swap between SegWit and Legacy simply by tapping on the "Segwit" and "Legacy" tabs on the "Receive" screen... it swaps from one to the other. On the main screen it simply shows all the transactions from both the SegWit and Legacy "wallets"... at least, it should, but like I said, it seems to be missing a transaction or two? |
|
|
|
What a fiasco! Confirms my HATE for closed source. My .02
How is this in any way related to open source/closed source? The initial hack occurred because of a misconfigured 3rd Party API key... and the Shopify leak was because of an "evil maid"... neither of those things would have been prevented by Ledger having open source products. |
|
|
|
|
Show Posts
