So : 1. Private keys are indeed generated through random numbers. Are these numbers simply converted into SHA256 to generate the Private key? Or are they hashed twice? Or is there more to it? 2. Brainwallets. Who the hell came up with such a stupid idea? Reducing bruteforcing techniques to only include dictionary words that can be counted by the finger. Do many people still use Brainwallets? 3. Are all the adresses (who would be generated) from 0 to 0xFFF... already generated? Could I land on wallets that are not existent if I bruteforce numbers? |
|
|
|
So, I have been thinking this through, and I kind of decided to go crazy all the way now. We all know that every BTC address has its own unique private key. And so for extra security, the private key is generated randomly, from a completely random set of 64 HEX chars. But this is where I'm lost. What exactly is "randomly"? I have searched and found over 4 or 5 essays about types of private key generation. And in many places I cannot understand some few nuances. Specifically, any 256-bit number from 0x1 to 0xFFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFE BAAE DCE6 AF48 A03B BFD2 5E8C D036 4140 is a valid private key. Why 0xFFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFE BAAE DCE6 AF48 A03B BFD2 5E8C D036 4140? Why not 0xFFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFE FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF? And when you're reading about Private keys you get to the " Elliptic Curve Digital Signature Algorithm" And again, " A private key is essentially a randomly generated number." What exactly is randomly generated? Is it as simple as rand() % 0xFFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFE BAAE DCE6 AF48 A03B BFD2 5E8C D036 4140 ? Where it takes any random number from 1 to 1.157920892373162e+77? and then hash them to SHA-256 twice? or is it more complicated than that? Wouldn't that lead to some wallets being completely easy to crack as their initial code being only a 6 char or 18 char number? It is random after all, don't go tell me about how low the chances are, I know they're almost infinite, but they're still a chance. Bottom line is, I want a clear idea of how "random" in generation bitcoin private keys is? Thanks for reading. |
|
|
|
I think registrations are closed, if this means something, it means that OP cannot pay any more members that enroll. The only good news here is that he may be serious about paying the ones aready enrolled, we'll wait and see I guess! |
|
|
|
Waaaaaaaah finally  [img ]http://puu.sh/cBz12/da258a6c55.png[/img] Thaanks! Congrats, friend! First time, I am getting involved in API related issue which I don't know anything. Because of you, I studied some!  Thanks!  ~~MZ~~ Well, I guess you know enough to help me out! I doubt I'd have ever thought of ssl settings before a loong search Thanks again and have a great day |
|
|
|
Maybe the ssl certificate is not there? Where can I find server.pem / server.cert
You just want to write rpcssl. Try removing ssl related contents. From Blockchain.info , read this too: Security:
This api is currently incompatible with two factor authentication and it must therefore be disabled. We HIGHLY recommend you enable double encryption which can be found on the My Wallet account details page.
If you will be accessing this API from a server with a static ip address is recommended you enable the IP Lock found in the Security Section of your My Wallet account.
P.S. Try: $ ./bitcoind -rpcconnect=rpc.blockchain.info -rpcport=443 -rpcssl -rpcuser=YourWalletIdentifier -rpcpassword=YourPassword getinfo
~~MZ~~ Waaaaaaaah finally  Thaanks! |
|
|
|
These are the important ones, others are optional:
-rpcuser - Should be set to your wallet identifier. This is a 36 character random string which can be found on your wallet login page.
-rpcpassword - Should be set to your main wallet password. If double encryption is enabled your second password will need to be set using walletpassphrase
-rpcport - Should be set to 443 for https:// (when the -rpcssl is provided) or 80 for plain text http://
-rpcssl - Set to use a secure connection (Recommended)
~~MZ~~
Maybe the ssl certificate is not there? Where can I find server.pem / server.cert |
|
|
|
Have you enabled double encryption? If yes, you will have to change config file. -rpcpassword -- Should be set to your main wallet password. If double encryption is enabled your second password will need to be set using walletpassphrase You probably want to read 'Methods' in https://blockchain.info/api/json_rpc_api for API calls and its description. ~~MZ~~ No I haven't :/ I don't understand, when I run the bitcoind with no method/command, It starts downloading random blockchain data, but when I send the getinfo command, it gives me this error |
|
|
|
Some may have not seen the post or they couldn't get what was the problem, this maybe the reason there was no reply. Anyway, lets come to the problem! The config file isn't correct, rpc host must be set to rpc.blockchain.info, i.e., rpcconnect=rpc.blockchain.info . Connecting using Bicoind: $ ./bitcoind -rpcconnect=rpc.blockchain.info -rpcport=443 -rpcssl -rpcuser=YourWalletIdentifier -rpcpassword=YourPassword getinfo
P.S. Bitcoind Commands Not Available:getwork setgenerate getmininginfo getmemorypool - Not intended for bitcoin mining keypoolrefill - blockchain.info wallets have no keypool stopwalletpassphrasechange - Disabled for security reasonsdumpprivkey - Disabled for security reasonsencryptwallet - All blockchain.info wallets are encrypted by default. Password change is disabled for security reasons ~~MZ~~ Oh I aready set it to rpc.blockchain.info, sorry if the other person didn't. Here is everything on my bitcoin.conf, I looked for a pre-set one, and edited it removing what was useless, should I remove anything else? server=1
rpcuser=xxxxxx-xxx-xxxx-xxxx-xxxxxx
rpcpassword=password
rpctimeout=30
rpcport=443
rpcconnect=rpc.blockchain.info
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem |
|
|
|
I did a little improvement and now instead of not knowing at all how this works, I only get this error "error: could not parse reply from server". It's funny how there is only one post in here with the exact same problem as mine, but absolutely nobody cared about this guy. I was trying to get bitcoind v0.8.1 hooked up to the blockchain.info JSON-RPC and I kept getting: $ bitcoind getinfo
error: couldn't parse reply from server
My ~/bitcoin/bitcoin.conf file: rpcconnect=blockchain.info
rpcport=443
rpcssl=1
rpcuser=MyWalletGUID
rpcpassword=MyS00perS3cretPassword
printtoconsole=1
debug=1
I can't figure out what is wrong, I can get curl to work fine and it returns results as expected. I know I had this working some months ago, which makes me think that maybe it is a problem with the newer bitcoind (which I just installed from apt this morning: Bitcoin version v0.8.1.0-g34d62a8-beta)? |
|
|
|
|
Hi, I am a complete newbie in using any JSON RPC API, I looked a bit in the several APIs out there and decided I would use the Blockchain.info RPC host.
But then I'm now stuck on how exactly do we connect to this host. I am using a windows 7, should I have another OS? I can put a linux on a virtual machine, but only if it's completely necessary.
I also downloaded Ruby, but I didn't understand how exactly I can connect.
Can anyone give me a short procedure on how to you connect to the blockchain rpc host? I would be really glad, thank you.
|
|
|
|
wow, big rate
Hopefully not too big to be true |
|
|
|
Well, I don't know about that. I'm not defending them or anything, just posting my experiences so anyone else who's in doubt or afraid can at least find a thread of other people's findings. The amount of money involved in my case is a lot more than $100.
Unfortunately when I now login I get the message 'The user is suspended. Contact support' so I can't post a screenshot of all withdrawals. Instead this list just of e-mails to show what went through after their shutdown-email:
* 2014/10/29 11:07 Your request to withdraw 0.1xxx BTC has been completed. Note that I did this withdrawal 18 hours prior to the actual transfer of the funds.
* 2014/10/29 13:50 Your request to withdraw 3.xxx BTC has been completed. This and the following withdrawals went through within an hour or so.
* 2014/10/29 14:02 Your request to withdraw 0.2xxx BTC has been completed.
* 2014/10/29 19:41 Your request to withdraw 0.9xxx BTC has been completed.
* 2014/10/30 11:50 Your request to withdraw 1xxx EUR has been completed. This means that we've queued the transfer with our bank. A fee was deducted to cover our banking costs.
Those were all my funds that were there and that I acquired by trading just until the very end. So my balance is 0 (and probably therefore my account is suspended). I will let it know when the Euro withdrawal is received.
I think that between all this something else is going on, for example that there is some kind of announced audit because they filed for bankruptcy or something. I don't know but maybe there is a reason for them to clear out the exchange as soon as possible. Still I am satisfied that, up until now, it looks like my funds are not goxxed.
EDIT: I didn't use Stellar or Ripple just BTC/EUR so about that or the hack/implementation error I can't comment.
I myself got my account suspended for no reason a week before the "We're closing statement". The support completely ignored me. Nothing. I lost over 2 BTC because of this. |
|
|
|
|
He's scamming the big guys, anyone with less than 100$ invested "can withdraw", most of the people I know still have problems with their withdrawals..
|
|
|
|
|
Aaaand I'm joining this one!
Post count : 125
Address : 1UpZee6w3MZgiQ4EHehBCnT9jLQxMeoh9
|
|
|
|
|
Thanks RCHumphrey for the ride! Leaving campaign to another one that pays monthly because I'm that lazy. RC is a good member and paid out for all weeks. Too bad I lost all of those payouts because of a shit exchange.. But oh well, good luck to your forum man! Cheers.
|
|
|
|
|
Last Member Enrolling!
Post Count: 124
Rank: Member
Bitcoin Address: 1UpZee6w3MZgiQ4EHehBCnT9jLQxMeoh9
EDIT : Derp. Never mind.
|
|
|
|
I think they had other problems on their mind than dealing with your suspension. The e-mail said their bank wanted to shut them down and they couldn't find another bank in Norway that would accept a digital currency business.
I still trust these guys. I wish they didn't quit but continued as a cryptocoin-only exchange.
Being an exchange, is not an easy job. You have to be able to deal with not only the pressure of banks and funds and legal commitments and whatnot, but also to your users inquiries. The support has not replied to me in 5 days. That is not behavior of an exchange. That is the behavior of a scammer that just took your funds worth 1000$ and ignored you because he has the money. You trust them because you're not in my shoes. You withdrew your money and you're like 'oh well I'll miss the exchange', but I'm afraid I'll carry this to a lawsuit if I don't receive my funds and the website closes permanently. |
|
|
|
I have been suspended! I can't withdraw them! What sort of joke is this?
They used STR & XRP fund to cover their losses. Those guys are crooks after all ! I am losing funds of up to 2 BTC... It took me 3 full days of socializing with every single person I know to gather this much funds. And now I'm losing it just like that. |
|
|
|
|
I have been suspended! I can't withdraw them! What sort of joke is this?
|
|
|
|
Hi, sorry to bother all of you guys here, I feel like I'm knocking on a mafia mob's door. Anyways, can anyone of you here help me with some image files that I need explained please? They're in Russian and I have zero knowledge about the language. Would greatly appreciate the help. Thank you! EDIT : I have paid a russian mob to help me! And am now in debt for the mafia! (but seriously I've already translated what I need, thanks guys! ) |
|
|
|
|
Show Posts
