The TOR browser I have installed has a problem connecting to its own control port if that's useful information. I made a new tor browser that functions perfectly if there's a way to get that to override connections sent to the other tor browser?
Or a way for it to not need the tor control port as I don't think it's used anyway.
I don't think that matters. Is TOR running? If so, what happens if you stop it and then run Core? |
|
|
|
This topic has been moved to Trashcan. Duplicate |
|
|
|
|
Start with the -debug option and post the full debug.log from that (it may be very large).
|
|
|
|
Lovely. Still I'm perplexed as to why this topic cannot be hidden/deleted as I'm perfectly sure SMF can do that.
The forum does not moderate scams or scam accusations. Topics will not be deleted or moved to the trashcan for being misleading, being a scam, or anything else. The only reasons for a thread's removal is for violating any forum rules which do not have anything pertaining to scams or scam accusations. They only pertain to posting behavior (i.e. spamming, off topicness, duplicate threads, etc.), and those are the only things which will be moderated. |
|
|
|
is there a way to adjust the fee manually?
You can click on the Fee in the send dialog and a new dialog should appear that allows you to set the transaction fee. |
|
|
|
I know, it is what I meant to say. I just assumed that like in RSA keys, if you start with one public key and change just the exponent of it in order to change the hash, then it's private keys of all of these new keys would have the same factors and be able to calculate the private exponent for all these public keys.
Assuming that during key generation factors are not discarded and just private exponent kept.
I made a lot of assumptions here based on my understanding of RSA keys and how you could generate different hashes for public keys with same module by just changing the public exponent, so that the owner of private keys could generate a private exponent corresponding to the new public exponent. I assumed it is a similar process and that all of these public keys would be (visibly) connected in such a way. Am I correct?
No, ECDSA keys are not like RSA keys. You can't do that to ECDSA keys. |
|
|
|
This topic has been moved to Trashcan. Duplicate |
|
|
|
How many wallet.dat files can you manage at the same time?
As many as you want. What is the difference between using the native segwit format (that begins with b) from the one that begins with 3?
Is it just a temporal way to use segwit until the ones that begin with b are available or there are any pros and cons?
Native segwit addresses (bech32) make native segwit outputs which are smaller than the P2SH nested ones (3.. addresses). This saves you 22 bytes when you go to spend the output. |
|
|
|
However, you can generate many vanity addresses at once. Accordingly, the more simultaneously generated vanity addresses, the greater the chance to find one of them and the less its cost.
It all depends on the chance: the more the chance to find a vanity address, the cheaper it is.
Oh, I see. So any address generated can be a vanity address for a large list of prefixes so it can be more efficient. The only problem with this setup is the trusted third party. Everyone would have to trust that you don't give them the generated private key and that they don't give you their private key. But everyone is going to know their private key anyways, so there is a lot of security risk there. Instead of using a trusted third party, what you could do is have each participant generate their own new key pair. When you generate addresses, you add all participants' public keys along with the one you generated in order to find a vanity address. This would be multi-party split key generation. Once an address is found, all participants send their private keys to the person who got their vanity address. Then they generate new key pairs and send the public keys back to you for the next vanity address to be generate. In this way, no one but the receiver of the vanity address can actually know the full private key to it. I don't understand the goal here. If you want to create many vanity addresses from the same public key, then all of them will have one private key. So this isn't really for many users, it is if one user wants many vanity addresses and that they are transparently connected to each other for anyone to see.
You can't make multiple addresses from one public key, that's not how addresses work. It is only one public-private key pair for each address. What he is doing is that he would be doing split key generation where the public key generated is added to the public key owned by a trusted third party so that a final public key can be generated and its address generated. |
|
|
|
Add the following line to your bitcoin.con file: Note that this will mean nothing will be banned if your node thinks that all connections come from your router. What you should really do is have your router forward the connection to your computer instead of proxying it. That way your node knows that actual IP address of the node it wants to ban and bans that instead of banning your router. |
|
|
|
(for a 70% increase in capacity - hmm).
That's incorrect. Segwit does not make blocks 4 MB but only allow for a 70% increase in capacity. It almost doubles the transaction capacity and also only doubles the absolute size of a block. |
|
|
|
Those are called vanity addresses. Use vanitygen to generate vanity addresses: https://bitcointalk.org/index.php?topic=25804.0Or you can look in the services section and see if anyone is offering a vanity address generation service. If you do see one, make sure that they are doing split key generation. Split key generation means that you have a private-public key pair and give them the public key. They combine that with a randomly generated private key's public key and check if that matches the vanity address that you want. To get that vanity address's private key, you combine their generated key with your generated key. If they are not using split key generation, then they will have the private key to your vanity address and can steal all of your funds. |
|
|
|
Install a more recent version of Windows. You immediately get rid of many problems, such as drivers. Alternatively, you can run a virtual machine with Windows 10. To create a virtual machine, use this software https://www.virtualbox.orgThanks for the advice, but I think the devs would probably want Bitcoin to work on Windows 7 also. [EDIT: I guess I should add that this has not been shown to necessarily be a Windows 7 problem. No one else seems to be reporting the issue, but no one on this thread has claimed to have it working on Win7 either, so it's still unclear. The problem may be unique to my personal situation for all I know. All I am sure of is that 0.14.2 release worked fine on this machine, and the 0.15.0 rc's have not worked.] I'll take a look and try to replicate this on Windows 7. Bitcoin Core should work on Windows Vista and later; the only "modern" version of windows no longer supported is Windows XP. |
|
|
|
Yes, I tried that... The only thing I saw that looked like an error was this, at the tail end:
Can you please post the entire thing? What you posted are not errors that matter. |
|
|
|
The wallet is bitcoin core from around 2013 and I am only scanning the wallet.dat on a usb stick. Could you offer any pointers for finding what I need?. If I search for text with the editor I do get the words pkey appearing, would the hex strings around their occurrence be of use to me?. Thanks again.
What is preventing you from just loading it in Bitcoin Core or using a tool like pywallet? Unless your wallet is horribly corrupt, you shouldn't need to dig around in the wallet file manually. |
|
|
|
|
Install electrum on your computer. Then when you go through the "Make a new wallet" wizard, choose the option to enter a seed. Enter your seed phrase and use the Electrum defaults for everything else. Your wallet will be regenerated and you will be able to access your coins again.
|
|
|
|
So, a SHA256 private key is just a random 256 bits number.
There is no such thing as "a SHA256 private key". SHA256 is not a private key generation algorithm, it is a hashing algorithm. Do not use SHA256 to generate your private keys as it is not secure. The data that you are hashing will most likely not be random enough to be a secure private key. Private keys are ECDSA private keys, specifically private keys for the secp256k1 curve. They are just 256 bit random integers. Does it means that I can use a bitcoin address on any coin using the SHA256 algo?
You can use your Bitcoin private keys with anything that uses ECDSA and secp256k1. You won't have the same address and the import formats will be different because there is additional encoding to differentiate so that people don't accidentally use the wrong addresses. |
|
|
|
Probably not the best place to post this but I didn't want to post a thread because other people have more important problems. I'm with the translations once again, I want to know what the percentages refers to? like 'Wallet: %1' or something similar, they shouldn't be deleted in any case?
Those are format specifiers. There will be strings that go in the place of those percentages that won't be translated. These strings are usually IDs and such, e.g. "Wallet: %1" may become "Wallet: xFjsjKSn" |
|
|
|
|
The private key is just a 256-bit number. How wallets store them is up to the wallet implementation. You should not be expecting all wallets to use the same implementation for storing private keys.
|
|
|
|
|
Show Posts
