mirror of
https://github.com/serai-dex/serai.git
synced 2024-12-24 20:49:27 +00:00
8ea5acbacb
The caller is paid a fixed fee per unit of gas spent. That arguably incentivizes the publisher to raise the gas used by internal calls, yet this doesn't effect the user UX as they'll have flatly paid the worst-case fee already. It does pose a risk where callers are arguably incentivized to cause transaction failures which consume all the gas, not just increased gas, yet: 1) Modern smart contracts don't error by consuming all the gas 2) This is presumably infeasible 3) Even if it was feasible, the gas fees gained presumably exceed the gas fees spent causing the failure The benefit to only paying the callers for the gas used, not the gas alotted, is it allows Serai to build up a buffer. While this should be minor, a few cents on every transaction at best, if we ever do have any costs slip through the cracks, it ideally is sufficient to handle those. |
||
|---|---|---|
| .. | ||
| bin | ||
| bitcoin | ||
| ethereum | ||
| frost-attempt-manager | ||
| key-gen | ||
| messages | ||
| monero | ||
| primitives | ||
| scanner | ||
| scheduler | ||
| signers | ||
| src | ||
| view-keys | ||
| README.md | ||
Processor
The Serai processors, built from the libraries here, scan an external network
and report the indexed data to the coordinator. For details on its exact
messaging flow, and overall policies, please view docs/processor.