Bitcoin Forum
May 28, 2024, 01:58:17 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 [149] 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 ... 590 »
2961  Other / Beginners & Help / Re: Why is compiling Bitcoin still such a PITA? on: June 11, 2017, 11:33:19 PM
Yeah I just learned that Berkeley DB is used for the wallet.dat
This works for a fresh installation but not if you want to use your old wallet.dat

Which makes this solution to the DB issue rather awkward.

Unless however there was a converter for the wallet.dat file...
With a pre-existing wallet, you do need to use BDB 4.8.

You can try using the depends system which you can read about here: https://github.com/bitcoin/bitcoin/tree/master/depends. With that, you should end up doing something like this: (starting from the repository root):
Code:
cd depends
make
cd ..
./autogen.sh
./configure --prefix=`pwd`/depends/x86_64-linux-gnu # Note: Check in the depends folder and actually see what folder is created. You have to use the path to that
make

The depends system is what is used for Bitcoin Core's official builds that are released. You will be using the correct versions for all of the dependencies.
2962  Bitcoin / Development & Technical Discussion / Re: How to signal support for BIP 148 ? on: June 11, 2017, 11:20:46 PM
Do I enforce BIP148 If I signal BIP148 with Bitcoin Core 0.14.1?
No. Bitcoin Core does not support BIP 148. You have to use a modified version of Core which has BIP 148 support built into it. Please actually read the thread you are posting in. I explained this earlier.
2963  Bitcoin / Development & Technical Discussion / Re: August 1st consideration and important unaswered questions on: June 11, 2017, 05:08:11 PM
2.  Even if UASF is supported by the community, if LN isn't ready I'm afraid from a practical point of view users will turn to a BU fork because of lower transaction costs even if they themselves think BU is a shit long term scaling solution. If you needed to send a $10 payment and had some money on an exchange, wouldn't you buy the BU coins with your BTC and initiate a $0 fee transfer instead of paying $5 in fees?
Segwit in itself provides a capacity increase that will, in theory, decrease transaction fees like the BU fork would, in theory. It does not exist to just enable LN but is itself a way to increase the number of transactions that can fit in a block.

3.  If LN isn't instantly deployable how long will it take to be deployed?  Will sites like exchanges which create an enormous amount of on chain transfers be able to instantly reduce their transfer load through LN and if so by how much?
LN is still being worked on but it is available on testnet, so it certainly is close to being deployed. I don't think it is instantly deployable though. I don't think it would be particularly useful for exchanges as LN is (so far) only useful for small, recurring payments. Most exchanges don't perform on chain transactions except when their customers are depositing or withdrawing money. The exchanging itself is all internal database records.

4.  A continuation of question 3, in terms of development time and effort what cost will merchants pay to switch to using LN?  I'm not saying what it will take them to recognize non-segwit transactions on the segwit chain, I know that is trivial.  I am asking how long will it take and how tedious will it be for them and their users to start benefiting from lower transaction costs.
Given that there will be software available that can be used by other customers and merchants, it shouldn't really be that much effort to switch to using LN. The most work will be from setting up payment channels, but in most scenarios, the merchant would only be receiving money, not sending, so they risk almost no money. The only issue there is that they would not be able to access the money until after the channel is closed.

5.  If we agree that the ASICBOOST miners have acted Machiavellian up to this point, why exactly would we ever expect them to honor any agreement where they would sacrifice their profitability?  If they lose the ability to exploit ASICBOOST, that means they could go from being high profit miners to being losers in the mining space no matter what price bitcoin reached. If they no longer have a competitive advantage against other miners, they will lose money regardless of the BTC price.  With this in mind how is a malicious attack on BIP148 different from their secretive ASICBOOST exploitation and the faux politics of certain miners?  Why would they possibly not attack the BIP148 chain if what they have done so far is actually worse?  A long chain reorg that causes user losses would be worse but an above board attack where BIP148 users are not given a false sense of security would not be worse, it would just be a continuation of disruption.
Not using ASICBOOST is still profitable. Just because ASICBOOST miners stop using ASICBOOST does not mean that they will suddenly be mining at a loss. It just means that their profits will decrease.

