Summary
When a beneficiary claims vested keys on-chain the server vesting record is not updated. A POST /vesting/:keyId/claim endpoint that submits the claim_vested contract call and updates the claimedAmount on the vesting record should be added.
Scope
- Add POST /vesting/:keyId/claim requiring a JWT matching the vesting beneficiary
- Read the current claimableAmount from the on-chain contract before submitting
- Submit the claim_vested contract call and update the claimedAmount on the vesting_schedules record
- Write a keys_claimed activity record to the activity_log table
- Return the amount claimed and the updated claimableAmount in the response
Acceptance Criteria
ETA: 12 hours
Coordinate on Telegram
Summary
When a beneficiary claims vested keys on-chain the server vesting record is not updated. A POST /vesting/:keyId/claim endpoint that submits the claim_vested contract call and updates the claimedAmount on the vesting record should be added.
Scope
Acceptance Criteria
ETA: 12 hours
Coordinate on Telegram