MMashDiv

Installing the Tron addon

Activate the licence, enable the chain, set the four environment variables, create and fund the master wallet, import your TRC-20 tokens, then prove it with the diagnostics probe.

11 min readUpdated 26 August 2026install, licence, trongrid, master-wallet, diagnostics

Tron is gated three times. The licence must be activated, the addon code must be present on the server, and the chain must be switched on. All three are checked, they are checked separately, and two of them produce the same unhelpful message when they fail. Work through them in order.

Everything on this page assumes Ecosystem is already installed and its vault is unlocked. Creating a Tron wallet encrypts key material immediately; a locked vault fails the operation partway through.

Before you begin

  • A working Bicrypto install with Ecosystem enabled and its vault unlocked
  • The Tron addon purchased and its licence activatable on this machine
  • Shell access to the project root — the .env edits have no admin-panel equivalent
  • A TronGrid account, for the mainnet API key
  • TRX to fund the master wallet, on the network you are configuring

1. Activate the licence and install the release

  1. Open the Extension Manager. Go to Admin → System → Extension Manager — the page heading is Add-ons & Integrations. On the Blockchains tab (or by searching for Tron) find the Tron Blockchain for Ecosystem Addon card — product ID 54577641 — and click it. Until its licence is activated the card reads Activate and its switch is disabled, with the tooltip Activate license first.

    1. The Tron card — click it to open the product page
    2. Its switch stays disabled until the licence is activated

  2. Activate the licence. On the product page press Activate License. Paste the purchase code from your MashDiv dashboard, optionally an email address for update notifications, and press Activate License. The screen confirms License Activated! and sends you back to the product page a couple of seconds later. If the server has no outbound access, use the License File tab on the same screen instead: download the licence certificate from your MashDiv dashboard, place it as license.txt in the /lic folder at the project root, and press the button on that tab.

    Activation writes lic/54577641.lic — an encrypted, machine-bound file, and the gate the chain service checks before it will initialise. 54577641 is Tron's product ID.

    1. Paste the purchase code here
    2. Activate License — then wait for the redirect back to the product page
    3. The offline route, for a server with no outbound HTTPS

  3. Install the release. Back on the product page, now licensed, the Overview tab has a release panel. If it offers Install v…, press it; if it says Up to date on a product you have only just licensed, press Check for Updates once, then install whatever it offers. The Releases tab holds the notes for the version you are being offered — read them first.

    Install is what puts the chain service on the server: it downloads the release, verifies it and extracts it over the project root, landing backend/src/blockchains/tron.ts and its compiled counterpart in backend/dist. Ecosystem loads that file through a safe import, so an install that never received it reports "Chain service installed: no" in the diagnostics rather than failing at boot. Install runs no migrations, builds nothing and restarts nothing, so finish it from the project root:

    pnpm updator

    That is the finalise chain — stop, dependencies, schema, seed data, frontend build, start — and its seed-data pass is also what makes the chains appear under Admin → Ecosystem → Blockchains if they have never been listed on this install. If the release panel still says Up to date after the check, the files already on the server are current — move on.

    1. Check for Updates, then Install v… when it is offered
    2. Releases — the notes for the version you are about to install
    3. The Enabled switch — section 2, not yet

2. Enable the chain

Switch Tron on. The Enabled switch sits in the product page heading, and the switch on the Tron card — Blockchains tab of the Extension Manager — does the same job; both are usable now that the licence is verified. Enabling is what switches the chain on for the Ecosystem addon. Admin → Ecosystem → Blockchains shows the same chains with their product IDs from the Ecosystem side, with its own enable control and the Requirements view the verify step uses.

PUT/api/admin/ecosystem/blockchain/{id}/statuspermission: edit.ecosystem.blockchain
Enables or disables a blockchain by product ID. Refuses with 403 if the licence file is absent.

The licence check happens before the write, so a 403 here means activation never completed — go back to step 2 of the section above rather than pressing the switch again.

The licence and the enabled state are then read together by the chain service on first use, and the result is cached for five minutes. A chain you just enabled can still report itself inactive for a few minutes; the service re-checks its own status on the next call once it has seen an inactive result, so it recovers without a restart.

3. Set the environment variables

Add these to the project root .env. None of them appear in .env.example.

TRON_NETWORK="mainnet"
TRON_MAINNET_RPC="https://api.trongrid.io"
TRON_API_KEY="your-trongrid-api-key"
TRON_NETWORKtype: stringdefault: mainnet
Which Tron network the service runs against. Accepts mainnet, shasta or nile and nothing else — any other value throws while the service is being constructed and kills every Tron flow on the install.
TRON_MAINNET_RPCtype: urldefault: https://api.trongrid.io
Full-host URL used as the TronWeb fullHost and as the base for every direct REST call. Defaults to the public TronGrid host.
TRON_API_KEYtype: secret
TronGrid API key, sent as the TRON-PRO-API-KEY header on every request. Effectively mandatory on mainnet.

