Topic: Blockchain.info type wallet development (Read 2197 times)

I think this is how blockchain retrieve the wallet after success login user : https://github.com/blockchain/My-Wallet/blob/master/bitcoinjs-lib/src/wallet.js
There are name "keychain" same as public key.

CMIIW

Late report, but from what I've finally had time to read on, I think that blockchain runs the client software but sending the wallet.dat file to the browser and back again to blockchain servers.  It updates the balances on login, refresh (the button next to logout), and (I think) any time the client password is entered.  So essentially, the data they store is encrypted password, 2FA, and private keys via wallet?

I have not worked on it as of yet... but I wish to do that soon. Moreover, the main dev of Carbon Wallet are talking in the thread I linked. Please report in that thread if u experiment with Carbon Wallet or come to know about any other open source wallet...

I think this is most likely, as far as I know, blockchain.info doesn't store any form of unencrypted wallets.


That's too bad. I'll check Carbon wallet out some more. Hopefully it's secure enough.
What do you guys think? Have you ever cloned the repo and tried it out?

Seems u r correct. It clearly states...


So, the only option left is Carbon Wallet.

If I'm not mistaken, Blockchain only published its client side code to be reviewed by the community for security reason (see https://blockchain.info/fr/wallet/security)

I don't think you can use it to clone easily a wallet

Oh lol no worries   

As a technology consultant in IT (and back as an engineer/econ major in school), I'm used to having to take a guess at how things work first and then rely on the more hard-technology-apt cohort to break things down for me...then I translate how systems/networks/databases can be used for business applications.  I've done some coding in my day, but like my Spanish (6 years in school), I read much better than I write (i.e. architect) when it comes to code.

That being said, I'll go read up on the repo again and see if I can't figure out how DBs are incorporated.  You're right - the simple authentication process (no 2FA) would have to go something like:

1 - user sends identifier+password to blockchain server through SSL channel to log in

2i - server hashes password, which if matched to hashed value, decrypts wallet.dat stored on server, granting access to the private key on client side

-or-

2ii - server sends wallet.dat file to user browser, where it is then decrypted

I think 2ii is the way it works - this is what I meant when I originally thought that the server didn't directly store the private keys.  The identifier must be another hash of the public address corresponding to the individual user's wallet.dat file.  So now that I think about it, the wallet must be the only thing stored on the server (illustrating why it's essential to back up your wallet if you use blockchain).  I'll keep reading through the code and maybe get a buddy to break it down for me further - I'll post back with any revelations.

Ooops...OK !!! It seems u are hurt at my reply. But I did not mean to do that. I just tried to give a logical conclusion to our discussion so that the next person can take up the actual issue, i.e. whether the github repo of blockchain.info can be used to clone a wallet.

Please dont mind about reply and let us know if u can enlighten something on this issue. Your point was correct that blockchain.info does not store our passwords. That is why their service is reliable and cloning may have a value because it can still be run without trusting the operator.

Heh, I do admit when I've realized things I was ignorant on previously...and then I post 'em.  Always figure maybe the thought process will teach others how to think about things.  I've certainly learned a lot from the open discussions on here.

U just replied your own question !!!

I guess they'd need to store associated 2FA account information as well

They may not store the password directly, but have to store it in some other format, probably hashed. Otherwise, how will the allow an user to log in ? What will be the check condition ?

They don't store passwords or balances, so what data do they need to store?

I was checking the files/folders on github. I dont see any .sql files or db folder in the project !!! How are they storing data ?

As it is on Github, I suppose it is. Some pro may confirm my guess...

Interesting, I've heard about CarbonWallet in the past. Made me read up some more on deterministic wallets.
But, what about the blockchain.info wallet service? Is it opensource?

There is another open source wallet project called CarbonWallet => https://bitcointalksearch.org/topic/how-is-carbonwallet-602240

But it is a deterministic wallet.

I'm also interested in this. Also curious if there are other open source wallet projects.

Does anyone know if https://github.com/blockchain/My-Wallet can be used to to run similar wallet service like blockchain.info ?