how's is it still revealing my private key? if I show you my key as
5hutyAewDs9BsUqVh1Nivythf49VvEzGXpDYj37ZLtDxdDyXN7D
how would you even decode this to my real key?
Because that is the real private key. That is in what is known as Wallet Import Format. You enter this type of string into a wallet in order to import a private key, so it stands to reason that the private key can be derived from this string, and it can. That is actually the private key, just encoded into a certain format. That is the private key encoded in Bitcoin's base58CheckEncoding. Since the actual private key that is encoded is not hashed, it can thus be decoded into the actual key. So sharing your private key like this is actually sharing your private key and will result in your Bitcoin being stolen. This is not my Actual Private Key! I wanted a way to generate a Private Key like 5 BitcoinwDs9BsUqVh1Nivythf49VvEzGXpDYj37ZLtDxdDyXN7D so I can print it out on paper as 5 hutyAewDs9BsUqVh1Nivythf49VvEzGXpDYj37ZLtDxdDyXN7D Yes, I realize that, I misunderstood your question there. As others pointed out. Those 7 characters is not much protection. It will not take terribly long to brute force what those seven characters are.
|
|
|
Will stage two go back to a maximum of 200 posts or will it remain at 100?
|
|
|
how's is it still revealing my private key? if I show you my key as
5hutyAewDs9BsUqVh1Nivythf49VvEzGXpDYj37ZLtDxdDyXN7D
how would you even decode this to my real key?
Because that is the real private key. That is in what is known as Wallet Import Format. You enter this type of string into a wallet in order to import a private key, so it stands to reason that the private key can be derived from this string, and it can. That is actually the private key, just encoded into a certain format. That is the private key encoded in Bitcoin's base58CheckEncoding. Since the actual private key that is encoded is not hashed, it can thus be decoded into the actual key. So sharing your private key like this is actually sharing your private key and will result in your Bitcoin being stolen.
|
|
|
There are many proposals which are dynamic block sizes. BIPs 100, 106, and 105 all are dynamic block sizes.
BIP 100 is a consensus voting algorithm for miners. It is not necessary to have a vote - the system can simply decide when the block size needs to be increased or decreased and do it automatically. No outside input would be required. Therein lies the problem. What is the correct block size? What does it need to be? That is where all of the debate is centered. What is considered right and how is that determined.
|
|
|
There are many proposals which are dynamic block sizes. BIPs 100, 106, and 105 all are dynamic block sizes.
|
|
|
I know you can create a vanity Bitcoin Address, but is there a way to create a Vanity Bitcoin Private key?
Sure. It's typically called a "brainwallet" and it's a really, Really, REALLY bad idea. Brainwallet is just a Passphase, what I wanted to do is have a private key that is BitcoinDjs9BsUqVh1Nivythf49VvEzGXpDYj37ZLtDxdDyXN7D Theoretically it is possible, but it probably is not secure. It would have to start with 5, K, or L since those are the WIF prefixes for Bitcoin.
|
|
|
I am finding it hard to get one in europe though so will have to pay a bit extra to get one over here, unless you know any decent place to get one in europe.
You don't need to have an escrow to be near you. The escrow can just hold the Bitcoin until either you confirm the receipt of the goods and they are as advertised, or one of you disputes. Of course that escrow will probably need information and proof like pictures, video, and tracking numbers. If they only hold the Bitcoin, then they do not need to be anywhere near you.
|
|
|
Auction closed. Someone bought the account for the BIN price.
|
|
|
You would have to use a trusted escrow. You send the Bitcoin to an escrow and then he sends you the miner. You confirm that the miner has reached you and then you tell the escrow to release the funds.
|
|
|
IIRC Bitcoin Core does not actually handle or store the multisig addresses, they are never actually added to the wallet. So actually none of transactions should show up. You will need to create the transaction manually using the necessary console commands.
|
|
|
Bitcoin and most forks use and support Qt 4.8. You can also use anything newer but it might not always work. It should though.
|
|
|
Thanks @altcoinhosting,
I've kept a record of the Date Stamp and also my Wallet Words however, I don't know what the "seed" is. What exactly is the seed?
Cheers
The wallet words are the seed.
|
|
|
What do you mean by install a blockchain? Downloading the blockchain for any coin is just installing the main client forked from bitcoin. It so automatically download the corresponding blockchain if people are using that coin.
|
|
|
Are you basically asking someone to run the website but you will provide the funds for the faucet?
|
|
|
Let's give it a try: 0.04BTC GL. Big accepted
|
|
|
Hi OP,
Just tried to check a different account on your site - was returned with a 'Remote Procedure Call - Failure. Please try again' error message.
I got the same result a few months ago when I tried inputting the Sam UID. What seems to cause this problem? Thank you, nice job with the site regardless!
Try it at a different time. If you use it around midnight Eastern Time, then it won't work since that is when the server restart happens.
|
|
|
They use different algorithms to generate the address. I don't think there is any standard way to generate a brain wallet address.
|
|
|
Potential activity is the activity that an account can potentially have. You can get up to 14 activity every two week period. If you make one post in that two week period, you get 14 potential activity. There is a whole description of how the activity works in a sticky in meta There are a few sites which can calculate the potential activity of an account such as http://bctalkaccountpricer.info
|
|
|
You need to specify the private key(s) you are signing with in the signrawtransaction command. The second one you did should work. I think you need to escape the double quotes, so just put a backslash (\) before the double quotes.
|
|
|
|