ArticMine I'd like to protest your long term block weight algorithm. What is this??

Also, from what I can tell the new fee algorithm is ~30% less fee per byte, does that sound accurate?

And, does anyone know the historical context around FEE_PER_KB_OLD

Also wondering about HF_VERSION_MIN_V2_COINBASE_TX and HF_VERSION_REJECT_SIGS_IN_COINBASE. They seem to implemented at protocol level, were those requirements previously not enforced (were there any violating transactions?)?

update_next_cumulative_weight_limit() uses a lot of CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE_V5 instead of full_reward_zone, is this intended or not written with best practice?

P.S. I no longer have irccloud so if there are responses I don't acknowledge, please email me about it ukoe⊙pc

This comment "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." implies

longtermblockweight isn't verified when downloading new blocks, is that accurate?

Wait ArticMine then says "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." which implies everyone must calculate it the same way (no consensus issues from rounding)

merry christmas, peeps

merry christmas WhatDo_.

The long term median is to mitigate against spa attacks such as big bang while at the same time allowing for a short term 50s boost is block weight to deal with seasonal demand such as the current season

Long term scaling requires a much lower rate of scaling

lol there is a LOT of min(max(min())) going on

I am traveling Dec 25th for the 36c3 in Germany where I will be speaking on this very subject

oh sweet :) I think I figured it all out though, just took some digging

So there will be periods when I will be off line

ArticMine can you explain about the consensus issues from rounding LongTermBlock Weight? Is it not fully deterministic within the protocol?

koe there is no issue with rounding as long as the calculations are done with properly defined integer math, which afaik, they are

i believe the document you referened was an early draft which was just making clear this point with one possible implementation but not the only one

that makes sense thanks smooth