Bitcoin Forum
December 11, 2018, 07:12:08 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 [44] 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 ... 547 »
861  Bitcoin / Bitcoin Technical Support / Re: Question about addresses - different addresses controlled by single private key on: December 04, 2017, 04:15:15 AM
I can send coins to all of those addresses, and to 3rd party observer that will look like balances on different unrelated addresses.
If I'm correct, are there any flaws or security risks in this?
Not necessarily.

P2PKH (legacy) and P2WPKH (bech32) addresses contain the same data, the hash160 of your public key. So anyone scanning the blockchain will immediately know that if a P2PKH output and a P2WPKH output have the same hash160, then the owner is the same person.

Regarding security risks, there are none.

And if I'm importing private key to some kind of wallet software, how wallet determines which address to scan on blockchain and which balance to consider as wallet's balance?
It doesn't know. Currently, if you import a WIF format private key (as is the current standard), most wallets will interpret it as the private key for a P2PKH address. Some wallets may have settings that let you tell it to make a P2WPKH or P2SH-P2WPKH address, but there is no standard for that. It is currently up to the implementations.

However the creator of the bech32 standard is currently working on a similar encoding for private keys. This encoding would specify the type of witness output that a private key is for so wallets can use that to determine what address to create and scan for.
862  Bitcoin / Armory / Re: btc change address help on: December 04, 2017, 04:11:21 AM
The change address is part of the wallet itself. So you already have the private keys for all addresses (the ones you give out and the change addresses) and Armory will manage them for you. You do not need to worry about them yourself.
863  Bitcoin / Bitcoin Technical Support / Re: I need help !!! boost::filesystem::space: Operation not permitted on: December 04, 2017, 04:10:28 AM
Thanks for the reply. Ive been trying for days to fix this. I still have no idea what to do. I am totally surprised how little there is in terms of dev support.
If you want help from the developers, this forum is not the right place. The place for that would be either the github issues page or the Bitcoin stackexchange (more Bitcoin Core developers are active there than here).

I am reformatting my storage drive and removed bitcoin core entirely. I am going to try to reinstall once more
Reinstalling will do nothing to help. The issue is not with your installation but more likely with the data in the datadir itself. That data is not removed or touched by any installation process, so reinstalling will not do anything to that. I suggest that you first backup your wallet then wipe everything in the datadir except the wallet file and let Bitcoin Core redownload the full blockchain.

The total lack of help is kind of stunning...
Your problem is extremely specific about an issue that few or no people have seen before. The only people who might be able to help you are the developers (of which I am one of) and even then some may not know because this issue pertains to a part of the codebase that few people actually have worked on.
864  Bitcoin / Armory / Re: Armory, BCH, BTG and "old" BTC on: December 03, 2017, 02:10:44 AM
I am sorry, but this is a totally useless answer, as far as I am concerned.

First, is the answer to my question yes or no ?
I guess you didn't read the thread that was linked, because it should be clear from my answer that the answer to that question is Yes.

Then, can someone name a wallet that support BCH and BTG ?
AFAIK, there is no trustworthy wallet that supports both BCH and BTG simultaneously.

Finally, can someone name the different steps to be followed ?
The steps are right here:
For BCH, please read http://fonstavka.com/index.php?topic=2070058.0

Armory currently does not support BTG, so you will need to export your private keys into a wallet that does.
865  Bitcoin / Bitcoin Technical Support / Re: Hardware wallets, missing information in every explanation. Help me understand! on: December 02, 2017, 06:40:44 PM

When are they generated, when I decide one to be generated? Or before I get the device?
How can I confirm that? can I review the source code on ledger, bitbox (not trezor) etc?

To be honest, if people seriously buy a piece of hardware with a preloaded pk and uses that..... oh my. For me that would be like security 101, NOT TO.
Even if I decide to trust the manufacture/company... which I dont. How could i know the ratailer didn't duplicate that key, how could I know that the post mail main who delivered the device didn't unpack my package and duplicated the key? How could I know that some intern in the production factory didn't duplicate the keys etc. 
The keys are generated when you initialize the device. The devices come uninitialized. You can also reinitialize an already initialized device. This will wipe the existing private keys from the device and have it generate new ones.

