Bitcoin Forum
December 11, 2018, 06:44:33 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 ... 547 »
381  Bitcoin / Development & Technical Discussion / Re: Core's next version 0.16.xx or 0.17? on: March 16, 2018, 05:47:16 PM
Are there plans for a minor or bugfix update for Core
There will be minor updates if there are bugs in need of fixing tat can't just wait for the next major version. There are currently no plans for a minor release, but there may still be one as bugs are found and fixed.

or is the next version going to be 0.17?
The next major version will be 0.17 (or 17.0, depending on whether we change the version scheme). That does not necessarily mean that it will be the next version released.
382  Bitcoin / Development & Technical Discussion / Re: Why per-wallet db.log and database? on: March 16, 2018, 05:45:34 PM
So wallet.dat is BDB, and ./database/ is a transactional log?
database/ is used for whatever other temporary data BDB needs. This includes (but is not necessarily limited to) database transaction logs.
383  Bitcoin / Development & Technical Discussion / Re: Right way of pushing to Github? on: March 16, 2018, 05:44:14 PM
Github uses git. You use git push to push changes to github (assuming that you used git clone to download the source code). Read GitHub's documentation.
384  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core 0.16 and bech32 on: March 16, 2018, 05:41:29 PM
I think you're right but I the getaddressinfo command does not exist and I can't find a similar command in the list of commands you get by typing help. Do you know what you meant instead?
Right, getaddressinfo was merged for 0.17, not 0.16. It's validateaddress for 0.16.
385  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core 0.16 and bech32 on: March 16, 2018, 04:34:26 AM
Get an address from your wallet and go to the debug window. Then type
Code:
validateaddress <address>
Find the field for
Code:
iscompressed
and tell us what it says. I suspect it will say false.

Since you say that your wallet is old, there's a good chance that you still are using uncompressed public keys which are not allowed by segwit. This has nothing to do with a wallet being non-HD; it just means that you are using a wallet that does not support compressed public keys.

To use compressed public keys (so that you can use segwit), you can upgrade your wallet to use compressed public keys by starting Bitcoin Core with -upgradewallet. Note that this will not make your wallet HD, it will only upgrade it to support compressed public keys. Then you will need to flush and regenerate the keypool. Unfortunately I don't think there's a way to do that right now besides just generating a few hundred addresses. At some point it will start giving you p2sh wrapped addresses instead of legacy addresses as the keypool runs out of the old uncompressed public keys.

If your wallet is not encrypted, you can encrypt it and that will automatically flush and regenerate the keypool for you.

edit: validateaddress, not getaddressinfo
386  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core: Network settings tab options on: March 15, 2018, 10:18:43 PM
Main question is what's difference between 3rd and 4th options?
The 3rd option proxies all of your traffic. The 4th option only proxies TOR connections. So setting the 4th option allows you to connect to node's that are listening over TOR while connections to IPv4 and IPv6 nodes happen over your normal connection. The 3rd option will proxy ALL connections.

