Mainnet 1mxym to vote#26
Open
dusanjp-and-pasomi wants to merge 16 commits into
Open
Conversation
…ades (symbol#6) problem: MongoDB checks the feature compatibility version on upgrade. The upgrade will fail if it is not set to the previous release. This value does not automatically get set on upgrades. solution: set the feature compatibility version on upgrade.
problem: no way to import the node key from bootstrap solution: add support for importing the node key
problem: config does not support light rest node solution: added light rest config
problem: no routeExtensions in rest config solution: add routeExtensions to rest config
problem: image version needs to be updated for release solution: update REST and Catapult image version to the release
problem: setFeatureCompatibilityVersion fails on mongodb 7 since the confirm is required solution: add the confirm true in the setFeatureCompatibilityVersion
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
現在、symbolの votingNodeの条件として、「mainAccountに 300万xym以上の保有」とありますが、
これは条件が厳しい為に、votingNodeが増え無く、総合 votingPowerが伸び悩んでいます。
総合 votingPowerとは、全ての votingNodeの mainAccountの xym残高の合計を指します。
この総合 votingPowerが低いままだと、数基の大きな votingPowerを持つノードが停止するだけで、
finalizeが停止します。finalizeの停止は、取引所の送金業務に支障をもたらし、「すぐ送金出来なくなる通貨」と
認識されます。現にここ 1年でも 2回の finalizeの停止が発生しています。
この現状を改善する為に、votingNodeの条件「300万xym以上の保有」を緩和し、
「100万xym以上の保有」とする事が、より多くのノード参加者に votingNodeになれる様にし、
総合 votingPowerの増加によって、個別の大きな votingPowerを持つノードの停止による「finalize停止事故の防止」を期待出来るでしょう。
Currently, the requirement for becoming a votingNode on Symbol is that the main account must hold 3 million XYM or more. However, this threshold is quite high, which has resulted in very few new votingNodes being added, and the total votingPower has been stagnating. Total votingPower refers to the sum of the XYM balances held in the main accounts of all votingNodes. If the total votingPower remains low, the finalization process can stop if just a few nodes with large votingPower go offline. A halt in finalization disrupts exchange withdrawal and deposit operations, causing Symbol to be perceived as “a coin that may suddenly become impossible to transfer.” In fact, finalization has already stopped twice in the past year. To improve this situation, we propose relaxing the votingNode requirement from “3 million XYM or more” to “1 million XYM or more.” This change would allow many more participants to run votingNodes, increase the overall votingPower, and significantly reduce the risk of finalization stopping due to the outage of a few large nodes.