<feed xmlns='http://www.w3.org/2005/Atom'>
<title>monzero-core.git/tests/block_weight/CMakeLists.txt, branch main</title>
<subtitle>Monzero core node, command-line wallet, consensus code, and release tooling.
</subtitle>
<id>https://code.monzero.org/monzero-core.git/atom?h=main</id>
<link rel='self' href='https://code.monzero.org/monzero-core.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/'/>
<updated>2022-03-04T05:59:20Z</updated>
<entry>
<title>Copyright: Update to 2022</title>
<updated>2022-03-04T05:59:20Z</updated>
<author>
<name>mj-xmr</name>
<email>mjxmr@protonmail.com</email>
</author>
<published>2022-03-01T11:16:17Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=da9aa1f7f802552b9de459f331a2f39c84898009'/>
<id>urn:sha1:da9aa1f7f802552b9de459f331a2f39c84898009</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr)</title>
<updated>2020-10-28T19:08:26Z</updated>
<author>
<name>mj-xmr</name>
<email>mjxmr@protonmail.com</email>
</author>
<published>2020-10-26T19:53:21Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=8a282f64c9c99f584d2a1bd06a11ad5651cd2413'/>
<id>urn:sha1:8a282f64c9c99f584d2a1bd06a11ad5651cd2413</id>
<content type='text'>
Add monero_add_minimal_executable and use in tests

This is done in order not to have to relink targets, when just an .so changed, but not its interface.
</content>
</entry>
<entry>
<title>tests: handle any cmake detected python interpreter</title>
<updated>2019-03-07T16:46:02Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-02-27T20:57:07Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=fa43b547804496ea2bd7ad42893708f97b4f442c'/>
<id>urn:sha1:fa43b547804496ea2bd7ad42893708f97b4f442c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ArticMine's new block weight algorithm</title>
<updated>2019-03-04T09:33:58Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-01-21T17:18:50Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=b8787f430262520a9e81267802b869b1a7cde245'/>
<id>urn:sha1:b8787f430262520a9e81267802b869b1a7cde245</id>
<content type='text'>
This curbs runaway growth while still allowing substantial
spikes in block weight

Original specification from ArticMine:

here is the scaling proposal
Define: LongTermBlockWeight
Before fork:
LongTermBlockWeight = BlockWeight
At or after fork:
LongTermBlockWeight = min(BlockWeight, 1.4*LongTermEffectiveMedianBlockWeight)
Note: To avoid possible consensus issues over rounding the LongTermBlockWeight for a given block should be calculated to the nearest byte, and stored as a integer in the block itself. The stored LongTermBlockWeight is then used for future calculations of the LongTermEffectiveMedianBlockWeight and not recalculated each time.
Define:   LongTermEffectiveMedianBlockWeight
LongTermEffectiveMedianBlockWeight = max(300000, MedianOverPrevious100000Blocks(LongTermBlockWeight))
Change Definition of EffectiveMedianBlockWeight
From (current definition)
EffectiveMedianBlockWeight  = max(300000, MedianOverPrevious100Blocks(BlockWeight))
To (proposed definition)
EffectiveMedianBlockWeight  = min(max(300000, MedianOverPrevious100Blocks(BlockWeight)), 50*LongTermEffectiveMedianBlockWeight)
Notes:
1) There are no other changes to the existing penalty formula, median calculation, fees etc.
2) There is the requirement to store the LongTermBlockWeight of a block unencrypted in the block itself. This  is to avoid possible consensus issues over rounding and also to prevent the calculations from becoming unwieldy as we move away from the fork.
3) When the  EffectiveMedianBlockWeight cap is reached it is still possible to mine blocks up to 2x the EffectiveMedianBlockWeight by paying the corresponding penalty.

Note: the long term block weight is stored in the database, but not in the actual block itself,
since it requires recalculating anyway for verification.
</content>
</entry>
</feed>
