Open pyAndr3w opened 1 year ago
UPD: Currently, TIPs use Solidity code instead of ABI to describe interfaces, which further limits the potential pool of developers.
UPD: Currently, TIPs use Solidity code instead of ABI to describe interfaces, which further limits the potential pool of developers.
Included in the main message
,_ _
|\\_,-~/
/ _ _ | ,--.
( @ @ ) / ,-'
\ _T_/-._( (
/ `. \
| _ \ |
\ \ , / |
|| |-_\__ /
((_/`(____,-'
Let's create a separate improvement proposals repository in everscale-org and publish this proposal there. So that we migrate proposals from docs.everscale.network website to github.
Let's create a separate improvement proposals repository in everscale-org and publish this proposal there. So that we migrate proposals from docs.everscale.network website to github.
@elasticLove1 done
Hi, I would love to apply for this. I will complete the bounty in 2-3 hours. I am thinking of a bounty of $500 .
Hi, I would love to apply for this. I will complete the bounty in 2-3 hours. I am thinking of a bounty of $500 .
@pyAndr3w Please specify and better give an example of how it will be possible to use the result of this task?
@ilyar The result of completing the bounty will enable a more precise description of the standards and allow for the creation of custom implementations of smart contracts based on this standard.
An example of such can be found in a standards in the TON Blockchain, where they are accurately described, making it easy to create one's own implementation of a smart contract based on them.
https://github.com/ton-blockchain/TEPs/blob/master/text/0074-jettons-standard.md
Brief Introduction
This proposal aims to document all interfaces from the Everscale standards (TIPs) using the TL-B and ABI format. Currently, TIPs use Solidity code samples instead of ABI to describe interfaces, which further limits the potential pool of developers and can lead to problems in standards with compiler changes.
Goals
TL-B is a special format for describing data and interfaces for TVM blockchains. It is more flexible and accurate (and low-level) than the currently used ABI.
Describing standard interfaces in the TL-B format will allow the use of development tools that do not support ABI, and may also attract developers who use these tools to Everscale.
What's the result
Comprehensive TL-B schemes and ABIs for TIP-3.1, TIP-3.2, TIP-4.1, TIP-4.2, TIP-4.3, TIP-4.4 Everscale standard interfaces (TIPs), provided alongside existing ABI documentation.
Reward
TBD in EVER