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
In fhEVM native upon re-executing runTrivialEncrypt, it was observed that the existing ciphertexts for previously computed handles are not reused. Instead, the Executor is retasked to recompute them again
function runTrivialEncrypt() externalvirtualreturns (uint256result) {
bytes1 toType =0x03;
for (uint256 i =1; i <=3; i++) {
this.trivialEncrypt(i, toType);
}
}
Scenario
Execute runTrivialEncrypt in BLOCK_N
Wait until BLOCK_N + 5 for the handles to be persisted in EVM (materialized)
Re-execute runTrivialEncrypt in BLOCK_N + 5 + 1
Expected result
As with fhevm-go-coproc, we should leverage precomputed ciphertexts. In fhevm-go-coproc, successfully computed handles are marked as done in SQLite storage.
The text was updated successfully, but these errors were encountered:
Problem
In
fhEVM native
upon re-executingrunTrivialEncrypt
, it was observed that the existing ciphertexts for previously computed handles are not reused. Instead, the Executor is retasked to recompute them againScenario
runTrivialEncrypt
in BLOCK_NBLOCK_N + 5
for the handles to be persisted in EVM (materialized)runTrivialEncrypt
inBLOCK_N + 5 + 1
Expected result
As with fhevm-go-coproc, we should leverage precomputed ciphertexts. In fhevm-go-coproc, successfully computed handles are marked as done in SQLite storage.
The text was updated successfully, but these errors were encountered: