IOG Partner Chain Work stream #8
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add cardano-node to flake and the corresponding start-up script
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Executable Specifications
Property 1 - Non Fungible Property Transitivity : EN Token is an NFT => the ENOP Token should be an NFT
Property 1.0: Tokens Quantities are verifiedr.1.0.0 violation- No ENNOP Minted (can't be enforced)r.1.0.1 violation- ENNOP Minted Quantity > 1r.1.0.2 violation- No ENNFT on Registration validator outputr.1.0.3 violation- ENNFT Quantity > 1Property 1.1: NFTs Token Names & Cardinality equality : There is 1-1 relationship between the ENNFT and the ENOPNFTr.1.1.0 violation- ENOPNFT TokenName =/ ENNFT TokenNamer.1.1.1 violation- |ENOP NFT| > 1 (Cardinality Violation)r.1.1.2 violation- |EN NFT| > 1 (Cardinality Violation)Property 1.0: Tokens Quantities are verifiedu.1.0.0 violation- ENNOP Not Output to Operatoru.1.0.1 violation- No ENNFT on Registration validator outputu.1.0.2 violation- No Minting Allowedu.1.0.3 violation- No Burning AllowedProperty 1.1: NFTs Token Names & Cardinality equality : There is 1-1 relationship between the ENNFT and the ENOPNFTu.1.1.0 violation- ENOPNFT TokenName =/ ENNFT TokenName:u.1.1.1 violation- |ENOP NFT| > 1 (Cardinality Violation)u.1.1.2 violation- |EN NFT| > 1 (Cardinality Violation)Property 1.0: Tokens Quantities are verifiedd.1.0.0 violation- No ENNOP NFT To Burnd.1.0.1 violation- No Minting Allowedd.1.0.2 violation- ENOP NFT Quantity to Burn > 1 (enforced by Non Fungible Property of EN Tokens )d.1.0.3 violation- No ENNFT Released To OperatorProperty 1.1: NFTs Token Names & Cardinality equality : There is 1-1 relationship between the ENNFT and the ENOPNFTd.1.1.0 violation- ENOPNFT TokenName =/ ENNFT TokenName:d.1.1.1 violation- |ENOP NFT| > 1 (Cardinality Violation)d.1.1.2 violation- |EN NFT| > 1 (Cardinality Violation)d.1.1.3 violation- No Registration validator Output AllowedProperty 2 - Preserving NFTs ownership : ENOP and ENNFT can be swapped only between the operator and the registration smart contract
Register
Property 2.0: ENOP NFT should be given to the operatorr.2.0.0 violation- ENNOP Minted Not Output to OperatorProperty 2.1: ENNFT should be output on script (Already Validated by -1.0.2 violation- No ENNFT on Registration validator output )Update
Property 2.0: ENOP NFT should be spent and given back to the operatoru.2.0.0 violation-ENNOP Not Output to Operator(Already Validated by -u.1.0.0 violation)Property 2.1: ENNFT should be output on script (Already Validated by -u.1.0.2 violation- No ENNFT on Registration validator output )Deregister
Property 2.0: ENOP NFT should be spent from the operator and burntd.2.0.0 violation- No ENNOP Burn (Already Validated by -d.1.0.0 violation)d.2.0.1 violation- Burn Without A Proper Registration Validator Input Not AllowedProperty 2.1: ENNFT should be spent from Registration scipt and output to Operator (Already Validated by -d.1.0.1 violation)Register & Update & Deregister
Property 2.2: Only the operator should sign the transaction2.1.0 violation- No signer found (Enforced by Ledger Properties)2.1.1 violation- signer is not uniqueProperty 3 - Datum Authenticity & Validity : The registration details (datum) should be verifiable and Valid (Signed and Provided by the owner of the ENNFT)
3.0.o violation- Registration datum Output should be valid3.0.1.o violation-ennftTokenNamefield should be equal to the spent ennft token Name3.0.2.o violation-enopNFTCurrencySymbolfield should be equal to the ENOP NFT currency Symbol minted3.1.o violation- Registration datum Output can not be deserialized3.2.o violation- Registration datum Output is not Auhtentic3.3.o violation- Registration validator Output not found (not verifiable)3.4.o violation- Registration validator Output has no datum (not verifiable)3.5.o violation- Registration validator Output has only the hashed datum (not verifiable)3.6.o violation- More than one Registration validator Output is not allowed (Reducing complexity)