2. Is it possible to "swipe" the hardware wallet and load your own private keys? And if so, is this easily done?
It depends. If your private keys are part of a BIP 32 HD wallet and you have a BIP 39 mnemonic for that wallet, then yes. You can load the BIP 39 mnemonic onto the device and it will generate the proper keys. If you just have a bunch of private keys that were randomly generated (or you don't have the BIP 39 mnemonic), then no, you cannot.

3. If I can put the hardware wallet in my laptop and send crypto currency stored on it to other address, what would keep a malicious piece of software on my computer from changing the address as I confirm the transaction?
You have to confirm on your device before it signs the transaction. If the outputs are changed after signing, the transaction will be invalid. If they are changed before signing, then you will see the changed address on your device and can tell it to not sign the transaction.

4. Is it possible to; from a totally offline computer holding the private keys. Make an transaction, move the transaction to a usb key, plug that key in a online machine, publish the transaction to the blockchain, so that the private keys never "touches" a machine with internet access.
Yes.

I feel that the info text and video explanations on trezor and legder, bitbox is just showing some little usb thing and showing that "when you plug it out your money is safe" but they never explain the technical background that makes that possible. There is no explanation on why your private keys was not duplicated the moment you plugged it in to your computer, or before you even got the device. And there is no noob safe guide to load your own pks to the hardware wallet.
It is impossible to duplicate the private keys when the device is plugged in as they keys cannot leave the hardware (well they could if you have malicious firmware installed). The firmware for all of the devices are open source and publicly viewable and auditable. If you don't trust the firmware that came with the device, you can install your own self-compiled version. The only firmware that is not open source is the firmware for Ledger's Secure Enclave. The Secure Enclave is where the private keys are stored. However things to and from the Secure Enclave must pass through the rest of the Ledger's open source firmware sop you would be able to see whether the Secure Enclave is leaking your private keys.
866  Bitcoin / Armory / Re: Armory, BCH, BTG and "old" BTC on: December 02, 2017, 06:32:09 PM
For BCH, please read http://fonstavka.com/index.php?topic=2070058.0

Armory currently does not support BTG, so you will need to export your private keys into a wallet that does.
867  Bitcoin / Bitcoin Technical Support / Re: Transactions to Segwit-Wallet gets rejected on: December 02, 2017, 06:29:49 PM
Please post screenshots.

What is the exact error that you are getting?
868  Bitcoin / Bitcoin Technical Support / Re: How to pass raw transaction from cold storage upon hot node? on: December 02, 2017, 06:27:44 PM
Looks like you must use these 2 commands and this second command will automatically choose the correct fee for you?
Yes.

When you open the green icon, I will get the same coins I have on my real wallet.dat but these coins don't have value?
No. Testnet is an entirely separate network. Think of it as an altcoin that has no value. You have to get testnet coins, and there are several testnet faucets. Just google "Testnet faucet" and you will find one that will give you coins to test with.
869  Bitcoin / Development & Technical Discussion / Re: Question about fees and transaction size on: December 02, 2017, 06:25:34 PM
It still is. Bitcoin is good for paying for things that are at least $10. Paying very low amounts (only a few dollars) is not all that good to do on Bitcoin. Nor are credit cards at those low values. Many merchants (particularly Mom & Pop shops or local restaurants) will not accept credit cards if the purchase is less than $10.
870  Bitcoin / Development & Technical Discussion / Re: How do blockchain nodes find each other? on: December 02, 2017, 06:20:35 PM
Some of those DNS seeds provide a static list of IP addresses of stable bitcoin listening nodes.
None of the DNS seeders provide a static list of IP addresses. They all provide a random subset of IPs that are gathered by a crawler. It is against Bitcoin Core's DNS Seeder policy to have a seeder that returns static addresses.
871  Bitcoin / Development & Technical Discussion / Re: New Bitcoin Block Format on: December 02, 2017, 06:12:26 PM
Download the block chain with Bitcoin Core and use a hex editor to look in the files. Or is that too low a level?
Or you could use the getblock command to get the block as a hex string or decoded in JSON.
872  Bitcoin / Development & Technical Discussion / Re: Segwit question on: December 02, 2017, 06:01:25 PM
There are no "extended blocks". Blocks are the same as before; they only contain the block header and the transaction. What changed was the transactions. The transactions have two different formats: legacy, and segwit. When a segwit capable nodes receives a block, it will receive the block with transactions in the segwit format. When a non-segwit node receives a block, it will receive the transactions in the legacy format.

When you run a segwit capable node, using the getrawtransaction or gettransaction commands will give you all of the details of the transaction, including the witnesses.
873  Bitcoin / Development & Technical Discussion / Re: Corrupt wallet.dat, salvage not working, using pywallet.py - Please help :) on: December 01, 2017, 09:54:54 PM
Make sure that the path K:\Bitcoin exists and that your user is allowed to read and write to it. The error is very clear, you did not have the permission to access it.
874  Bitcoin / Bitcoin Technical Support / Re: How to dump a bunch of addresses in empty wallet? on: December 01, 2017, 09:46:17 PM
But the question to move the coins from cold wallet to hot wallet still remains (i mean the transaction), it is very complicated to deal with the rawtransaction specially due fee not calculated automatically as celard posted (I watched the video). Do you have any work arounds achow101? and also hope for gui support for this too in the future, not everyone here is a command line wizard.
Instead of creating the entire transaction by hand, use the fundrawtransaction command. What you do is first use createrawtransaction to create a transaction with 0 inputs and the outputs that you want to have. Then you pass that into fundrawtransaction with the other parameters it takes. It will then choose the inputs to use, calculate the fee, and create a change output if necessary. Then you can take the transaction from that and sign it on your offline machine.
875  Bitcoin / Bitcoin Technical Support / Re: wallet.dat backup on: December 01, 2017, 09:42:32 PM
Thank you. If I generated a witnessaddress and do not know the public key used to generate it, how do I spend funds that are on witnessaddress if I move wallet.dat to another core?
The private and public keys are stored in your wallet. The software will allow you to spend from the witness address.

