Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
What is the approach to adopt for supporting dApp to dApp calls/communications?


I'm considering to move my projects from another blockchain to TON but I still don't understand how to handle the asynchronous part.

One of my projects is a NFT marketplace with 4 dApps: artists, primary market, secondary market, and gateway.
Each dApp depends on data query to each other and some do dApp to dApp calls that changes states on each side.

With TON being non-atomic, without dApp to dApp calls (since they would be asynchronous), I struggle to understand how developers tackle this? Does it mean the best approach is to gather all dApps in one? Are there other options I can study?

Votes Newest


First of all, messages in TVM (TON Network) don't allow us to access the state data of other contracts in the same way we do in Solidity (EVM).

This is because the data for a contract can change dynamically in an asynchronous chain. The only way to access data from a smart contract is through message calls, which means asking the contract to send the data through itself.

More information here:

Posted 10 months ago
Edited 9 months ago
Howard Peng
10 × 1 Administrator

Thank you for the link, look like it have interesting info, i'll take the time to read it and come back if needed :)

Chris   10 months ago Report
1 Answer
10 months ago
9 months ago