8.  LTC already has working Segwit but doesn't afaik have LN set up on it.  Why is this?  When will LN be deployable on LTC?
Because all LN development has been for Bitcoin. While Bitcoin and litecoin are similar, there is still a non-trivial amount of work to do to make LN work on Litecoin. Fron what I understand, those working on LN will finish it for Bitcoin first (except for segwit) and then port it over to Litecoin once the Bitcoin version is completed.

9.  How could a post-UASF chain ever truly know within a reasonable time period that there will not be a reorganization?  If we assume that there isn't any decrease in the ASICBOOST hashing power and that a large amount of malicious miners have not been dormant in anticipation and or are not just coming online can we be confident in the BIP148 chain?  Are those reasonable assumptions to make?
A BIP148 chain cannot be reorged with a non-BIP 148 chain. This is because it is a restriction of the current consensus rules so BIP 148 nodes considers the non-BIP 148 chain to be invalid. However the non-BIP 148 chain can be reorged with the BIP 148 chain since non-BIP 148 nodes still consider the BIP 148 chain to be valid.

10.  To end off on a note of more personal politics, I think both Core and BU have a terrible actor or two.  Ver is obviously not honest and Theymos who I am aware doesn't work for Blockstream could have done a much better job at constructively moderating /r/bitcoin.
Theymos is not involved with Core at all. He has never contributed to Bitcoin Core and does not participate in its development whatsoever.
2964  Other / Beginners & Help / Re: Why is compiling Bitcoin still such a PITA? on: June 11, 2017, 04:38:47 PM
But what issues could that cause? Is there a list of caveats for incompatible db?

"If you do not care about wallet compatibility, pass --with-incompatible-bdb to configure."

What does that mean?
That means that you can't use the wallet.dat file with any version of Bitcoin Core compiled with a version of BDB that is different from yours. You wouldn't be able to switch to using the officially released binaries without creating a new wallet. Nor can you upgrade your version of BDB without creating a new wallet. This is all because BDB is incompatible with other versions of BDB, even between minor versions.
2965  Bitcoin / Development & Technical Discussion / MOVED: [GUIDE] Raspberry Pi 3 with WD PiDrive 1TB - UASF BIP-148 Bitcoin Full Node on: June 11, 2017, 04:36:07 PM
This topic has been moved to Trashcan.

Duplicate
2966  Bitcoin / Development & Technical Discussion / Re: Does any of the following enables bitcoin earning by running full node? on: June 11, 2017, 05:26:42 AM
I have heard running a node can earn you bitcoins ? Is this true ? If so how ?
Seems different to mining. Which earns more ?
No, running a node cannot earn you any Bitcoin. Mining is completely different from running a node and from any of the above proposals. Given that none of the above proposals have been deployed, mining will earn you more, but not very much.
2967  Other / Beginners & Help / Re: Why is compiling Bitcoin still such a PITA? on: June 11, 2017, 01:44:53 AM
Yes, I used that guide. It still doesn't work.
Care to explain where the problem is?

Code:
./configure CPPFLAGS="-I/usr/local/BerkeleyDB.4.8/include -O2" LDFLAGS="-L/usr/local/BerkeleyDB.4.8/lib"

checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing, Bitcoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)
Stop attempting to use BDB 4.8 with whatever options you are using. Just install whatever BDB version you want and then run
Code:
./configure --with-incompatible-bdb
2968  Other / Beginners & Help / Re: Why is compiling Bitcoin still such a PITA? on: June 10, 2017, 09:57:51 PM
It really isn't that hard to do. There are explicit instructions right in the repo: https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md

