Reporting:
npub1… and hex — and they are interchangeable. The four characters after the # in a nickname are the last four of the hex format.
##\ ##\
## | ## |
#######\ ##\ ##\ ######\####\ #######\ #######\ ######\ ######\
## __##\ ## | ## |## _## _##\ ## _____|## __##\ \____##\\_## _|
## | ## |## | ## |## / ## / ## |## / ## | ## | ####### | ## |
## | ## |## | ## |## | ## | ## |## | ## | ## |## __## | ## |##\
## | ## |\####### |## | ## | ## |\#######\ ## | ## |\####### | \#### |
\__| \__| \____## |\__| \__| \__| \_______|\__| \__| \_______| \____/
##\ ## |
\###### |
\______/
Pick a frontier model to power every reply in this chat. Pro replies use separate Pro credits (100 sats each); standard routing picks the best model per task and uses standard credits.
Pro replies can read your code and, with writes on, commit, branch, and open pull/merge requests — Claude Code-style. Your access token is stored only on this device (Panic Mode wipes it) and sent to the Nymbot worker per request — never stored server-side or published to relays.
Your premium chat is already end-to-end encrypted, but Nymbot still sees which pubkey is talking to it. Turn this on and every message, and every reply, travels under a throwaway key generated on this device — the same trick group chats use. Nymbot bills that key, answers it, and never learns your nym. Credits move across as blind vouchers Nymbot signs without seeing, so its own records cannot link the two.