Can i just use 3rd option with 127.0.0.1 port 9050 (it's TOR port)?
Yes.

Also, i want to ask you about 1st and 2nd option. For what purpose they are?
The first option enables UPnP which will automatically tell your router (if it supports UPnP) to allow connections through to Bitcoin Core's P2P port. Typically routers will block such connections. Such routers will need port forwarding enabled for the P2P port. UPnP does that automatically.

The 2nd option disables the incoming connections entirely.

Do i need to disable incoming connections for maximum security?
No. The security risk is the same.
387  Bitcoin / Bitcoin Technical Support / Re: Broadcasting non standard transactions on: March 15, 2018, 04:35:37 AM
You can use a tool like http://github.com/laanwj/bitcoin-submittx to broadcast it. However your transaction probably won't be relayed and probably won't propagate well since it is non-standard.
388  Bitcoin / Development & Technical Discussion / Re: connect two bitcoin core nodes on different machine, using regtest on: March 15, 2018, 04:33:54 AM
The bitcoind is still trying to connect to
`2018-03-15 01:31:32 Binding RPC on address ::1 port 18332 failed.
2018-03-15 01:31:32 Binding RPC on address 127.0.0.1 port 18332 failed.`

Anyone knows why ?
You have two programs that are trying to use the same port. You can't do that. One of your bitcoind instances will need to use a different rpcport (-rpcport) and normal p2p port (-port)
389  Bitcoin / Development & Technical Discussion / Re: Future ("scheduled") transaction for inheritance on: March 14, 2018, 03:16:04 PM
This transaction would be in the mempool until could be included in a block.
The transaction won't be in most node's mempools (note that there is no "the mempool"). Most nodes will not accept a transaction whose locktime has not yet passed.

Can a "well paid" transaction hang around in the mempool for months/years?
No. Transactions that have been in a node's mempool are automatically evicted after a certain amount of time (default is 2 weeks). You could rebroadcast the transaction routinely, but in your case, that won't help.

How can it be checked if trown out of mempool?
Not a concern because it won't be accepted to the mempool in the first place.

Is the locktime strictly enforced?
Yes. If a block contains a transaction that has a lock time that has not yet passed, it will be invalid.

Is the locktime value unmodifiable?
Yes. Your digital signature protects the locktime, just like all other parts of the transaction. Changing the locktime would make the signature invalid thus making the entire transaction invalid.

I assume the future timelocked mempool transaction shouldn't prevent spending the funds without current locktime?
Yes, You can spend the same output in a different transaction thus invalidating the locktimed transaction.
390  Bitcoin / Development & Technical Discussion / Re: Quantum computing and Bitcoin's use of ECDSA on: March 13, 2018, 09:54:18 PM
1) Aside from the specific case of Pay-to-IP in earlier versions, is the above correct?
Yes (aside from the estimates; it's hard to predict the future).

2) What is the general plan when ECDSA is broken? Hard fork to a new signature algorithm?
Yes.
391  Bitcoin / Development & Technical Discussion / Re: Genesis hash again on: March 13, 2018, 09:50:39 PM
1. How can I get a Merkle root hash?
By constructing the coinbase transaction of the genesis block and hashing it. Because the genesis block only contains one transaction (the coinbase transaction), the merkle root hash will be the same as the hash of the coinbase transaction.

To construct the coinbase transaction, you will need more information, such as the transaction version number, any other data that is going into the coinbase script, and the output value. The pubkey will be used in the output script.

2. Why is it necessary to generate a "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks"? :-) We are create a genesis-hash without to use it Smiley
Because it is necessary in order to generate the coinbase transaction whose hash is the merkle root.
392  Bitcoin / Development & Technical Discussion / Re: How to find the block header ? on: March 13, 2018, 04:28:26 PM
I made some changes in chainparams.h of bitcoin core and I am trying to create genesis block. I have genesis block hash and merkel root but debug.log says hash too high

What I am actually trying to do is compare the target value with hash of genesis block header.
You have to actually mine the genesis block. You can do that with a while loop in chainparams.cpp that calls CheckProofofWork (with some modification). Or just use a script like http://github.com/lhartikk/GenesisH0 to do it for you.
393  Bitcoin / Development & Technical Discussion / Re: Genesis hash again on: March 13, 2018, 02:58:05 PM
Just knowing those 5 things is not enough to construct the block header. Furthermore, knowing the merkle root means that there is no need to know the phrase or the pubkey; those are part of the coinbase transaction which is part of the merkle root.

