Repository navigation
contract should not store full Attestation submission #1629
Description
Background
@barakeinav1 observed that gas usage is too high when deploying two nodes with TEE, and attempting to vote in a new node. We also observed that verify_tee is using ~270Tgas per call, which is only to verify 2-3 nodes with attestation.
We believe our current tests did not uncover this bug earlier, as all our sandbox tests that use a runtime use mocked attestations which are very cheap to verify.
The issue is that resharing votes failed due to max gas (300tgas) being exceeded. This is due to resharing votes currently re-verifying every participant + the proposed one.
User Story
No response
Acceptance Criteria
- the contract does not store the full attestation for any participant
- re-verifications only manually checks for expiry and the allowed hash
- re-run @barakeinav1 's manual test and verify that gas usage is acceptable
Resources & Additional Notes
No response
Activity
barakeinav1 commentedon Dec 10, 2025
I check several pck_crl certificates we got from DTX collateral (from phala endpoint)./
the CRLs
Next updatefield is 30 day ahead of theThis updatefield - e.g CRL are valid for 30 days.if we can extract this value during verification - great.
but if it hard, I think we can assume this will be the value.
barakeinav1 commentedon Dec 10, 2025
TL/DR
Certificate & CRL Validity Table (example):
DSharifi commentedon Dec 10, 2025
Thanks for digging this up @barakeinav1. I'll create a follow up issue in case we want to use these TTLs that are part of the certificate.
For this Issue I'll go ahead and use a timeout value that the contract can enforce that is less than 30 days.
DSharifi commentedon Dec 10, 2025
@barakeinav1 #1639