Changes

• Refactor some code to optimize the TVM performance. VM #3482 #3484 #3485

Notices

Forced upgrade

New Features

Core

• TICP-Optimized-PBFT Introduce new TPOS consensus to speed up the confirmation of the block. #3082
• TIP-128 Add a new node type: Lite Fullnode that can dramatically reduce the data volume of the node. #3031
• TIP-127 Add new system contracts to support the exchange of token, including TRX and TRC-10. #3302

TVM

• TIP-174 Add 1 new instruction (chainid) in TVM to distinguish the chains. #3351
  • CHAINID: used to get the genesis block id of the current chain.
• TIP-175 Add 1 new instruction (selfbalance) in TVM to improve security. #3351
  • SELFBALANCE: used to get the balance of the current address.
• TIP-176 Add altbn128 operation energy reduction in TVM. #3351

API

• Add some APIs to get node metrics information. #3350
• Add HTTP&gRPC APIs for pBFT. #3082
• Add a new API GetContractInfo to get contract runtime code information. #3351
• TIP-127 Add the APIs to support the exchange of token. #3302
  • MarketSellAsset: Create a market order
  • MarketCancelOrder: Cancel the order
  • GetMarketOrderByAccount: Get all orders for the account
  • GetMarketPairList: Get all trading pairs
  • GetMarketOrderListByPair: Get all orders for the trading pair
  • GetMarketPriceByPair: Get all prices for the trading pair
  • GetMarketOrderById: Get order by id

Changes

• TIP-127 Add market order detail into transactionInfo. #3302
• Update docker deployment. #3330
• Optimize TVM instruction CREATE2. #3351
• Fix encoding problem in HTTP API when visible is set to true. #3469
• Fix the event filter config not work. #3401
• Fix an issue in the type DataWord. #3472

Changes

Fix an issue in the type DataWord. Updates are available here.

Release Note:

Notices

Forced upgrade.

Changes

• Improves the java-Tron upgrade mechanism and achieves more efficient decentralized governance (#3314).

Release 4.0 has implemented the shielded TRC-20 contract, which can hide the source address, destination address, and the token amount for TRC-20 transactions and provide users with better privacy. The shielded TRC-20 contract has three core functions: mint, transfer and burn. mint is used to transform the public TRC-20 token to shielded token; transfer is used for shielded token transactions; burn is used to transform the shielded token back to the public TRC-20 token. To support the shielded TRC-20 contract, four new zero-knowledge instructions (verifyMintProof, verifyTransferProof, verifyBurnProof and pedersenHash) are added in TVM, which make it convenient to provide privacy for arbitrary TRC-20 contract.

Notices

Forced upgrade

New features

• Add 4 new instructions (verifyMintProof, verifyTransferProof, verifyBurnProof and pedersenHash) in TVM to support TRC20 shielded transactions based on zk-SNARKs (#3172).

  • verifyMintProof: used to validate the zero-knowledge proof for mint function.
  • verifyTransferProof: used to validate the zero-knowledge proof for transfer function.
  • verifyBurnProof: used to validate the zero-knowledge proof for burn function.
  • pedersenHash: used to compute the Pedersen hash.

• Update the initial parameters of zk-SNARKs scheme generated by the MPC Torch (#3210).

• Add the APIs to support shielded TRC-20 contract transaction (#3172).

  1. Create shielded contract parameters

  rpc CreateShieldedContractParameters (PrivateShieldedTRC20Parameters) returns (ShieldedTRC20Parameters) {}

  2. Create shielded contract parameters without ask

  rpc CreateShieldedContractParametersWithoutAsk (PrivateShieldedTRC20ParametersWithoutAsk) returns (ShieldedTRC20Parameters) {}

  3. Scan shielded TRC20 notes by ivk

  rpc ScanShieldedTRC20NotesByIvk (IvkDecryptTRC20Parameters) returns (DecryptNotesTRC20) {}

  4. Scan shielded TRC20 notes by ovk

  rpc ScanShieldedTRC20NotesByOvk (OvkDecryptTRC20Parameters) returns (DecryptNotesTRC20) {}

  5. Check if the shielded TRC20 note is spent

  rpc IsShieldedTRC20ContractNoteSpent (NfTRC20Parameters) returns (NullifierResult) {}

  6. Get the trigger input for the shielded TRC20 contract

    rpc GetTriggerInputForShieldedTRC20Contract (ShieldedTRC20TriggerContractParameters) returns (BytesMessage) {}

• Support the ovk to scan the transparent output of burn transaction (#3203).

• Support the burn transaction with zero or one shielded output (#3224).

• Add data field in transaction log trigger class for future memo note (#3200).

The following TIPs are implemented in this release:

• TIP-135: Shielded TRC-20 contract standards, guarantee the privacy of the shielded transfer of TRC-20 tokens.
• TIP-137: Implements three zero-knowledge proof instructions in TVM to support the shielded TRC-20 contract (#3172).
• TIP-138: Implements the Pedersen hash computation instruction in TVM to support the shielded TRC-20 contract (#3172).

Changes

• Check if null before getInstance when get transaction info from DB to fix exception of getTransactioninfoByBlkNum (#3165).

Notices

Non-mandatory upgrade

Changes

• (#2533) Several independent modules are separated, including consensus module, crypto module, chainbase module, framework module, protocol module and actuator module, which makes decoupled code easier to be extended and enable developers to implement custom logic freely.

• (#2947) Extend solidity event subscription trigger, user can get the event which is solidified.

• (#2958) Add gettransactioninfobyblocknumAPI including HTTP and GRPC, user can get the list of transaction information by block number.

• (#2352) Add broadcasthex API for HTTP, the user can broadcast the hex of the transaction.

Instructions

• How to get the list of transaction information in a specific block: TRON Documentation

• How to broadcast the hex of the transaction: TRON Documentation

Notices

Forced upgrade.

Changes

• (#2766) Fix HTTP API updateBrokerage to support base58 encoding.
• (#2813) Extend the allowed instruction sets for off-chain smart contract call, including LOGn, SSTORE,
  CREATE, CREATE2, STATICCALL, SUICIDE instructions.
• (#2824) Remove the functionality “Forbid transfer asset to a smart contract using TransferContract and TransferAssetContract” from proposal 32 and implement it with a new proposal 35.