Given that the initial number of attestation nodes is small, and the cross replication rate is also small, this is likely fine. Moreover, these costs will be rotate among node participants.
However, it is probably more robust to have a system where execution nodes do not update anyone else state, except for itself (and potentially the user?).
This can be done, by introduce an AttestationClaimProof that is stored on the AtomaDb whenever an attestation node submits its commitment.
Given that the initial number of attestation nodes is small, and the cross replication rate is also small, this is likely fine. Moreover, these costs will be rotate among node participants.
However, it is probably more robust to have a system where execution nodes do not update anyone else state, except for itself (and potentially the user?).
This can be done, by introduce an
AttestationClaimProofthat is stored on theAtomaDbwhenever an attestation node submits its commitment.