|
Check out Electrum. It should be able to do everything that you want.
|
|
|
|
It is not working at all. I backed up my .armory directory, then I deleted it and launched armory. It always complains about: The DB has returned the following error:
DB version mismatch. Use another dbdir!
Armory will now shutdown. Log files please. Are you sure you are deleting the right folder? Are you sure that is the folder that Armory is actually using as its datadir? Deleting the databases folder inside of the datadir should do the trick. |
|
|
|
|
Most Bitcoin wallets support importing private keys.
Bitcoin Core, Electrum, Armory, Mycelium to name a few.
|
|
|
|
I remembere that with the old edition of Electrum, I used a software called KeePass 2, for create the password or for to have a better use, I don't forget.
What version of Electrum did you originally use? If you still have KeePass, you can check to see if you have the password for electrum there. I tried to creat a new wallet from menu file, New/restore for move the bitcoin in this new wallet.
Creating a new wallet is not going to do anything to help you. Bitcoin doesn't work like that. I remember that in the period of setup, electrum don't ask me, addition of password neither the seed phrase.
How is it possible?
Are you sure? If you do New/restore > create a new standard wallet it should prompt you to set a password and backup the seed phrase. |
|
|
|
|
When you first installed electrum, did you go through the wizard to create a wallet? You should have. It should have prompted you to both set a password and backup your seed phrase.
If you do not have the password or the seed phrase for the wallet, the Bitcoin is lost.
|
|
|
|
seriously??
her goes i can grab your address of funds you have not spend.
You cannot do this with any address. You can only do that with a segwit output type which does not have any address type associated with it. Addresses for segwit will actually be P2SH addresses with the segwit script being the redeemscript of that p2sh address. Thus you cannot execute this attack with most segwit stuff since they will be protected by the Hash160. and not sign it.. and push it through a malicious pool i bribe to add in the transaction knowing that 3000 nodes will not be asked to check for a signature anyways.
so the block (containing the tx) gets relayed around the majority of the nodes. BLINDLY
however 3000 nodes have to wait and "trust" segwit nodes that have seen the signature to validate it on your behalf. for you to blindly ACCEPT IT
if a node is not validating a transaction signature itself then the node is not validating the transaction. it is BLINDLY ACCEPTING it and trusting that its valid by the hopes of previous nodes doing the job for them.
It is still checking other parts of the transaction for validity. Signatures are not the only thing to check for when checking validity of a transaction. The fact that it still checks validity as best as it can means that it is not just blindy accepting the transaction. Blindly accepting would be accepting a transaction regardless, even if it is invalid in some other way than just signatures, i.e. included in block but locktime has not passed yet. |
|
|
|
Thanks Danny (and achow101).
Do you know what the structure of a multisig output looks like (in OP codes)?
They look like this: OP_0 <pubkey1> ... <pubkey n> OP_y OP_CHECKMULTISIG
n and y must be below 15. OP_y specifies how many of the previous pubkeys must be used to sign the transaction. |
|
|
|
you will not be fully validating segwit transactions (but you will still be blindly accepting them while validating all other traditional transactions).
edited other post to be more upfront and avoid the contradiction which leads to misinterpretation They are still validating them as best as they can. It is not just blindly accepting them, the only blind acceptance part is of the signatures for segwit inputs, but the transaction is still being validated. It still has to check that the inputs are spending non-spent outputs. It still has to check the locktime. It still checks inputs that are not segwit inputs. It still runs the script validation for the segwit input, but it simply does not know of the signatures for those inputs. |
|
|
|
consequences?
You'll miss out on some optimizations and improvements added since whatever version you are running. Once segwit activates, you will not be able to take advantage of it, and you will not be fully validating segwit transactions (but you will still be validating them and all other transactions). You'll also see an annoying alert about how some unknown rules have activated and that you should upgrade. If you run a version of Bitcoin Core earlier than 0.12.1, you'll see an alert about the alert system retirement. After 0.14 comes out, that message will change to "Alert key compromised" |
|
|
|
Is one of these a scam?
No. Bitcoin.com is a website run by Roger Ver. It is primarily a site that gives out high level information about Bitcoin and contains news and some other stuff. It also tends to be not neutral. Bitcoin.org is the website created by Satoshi for Bitcoin. It is in the control of primarily Cobra and Theymos. The site provides both high level and low level technical information about Bitcoin, as well as a primarily neutral and unbiased information. It does not have news like bitcoin.com. Bitcoin.org also hosts the downloads for Bitcoin Core. Bitcoin.com serves a more commercial purpose whereas bitcoin.org is more informative. |
|
|
|
I upgraded my client to ver 0.13.1 today but I encountered some problem with my antivirus - Avast.
After an upgrade when I wanted to start my wallet Avast stopped the process did a deep scan and quarantined the bitcoin-qt.exe.
Apparently bitcoin-qt.exe is infected with Dyna:BitCoinMiner-CR[PUP] - but I am pretty sure it is a false positive.
Verify the hashes. The antivirus flagging bitcoin-qt isn't new, it has happened before with other versions. And they aren't wrong about it containing a bitcoin miner, it does have one, just for testnet and regtest, not mainnet. |
|
|
|
I'm using Windows 10. Just downloaded .95 and the latest bitcoin core release after deleting my .93.3 file.
Get 0.95.1 (literally just released) since 0.95 is a bit broken with windows. Use Bitcoin Core 0.13.1 |
|
|
|
|
Firstly, what operating system are you using? What version of Armory are you using? What version of Bitcoin Core?
|
|
|
|
There are only two versions of address, '1' and '3' addresses. '1' is for P2PK and P2PKH outputs, and '3' for P2SH outputs. These three output types are the only standard output types for now.
You can represent anything you want as an address. You just have to create your own algorithm for generating the representation. Really, it's only the P2PKH and the P2SH outputs that have a standard bitcoin address. Anything else (including P2PK) is non-standard and is up to the person doing the conversion to decide how they want to represent it. It is common to represent a P2PK output as a version 1 address, but if you gave someone that version 1 address there are no wallets that would build such an output, and when the output was created it was NOT done with that address. Thank you. With regards to P2SH, is it only possible to get an address from the pattern: OP_HASH160 <hash160> OP_EQUAL Or can you also get an address when the P2SH is: P2SH addresses only are for output scripts of the form OP_HASH160 <hash> OP_EQUAl because that specific script is a P2SH script. |
|
|
|
using this code: signrawtransaction "010000000164518c0612559b8b47af331be4b33741ebed40298ce1df557e99e8955c0371690100000000ffffffff01809698000000000017a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a8700000000" "[{\"txid\":\"6971035c95e8997e55dfe18c2940edeb4137b3e41b33af478b9b5512068c5164\",\"vout\":1,\"scriptPubKey\":\"a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a87\",\"redeemScript\":\"\"}]" '["xxx"]' "ALL"it shows: error: {"code":-8,"message":"redeemScript must be hexadecimal string (not '')"}What should I use as value for redeemScript? redeemScript should be blank. Also, you need the amount field, I forgot about that. Something's wrong with your command. I need to look a bit into it some more. Edit: I found the problem. The scriptPubKey is the scriptPubKey of the output that you are spending from, not the one you are spending to. It should be 76a90ddfd0dee20dbe590f70298817810acc0c3c955888ac |
|
|
|
|
There are only two versions of address, '1' and '3' addresses. '1' is for P2PK and P2PKH outputs, and '3' for P2SH outputs. These three output types are the only standard output types for now.
|
|
|
|
Oops. Forgot a bracket. This should work. signrawtransaction "010000000164518c0612559b8b47af331be4b33741ebed40298ce1df557e99e8955c0371690100000000ffffffff01809698000000000017a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a8700000000" "[{\"txid\":\"6971035c95e8997e55dfe18c2940edeb4137b3e41b33af478b9b5512068c5164\",\"vout\":1,\"scriptPubKey\":\"a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a87\"}]" '["<privkey>"]' "ALL"
|
|
|
|
I updated to: signrawtransaction "010000000164518c0612559b8b47af331be4b33741ebed40298ce1df557e99e8955c0371690100000000ffffffff01809698000000000017a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a8700000000" "[{\"txid\":\"6971035c95e8997e55dfe18c2940edeb4137b3e41b33af478b9b5512068c5164\",\"vout\":1,\"scriptPubKey\":\"a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a87\", ,\"redeemScript\":\""]" "ALL"What is missing now and where to insert? signrawtransaction "010000000164518c0612559b8b47af331be4b33741ebed40298ce1df557e99e8955c0371690100000000ffffffff01809698000000000017a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a8700000000" "[{\"txid\":\"6971035c95e8997e55dfe18c2940edeb4137b3e41b33af478b9b5512068c5164\",\"vout\":1,\"scriptPubKey\":\"a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a87\", ,\"redeemScript\":\""]" '["<privkey>"]' "ALL"where <privkey> is the private key. Also, protip. Use a single quote to wrap all the JSON stuff and you won't need to escape the double quotes since they are all read as literals. still the same problem:  You have an unclosed quote somewhere. Edit: This is your fixed command: signrawtransaction "010000000164518c0612559b8b47af331be4b33741ebed40298ce1df557e99e8955c0371690100000000ffffffff01809698000000000017a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a8700000000" "[{\"txid\":\"6971035c95e8997e55dfe18c2940edeb4137b3e41b33af478b9b5512068c5164\",\"vout\":1,\"scriptPubKey\":\"a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a87\"]" '["<privkey>"]' "ALL" |
|
|
|
I updated to: signrawtransaction "010000000164518c0612559b8b47af331be4b33741ebed40298ce1df557e99e8955c0371690100000000ffffffff01809698000000000017a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a8700000000" "[{\"txid\":\"6971035c95e8997e55dfe18c2940edeb4137b3e41b33af478b9b5512068c5164\",\"vout\":1,\"scriptPubKey\":\"a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a87\", ,\"redeemScript\":\""]" "ALL"What is missing now and where to insert? signrawtransaction "010000000164518c0612559b8b47af331be4b33741ebed40298ce1df557e99e8955c0371690100000000ffffffff01809698000000000017a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a8700000000" "[{\"txid\":\"6971035c95e8997e55dfe18c2940edeb4137b3e41b33af478b9b5512068c5164\",\"vout\":1,\"scriptPubKey\":\"a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a87\", ,\"redeemScript\":\""]" '["<privkey>"]' "ALL"where <privkey> is the private key. Also, protip. Use a single quote to wrap all the JSON stuff and you won't need to escape the double quotes since they are all read as literals. |
|
|
|
sign it: signrawtransaction "010000000164518c0612559b8b47af331be4b33741ebed40298ce1df557e99e8955c0371690100000000ffffffff01809698000000000017a9147ecbc7d9cbb793ffb9a2905876c49f19cef8f75a8700000000" "[{\"txid\":\"6971035c95e8997e55dfe18c2940edeb4137b3e41b33af478b9b5512068c5164\",\"vout\":1,\"scriptPubKey\":\"XXX\", ,\"redeemScript\":\""]" "ALL"This is incorrect. The scriptPubkey is not the private key. The scriptPubKey is the hex of the output script that you are spending from. You are also missing the parameter for the private key array that goes right before the sighash parameter. Even if you don't need that parameter (i.e the key is in your wallet), you still need to specify it if you are going to have the sighash parameter as well. If the transaction you are spending from is in your wallet, you do not need anything except the hex of the unsigned transaction. The rest will be automatically filled in for you. |
|
|
|
|
Show Posts
