Editorial policy and product sources

Who publishes these guides?

TokenGeneratorApp publishes the product documentation and blog. We describe our own application and have a commercial interest in its use. Our comparison articles are not independent rankings, and we do not claim external endorsements unless a source is identified.

Blog pages show the original publication date and, when revised, the modification date. A modified date records an editorial change; it is not evidence of a new security audit.

Sources for product claims

Available controls are determined by the current contract templates and the creation form. The contract reference links to the Basic, Standard and Premium source files and their compiler input. For an existing token, inspect the source and settings of that particular deployment: older tokens can use older templates.

Network specifications and verification requirements should be checked against the network or explorer’s official documentation. Guides link to those sources where relevant. Platform behavior and third-party network behavior are separate claims.

Prices and examples

The pricing page and final creation quote are the references for current platform fees. Network gas is additional. Campaign expiry, enabled features and validated referral discounts can change the quote.

Liquidity examples explain a calculation, not a recommended investment or a guaranteed launch budget. Historical changelog prices describe a past release. Neither is a current offer.

Verification, testing and audits

Explorer verification connects source code with deployed bytecode. Automated tests check specific expected behaviors. OpenZeppelin supplies reusable components. None of these is an independent audit of the complete token contract or a guarantee that a configuration is safe.

Read the security and ownership limitations, test the intended configuration and inspect owner permissions before deployment.

Corrections and contact

Report an outdated statement through our contact page. Include the page URL, the statement and a supporting source when available. Never send private keys or recovery phrases.