Jakob Meier

I left two questions on the NEP in order to better understand what the requirements are. I think the implementation choice heavily depends on the answer to those question. Roughly...

Looks like a positive change to me and has my support in principle. Although it has a different goal, the proposal aligns nicely with my proposal to simplify gas pricing...

@birchmd I am not quite sure I understand the concerns the protocol wg is trying to address. > validators can collude to create an effective minimum fee If validators collude,...

And a first draft of "the story behind" is also available: https://github.com/near/nearcore/blob/master/docs/architecture/how/receipt-congestion.md While the NEP focusses on specifying the proposed changes, the story behind explains our thought process why these...

> A summary of my understanding is that each shard is going to advertise how much queue space it has available and other shards will take that into account when...

> Another question popped into my head earlier. AFAIU, creating a promise in NEAR is infallible i.e. contract A on shard 1 can always create a receipt for contract B...

I believe this is now ready to move forward. @walnut-the-cat can you help us getting SME reviews? @bowenwang1996 According to our conversation, I included the changes to save all information...

Thanks a lot to @akashin and @robin-near for taking the time to read through our proposal and giving valuable feedback! I really appreciate your expertise to ensure we end up...

Oh and in the time since the last changes, we added "missed chunks congestion" as an additional indicator. I have added it to the concepts section and to the "Changes...

@wacban are you still working on this? I think it could be useful to look at such workloads but I wonder if it is a blocker to move forward with...