๐—ฆ๐—ข๐—Ÿ๐—œ๐——๐—œ๐—ง๐—ฌ ๐—œ๐—ฆ ๐—ก๐—ข ๐—Ÿ๐—ข๐—ก๐—š๐—˜๐—ฅ ๐—–๐—ข๐—ก๐—™๐—œ๐—ก๐—˜๐—— ๐—ง๐—ข ๐—ข๐—ก๐—˜ ๐—•๐—Ÿ๐—ข๐—–๐—ž๐—–๐—›๐—”๐—œ๐—ก ๐—˜๐—ก๐—ฉ๐—œ๐—ฅ๐—ข๐—ก๐— ๐—˜๐—ก๐—ง.

Developers increasingly think in terms of portable smart-contract logic.

TRONโ€™s EVM-compatible TVM helps make that possible.

The familiar Solidity development model can be combined with TRON-specific infrastructure and resources.

๐—ง๐—›๐—˜ ๐—ฅ๐—˜๐—ฆ๐—จ๐—Ÿ๐—ง ๐—œ๐—ฆ ๐—” ๐——๐—˜๐—ฉ๐—˜๐—Ÿ๐—ข๐—ฃ๐—˜๐—ฅ ๐—ฃ๐—”๐—ง๐—› ๐—ง๐—›๐—”๐—ง ๐—–๐—ข๐— ๐—•๐—œ๐—ก๐—˜๐—ฆ ๐—™๐—”๐— ๐—œ๐—Ÿ๐—œ๐—”๐—ฅ๐—œ๐—ง๐—ฌ ๐—ช๐—œ๐—ง๐—› ๐—ก๐—˜๐—ง๐—ช๐—ข๐—ฅ-๐—ฆ๐—ฃ๐—˜๐—–๐—œ๐—™๐—œ๐—– ๐—–๐—”๐—ฃ๐—”๐—•๐—œ๐—Ÿ๐—œ๐—ง๐—œ๐—˜๐—ฆ.

A Solidity engineer can bring knowledge of contracts, interfaces, inheritance, events and application architecture.

Then the developer learns how those concepts operate within TRONโ€™s resource model and network infrastructure.

That is an important distinction.

Portability should not mean pretending all chains are identical.

It should mean reducing unnecessary barriers while allowing developers to take advantage of the destination network.

TRONโ€™s developer tooling reflects this philosophy.

Builders can work with familiar languages and frameworks while accessing TRON-specific APIs, resources and infrastructure.

๐—™๐—ข๐—ฅ ๐—ง๐—›๐—˜ ๐—ช๐—œ๐——๐—˜๐—ฅ ๐—ช๐—˜๐—•๐Ÿฏ ๐—˜๐—–๐—ข๐—ฆ๐—ฌ๐—ฆ๐—ง๐—˜๐— , ๐—ง๐—›๐—”๐—ง ๐— ๐—˜๐—”๐—ก๐—ฆ ๐— ๐—ข๐—ฅ๐—˜ ๐——๐—˜๐—ฉ๐—˜๐—Ÿ๐—ข๐—ฃ๐—˜๐—ฅ๐—ฆ ๐—–๐—”๐—ก ๐—˜๐—ซ๐—ฃ๐—Ÿ๐—ข๐—ฅ๐—˜ ๐—ง๐—ฅ๐—ข๐—ก ๐—ช๐—œ๐—ง๐—› ๐—Ÿ๐—˜๐—ฆ๐—ฆ ๐—™๐—ฅ๐—œ๐—–๐—ง๐—œ๐—ข๐—ก.

@TRON DAO
@Justin Sunๅญ™ๅฎ‡ๆ™จ
#TRONEcoStar