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
Similar to #4070, nodes should listen to events emitted by the contract instance deployer contract, and store the instances information in their local db. Again, nodes should be able to collect this information from the DAL, which we can test by checking that a node that did not push a deployment tx has information on the instance once the tx is mined and pushed to L1.
With this, a node should have all required information to run a public function. Test that it's possible to call a public function on a deployed contract, even on the same tx in which it was deployed.
The text was updated successfully, but these errors were encountered:
Implementation for the initial contract instance deployer contract.
Tracks instance deployed events in nodes and stores them locally.
Skips validations for class id and eth address for now.
Fixes#4071Fixes#4072
Implementation for the initial contract instance deployer contract.
Tracks instance deployed events in nodes and stores them locally.
Skips validations for class id and eth address for now.
FixesAztecProtocol#4071FixesAztecProtocol#4072
Similar to #4070, nodes should listen to events emitted by the contract instance deployer contract, and store the instances information in their local db. Again, nodes should be able to collect this information from the DAL, which we can test by checking that a node that did not push a deployment tx has information on the instance once the tx is mined and pushed to L1.
With this, a node should have all required information to run a public function. Test that it's possible to call a public function on a deployed contract, even on the same tx in which it was deployed.
The text was updated successfully, but these errors were encountered: