From 777a27a80e7f962a74970d9ee505dec18e078e7e Mon Sep 17 00:00:00 2001 From: Fabrizio Romano Genovese Date: Fri, 5 Jan 2024 14:41:52 +0100 Subject: [PATCH] Cosmetics. --- _posts/2024-01-05-correctly-pricing-txs-parallel.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2024-01-05-correctly-pricing-txs-parallel.md b/_posts/2024-01-05-correctly-pricing-txs-parallel.md index 20ada07..41b7205 100644 --- a/_posts/2024-01-05-correctly-pricing-txs-parallel.md +++ b/_posts/2024-01-05-correctly-pricing-txs-parallel.md @@ -38,7 +38,7 @@ One consequence of this is that whatever gas pricing mechanism we adopt, it cann - The block builder instead receives the whole value of the user transaction, maybe plus a small bonus; - The delta between what the user pays and what the builder receives is simply created, as block rewards are created now. -We are not claiming that this is the right way to do it. The example above only shows how one must be a bit creative when it comes to incentive design to make sure all actors are aligned. Luckily for us, there's a vast literature on topics such as cloud infrastructure pricing that we can boorrow from, so we don't have to start from scratch. We will probably come up with some follow-up posts about this in the future. +We are not claiming that this is the right way to do it (and indeed it's not, because it may require to sequentially simulate the block to calculate the improvement coefficient, that defies the purpose of parallelization completely). The example above only shows how one must be a bit creative when it comes to incentive design to make sure all actors are aligned. Luckily for us, there's a vast literature on topics such as cloud infrastructure pricing that we can boorrow from, so we don't have to start from scratch. We will probably come up with some follow-up posts about this in the future. ## A story of ordering