Abstract How do we price the cost of service interruption for end users for Sushi Relay?
Sushi Relay is a service that accepts user transactions for purposes of private inclusion and rebating this transaction flow by reimbursing end users / protocols with a percentage of profits obtained by arbitrage/MEV transactions. It operates as a private and permissioned mempool. Since users are paid for their submissions of transactions the question evidently rises on how to price transaction inclusion delays.
How do price a network outage for our transaction services? The current existing Gas Pricing API can be used for this purposes by applying the principle of Little’s Law .
We can take the value for Littles Law (we apply this to a new field called ‘networkCongestion’) and apply it to the time of networkOutage , which is the time that zero transactions are able to be included in the network . A period of networkOutage can be defined as a value that is three standard deviations above networkCongestion . Think of this as the time it takes to return to a normal value of networkCongestion after the outage is over, i.e. how long it takes to return to normal network congestions (how long it takes to process the transactions that have accumulated during an outage) after networkOutage is over.
Read the entire new gas pricing API and example here:
Feedback, comments, questions are welcomed