Your poa1… address is public
Keep the complete address with your account records. It identifies where rewards are recorded and lets you look up public ledger activity. You can share it when someone needs to identify your account or send it POA.
An address does not sign requests. Pasting it into an API-key field will not connect a miner. A shortened address shown in a screenshot may also be insufficient for an exact lookup.
Your pk_… API key is private account access
The hosted API uses this credential to authorize account actions. Someone with the credential may be able to control the account, so do not publish it or include it in a source repository.
For a backend app, put the key in the platform’s server-side secret store. The frontend should ask the backend to perform a narrowly defined operation; it should never receive the key back.
Connecting the SearchPoA owner console
The current console expects a Base44 secret named POA_API_KEY containing the existing key. After saving the secret, the owner can refresh status to check the returned full address and balance.
The console only permits admin access and does not provide public account registration or credential collection. Visitors can read the guides without entering an address or key.
Keep a backup before relying on automation
- Save the private key in a password manager or another secure place you control.
- Keep it out of screenshots, public chat, browser URLs, analytics, and logs.
- Record which public address belongs to the saved credential.
- If access is lost, check the official recovery options; creating a new account does not restore the old balance.
Sources & further reading
Project rules can change. The primary documentation takes precedence over this independent guide.