The RPC variable is per network and only the selected one is read. TRON_SHASTA_RPC defaults to https://api.shasta.trongrid.io and TRON_NILE_RPC to https://api.nileex.io. Full details in the environment reference.

The service resolves its host from TRON_NETWORK inside its constructor. An unrecognised value throws there, so the singleton is never built and every call site — deposit monitor, withdrawal queue, master wallet creation, admin balance lookups — fails with "Tron service not available". The diagnostics page reports this explicitly; nothing else does.

Why the API key matters more than it looks

Both deposit endpoints are plain REST calls to TronGrid, and the deposit monitor polls them every 30 seconds per watched address. Without a key you are on the anonymous quota.

The monitor handles this gracefully at first — a 429 doubles its interval, a 403 triples it, up to a five-minute ceiling. But after ten consecutive errors it logs "Max consecutive errors reached" and deletes its own polling loop. Deposits on that address then stop being detected until the user reopens the deposit page or the background scanner reaches it.

Restart the backend after editing .env. The service is a singleton constructed on first use, and nothing re-reads these values.

pm2 restart backend

4. Create and fund the master wallet

POST/api/admin/ecosystem/wallet/masterpermission: create.ecosystem.master.wallet
Generates, encrypts and stores a master wallet for a chain

Admin → Ecosystem → Wallets → Master Wallets, choose TRON. One per chain is enforced; a second attempt returns 409.

  1. Fund it with TRX and watch this balance

The Tron master wallet is generated by the chain service itself — a fresh BIP-39 mnemonic and a key at m/44'/195'/0'/0/0, encrypted with the Ecosystem vault key and stored in ecosystem_master_wallet.data. It is not an HD parent. Unlike the EVM chains, no user address is derived from it, so its role here is narrower than the master wallet guide describes for EVM: on Tron it is a gas tank and nothing else.

Fund it with TRX. How much depends entirely on your TRC-20 volume and whether you stake — see Energy and bandwidth. Start with enough for a few hundred transfers and watch what it actually burns.

A Tron install with an empty master wallet still pays out native TRX perfectly well. Only TRC-20 payouts stall. The symptom is selective — USDT withdrawals sit in the queue while TRX ones complete — which reads like a token configuration problem and is not.

5. Import your tokens

Tron token contracts are imported, never deployed. The deployment endpoint supports EVM chains and Solana only.

POST/api/admin/ecosystem/token/importpermission: create.ecosystem.token
Registers an existing on-chain token contract as an Ecosystem token

Admin → Ecosystem → Tokens → Import. Supply chain TRON, the contract address, the currency symbol, decimals and precision. Native TRX is imported with contractType: NATIVE and no contract address.

Get decimals right. It is used to convert raw on-chain integers into a balance, to compute the deposit dust floor, and to convert a withdrawal amount back into the smallest unit. A wrong value does not error — it credits and debits the wrong number.

Set the token's fee object deliberately. It is denominated in the token, it is the only thing the user is charged, and it is where you recover the TRX the master wallet burns on their behalf. The network cost is never added to a customer's debit.

6. Verify

GET/api/admin/ecosystem/blockchain/requirementspermission: view.ecosystem.blockchain
Full per-chain requirements report — every variable the runtime reads and every non-environment prerequisite
POST/api/admin/ecosystem/blockchain/requirements/testpermission: view.ecosystem.blockchain
Runs live read-only probes against the chain and returns per-flow readiness

Admin → Ecosystem → Blockchains → Requirements, select Tron, run the test. It performs four checks:

Check What it proves
Network configured TRON_NETWORK resolves to a real host and that host is a valid http(s) URL
Node liveness POST /wallet/getnowblock returns a block height
TronGrid REST + API key The account-transactions endpoint answers 200 — this is the exact path deposit polling uses
Chain service installed / licence + enable switch The addon files are present and the licence and enable gates both pass
  1. Select Tron and run the test

The REST check passes with a warning when there is no API key: it works, and it will not keep working under load. Treat that warning as a failure on a production install.

Readiness is then reported per flow — deposits and withdrawals — and the overall result is a pass only when every check passed and no flow is broken. An RPC that answers is not a pass while the vault is locked or the master wallet is missing, because a customer still cannot get their money out.

Finally, open the deposit page for a Tron-backed currency as a real user. You should get a base58 address starting with T. Send a small amount, watch it credit, and withdraw it back out. Do this on Shasta or Nile first if you can — set TRON_NETWORK="shasta", restart, and use a public faucet for test TRX.

Tron addresses are the same format on every network, and the platform's token-network guard treats Tron as network-agnostic, so nothing warns you. After changing TRON_NETWORK, existing addresses are still issued and still look correct — they are simply being watched on a chain where the user's coins are not. Decide the network before you take real deposits.