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
Describe the bug
Running tests of the Demo (Incredible Squaring AVS) with a POS DevNet I hit the invalid reference block error (more in Layr-Labs/incredible-squaring-avs#61).
It is trigger because the check enforce that a block has to be from the past. In the real Ethereum network, a block is a unit of time of around 12 seconds. If I understand correctly, every AVS can fail in the same way as the Demo in my tests, if conformation of the task comes in period shorted than a block.
That might not be a bug, but rather a feature/design choice (e.g. because in real life/production, a task won't have time to be deal in less than 12 seconds).
revert back the change enforcing the block to be in the past
Low priority and not a lot of work
The text was updated successfully, but these errors were encountered:
wawrzek
changed the title
AVSes cannot guarantee transaction faster than 12 seconds
AVS cannot guarantee transaction faster than 12 seconds
May 16, 2024
This is more a question for design clarification
Describe the bug
Running tests of the Demo (Incredible Squaring AVS) with a POS DevNet I hit the invalid reference block error (more in Layr-Labs/incredible-squaring-avs#61).
It is trigger because the check enforce that a block has to be from the past. In the real Ethereum network, a block is a unit of time of around 12 seconds. If I understand correctly, every AVS can fail in the same way as the Demo in my tests, if conformation of the task comes in period shorted than a block.
That might not be a bug, but rather a feature/design choice (e.g. because in real life/production, a task won't have time to be deal in less than 12 seconds).
To Reproduce
(cd contracts ; forge script script/IncredibleSquaringDeployer.s.sol --rpc-url http://localhost:8545 --broadcast --unlocked --sender 0x123463a4b065722e99115d6c222f267d9cabb524 )
make DEPLOYER_PRIVATE_KEY=0x2e0834786285daccd064ca17f1654f67b4aef298acbb82cef9ec422fb4975622 CHAINID=32382 send-fund
make CHAINID=32382 start-aggregator
make CHAINID=32382 start-operator
Expected behavior
Tasks should be validated in the same block
Environment
https://github.com/ivy-net/iv1
Potential solutions
The text was updated successfully, but these errors were encountered: