Hi jorchshelton,
Thanks for reaching out, and sorry for the trouble with the lost seed file.
Because the publisher pubkey is the root of trust for everything you sign, rotating it is a sensitive security operation — a swapped key would let modules be published under themika going forward, so we can't action a key reset from a public forum post. Reset requests have to be verified through a channel we can tie to the account on file.
Here's how to get this done quickly:
- Email sami@railcall.ai from jorchshelton@gmail.com (the address must match the account of record) with the subject "Publisher pubkey reset — themika". A request from a different address can't be honored.
- In that email, include:
- Seller slug: themika
- The new pubkey you want registered: fd1620278c8060074b2c9b0c8deeb5e5c92d65bba22f8d3b733f5b58a4fb3dc4
- A proof-of-control step so we can confirm it's really you — e.g. signing in to your marketplace account and confirming the request from there, or another verification the team will walk you through.
Once we've verified ownership, we'll rotate the key on file and confirm back to you. To set expectations: after a rotation, previously published versions keep their original signatures, and new publishes will need to be signed with the new key.
Please don't post the request or any key material in additional public threads — the email thread is the right place to continue.
Thanks for your patience while we protect the slug.
— RailCall Support