feat: add credential and es256 keys

interfacerproject · Feb 23, 2024 · 2cd78d3 · 2cd78d3
1 parent acb214e
commit 2cd78d3
Show file tree

Hide file tree

Showing 2 changed files with 24 additions and 0 deletions.
diff --git a/src/keypairoomClient-8-9-10-11-12.zen b/src/keypairoomClient-8-9-10-11-12.zen
@@ -18,6 +18,7 @@ Scenario 'ecdh': Create the key
 Scenario 'ethereum': Create key
 Scenario 'reflow': Create the key
 Scenario 'eddsa': Create the key
+Scenario 'es256': Create the key
 
 
 # Loading the user name from data
@@ -72,19 +73,29 @@ When I rename the 'hash' to 'seed.reflow'
 When I create the hash of 'seed.reflow'
 When I rename the 'hash' to 'seed.bitcoin'
 
+When I create the hash of 'seed.bitcoin'
+When I rename the 'hash' to 'seed.es256'
+
 # end of the sorted creation flow
 
 When I create the ecdh key with secret key 'seed.ecdh'
 When I create the eddsa key with secret key 'seed.eddsa'
 When I create the ethereum key with secret key 'seed.ethereum'
 When I create the reflow key with secret key 'seed.reflow'
 When I create the bitcoin key with secret key 'seed.bitcoin'
+When I create the es256 key with secret key 'seed.es256'
+
+# Here we create the "credential" key (used to request a Coconut zkp credential)
+# from the reflow key, cause they both are BL381 keys the credential sk doesn't have a pk
+When I pickup from path 'keyring.reflow'
+When I create credential key with secret 'reflow'
 
 When I create the ecdh public key
 When I create the eddsa public key
 When I create the ethereum address
 When I create the reflow public key
 When I create the bitcoin public key
+When I create the es256 public key
 
 # Creating the hashes of the single challenges, to OPTIONALLY help
 # regeneration of the keypair

diff --git a/src/keypairoomClientRecreateKeys.zen b/src/keypairoomClientRecreateKeys.zen
@@ -18,6 +18,7 @@ Scenario 'ecdh': Create the key
 Scenario 'ethereum': Create key
 Scenario 'reflow': Create the key
 Scenario 'eddsa': Create the key
+Scenario 'es256': Create the key
 
 # here we load the seed as a mnemonic
 Given I have a 'mnemonic' named 'seed'
@@ -39,19 +40,30 @@ When I create the  hash  of 'seed.ethereum'
 When I rename the 'hash' to 'seed.reflow'
 When I create the  hash  of 'seed.reflow'
 When I rename the 'hash' to 'seed.bitcoin'
+When I create the  hash  of 'seed.bitcoin'
+When I rename the 'hash' to 'seed.es256'
+
 
 When I create the ecdh key with secret key 'seed.ecdh'
 When I create the eddsa key with secret key 'seed.eddsa'
 When I create the ethereum key with secret key 'seed.ethereum'
 When I create the reflow key with secret key 'seed.reflow'
 When I create the bitcoin key with secret key 'seed.bitcoin'
+When I create the es256 key with secret key 'seed.es256'
+
+# Here we create the "credential" key (used to request a Coconut zkp credential)
+# from the reflow key, cause they both are BL381 keys the credential sk doesn't have a pk
+When I pickup from path 'keyring.reflow'
+When I create credential key with secret 'reflow'
+
 
 # PKs generation
 When I create the ecdh public key
 When I create the eddsa public key
 When I create the ethereum address
 When I create the reflow public key
 When I create the bitcoin public key
+When I create the es256 public key
 
 # This prints the keyring containing the SKs
 Then print the 'keyring'
@@ -62,6 +74,7 @@ Then print the 'eddsa public key' as 'base58'
 Then print the 'ethereum address'
 Then print the 'reflow public key' as 'base58'
 Then print the 'bitcoin public key' as 'base58'
+Then print the 'es256 public key' as 'base58'
 
 # This prints the seed for the private keys as mnemonic
 Then print the 'seed' as 'mnemonic'