Also, will my wallet.dat hold the private keys of all my regular addresses? Even if I used the wallet.dat to generate let's say 5, 10 or 25 thousand regular addresses?
Yes. It always does. Keys are never removed from the wallet.dat file unless it is corrupted.

And I suppose that if I have the public and private key of a regular address, I can always regenerate the segwit address and spend all funds that are on that specific segwit address, right? Will the "bitcoin-cli addwitnessaddress 1myregularaddress..." command always generate the same segwit address?
Yes.
876  Bitcoin / Development & Technical Discussion / Re: Why do people hate segwit so much? on: December 01, 2017, 09:35:55 PM
I am also have the question about OP questions.  So i search some possible factors why segwit is not that popular to most of us. Will highlight the important matter.
The problem is that those arguments are incorrect. While they are what people believe, they are also false.

1. SegWit doesnít solve the most urgent capacity issue - SegWit, which is a soft fork solution for malleability, cannot solve the capacity problem.
It does not solve the capacity problem (there really cannot be a solution to that problem though), but it certainly helps. The redefinition to block weight and the lower weight given to segwit spends helps to increase the number of transactions in a block.

Furthermore, by fixing transaction malleability, Segwit enables 2nd layer solutions like the Lightning Network to work much better and more securely. These solutions allow for even more transaction capacity.

2. SegWit will deepen Coreís impact on the community - As an implementation reference for Bitcoin, Bitcoin Core was of significant influence in the community. However, their influence has long been overrated by their actions. By abusing their previous influence, theyíve obstructed Bitcoin block size increase from happening, against the will of the community.
The problem with that is that the Bitcoin Core developers did allow a block size increase to happen. Segwit is a block size increase, and it happened. Furthermore, if Bitcoin were ruled by Bitcoin Core, then Segwit would have activated immediately after it's release, not 10 months later.

