Avascriptions

If your website is on the scam list and you think that you are not a scammer, contact us. After you provide us with all the proof that you are in Crypto World with good intentions, we will delist you. Usually, you get in this category because you are hiding your team, you have a bad reputation(you are tricking, deceiving, scamming people), and you haven't got a written project whitepaper or is a shitty one....

Their Official site text:

ASIP-1: Smart Contract Avascription ASC-20 Transfers

This ASIP is LIVE

Specification

Incorporate one new smart contract event into the Avascriptions Protocol:

avascriptions_protocol_TransferASC20Token(

    address indexed from,

    address indexed to,

    string indexed ticker,

    uint256 amount

)

Event signature:

// "0x8cdf9e10a7b20e7a9c4e778fc3eb28f2766e438a9856a62eac39fbd2be98cbc2"

keccak256("avascriptions_protocol_TransferASC20Token(address,address,string,uint256)")

When a contract emits the avascriptions_protocol_TransferASC20Token event, it signifies that the protocol is registering a valid ASC-20 token transfer from the emitting contract to the recipient. This transfer is valid if the emitting contract possesses a sufficient number of corresponding tokens at the time of emitting the event, and the event is emitted in block number 38896000 or a later block.

In the case of multiple valid events, they should be sequentially processed based on their log index. Additionally, if the input data of the transaction also represents a valid transfer, this transfer will take precedence and be processed before any event-based transfers.

Rationale

ASC-20 Tokens are transferable to any address, enabling their ownership by smart contracts. However, the current limitation exists wherein smart contracts are unable to directly transfer or create these avascriptions themselves. This restriction hampers the development of protocol dApps relying on smart contracts, such as marketplaces. 

To address this, the proposal outlines a direct and cost-effective mechanism that enables smart contracts to carry out ASC-20 token transfers.

​

​ASIP-2: Safe Trustless Smart Contract ASC20-Token Escrow

Specification

Add a new smart contract event into the Avascriptions Protocol:

event avascriptions_protocol_TransferASC20TokenForListing(

    address indexed from,

    address indexed to,

    bytes32 id

);

Event signature:

// "0xe2750d6418e3719830794d3db788aa72febcd657bcd18ed8f1facdbf61a69a9a"

keccak256("avascriptions_protocol_TransferASC20TokenForListing(address,address,bytes32)")

When a contract emits this event, the protocol should register a valid ASC-20 tokens transfer from the emitting contract to recipient, provided:

from:  the address of the user who initiated the valid list.

to:  the address of the token recipient.

id: the avasription ID of the listing transaction.

After receiving this event, the indexer needs to retrieve corresponding information from the previously recorded list avascription. It's necessary to verify whether the contract address and the initiator's address match the previously recorded listing. If they match, the ASC-20 tokens are transferred according to the tick and amount information recorded in the listing.

Rationale 

ASIP-2 is primarily designed to facilitate secure escrowing of ASC-20 tokens by smart contracts.

The concept of smart contract escrow involves sending ASC-20 tokens to a smart contract, where the tokens are owned by the contract, yet the sender retains certain control over them—usually the ability to withdraw them or direct the smart contract to transfer them to another party.

Marketplaces represent a prevalent use case for smart contract ASC-20 token escrows. Presently, individuals cannot grant smart contracts permission to transfer their ASC-20 tokens. Therefore, to list an ASC-20 token for sale, it must first be transferred to the marketplace contract.

While the introduction of avascriptions_protocol_TransferASC20Token in ASIP-1 grants smart contracts the capability to send and receive ASC-20 tokens and function as marketplaces or escrows, ASIP-1 alone doesn't equip smart contracts with the necessary information to operate securely as escrows without additional assistance.

The aim of ASIP-2 is to empower smart contracts to overcome this limitation.

Verified Badge

Avascriptions Verified Badge

Avascriptions is dedicated to fostering a healthy and vibrant trading environment within the ASC-20 ecosystem. To recognize the achievements and contributions of specific inscriptions in trading, we have implemented the Avascriptions Marketplace Verified Badge System. This system awards different levels of badges to inscriptions based on their trading volume, symbolizing their contribution to the ASC-20 ecosystem. The following table outlines the various ASC-20 ecosystem contributors and their corresponding badges:

Title

Badge

Trading Volume (AVAX)

ASC20 Eco-Builder

Blue Badge

20,000

ASC20 Eco-Pioneer

Gold Badge

100,000

ASC20 Eco-Navigator

Red Badge

500,000

ASC20 Eco-Legend

Legendary Badge

2,500,000

This tiered badge system not only acknowledges the milestones in inscription trading but also aims to encourage the active development of more inscriptions within the ASC-20 ecosystem, helping to create a more active and dynamic ASC-20 trading environment.

Developer Service

Welcome to Avascriptions Developer Service documentation

Please read before using Avascriptions Open API Service.

Overview

Avascriptions Developer Service is open to community developers, allowing you to explore the world of Bitcoin and ordinals. You can deploy your own inscribing services, build wallet applications, develop browsers, and much more using the API.

Getting an API Key

To use the OpenAPI, please request an API_KEY from us by sending an email to [email protected] with the name and description of your project and the reason for using it. After we review it, we will send you the API_KEY.

When you obtain the API key, please add it to the request header with the Authorization format as follows:

curl --location 'http://open-api.avascriptions.com/v1/asc20/info' \

--header 'Authorization: Bearer YOUR_API_KEY' \

--header 'Content-Type: application/json' \

--data '{

    "ticker":"avav"

}'

​

​