Summary
The on-chain holder cap can be set by the creator but there is no server endpoint for this. A POST /creator/:keyId/holder-cap endpoint that submits the set_holder_cap contract call and records the new cap in the database should be added.
Scope
- Add POST /creator/:keyId/holder-cap with { capBps: number } body requiring a JWT matching the key creator
- Validate capBps is between 100 and 2500 (1%–25%)
- Submit the set_holder_cap contract call
- Update the holderCapBps field on the key record in the database
- Return the updated holderCapBps and the equivalent percentage in the response
Acceptance Criteria
ETA: 12 hours
Coordinate on Telegram
Summary
The on-chain holder cap can be set by the creator but there is no server endpoint for this. A POST /creator/:keyId/holder-cap endpoint that submits the set_holder_cap contract call and records the new cap in the database should be added.
Scope
Acceptance Criteria
ETA: 12 hours
Coordinate on Telegram