HTTPWalletJSON
Reveals specific key linkage
Changed onpost/revealSpecificKeyLinkage
Request
- Base URLhttp://localhost:3321
- Authnone declared
Request body
Example request
{
"counterparty": "027facf8e28228eea25abd69c4f23f15573e1d0f9180718af297e1458827cd5aef",
"verifier": "03c378a866d72c391343eddeadf64c4f896637c4160ac6073e7b80b5717310153b",
"protocolID": [
0,
"todo token"
],
"keyID": "1",
"privilegedReason": "special stuff"
}Response
The specific key linkage
Example response
{
"prover": "02790ab2d725d04af29e20bf46e1dbc40ba8b49f1355146884c5bd06819273d101",
"verifier": "03c378a866d72c391343eddeadf64c4f896637c4160ac6073e7b80b5717310153b",
"counterparty": "027facf8e28228eea25abd69c4f23f15573e1d0f9180718af297e1458827cd5aef",
"revelationTime": "2024-12-12T12:12:12.120Z",
"protocolID": [
0,
"todo token"
],
"keyID": "1"
}Changes
- breaking
the
request property's minItems was increased to2 - info
added
subschema #1subschema #2to therequest property 'prefixItems' list - info
added the optional property
to the response with the status
- breaking
- breaking
removed
subschema #1subschema #2from therequest property 'prefixItems' list - warning
removed the optional property
from the response with the status
- breaking