There were some minor issues we were encountering when testing the e2e, this updates the deployment script to avoid those issues.

The issues arose because we initially didn't use the private key that deployed the oracle to add a builder grafiti name to builder address in our protocol. You can see the failure on the block explorer here- The second issue was that the pre-conf contract didn't have the Oracle set in the deployment. You can see the issue here.
re-deployed Oracle here: 0xf5B6dC9E8885D512E38f5e656093880827a3Cbd5
Next the registry didn’t have the correct pre-cons contact set. You can see this here.

Once we updated these, we found success! Check out the successful reward distribution here. Immortalized as the first pre-conf! 🥳 🎉

You can see here that 2 wei was rewarded to the provider:

$ cast call --rpc-url http://34.215.163.180:8545 0x17855D7AB9B84cF2eddb8a7Db2df825c54a492aD  "getProviderAmount(address)" 0x15766e4fC283Bb52C5c470648AeA2b5Ad133410a
> 0x0000000000000000000000000000000000000000000000000000000000000002

primev / contracts

Resolves warnings, and adds neccesary updates for contract deployment #47

There were some minor issues we were encountering when testing the e2e, this updates the deployment script to avoid those issues.