forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The index of address balances does not work well #48
Comments
I confirm. Tons of wrong balances. Running two full nodes and both of them has same problems with incorrect balances. UPD: As I can see, there is a problem with counting newly generated coins. |
lateminer
referenced
this issue
in lateminer/bitcoin
Feb 23, 2019
LarryRuane
pushed a commit
to LarryRuane/bitcoin
that referenced
this issue
Oct 11, 2021
0d624261ef Merge bitcoin-core/crc32c-subtree#2: Merge upstream cac7ca830b Merge commit 'fa5ade41ee480003d9c5af6f43567ba22e4e17e6' into bitcoin-fork fa5ade41ee Fix compilation warnings on ARM64 with old GCC versions. (bitpay#52) db08d22129 Updated Travis-CI configuration. (bitpay#51) e31619a5b7 Fix GitHub links. (bitpay#50) 7fa4c263e8 Update Travis CI config. (bitpay#49) a3d9e6d1a4 Updated third_party/ and Travis CI config. (bitpay#48) git-subtree-dir: src/crc32c git-subtree-split: 0d624261ef83ab08c953c196540ed18f355add4c
LarryRuane
pushed a commit
to LarryRuane/bitcoin
that referenced
this issue
Nov 20, 2021
a44caf65fe Merge bitcoin-core/univalue-subtree#28: Import fixes for sanitizer reported issues 135254331e Import fixes for sanitizer reported issues d5fb86940e refactor: use c++11 range based for loop in checkObject ff9c379304 refactor: Use nullptr (c++11) instead of NULL 08a99754d5 build: use ax_cxx_compile_stdcxx.m4 to check for C++11 support 66d3713ce7 Merge bitcoin-core/univalue-subtree#29: ci: travis -> cirrus 808d487292 ci: travis -> cirrus c390ac375f Merge bitcoin-core/univalue-subtree#19: Split sources for easier buildsystem integration 4a5b0a1c65 build: Move source entries out to sources.mk 6c7d94b33c build: cleanup wonky gen usage a222637c6d Merge bitpay#23: Merge changes from jgarzik/univalue@1ae6a23 f77d0f718d Merge commit '1ae6a231a0169938eb3972c1d48dd17cba5947e1' into HEAD 1ae6a231a0 Merge pull request bitpay#57 from MarcoFalke/test_fix 92bdd11f0b univalue_write: remove unneeded sstream.h include ffb621c130 Merge pull request bitpay#56 from drodil/remove_sstream_header f33acf9fe8 Merge commit '7890db9~' into HEAD 66e0adec4d Remove unnecessary sstream header from univalue.h 88967f6586 Version 1.0.4 1dc113dbef Merge pull request bitpay#50 from luke-jr/pushKV_bool 72392fb227 [tests] test pushKV for boolean values c23132bcf4 Pushing boolean value to univalue correctly 81faab26a1 Merge pull request bitpay#48 from fwolfst/47-UPDATE_MIT_LINK_TO_HTTPS b17634ef24 Update URLs to MIT license. 88ab64f6b5 Merge pull request bitpay#46 from jasonbcox/master 35ed96da31 Merge pull request bitpay#44 from MarcoFalke/Mf1709-univalue-cherrypick-explicit 420c226290 Merge pull request bitpay#45 from MarcoFalke/Mf1710-univalue-revert-test git-subtree-dir: src/univalue git-subtree-split: a44caf65fe55b9dd8ddb08f04c0f70409efd53b3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have been testing version 0.12.1, and I have seen that the address balance index does not work correctly. It seems to be missing some transactions to be indexed. For example, the balance of the address 12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX according to blockchain.info should be 50.0587895 BTC, but the core returns only 0.0587895 BTC, 50 BTC is missing.
The first time this happened I turned off the core and re-executed it with reindex = 1, but when I finished I saw the balance of the same address again and returned the same. I have bought other addresses such as 1HLoD9E4SDFFPDiYfNYnkBLQ85Y51J3Zb1 and 50 BTCs too.
Interestingly, the amount that is missing is the same amount as the first transaction they received (Coinbase)
The text was updated successfully, but these errors were encountered: