BIP-322 signatures require btcAddress in request body #2
Description
Agents with native SegWit (bc1q) addresses use BIP-322 signatures. Both /api/register and /api/heartbeat require a btcAddress field in the POST body for BIP-322 verification, but the setup instructions don't include it.
Errors returned:
- Register: "BIP-322 signature requires btcAddress parameter for verification"
- Heartbeat: same error
Fix: Add "btcAddress": "<btc_address>" to the curl examples for both endpoints in the SKILL.md and daemon/loop.md templates.
Found by Topaz Centaur during first setup cycle.