To fund and top up Identity in secure way we need to verify that asset lock transaction exists. There are two ways to do that: with instant lock and chain lock. This is the first iteration with instant lock proof type.
What was done?
Introduced AssetLock structure with transaction, output index and proof
Introduced Instant asset lock proof
Structure validator checks for identity existence instead of data validation for Identity Top Up Transition
Removed unnecessary dot env
Improved validate state transition fee test
How Has This Been Tested?
With unit and integration tests
Breaking Changes
identity.create and identity.createIdentityTopUpTransition expect asset lock transaction, output, and proof instead of outpoint.
renamed skipAssetLockConfirmationValidation DPP option to skipAssetLockProofSignatureVerification
Checklist:
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation
For repository code-owners and collaborators only
[x] I have assigned this pull request to a milestone
Issue being fixed or feature implemented
To fund and top up Identity in secure way we need to verify that asset lock transaction exists. There are two ways to do that: with instant lock and chain lock. This is the first iteration with instant lock proof type.
What was done?
How Has This Been Tested?
With unit and integration tests
Breaking Changes
identity.createandidentity.createIdentityTopUpTransitionexpect asset lock transaction, output, and proof instead of outpoint.skipAssetLockConfirmationValidationDPP option toskipAssetLockProofSignatureVerificationChecklist:
For repository code-owners and collaborators only