Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes more changes to PRC3 based on my discussion with @matejos
IInverseAppProjectedNft
optionally takes a new parameter_verificationData
to its mint function for cases where the mint validity can be verified (ex: zk proof). See Update inverse app projection to work with ZK proofs paima-engine#327IInverseAppProjectedNft
now exposes acurrentNonce
getter for cases frontends want to know the nonce for the user's addressTracking invalid mints
section moved because it was in the wrong placevalidity
trait type to allow users to safely place collection offersthe state transition to process the inverse projection should never fail
→should never fail for any reason other than signature mismatch
. If the user's signature doesn't match, we shouldn't incrementuserTokenId
otherwise you could grief a user by minting many failed txs on their behalf