Crypto API permissions need an owner and a revocation record
Distinguish viewing, trading, transfers and key administration; a teaching site is not a credential vault or account operator.
Authority belongs to the selected permission contract
An API key can have selected capabilities under its venue's current setup. Viewing, trading, transfers and administration are not interchangeable categories. Preserve the actual account, permission scope, creation source and effective restrictions without disclosing the secret. Official setup documentation explains its own mechanism, not every exchange's control model or a guarantee of least privilege. This publication accepts no key and performs no permission test. A website tutorial therefore cannot certify a reader's credential, withdrawal protection, account ownership or authorised automation scope.
Custody and execution are different responsibilities
Who holds the asset and who can submit a trade may be different actors. A bot entitlement, model subscription or copied signal does not automatically grant account administration. Actual operations need a named authorised cloud owner and durable evidence, not a laptop process that happens to be running. The static amount lens neither signs orders nor watches positions. Its declared asset label is not a wallet address or proof of a funded account. No custody transfer, subscriber route or actual paid service access is created by reading a detailed profile.
Revocation needs its own result
A request to revoke a key is an intention; the selected service's authenticated acknowledgement and applicable account state supply its result. Preserve responsible actor, scope, request identity and verified outcome where genuinely available. Do not paste secrets into references or exported notes. An absent verification remains unresolved. The paper outage drill similarly separates requests from account effects without becoming a key-management tool. There is no real revocation event or measured security incident in the examples, and no fabricated contact inbox is offered as an operational response channel.
Training must not quietly become production
A browser-local calculation or temporary QA server is not an authorised live account controller. Production publishers, refreshes, schedulers and verifiers belong in managed cloud services with personal computers off. No page introduces a workstation tunnel or PC fallback. Research source completion and production promotion remain separate tasks. TODO(Darren): confirm actual publisher/security contact and authorised service ownership before stronger accountability statements. The invented permission table below names absent evidence rather than certifying account safety, successful revocation, legally adequate controls or independently validated strategy returns.
Fictional crypto evidence case
An invented checklist says view scope documented, trade scope unresolved and revocation requested without verified acknowledgement. There is no actual key or account. The completed exercise retains the two missing authority/result objects instead of claiming a protected funded balance or completed credential removal.
| Object | Record | Bounded finding |
|---|---|---|
| View | Declared document | Not a tested key |
| Trade | Scope absent | No execution permission |
| Revoke | Request only | Result unresolved |

Primary references and scope
Source review: 14 October 2026. Official mechanism descriptions are not this desk's paid-account test, independently captured fills or vendor-return audit.