Lock In: 403 Output Already Locked
dexX7 opened this issue · comments
Endpoint:
POST /lock
Request:
{
"pubkey": "024c057b5f8e0b444fb2987989e12129af834a173f6374bb1f2a0b6af6b34cb5ee",
"txid": "1f90d7e40bc0e3a664693933f9588a1c8bf4c337e7385080c1af6291e5111034",
"vout": 2
}
Response:
Status: 403 Bad Forbidden
{
"error": "output already locked"
}
Mechanism:
- Parse request
- Retrieve status of outpoint
- Return error if outpoint is locked
Not needed, because outputs are inherently locked due to the use of new keys for each request.