3. SegWit makes it harder for future block scaling - On technical terms, SegWit uses a transaction format that can be spent by those who donít upgrade their nodes, with segregation of transaction data and signature data. This means SegWit is irrevocable once itís activated, or all unspent transactions in SegWit formats will face the risk of being stolen.
That is the nature of ALL soft forks, not just segwit. All soft forks are irrevocable once activated, or all unspent transactions that used anything deployed in a soft fork can be stolen. But also any fork that "reverts" segwit (or a different soft fork like P2SH), will just be a hard fork.
877  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core wallet shows old spent bitcoins from 2012 in balance after sync on: December 01, 2017, 09:30:14 PM
Start Bitcoin Core with the -rescan option. It will rescan the blockchain for all of your transactions.
878  Economy / Exchanges / Re: +44-8004049463 Bitcoin Support Number on: December 01, 2017, 09:28:32 PM
If you cannot find any official documentation or statement from Bittrex that lists this phone number, then it is probably a scam.
879  Bitcoin / Development & Technical Discussion / Re: I've been challenged with a prize of 10BTC to speculate with on: December 01, 2017, 12:12:28 AM
So he proposed to me that he could give me 10 BTCTC, but if I lost it or if "the bubble bursted", I would pay it to him at least two times worth. If I manage to secure it and the value increases, I get half of the profits.
Over what time frame? You had better clarify that, because it could be "indefinitely" or whatever suits your friend.

Anyway, he doesn't really expect to break the blockchain's encryption, I think.
The blockchain does not use any encryption. What you would need to break is ECDSA, SHA256, and RIPEMD160. Those have so far been unbreakable.

What is far more likely is error on your part that results in the coins being stolen. That would be human error, not a failure of the system.


I recommend that you use a hardware wallet or a paper wallet.

A hardware wallet like Trezor or the Ledger Nano S is very secure and the only way to get the private keys is to get physical access to the device, know the PIN, and know the passphrase (passphrase is optional, but you should do it anyways as it is an extra security measure). Assuming you know the PIN and the passphrase, you just need to keep the mnemonic safe. You can do that by storing it in a secure place like a safe deposit box. Note that even if the mnemonic is stolen, if you have a passphrase, your coins will still be fairly safe.

To be absolutely sure that you do not forget the PIN or the passphrase, I suggest that you routinely connect the device to a computer and open up the wallet. This does not leak any private keys onto your computer or compromise your coins security in any way. It just makes sure that you still remember what the PIN and passphrase are.

Alternatively you could use a paper wallet encrypted with BIP 68 encryption. If you do that, you must store the paper wallet in a secure place (e.g. a safe deposit box) but you cannot forget the passphrase. If you forget the passphrase, then the coins will be lost. You should use the encryption as it will protect against anyone stealing the paper wallet. You should also make multiple copies and store them securely in separate places.

I have a notebook that I don't use anymore, with a 320GB hard-drive, so the blockchain fits. I will use a bootable tool to cleanse it's hard drive once and for all, and I won't connect the notebook to the internet until I've got Tails Linux running. Anything I do on this notebook will be for opening the fullnode (or eletrum client) and storing my bitcoins.

What do I need to access the bitcoins contained on my paper wallet? Is Eletrum fully trustable? Is there any way I would lose my bitcoins with it, if used with Tails Linux and taking all the necessary precautions?
Electrum is trusted. However I would not recommend that you use a paper wallet of use an old device to store the coins on. I recommend that you use a hardware wallet. That way you can keep it on your person at all times and verify that it is functioning with basically any computer at any time.
880  Bitcoin / Development & Technical Discussion / Re: How do blockchain nodes find each other? on: November 30, 2017, 08:45:26 PM
Thanks for explanation achow101. Does it mean that DNS seeders (primary and built in) are set of "hardcoded" servers which are basically critical point of bitcoin core and if those servers won't be available whole blockchain will stop functioning (as eventually nodes won't be able to discover each other)?
No. Nodes can still discover each other without the DNS seeders. The DNS seeders can be swapped out with some other initial discovery process too.

Furthermore, as I said, nodes maintain their own internal database that persists across restarts of nodes that it can connect to. So it will use those nodes instead of the DNS seeders on all starts after the first start. For new nodes, new nodes will fall back to the hundreds of hard coded seed nodes.

Lastly, nodes can be added manually too.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 [44] 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 ... 547 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!