Latest posts of: oldseven

Show Posts
Pages: [1]

on: March 29, 2017, 07:12:21 AM

Quote from: achow101 on March 28, 2017, 01:43:18 PM Quote from: oldseven on March 28, 2017, 05:48:15 AM Quote In that case, then no full node wallet does what you want since BIP 32 does not always allow the xpub to generate addresses. When hardened addresses are used (they are considered more secure), the xpub is pretty much useless as it cannot be used to generate all of the addresses in a wallet. Ok. But I really need the xpub key. What should I do? Then no software meets your requirements. You can setup a local electrum server (which is a full node) and have the electrum client (on the same server) connect to your electrum server. That would provide exactly what you want, but it may be fairly difficult to setup. Thanks a lot. I will try this solution. It sounds a good idea.

on: March 28, 2017, 05:48:15 AM

Quote In that case, then no full node wallet does what you want since BIP 32 does not always allow the xpub to generate addresses. When hardened addresses are used (they are considered more secure), the xpub is pretty much useless as it cannot be used to generate all of the addresses in a wallet. Ok. But I really need the xpub key. What should I do?

on: March 28, 2017, 03:46:33 AM

Quote from: achow101 on March 28, 2017, 03:31:43 AM Bitcoin Core and Armory are pretty much your only choices for a full node wallet. There is mSigna, but I don't think it is supported or developed anymore. The latest version of Bitcoin Core meets all of your criteria. If you only want BIP 32 support because BIP 32 wallets are deterministic, i.e. you only need one backup, then Armory will also work as it is also a deterministic wallet (it was deterministic before BIP 32 existed). We are working on implementing BIP 32 for Armory, so that will be available in the next release or two. Thanks for your quick response. I also consider mSigna is not supported anymore because the last version is issued at Nov 2015 and the document cann't be downloaded properly. I need a BIP32 public key like "xpub..." for my straight server(payment gateway). Straight server can generate bitcoin addresses with the xpub. And when payment is confirmed, the bitcoin will straightly go to my wallet account which the xpub belongs to. So can Armory apply this kind of public key? Any solutions for me? Thanks.

on: March 28, 2017, 03:33:46 AM

Quote from: goatpig on March 27, 2017, 11:55:59 AM Quote from: oldseven on March 27, 2017, 01:52:57 AM My wallet version is 1.35c. I can see a root key(18 words phrase). Maybe it's the chain code you mentioned. It is not, that's just the root key. Let me get this straight, are you trying to implement Armory's derivation scheme, or are you under the misconception that a BIP32 compliant implementation can reproduce it? Because it cannot. I don't know the concept of ChainCode. Can you explain about it?

on: March 28, 2017, 03:15:42 AM

Recently, I was busy with selecting bitcoin wallet. But still not decided. Looking for some suggestion. What's I need? As following: 1.Running a full node. 2. Support BIP32/44. 3. Support Cold Storage or Hardware Wallet. Above three must be satisfied. 4.Multi-signature. 5. Support sending bitcoin as a batch. I already installed Armory and Bitcoin Core on win10. But Armory doesn't support BIP32. Above all.

on: March 27, 2017, 02:46:00 AM

Quote from: Holliday on March 24, 2017, 02:56:48 PM Is your Core client synced? Current number of blocks at the time of this post: 458737. Ah. My current number of blocks at the time of this post: 354414. Maybe something wrong with my installation of armory.

on: March 27, 2017, 01:52:57 AM

My wallet version is 1.35c. I can see a root key(18 words phrase). Maybe it's the chain code you mentioned.

on: March 24, 2017, 09:11:31 AM

Quote from: Carlton Banks on March 24, 2017, 08:57:30 AM The second key on your paper wallet backup is headed with the word "Chain Code". That key is the Chain Code, or extended public key in the BIP32 parlance. I have no a printer so I output it as a pdf file. And I still cannot found the Chain Code.

on: March 24, 2017, 08:47:25 AM

Quote from: Carlton Banks on March 24, 2017, 08:12:27 AM 1. It's represented by the Chain Code portion of your wallet backup (not sure how that's represented in the digital wallet, but it's clearly discernible on paper wallets) 2. Currently slated for version 0.97 Thanks. But when I tried to backup my wallet using "Make paper backup", I did't found the Chain Code portion you mentioned. Can you make it clear?

on: March 24, 2017, 08:00:22 AM

I'm using straight server which is a payment gateway server. It needs a BIP32 xpub key. But I know armory doesn't support BIP32. But I still want to know: 1.Where the Extended pulick key of my wallet like blockchain wallet or other wallet. 2.When will armory support BIP32 or BIP44? Thanks.

on: March 24, 2017, 07:41:52 AM

First step: I generated a receive bitcoin address of my account using my armory client which is watch only and offline. second step: I used my blockchain wallet to send a little amount btc(less than 0.001 BTC) to the address. third step: I rescaned my armory wallet and serval hours have passed, but the balance is still 0. fourth step: I queried the bitcoin address on blockchain.info and found it's balance is not 0. Transaction is successful. I don't know why?

on: March 24, 2017, 07:32:08 AM

Quote from: mocacinno on March 24, 2017, 07:11:13 AM Quote from: oldseven on March 24, 2017, 07:05:53 AM I generated a address on the page: https://bitcore.io/playground/#/address(on "LIVENET"). So I got one private key, one public key and one address. Then I used my armory client to import the private key above to my wallet. But I got an address which is different with the address I got from bitcore.io. I was confused. What's wrong? It seems to generate a private key in hexadecimal format, i have no idear if armory accepts this format or not, but it should be valid. you could potentially use the downloaded sourcecode of https://www.bitaddress.org, generate entropy, go to the "wallet details"-tab, enter the private key in hexadecimal format and convert it to WIF or WIF compressed and try to import those ones. The same page should show you the compressed address, which should match the address bitcore.io showed you. Once again: it has been ages since i last used armory, i have no idear what formats are accepted, for all i know, the keys should be in hexadecimal format.... Yeah. I got a correct address as I followed your advice.

on: March 24, 2017, 07:05:53 AM

I generated a address on the page: https://bitcore.io/playground/#/address(on "LIVENET"). So I got one private key, one public key and one address. Then I used my armory client to import the private key above to my wallet. But I got an address which is different with the address I got from bitcore.io. I was confused. What's wrong?

Pages: [1]