Deploy Contract to Tron

Deploy Contract to Tron

Tron has no Foundry support, so it does not go through deployContractToNetworks.sh or CREATE3 — it uses the TypeScript/TronWeb scripts in script/deploy/tron/, run from a separate fork repo, lifinance/contracts-tron. This skill is the Tron analog of /deploy-contract; use it whenever a target network is tron or tronshasta.

Why a separate repo

main in lifinance/contracts carries zero Tron branching by design — Tron USDT is a broken ERC-20, so the fix (a bypass in LibAsset.transferERC20 + a WithdrawablePeriphery re-route) lives only in the fork as a small, deliberate delta. Code flows one-way contracts → contracts-tron; deploy logs flow back the other way via a PR against upstream — never a direct commit to the fork. Full rationale, the exact fork delta, and the sync mechanism: docs/TronFork.md (read it if anything below is unclear on why, not just what).

Phase 0 — Locate the contracts-tron checkout

A normal session is rooted in contracts, but every step in this skill except Phase 5 must run from a contracts-tron working copy — a different clone, not a worktree of this repo (worktrees share one .git; forks don't).

1. Find it. Check, in order: $CONTRACTS_TRON_PATH if set, then a sibling directory next to the current repo root (../contracts-tron). Use the first that exists and has origin pointing at lifinance/contracts-tron.

2. Clone it if missing.

   gh repo clone lifinance/contracts-tron ../contracts-tron
   ln -s "$(git rev-parse --show-toplevel)/.env" ../contracts-tron/.env   # symlink, never copy — reuses this checkout's secrets
   

3. cd into it for the rest of Phase 0 through Phase 4. All commands below assume the working directory is the contracts-tron checkout.

Phase 0b — Preflight: branch, sync, delta

1. Confirm you're in contracts-tron, not contracts, and on main.

   git remote get-url origin | grep -q 'contracts-tron' || { echo "not in contracts-tron — abort"; exit 1; }
   git rev-parse --abbrev-ref HEAD   # must be main for a production deploy
   

2. Check the fork is synced for the contract you're about to deploy. If upstream contracts:main has changes to <Contract> (or to LibAsset/WithdrawablePeriphery) not yet in the fork, stop and merge the pending sync/upstream-YYYY-MM-DD PR first (or open one) — do not deploy stale code.

3. Verify the -tron delta survived the last sync. After any sync, confirm the bypass branch is still present:

   grep -q "TRON_USDT" src/Libraries/LibAsset.sol || { echo "Tron USDT bypass missing from LibAsset — sync broke the delta"; exit 1; }
   

   If missing, the sync merge dropped the fork's delta — resolve before deploying; do not deploy without the bypass on a chain where USDT is effectively all volume.