TRX Logo

VanityTRON

Custom Address Generator

Buy us a coffee

Our free tools run entirely on donations. Your support pays for the servers and GPU power that make every generation possible. If we helped you today, a small donation helps keep this service free for everyone.

ETH · Ethereum network
0xcf5777b71c31146bd396cece6d3128e42d0ad9f7

Thank you for keeping us running! ❤️

Keys

TRON secp256k1 Keys and Address Formats

TRON uses secp256k1 key pairs. The familiar 34-character T address is a Base58Check representation of an address with version byte 0x41.

By Updated 2 min readRead as Markdown

From key to TRON address. Public key: Derived using secp256k1; Hex form: 41 prefix followed by the account-address bytes; Base58Check: Encoded public form begins with T.
From key to TRON address. Public key: Derived using secp256k1; Hex form: 41 prefix followed by the account-address bytes; Base58Check: Encoded public form begins with T.Open full-size diagram (SVG)Download diagram (PNG)About these visual guides
Short answer: TRON uses secp256k1 key pairs. The familiar 34-character T address is a Base58Check representation of an address with version byte 0x41.

The key, public key and address serve different roles

A TRON private key is a secret scalar used for signing. A public key is mathematically derived from it. An address is then derived from public-key data and encoded for use by wallets and APIs. Knowing an address is not equivalent to possessing its private key.

TRON uses the secp256k1 curve. The familiar Base58Check receiving representation has 34 characters and begins with T; the hexadecimal address representation instead includes the 41 version prefix.

How the public address is formed

Address derivation hashes the uncompressed public-key coordinates with Keccak-256, takes the final 20 bytes, and adds the 0x41 version byte. A checksum and Base58 encoding produce the wallet-facing string. The public-key serialization marker is not part of those coordinates.

A hexadecimal address and a hexadecimal private key are both text encodings of bytes, but their role and length differ. Do not substitute one into an API field intended for the other.

Why the service derives the result again

The worker checks the engine’s exported secret by independently deriving its address and verifying the pattern. This detects output inconsistency before reporting success. It does not by itself certify the engine’s entropy or prove that a secret remained private.

See the verification and hosting limits and how to recognize the exported fields. The algorithm explains address formation, while the wallet handles the subsequent signing workflow.

Explore the related mechanism

Sources and editorial method

The technical references below support the concepts discussed in this article. Examples and comparison worksheets are explanatory, not measured service benchmarks.

Read how these articles are prepared.

Read next

Generation2 min read

How TRON Vanity Address Generation Works

A worker searches private keys, derives their addresses and stops when an address matches your prefix or suffix. TRON Base58Check addresses begin with T.

Networks2 min read

TRON Networks and Account Activation

Generating an address does not activate an account on a network or submit a transaction. Key generation and on-chain account state are separate.