In addition to the nonce, time, and merkle root, you also need the nBits, the block version number, and the previous block hash. For the genesis block, it is version one, nbits of 0x1d00ffff, and previous block hash of 0000000000000000000000000000000000000000000000000000000000000000. Following the format for the block header, you get a block header of 0100000000000000000000000000000000000000000000000000000000000000000000003ba3edf d7a7b12b27ac72c3e67768f617fc81bc3888a51323a9fb8aa4b1e5e4a29ab5f49ffff001d1dac2b 7c. This is then hashed with SHA256d to get 6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000 which is the block hash. It is interpreted as a little endian 256 bit integer, and displayed as a big endian 256 bit integer so you get 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f. Note that the hash is always in little endian byte ordering when used in other block headers.
394  Bitcoin / Development & Technical Discussion / Re: (Alpha Elements) Sidechains - state of the art? on: March 13, 2018, 02:48:10 PM
Just wondering if this project is under rework? I tried to get involved via the link on the webpage http://www.elementsproject.org/posts/announcing-elements/, but the link to the slack channel seems dead: http://chat.elementsproject.org. (At least my Safari is showing as "could not connect").
Also the Freenode IRC: #sidechains-dev is very quiet, no info since last November in the web archives.
AFAIK not many people are doing stuff with sidechains so it's fairly quiet. Elements is still being worked on, I don't know what the current state of it is.
395  Bitcoin / Development & Technical Discussion / Re: How to find the block header ? on: March 13, 2018, 02:44:57 PM
Assuming that you are running Bitcoin Core, you can use the getblockheader command to get the block header for a given block hash. To get the raw block header so you can hash it, you would do
Code:
getblockheader <hash> false
396  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: March 13, 2018, 01:55:54 AM
I heard that it was possible to print coins without transaction fee with Bitcoin core, is that true? In the documenation it says minimum tx is 1000 satoshi
What do you mean by "print coins"? Anyways, such questions are off topic for this thread.

Can it work on ubuntu?
Yes.

And if it can is there and special settings?
Special settings for what?
397  Bitcoin / Development & Technical Discussion / Re: Does Ledger Give Different Extended Public Keys for Segwit and Legacy Addresses on: March 13, 2018, 01:54:22 AM
Yes. The xpubs are derived from your seed at different paths, so they will be different.
398  Bitcoin / Bitcoin Technical Support / Re: Corrupted wallet.dat file on: March 12, 2018, 04:47:23 AM
First of all, do not necropost (posting in topics that have not had a post in a long time), especially with your own issue, not an attempt to help the OP. I've moved your post into its own thread.

I need help with a QT ver. 4.8.5 wallet.dat that is corrupt somehow.
Bitcoin Core is not called Qt, and the Qt version is completely irrelevant. What is the version of Bitcoin Core (which is not Qt).

#1  trying to replace the wallet.bat file into the same dir but keeps failing and just hang
    at "Loading block index" then no more.
How do you know that it is hanging? Sometimes Bitcoin Core can take a long time to start up, but that does not mean that it is hanging.

#3  remove all files except all the dll's and the config file
    and restart, starts fine but all frome day 1. (sync and no Bal)
Of course there won't be a balance, the blockchain isn't synced yet.

#5  replace wallet.dat while wallet running... a program error pops up
    and locksup the wallet completely.
Don't do that, you'll end up corrupting things further. You cannot just remove and replace files while they are still in use by the software.

Please post the contents of your debug.log file.
399  Bitcoin / Development & Technical Discussion / Re: Can hardware wallets suffer from ransomware? on: March 12, 2018, 04:42:55 AM
But I thought about it... can hardware wallets get encrypted by ransomware?
No.

Hardware wallets ONLY execute things from their firmware; you cannot get a hardware wallet to execute arbitrary code (barring some major vulnerability). Furthermore, hardware wallets are not just generic storage devices, so a computer infected with malware can't read or write arbitrary data to a hardware wallet as it would with any normal storage device.

Some hardware wallets (like the Ledger Nano S) have apps that can be loaded onto the device to run things. If the app were malicious, maybe it could do something which is like ransomeware. However apps are isolated within the device itself (at least for the Ledgers) and don't have access to read and write arbitrary data to and from the devices internal memory (barring some vulnerability).

or there are some at least theoretical ways to get inside the device with some malware?
In theory, if the user is incredibly stupid, some malware could flash a new firmware to the device (which requires the user to push physical buttons on the device itself in order for a new firmware to be flashed) which then results in the stored seed being stolen. In practice, no, there isn't.
400  Bitcoin / Development & Technical Discussion / Re: When first run the wallet, connect to seed nodes, then? on: March 10, 2018, 07:06:44 AM
Then it means DNS seeders has automatically updated by connected clients, fetch its ip address, and record and add it to seeder's own file, become bigger while time goes?
Yes. The DNS seeders maintain their own databases of nodes and have their own crawlers. They crawl the network to find nodes. Of course nodes are removed from the database as nodes drop offline so it doesn't grow infinitely big.

And about how to setup DNS seeder, this is valid? http://fonstavka.com/index.php?topic=599623.0
Looks like it is.
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 ... 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!