Wrong STX address registered — payout sent to uncontrolled wallet

[voidparrot0btc]

My agent Void Parrot was registered using the AIBTC MCP server (npx @aibtc/mcp-server). During registration, the MCP server generated its own internal wallet and used its STX address for registration — not my actual wallet address.
BTC Address (correct): bc1qn2wh460wvh4mkdfg9eyj7m4h3mr43cpaqvaasd
STX Address registered (wrong — MCP generated): SP1RXKCZESQBRF1DVNKDVHV1TYDBT1G0JR3183SMD
STX Address (correct — my wallet): SP42A8SJY8SXC60AMGXKT06C8FV6JW51XTPNFXH5
First payout already sent to wrong address:
TX: 6437a1eaae8124e8a7bcd797ec8425a461487a737305b525fda0e6dbdbaa4b32
Amount: 30,000 sats sBTC
Second payout still pending (payout_txid: null) — please update my STX address before processing.
I have verified that SP1RXKC... is not derivable from my mnemonic using any standard BIP32/BIP44 path. The MCP server must have generated it as a temporary wallet during setup.
Please advise on how to update the registered STX address and whether the first payout can be recovered.

[whoabuddy]

What do you mean by actual wallet address? You had one before setting up the agent?

The MCP server allows you to create or import a wallet but by default it expects to create one and you have to back up the seed phrase and the encryption password. The setup of the wallet is between you and the agent we have no control over that.

The agent should have passed that information to you at setup time, and if you've been able to participate in briefs then your Bitcoin and Stacks address was registered based on your signatures.

We've seen this with other issues where the LLM either hallucinated or incorrectly implemented it's own signature methods instead of using the MCP tooling.

We're tracking anyone affected by that in Discord and are working on a way to delete and allow re-registration for those affected. I'll add in your agent's information to that thread as well.

For now do not submit signals until resolved - our system automates the payouts based on the Stacks address you registered with via signature.

[whoabuddy]

Tracking under the STX migration umbrella aibtcdev/landing-page#614. Your
agent's entry is in the affected list there. Once the batch file publishes
(planned 2026-04-23), please submit both signatures within the 72-hour
verification window or reply on that umbrella if anything looks wrong. After
--apply runs, I'll close this issue with a reference to the migration
commit.