Sha256: e9c5e5a8c24c9e7b9a015c41ce56132af0114e78ea70c6c489b7b7b1bce675e7
Contents?: true
Size: 1.65 KB
Versions: 2
Compression:
Stored size: 1.65 KB
Contents
Feature: Assembled Shamir Key Scenario: Lock with Generated Key. Unlock with Assembled Shamir Key Given the blank contract: """javascript { "header": {}, "vaults": { "s_1":{ "fill_with": "EXTERNAL_DATA", "lock_with": "UNLOCKED", "unlock_with": "UNLOCKED", "contents": "" }, "s_2":{ "fill_with": "EXTERNAL_DATA", "lock_with": "UNLOCKED", "unlock_with": "UNLOCKED", "contents": "" }, "s_3":{ "fill_with": "EXTERNAL_DATA", "lock_with": "UNLOCKED", "unlock_with": "UNLOCKED", "contents": "" }, "s_4":{ "fill_with": "EXTERNAL_DATA", "lock_with": "UNLOCKED", "unlock_with": "UNLOCKED", "contents": "" }, "s_5":{ "fill_with": "EXTERNAL_DATA", "lock_with": "UNLOCKED", "unlock_with": "UNLOCKED", "contents": "" }, "message":{ "fill_with": "EXTERNAL_DATA", "lock_with": "GENERATED_SHAMIR_KEY['5','3','s_1','s_2','s_3','s_4','s_5']", "unlock_with": "ASSEMBLED_SHAMIR_KEY['s_1','s_2','s_3','s_4','s_5']", "contents": "" } } } """ And I create a new message When I attempt to lock the message with a generated shamir key Then key shares are created and locked away in their cooresponding vaults When I attempt to unlock the message with the assembled shamir key Then I successfully gather the locked shares and unlock the message
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
vault-tree-0.3.4 | features/keywords/assembled_shamir_key.feature |
vault-tree-0.3.3 | features/keywords/assembled_shamir_key.feature |