Support for extra-currencies in local ton-http-api

In ton-http-api v2.0.53, which you can install by yourself on your server, support for extra-currencies and a number of other improvements have been made.

Recall that earlier support for extra-currencies was made in the public Toncenter V2 and Toncenter V3 APIs.

https://github.com/toncenter/ton-http-api/releases/tag/v2.0.53

Improved Metadata API

Last month we started providing metadata for Jettons and NFTs in the V3 API.

We are pleased to report a number of improvements:

— The metadata now enters the API in advance as soon as the token appears on the network. In the previous implementation, the metadata was indexed the first time the token was requested.

— Images and JSON are now proxied via toncenter.com. 3 image sizes are available, as well as original non-proxied urls for JSON and images. IPFS is supported.
Using a proxy increases security (you don't make requests to third-party hosting) and speed of downloading resources.

Now you can get all .ton and .t.me domains bound to a specific wallet using the new /dns/records method.

https://toncenter.com/api/v3/index.html#/dns/api_v3_get_dns_records

Now /api/v3/jetton/wallets supports the jetton_address array[string] field and /api/v3/nft/items supports the collection_address array[string] field.

You can request selected user jettons or NFTs, for example to display the most popular ones.

The peer_swaps field has been added to the Action API for complex swaps on DEXes. This field contains information about intermediate swaps (exchanges).

Emulation API now uses the same response models for transactions, messages, and actions as Index API v3.

Additionally, is_incomplete flag has been added to indicate if the emulated trace was truncated due to size limits.

Toncenter API supported hash of a normalized external message

API V3 (Index):

- hash_norm field added to the Message structure. If the field is not present, it means this message is not an external message, or the normalized hash_norm is equal to the regular hash.

- All methods with msg_hash parameter search also by normalized hash.

API V2:

- api/v2/sendBocReturnHash returns the normalized hash in addition to the normal hash.

Introducing the Pending API

Using this API you can track operations on the blockchain that have not yet completed.

As soon as an external message enters the blockchain, the Toncenter API Indexer notices it and builds a subsequent transaction series. Next, the action to be executed (e.g. "Swap on DeDust DEX") is recognized. As transactions are executed, the transaction series is re-indexed.

You can use this API to build responsive applications that respond quickly to user actions and show the progress of pending blockchain operations.

/api/v3/pendingActions

/api/v3/pendingTraces

MyTonWallet uses the Toncenter API

Another impressive example is how the popular non-custodial wallet MyTonWallet has enhanced the “Activity Feed” tab with user activity history using Toncenter's Actions API.

https://tg-me.sbs/MyTonWalletEn/227

The Emulation API now supports the optional mc_block_seqno parameter. You can emulate a transaction chain for a specific masterchain block. Only recent masterchain blocks (~7 days) are supported.

Instant appearance of pending transactions

Pending actions and transactions are now instantly available in the Pending API after message sending via Toncenter API.

New actions supported in Toncenter API

Multisig V2:

— Multisig order creation (multisig_create_order)

— Order approval (multisig_approve)

— Order execution (multisig_execute)

Vesting:

— Message sending (vesting_send_message)

— Adding to the whitelist (vesting_add_whitelist)

Evaa:

— Supply (evaa_supply)

— Withdraw (evaa_withdraw)

— Liquidation (evaa_liquidate)

Jvault:

— Stake (jvault_stake)

— Unstake (jvault_unstake)

— Claim (jvault_claim)

In addition, the current actions have been improved:

— Supported NFT discovery message (nft_discovery).

— A definition of unsuccessful TON transfer (ton_transfer) and Jetton transfer (jetton_transfer) has been added for cases where the execution failed on the sender's account (traces with a single transaction by an external message).

— Improved support for Jetton Mint action: added support for mints that run with opcode 0x00000015. Previously, only 0x642b7d07 was supported.

— Improved support for liquid staking (@stakee, Tonstakers) actions: added tokens_minted and tokens_burnt fields to deposit/withdrawal operations. Improved the method of calculating how many TON a user receives for burning tokens upon withdrawal. Added the definition of the pool address when burning NFT vouchers (deferred deposit withdrawal).

https://toncenter.com/api/v3/index.html#/actions/api_v3_get_actions

Versioning in the Actions API

We introduce versioning for actions in https://toncenter.com/api/v3/.

Specify the "supported_action_types" in methods api/v3/traces and api/v3/actions to desired version of action types and get the actions of supported types or set it to "latest" to get all newest actions from API v3.

Clients (e.g., wallet or blockchain explorers applications) can use it to receive the only actions that they support.

Version "v1":
— Basic: call_contract, contract_deploy, ton_transfer, tick_tock
— Jettons: jetton_burn, jetton_transfer, jetton_mint
— NFTs: nft_mint, nft_transfer, auction_bid
— DEXs: jetton_swap, dex_deposit_liquidity, dex_withdraw_liquidity
— Liquid staking: stake_deposit, stake_withdrawal, stake_withdrawal_request
— Elections: election_deposit, election_recover
— TON DNS: change_dns, delete_dns, renew_dns
— Subsctiptions: subscribe, unsubscribe

Version "v2":
— Multisig: multisig_create_order, multisig_approve, multisig_execute
— Vesting: vesting_send_message, vesting_add_whitelist
— EVAA: evaa_supply, evaa_withdraw, evaa_liquidate
— Jvault: jvault_stake, jvault_unstake, jvault_claim
— NFTs: nft_discovery

Version "latest": returns all newest action types.

Emulation and Pending API Updates

— In the Emulation API and Pending API, transaction chains are now emulated more accurately.
Previously, all transactions in a chain were emulated for a single block. Now, the emulator distributes transactions across different blocks (for example, an inter-shard message will occupy several blocks).
This allows for more accurate prediction of transaction order and results, as well as approximate timestamps and lt values for transactions, which makes it possible to estimate approximate execution times.

— Emulation API: added address_book and metadata.

ton-http-api 2.0.54

Normalized hash of external messages supported.

https://github.com/toncenter/ton-http-api

DeDust DEX now provides an instant link to pending action

After the exchange, you will immediately receive a link to the blockchain explorer, which you can share or use to track the transaction.

Please note that the DeDust DEX user interface does not block you, and you can make a new exchange even if the previous one is still in progress.

https://dedust.io/swap