-
Notifications
You must be signed in to change notification settings - Fork 98
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
valuePools (sprout, sapling) monitoring / calculation works incorrectly #604
Comments
Btw, jfyi, currently the value of pools in KMD chain are following: [
{
"id": "sprout",
"monitored": true,
"chainValue": 84948.93692198,
"chainValueZat": 8494893692198
},
{
"id": "sapling",
"monitored": true,
"chainValue": 3.07618319,
"chainValueZat": 307618319
}
] Since the |
fixes 'ERROR: ConnectBlock: ac_staked chain failed slow komodo_checkPOW' among other things squashed 00f8aa...820b99 add zk-SNARK proofs related comments zmq: Fix due to invalid argument and multiple notifiers fix value pools calculations (#63) KomodoPlatform/komodo#604 depends: patch boost to ignore -Wnonnull new gcc 11 warnings (#64) this patch fixes errors like: ``` include/boost/concept/detail/general.hpp:39:47: warning: 'this' pointer null [-Wnonnull] 39 | static void failed() { ((Model*)0)->~Model(); } ``` during build with gcc 11.x, more details can be found here: - boostorg/concept_check#27 - boostorg/concept_check#28 build: proper clean of ./src/qt/qrc_*.cpp in clean-help Add chain supply and transparent value to block index. Co-authored-by: Jack Grigg <jack@z.cash> Co-authored-by: Kris Nuttycombe <kris@nutty.land> Co-authored-by: Daira Hopwood <daira@jacaranda.org> bump version [0.8.1.3] from 0.8.1.3 diskblockindex have new fields, related to chain supply caused by this block and delta in the transparent pool produced by the action of the transparent inputs to and outputs from transactions in this block. See the: TRANSPARENT_VALUE_VERSION constant. fix transparent pool addition for unspendable outputs chain.h: change std::nullopt to boost::none in comments introduce burned coins value pool burned coins refer to the value sent for OP_RETURN scripts: ``` "vout": [ ... { "value": 2.00000000, "valueZat": 200000000, "n": 1, "scriptPubKey": { "asm": "OP_RETURN 6465636b6572", "hex": "6a066465636b6572", "type": "nulldata" } } ], "vjoinsplit": [ ] ``` burned coins are also excluded from transparent pool. bump version [0.8.1.4] this update activates burned coins value pool, see: BURNED_VALUE_VERSION revert fMiningRequiresPeers change on CMainParams The change was made solely for debugging purposes and was accidentally included in the PR. We are now reverting that change. remove unused CompareBlocksByHeightMain comparator bump COPYRIGHT_YEAR to 2024
Ever since we started using our own versioning system, which is similar to
0.7.x.y
, instead of the default ZCash versioning1.x.y.z
(meaning our release has lower versions than the initial), it appears that we have encountered issues with monitoring the valuepools.For example, version
0.8.1.1
resulting innVersion == 80101
. And here:komodo/src/chain.h
Lines 446 to 456 in d9144d0
We lost read/write of
nSproutValue
andnSaplingValue
for theCDiskBlockIndex
, as the values ofSPROUT_VALUE_VERSION
andSAPLING_VALUE_VERSION
is higher than current actual version:komodo/src/chain.h
Lines 40 to 41 in d9144d0
As a result this code for updating
nChainSproutValue
andnChainSaplingValue
don't work, becausepindex->nSproutValue
andpindex->nSaplingValue
areboost::none
(no read from index):komodo/src/main.cpp
Lines 6041 to 6094 in d9144d0
As a result
getblockchaininfo
RPC output looks like this:The offer is to change
SPROUT_VALUE_VERSION
andSAPLING_VALUE_VERSION
to80102
(0.8.1-beta3
) in KomodoOcean and komodod simultaneously, otherwise the bootstraps between original komodod and KomodoOcean will be incompatible (of course, it assumes publishing releases80102
,0.8.1-beta3
)Since monitoring value pools is not a critical issue, we can delay addressing it. However, if we decide to make changes now, both daemons in KomodoOcean and this repository should have the same version and the same read/write activation constants.
The text was updated successfully, but these errors were encountered: