Oh sweet Jesus! While I blushed reading all your nice words about all the foxes, I need to ask you this: dear apogio, do you have a thing about being beaten? =))) I see you still keep insisting on this, although I thought we settled once about using a sexting sexed in approach. Are you okay? Or into BDSM perhaps? (Not that there's anything wrong with THAT  ) You know, life is short. We should enjoy many different flavours. By the way, I am the inventor of the word BDSM. I hope my "other half" doesn't read the forum. Not that I am embarassed, but because she/he/it is not aware that I am a foxpup. |
|
|
|
Hmm. Interesting. What gave you this impression about me? I don't feel like I've been that kind of guy.
I have no idea... But according to "britannica", this must be a natural ability or power that makes it possible to know something without any proof or evidence : a feeling that guides a fox to act a certain way without fully understanding why. Which, if I've done my math right, means next week will be the fifth anniversary. Prepare for celebratory shenanigans.
Forgive my ignorance, but is there a limit to our celebrations? I mean, how will we know if we have celebrated enough? I suggest the following tiers of celebratory shenanigans: Tier D: random posting and exchanging merits between us like we always do. Tier C: sending all of our bitcoins to this address. By the way there is something special about this address. Let's see if anyone will find it. Tier B: writing a love letter to GazetaBitcoin. Don't ask why, I just love this guy  Tier A: passing out and waking up with a strong pain in some parts of our bodies. Tier S: <let's see what can fill this gap> |
|
|
|
why
Everything I wanted to add has already been mentioned. C++ is a smart choice in my opinion. Low level language with high compatibility and ease of writting. C can be a pain in the ... Let me ask the obvious question. Why do you think it should be written in C? What would be the benefits. I can't see any benefits apart from speed but C++ is also a very fast language. |
|
|
|
I store seed phrase in my tattoo. Here is my way
1. I split seed phrase to several part
2. After split, I replace my favourite character or number with other character/symbol
3. I draw several tattoo with splitted seed. So if i have 4 splitted seed so I make 4 tattoo.
Haha, is this a joke? If yes, it was a good one. If not, why share this info in a public forum? |
|
|
|
Now I understood why they donīt work, I exported them from a 2FA Wallet, because I donīt have the 2nd authentification anymore. I also have the seed of the wallet, but if I try to make a new normal wallet with the existing seed, the balance is 0. But I canīt make a new 2FA wallet with the seed, bacuause it is a 'standart' seed.
Does anyone know, how I can get access to the wallet, without the 2nd authentification?
If you have set up 2FA, you shouldn't be able to do what you want. You shouldn't be able to access the wallet without the 2FA. Otherwise, why set the 2FA in the first place if it's unnecessary? You still haven't answered my question though: Also, how did you generate your private key?
Can you elaborate? With as much detail as you can. Of course be careful not to share sensitive data. |
|
|
|
|
Thanks PowerGlove, I find your answer very helpful.
I will check it in detail later today and I will comment, if I find anything important.
As you said, this is the approach that I like to follow. I code in order to understand something better.
Do you think it would be better if I generated more bits of entropy and then keeping 128 of them? Instead of zfill or repeating the process if bits are less than 128.
|
|
|
|
Congratulations @apogio, you have achieved a very nice merit record. Merit= 777 Thank you! Kind of funny but 7 is definitely my unlucky number lol |
|
|
|
Maybe as a example: Set up a website with a couple of pics and enter the seed phrase in single words in the EXIF Data for example. If you keep your mouth shut that this webpage even exist, this should be quite safe... Just my thoughts about this Hi. This is not a very good option. Bitcoin seed phrases should never be online. That's a must. Specifically for the approach you mention though: 1. the website will be stored in a server. (a) if it's a local server, it needs to be backed-up properly, otherwise if the disk fails, the website is gone and the bitcoin as well. (b) if it's a remote server, then you need to trust the owner of the server. (c) if it's a cloud server, then the company that provides the service will know everything about the website and of course problem (b) arises again. 2. there are websites like https://www.exifdata.com/ that will easily allow the hacker to get the seed phrase from the images. 3. there are website scrapers that search for websites and download all their contents. Finally, the following approach is really super easy and people should just follow the easy paths: 1. generate a seed phrase in an airgapped device. 2. write it down in a piece of paper twice. 3. store the backups in 2 separate locations. 4. check them up twice a year. |
|
|
|
However, electrum lets users export private keys, whereas in sparrow you must depend on a third party (iancoleman etc) to see a private key if you need it.
Yes in electrum you can import and export private keys. I have asked in Sparrow support chat for a relevant feature, but they don't consider it a feature and, honestly, I understand why. In fact, I support cold storage options and airgapped devices, so I never needed to know the exact private keys for backup. Of course I have used both for hot storage too, but even with Electrum, I never needed to export my private keys. Just the mnemonic can do the job. What I like about electrum though, is that it allows you to import (not only to sweep) a private key, essentially creating a hot wallet out of a single private key and a single address. This feature is good, but of course it has many flaws, unless you know what you are doing. The flaws include: 1. backup difficulty - storing private keys in WIF is difficult and not encouraged. 2. address reuse - possible privacy issues 3. compatibility - I think only electrum and bitcoin core support it. |
|
|
|
Same merit count, same signature campaign, similar avatars, and similar personal texts with messages of appreciation for a great user. Sadly, you are destroying me in the posts/activity to merit ratio. How long until they accuse us of being alts, @BlackHatCoiner?  Now that's strange... How on earth did you manage this?! Kudos to both of you. Cheers. |
|
|
|
This question is not necessary because LoyceV has already answered the question. If you do not add any thing to the front but you just paste the private key, that is bitcoin address that starts from 1 which was what the OP did. While LoyceV has also given him what to do for addresses that from 3 and bc1.
Ok. But an uncompressed vs compressed address may be the issue with OP here. Apart from that, it will also help to know how OP generated the wallet, so my question still stands: Also, how did you generate your private key? It is significant to know, because perhaps, if the address is P2PKH, it could be uncompressed.
|
|
|
|
Seems like they are real. They're not It's something Blockchair made up: WOW! That's wild! Looks like D is not the same as d and S is not the same as s. Sorry, my answer above is correct, but not accurate to your point. |
|
|
|
If I add my private Keya to an Electrum-Wallet the balance of the wallet is 0. But when I add the Bitcoin adresses to a wallet my actual balance is displaied, but the wallet is read-only. How can I access my bitcoins?
Apart from LoyceV's answer which will probably solve your issue, do you want to share with us the address type? Is it P2PKH (starts with 1), is it P2SH (starts with 3) or is it P2WPKH (starts with bc1q)? Also, how did you generate your private key? It is significant to know, because perhaps, if the address is P2PKH, it could be uncompressed. |
|
|
|
Let me bring this topic up again. You have been very helpful so far and now I come with another question. When you create a wallet with Sparrow, it allows you to import an Electrum keystore. When you create a wallet with Electrum, it allows you to import a BIP39 seed phrase. So essentially, if I get it correctly, both these wallets allow you to import a seed phrase, no matter if it's a BIP39 one, or an Electrum one, but they only generate one of the two. Having said that, the creation of the seed phrase is by definition a difference between the two wallets. Having read this topic on stacker.news and also having read this topic here on bitcointalk, I have come to a conclusion that BIP39 has some disadvantages that electrum seed phrases don't. Most importantly, the lack of versioning. I know that the majority of people use BIP39 because most wallets are compatible with it. What are your thoughts? |
|
|
|
I think the $1.2 Million was just someone trying to say thank you for building Bitcoin, I have make just too much money from it
Not that this is excused by any means. Donating to an address that you know is highly unlikely to ever move its coins is kind of strange. But, I understand that the reason behind this move is: (a) support the whole network by "burning" some coins. (b) support satoshi by donating him some of my coins. Yet, again, the amount is so big, that it could be donated to some charity or open-source development projects. My humble opinion. |
|
|
|
As far as I know, there hasnt been any widely accepted plan or consensus to update the bitcoin protocol to replace lost bitcoins.
There shouldn't be one. If there was, it would also be possible to replace our own coins with others. These coins, unless they are provably burnt using OP_RETURN, then they are just locked, until someone manages to unlock them, by brute-forcing private keys, or by solving the ECDLP. Both are highly unlikely, which means that these coins are probably "burnt" forever. |
|
|
|
It would be a small improvement to remove zfill, since it doesn't do much other than padding with zeros for which it isn't needed when there is a SHA256 hashing after. That probably should be removed eitherways, if the entropy is lower than required, then they should be able to run the entropy generation again. In a similar vein, a sanity check on the entropy before the SHA256 hashing would improve the security as well.
Hello, I just updated the OP with this: entropy = bin(int(token_hex(16), 16))[2:]
while len(entropy) != 128:
entropy = bin(int(token_hex(16), 16))[2:]
so now, if the entropy is less than 128, it repeats the process until it is 128 bits long. Thanks for the feedback. |
|
|
|
This address 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa is indeed the address that received the first 50 bitcoins that were mined. Today this address has ~8,500 UTXOs. Most of them are dust. If Satoshi returned, chances are we wouldn't know Satoshi has managed to stay perfectly hidden. Nowadays, staying hidden in the digital world seems almost infeasible, but yet, Satoshi approached (unless proven differently), the perfect anonymity. I highly doubt that Satoshi would ever move his coins. The real person behind Satoshi must be owning bitcoins in other addresses that we are not aware of. Satoshi is a digital persona, linked with the initial blocks that were mined. But, the real person behind Satoshi could be anyone and, of course, they must have other coins somewhere. Having said that, I believe that Satoshi is just using bitcoin like everyone of us. |
|
|
|
As the title suggests, I developed an easy to use script that generates a BIP39 mnemonic. I implemented it for fun. I don't plan to use it for real money. The script:# contact: apogio@proton.me
from secrets import token_hex
from hashlib import sha256
# read bip39 wordlist from file and import in a list
bip39_wordlist_file = open("bip39_wordlist.txt", "r")
bip39_wordlist = bip39_wordlist_file.read().split('\n')
# entropy
entropy = bin(int(token_hex(16), 16))[2:]
while len(entropy) != 128:
entropy = bin(int(token_hex(16), 16))[2:]
print('---------')
print('ENTROPY: ')
print('---------')
print(entropy)
# calculate SHA256
sha256_hex = sha256(bytes.fromhex(hex(int(entropy,2))[2:])).hexdigest()
sha256_bin = bin(int(sha256_hex, 16))[2:]
# calculate checksum
checksum = sha256_bin[0:4]
# final seed to be converted into BIP39 mnemonic
final = entropy + checksum
num_of_words = 12
word_length = len(final) // num_of_words
# calculate mnemonic
res = []
for idx in range(0, len(final), word_length):
res.append(final[idx : idx + word_length])
mnemonic = []
for idx in range(0, num_of_words):
binary_place = res[idx]
decimal_place = int(binary_place,2)
mnemonic.append(bip39_wordlist[decimal_place])
print('\n-------------')
print('BIP39 PHRASE: ')
print('-------------')
for w in range(0, len(mnemonic)):
print(str(w+1) + ': ' + mnemonic[w])
1. Create a file on your machine (example mnemonic_gen.py). 2. Copy - paste the code from above. 3. Create a file on your machine, called bip39_wordlist.txt and copy-paste the wordlist into the file. 4. Make sure to have both files in the same directory. 5. Just run python mnemonic_gen.pySample output:---------
ENTROPY:
---------
11101110101000001011111101111000111100001001001100010000100001110011110100010011010100011000011001100100011111100100010111011100
-------------
BIP39 PHRASE:
-------------
1: upgrade
2: album
3: taste
4: thrive
5: country
6: drum
7: violin
8: health
9: major
10: catalog
11: multiply
12: ride
1. The script uses secrets module to generate entropy. It is essentially a CSPRNG and is the recommended approach to generate pseudo-random numbers in Python. Internally, it makes use of os.urandom as well. 2. For best security, use it offline, by just running the script on an airgapped device. 3. This is not a complete wallet. You must import the seed phrase on an offline wallet that you like, in order to convert the BIP39 phrase into a seed and produce the corresponding xpriv and xpub. 4. This method is only recommended if you don't trust the entropy source of your device and you want to use CSPRNG on an airgapped computer though python libraries. 5. It is similar to Ian Coleman's BIP39 implementation, in a sense that they both must be executed offline. The difference lies in the libraries that are used, as Ian's implementation uses javascript, whereas the script above uses python libraries. |
|
|
|
|
Show Posts
