Integration FAQ

Questions

Indexer and SDK

SDK

Github - https://github.com/cryptoalgebra/tonco-sdk/

Examples and references

Github - https://github.com/cryptoalgebra/tonco-demo

Mainnet

Testnet

Retrieve pool data

The best way to get all the pools and general information about them is to use our indexer.

Indexer is critical for our system, and we keep it highly available, however, we encourage caching the pool list.

Alternatively, if you don’t want to depend on our infrastructure, you can rescan the blockchain in search of messages POOL_INIT sent by the router

Getting pool APR

For information about the APR of the pool in farming, you need to refer to the URL:

GET api-farming.tonco.io/apr?pool=<pool address>

The answer has “apr” as the base apr and an array of farmings. Farming is considered active if rewardsLeft is not equal to zero. Farming has a property - multiplier, it is a coefficient that denotes how many times farming increases the base apr.

APRfinal=APRifarming_multiplieriAPR_{final} = APR \cdot \sum_i farming\_multiplier _i

In most cases, a pool has only one active farming, but it is possible that it will have several in the future.

Example

Request:

Response:

Retrieving positions

There are several ways to get all positions and positions per person.

Getting positions by index

If you want to manually scan and enumerate all the positions for a particular pool you can first use the method getPoolStateAndConfiguration and get "Number of active NFT positions" from it. Then iterate from 0 as the index of NFT and call get_nft_address_by_index()

Getting positions with NFT API's

Position NFT is a real NFT so you can use TonConsole Api and TonCenter API to get NFT address info and metadata. For position parameters, however, you would need to call the NFT get-method - GetPositionInfo()

Getting positions from TONCO indexer

Please address the GraphQL schema documents for more details - GraphQL Schema Getting collected fees - https://docs.tonco.io/technical-reference/indexer#position-data Here is a small snippet that uses our indexer\

Retrieving position data using SDK

Below is an example of how to retrieve data for a specific liquidity position using the Position entity from the SDK. The Position instance calculates the current token amounts based on liquidity and price range, while accumulated fees can be fetched directly from the smart contract via the getCollectedFees method.

Forming messages for the swap

Sending swap can be done with our SDK - https://github.com/cryptoalgebra/tonco-sdk

An example of swap preparation can be found here - https://github.com/cryptoalgebra/tonco-sdk/blob/36eb0d7feadfcdcd60583ebe4098eb25fcc02591/src/classes/PoolMessageManager.ts#L649

A swap request is created as a payload in the jetton transfer and is sent to the router. The general logic of the input parameters can be derived from the SDK example above and the doc of the pool swap message POOLV3_SWAP

Swap estimate

This question depends on your requirements, limitations, and infrastructure of choice. Here are 4 options

  1. The simplest and most precise way is to call the pool contract get method - https://docs.tonco.io/technical-reference/contracts/pool#getswapestimategas

  2. If you have ever implemented integration with other Algebra EVM projects written in your language of choice - then the output simulation can be bit-precise

  3. You can use our Typescript implementation of user-side swap simulation using TONCO DEX SDK). It includes 2 ways to estimate a swap: on-chain and off-chain. Before actual blockchain execution please check that the estimates you made with TS match the contract call.

a) Estimate Swap 1 TON -> USDT Example (on-chain)

b) Estimate Swap 1 TON -> USDT Example (off-chain)

  1. You can use our Kotlin implementation of user-side swap simulation.

Marking transactions for referral tracking

With TONCO v1 It is possible to mark transactions to be able to index them for needs of referral tracking

  • You have 64 bits of query_id at your disposal. We don't alter it and copy it in the outgoing messages

  • A swap request is created as a payload for TRANSFER_NOTIFICATION. The current version of the swap request - Swap Cell Building uses at most 850bits and 1ref. In the current version, all remaining cell part is ignored. However, to be future-proof proof we recommend to occupy second maybe_ref (1 ref and 1 bit). This cell starts with 4 byte of your service id and any content you need as remaining data.

Forming Messages for Mint

Messages can be constructed using our SDK (@toncodex/sdk@mainnet) The source code for message construction can be found here: (https://github.com/cryptoalgebra/tonco-sdk/blob/36eb0d7feadfcdcd60583ebe4098eb25fcc02591/src/classes/PoolMessageManager.ts#L141).

Example: Minting a Position in the TON/USDT Pool Below is an example of mint preparation for the TON/USDT pool within the price range [3.1, 6.5], based on an input amount of 1 TON.

⚠️ Important ⚠️: The validation step inside the example is crucial. Skipping it may result in a loss of funds.

You can find it the code here - https://github.com/cryptoalgebra/tonco-demo/blob/main/sdk_examples/mint/message/createMintMessage.ts

Last updated