The reason that BDB 4.8 is still used is because changing the version to anything else will completely break backwards compatibility. Anyways, you don't have to use BDB 4.8, just configure with the --incompatible-bdb option.
2969  Other / Beginners & Help / Re: How can a transaction like this happen before confirming ? on: June 10, 2017, 09:22:46 PM
Well thank you. I always used to think that it was built in. Didn't know it was just the wallets preventing from creating a transaction when there was an unconfirmed one.

So if it turns out to be a double spend, then the whole transaction would disappear i suppose ?
Yes. If the first transaction is invalidated by a double spend which confirms, then any transaction which spent from it is also invalidated. This can also happen if the first unconfirmed transaction pays too low of a fee and is "forgotten" by the network. The network will "forget" the second transaction too since they don't "remember" the first one.
2970  Bitcoin / Bitcoin Technical Support / Re: Bitcoind Keeps crashing on: June 10, 2017, 08:57:18 PM
Ah okay thanks. How do I update if you please without having to lose data and the sync ? Ive tried several commands to no avail .
Updating the software will not touch any of the blockchain data as that is located elsewhere. There is no need to uninstall it, just install the new version on top.

If you installed bitcoind from the PPA, you should be able to upgrade in the same way you installed or by running
Code:
sudo apt-get upgrade
That command will also update everything else on the system except the OS itself.

If you did not install from the PPA, then just download the latest version from bitcoin.org and install it as you did originally.
2971  Other / Beginners & Help / Re: How can a transaction like this happen before confirming ? on: June 10, 2017, 08:51:07 PM
No, a transaction does not need to be confirmed before another one can be created that spends from it. There is no consensus or network rule that prevents you from spending from an unconfirmed output. However, most wallet software will prevent you from doing so as it can potentially lead to a loss of funds. But just because wallet software limits it does not mean that it cannot be done.
2972  Bitcoin / Bitcoin Technical Support / Re: Bitcoind Keeps crashing on: June 10, 2017, 08:49:56 PM
2 cores is not a lot of computing power, but that shouldn't really matter.

You are using an old version of bitcoind. Try updating to the latest version.
2973  Bitcoin / Bitcoin Technical Support / Re: Bitcoind Keeps crashing on: June 10, 2017, 07:32:02 PM
Is that all? There should be more to it.

Also, what version of bitcoind are you using? What are the specs of the machine you are running it on?
2974  Bitcoin / Bitcoin Technical Support / Re: Bitcoind Keeps crashing on: June 10, 2017, 07:05:03 PM
How are you trying to get the debug.log file? It a file on the system, you shouldn't be able to access it through any web server as you are doing now.
2975  Bitcoin / Project Development / Re: How to make personal RPC for bitcoin mining on: June 10, 2017, 06:13:06 PM
Do not try to make the transaction fees extremely low. That will only result in your transactions being unconfirmed for a long time. Furthermore, you should not be trying to set a fixed amount. Fixed transaction fees are no longer a viable option with the current state of the network. You should always be using a fee rate (and not a fixed fee rate either) and dynamic transaction feess.
2976  Bitcoin / Project Development / Re: open a business wallet anonymous on: June 10, 2017, 06:10:04 PM
If you are asking about how you should make an online wallet, then you don't have the expertise required to make such a wallet and shouldn't be doing it. Are you actually okay with holding the coins of others? If you fail to secure them properly, you will have a lot of angry customers who will try to take legal action against you.
2977  Bitcoin / Bitcoin Technical Support / Re: Bitcoind Keeps crashing on: June 10, 2017, 06:07:56 PM
Bitcoind shouldn't be crashing. Instead of making bitcoind restart on every crash, it would be better to figure out why it is crashing in the first place.

Can you please post your debug.log file?

One way to keep bitcoind up is to make a cronjob that just starts bitcoind. If it is running, the cronjob will do nothing since you can't have two bitcoinds running from the same datadir. If it is not running, the cronjob will start it.
2978  Bitcoin / Bitcoin Technical Support / Re: Brainwallet - BIP39 - seed words - backup phrase - same 12 words for all wallets on: June 10, 2017, 05:59:03 PM
What are you trying to do?

