

- #BITCOIN CORE STUCK ON ACTIVATING BEST CHAIN SOFTWARE#
- #BITCOIN CORE STUCK ON ACTIVATING BEST CHAIN CODE#
- #BITCOIN CORE STUCK ON ACTIVATING BEST CHAIN LICENSE#
- Make it scale: // - eliminate all the algorithms with quadratic complexity (or worse) // - don't require everything to be held in RAM at once // - consider allowing eviction of no longer re-orgable transactions or keys that were used up /** - saving to a backing store // - Key management // - just generally make Wallet smaller and easier to work with // - Make clearing of transactions able to only rewind the wallet a certain distance instead of all blocks. - Decompose the class where possible: break logic out into classes that can be customized/replaced by the user. - Simplify how transactions are tracked and stored: in particular, have the wallet maintain positioning information // for transactions independent of the transactions themselves, so the timeline can be walked without having to // process and sort every single transaction. - Split block chain and tx output tracking into a superclass that doesn't have any key or spending related code. - Only store relevant transaction outputs, don't bother storing the rest of the data. // - Take all wallet-relevant data out of Transaction and put it into WalletTransaction. To do list: // // This whole class has evolved over a period of years and needs a ground-up rewrite. import .Base64 import 3.tuple.ImmutablePair Import static .Utils.bitcoinValueToPlainString Import static .Utils.bitcoinValueToFriendlyString Import .TransactionConfidence.ConfidenceType
#BITCOIN CORE STUCK ON ACTIVATING BEST CHAIN LICENSE#
* See the License for the specific language governing permissions and * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * distributed under the License is distributed on an "AS IS" BASIS,
#BITCOIN CORE STUCK ON ACTIVATING BEST CHAIN SOFTWARE#
* Unless required by applicable law or agreed to in writing, software

* You may obtain a copy of the License at * you may not use this file except in compliance with the License. * Licensed under the Apache License, Version 2.0 (the "License")
#BITCOIN CORE STUCK ON ACTIVATING BEST CHAIN CODE#
The above gcc version and altered gcc switches were used only in my latest build based on commit mentioned above.IntroductionHere is the source code for .Wallet.java my build is 圆4, uses Ofast and AVX instruction set tuning (including all dependencies, with one exception being O3 due to Ofast failing).ĮDIT: when I reported this issue I was using standard mingw toolchain with default build optimization but due to linker issues on other program being compiled I was forced to change gcc versions over time. Not sure what causes it and if it could have any impact on tests being correct. However to confirm loosing connections I would need to re-download block chain (I think?).Īlso to be 100% sure I would need to note that I have one small error when building with gcc 4.9.4 (20150630 - prerelease windows mingw) on /leveldb/util/env_win.cc file which tells me that _beginthread is undefined until I compile the file manually while omitting D_REENTRANT.
/fakebitcoin-5a8147766edd6500367dec63.jpg)
My latest build bases on d0a10c1, which, I'm pretty sure, was still slowing down RPC (when I was 15h behind and run my PHP script to manually connect to selected IPs, after 3rd connection it started to response very sluggish).

I will give it a try after I build myself newest commit.
