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
This release 1.1.0 is a tag for production legacy contracts. All further changes will be committed to the main branch and a major version of the example will be released. All fixes to production example contracts (validators) will be made to this tag.
fixed lock file on main branch. You can use main version as example.
latest version 1.3.0 doesn’t contain Statev2, but it’s predicted and we are working on update.
I was able to to do most of the contract updates by replacing by Statev2 with State, etc.
I also had to manually add int256ToAddress that was removed from GenesisUtils.
But now my main problem is how to build the data for the setRequest call.
I have the values for the previous call:
bool res = setZKPRequest(
requestId,
validator,
schema,
claimPathKey,
operator,
value
);
but not for the new call: setZKPRequest(requestId, request);
Activity
vmidyllic commentedon Nov 13, 2023
This release 1.1.0 is a tag for production legacy contracts. All further changes will be committed to the main branch and a major version of the example will be released. All fixes to production example contracts (validators) will be made to this tag.
fixed lock file on main branch. You can use main version as example.
latest version 1.3.0 doesn’t contain Statev2, but it’s predicted and we are working on update.
vmidyllic commentedon Nov 13, 2023
or you can stick to version of 1.1.0 in your branch in case you use have own project.
joelamouche commentedon Nov 15, 2023
I was able to to do most of the contract updates by replacing by Statev2 with State, etc.
I also had to manually add int256ToAddress that was removed from GenesisUtils.
But now my main problem is how to build the data for the setRequest call.
I have the values for the previous call:
but not for the new call:
setZKPRequest(requestId, request);https://github.com/iden3/contracts/blob/master/contracts/verifiers/ZKPVerifier.sol
with request being:
struct ZKPRequest {
string metadata;
ICircuitValidator validator;
bytes data;
}
vmidyllic commentedon Nov 20, 2023
PR of upgrade to 1.3.2 is here
#12
Documentation will released this week.
joelamouche commentedon Nov 20, 2023
Awesome! Looking forward to it. I will take a look if I get the opportunity
vmidyllic commentedon Nov 21, 2023
Hi @joelamouche, we released a new tutorial and examples
Feel free to ask anything in support channels if you have any problems
Fixed in #17
https://github.com/0xPolygonID/tutorial-examples/tree/main/on-chain-verification
https://devs.polygonid.com/docs/verifier/on-chain-verification/overview/
joelamouche commentedon Dec 12, 2023
Hi @vmidyllic
Finally got around to implement this in our code base. Thank you for the work it was very helpful.
BTW I had to rewrite this function to use viem instead of web3 (might be useful to you or other users):
Also, I think verifier address in https://github.com/0xPolygonID/tutorial-examples/blob/main/on-chain-verification/scripts/deployValidators.js doesn’t seem to be correct. I had to deploy my own VerifierSigWrapper/VerifierSig for it to work