If you are thinking you can just make your own seed by thinking of 12 "random" words, it won't work. BIP 39 is much more than just a bunch of random words, it is an encoding for a random number. It includes a checksum, so you can't just think if 12 random words and call that a valid BIP 39 mnemonic. It is far better to use a wallet that supports BIP 39 to generate the mnemonic for you since they actually generate the random number first and then encode it as a mnemonic.
2979  Bitcoin / Development & Technical Discussion / Re: Removing the nonce field for ASIC resistance and preventing selfish mining. on: June 10, 2017, 08:08:59 AM
That's a good point about the coinbase, I almost forgot about that. Does it actually have a purpose or can we get rid of that in this hypothetical?
You could get rid of it in this hypothetical. It doesn't serve a consensus purpose, but it does help to track who mines a block as miners usually will put some identifying text in the coinbase.

Conjecturing on we can, doesn't this make the bitcoin algorithm ASIC resistant?

Although you say that ASIC resistance is based on the hashing algorithm, I'd argue that the calculation of the merkle root is in itself a giant hashing function. If we use the merkle root as the only source of randomness, then I get the following calculations:

If we take the current hash rate of about 5,000,000 TH/s and multiply that by 10 minutes we get, 5,000,000,000,000,000*10*60 Hashes.
No, that is not ASIC resistance. ASIC resistance means that the PoW algorithm (in this case sha256d) is hard to implement on an ASIC. Merkle root calculations are also SHA256d; the data for calculating a merkle root can just be passed through the same SHA256d hashing chips on an ASIC. The processing that is required to do this is also very minimal and could be done on an FPGA before being sent to the chips to be hashed. I don't think the actual hashing chips themselves are even the ones that change the nonce. IIRC the onboard FPGA processes the header and then sends it to the hashing chips to actually be hashed. That FPGA would just need to process a little bit more to make the merkle root.

Which would mean that the number of different merkle roots we need can be calculated via log2(5,000,000,000,000,000*10*60) = 61.3796682. Meaning that each block would require at least 61 transactions for the miner to find a block.
We cannot rely on there always being some minimal number of transactions to be included into a block except for the coinbase transaction. While requiring a minimal number of transactions would solve several issues, I don't think that should be done as we need to consider the scenario where few transactions are being made. The network would grind to a halt if for some reason transactions are not being made (could be from Bitcoin falling out of use and becoming an even more niche thing, some layer 2 solution makes onchain transactions few and far between, some vulnerability is discovered that people stop making txs but the blockchain must go on, etc.).
2980  Bitcoin / Development & Technical Discussion / Re: Removing the nonce field for ASIC resistance and preventing selfish mining. on: June 10, 2017, 06:33:11 AM
Difficulty and nonce go hand in hand, difficulty tells the nonce how many 0's to have.
No, that's the nBits field. The nonce is the field that is changed in order to find a valid hash as it is more efficient than changing the other fields.



First of all, this would require a hard fork.

Secondly, removing the nonce field won't really help. Miners can just keep changing something in the coinbase transaction which can effectively act as a nonce. In fact, since the coinbase part of a coinbase transaction can include whatever data a miner wants, they could just move the nonce into the coinbase transaction and basically continue as they do now. It would add an additional 13 hashes for each block header hashed so it effectively reduces the network hashrate to 1/13 of the current hashrate. However, that won't suddenly make CPU or GPU mining viable again and it most certainly does not make Bitcoin ASIC resistant. ASIC resistance is in the hashing algorithm itself, not the data that is being hashed.

Since miners can and will essentially move the nonce into the coinbase itself, selfish mining is not effected at all. All of the other transactions in the block would remain the same and only the coinbase transaction would change. That is enough to change the merkle root.
Pages: « 1 ... 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 [149] 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 ... 590 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!