You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IUC, the issue is that these signatures are sent as ordinary transactions in the subnet. The FVM verifies that the sender account exists and has sufficient balance to cover the maximum gas costs as per base fee and gas fee cap. What we could do:
Auto-create Eth accounts matching the secp256k1 public keys of validators at genesis and as new validators are added.
Make validators submit these transactions from their f410 identities.
Detect "system" transactions like this at the interpreter level through pattern matching, e.g.:
from == some validator address.
to == gateway.
data is ABI-encoded to addCheckpointSignature.
Execute those transactions as implicit transactions at the FVM level; this disarms gas charging and removes the need for the account to hold balance.
We will need to accompany this with rejecting the block if the validator spams or misuses the system, e.g. includes transactions satisfying the above but with non-zero exit codes (error).
We'd need to make changes to the mempool to accept such transactions at that level too.
Find a way to remove the need for validators to maintain a balance of circulating supply in order to create checkpoints.
Suggestion: Validators could receive automatic fund allocations from the network to cover the necessary balance.
The text was updated successfully, but these errors were encountered: