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
User Story
As a proposer I want to be able to call factory generated contracts without adding listings for each individual contract.
Alternative Solutions
Instead of specifying an address we will set the address to a specific value e.g. 0x99999999999
We then need an optional new hashed bytecode value in the rich contract schema that is read in these situations.
When creating a proposal with the specific address (0x99999999999) we know this is a factory contract and so will ask the user first in a modal to specify the address of the contract and we will set this as the to value. Here we can also verify the supplied address by comparing hashed bytecodes.
Then the user would simply get the usual param form for that contract.
Then in addition to finding trying to match addresses when decoding we should also check against hashed bytecode for a match.
This isn't the best solution because it requires some manual work from the user to find the contract address but we can improve this in future.
The text was updated successfully, but these errors were encountered:
User Story
As a proposer I want to be able to call factory generated contracts without adding listings for each individual contract.
Alternative Solutions
Instead of specifying an address we will set the address to a specific value e.g. 0x99999999999
We then need an optional new hashed bytecode value in the rich contract schema that is read in these situations.
When creating a proposal with the specific address (0x99999999999) we know this is a factory contract and so will ask the user first in a modal to specify the address of the contract and we will set this as the
to
value. Here we can also verify the supplied address by comparing hashed bytecodes.Then the user would simply get the usual param form for that contract.
Then in addition to finding trying to match addresses when decoding we should also check against hashed bytecode for a match.
This isn't the best solution because it requires some manual work from the user to find the contract address but we can improve this in future.
The text was updated successfully, but these errors were encountered: