Introducing the upcoming splitting solution for POLS, based on the PRC20s protocol designed by
@PolsMarket
.
1/ This splitting solution allows POLS inscriptions to be divided into any desired number of transferable Inscriptions while retaining the original POLS Inscription.
1/ For the comprehensive set of Index rules for
#Pols
, please refer to:
The index transfer rules for
#Pols
are identical to the index transfer rules for Eths. For single inscription transfer, calldata is used to pass the inscription ID.
4/ To address this, we have designed a secure and scalable Inscription token conversion protocol that enables centralized exchanges to list inscription tokens without any additional workload.
We'll continue to explore DeFi protocols based on Inscriptions alongside your support.
3/ Currently, there is a diverse range of protocols for Ethereum-based Inscriptions, making it challenging for exchanges to integrate Inscription tokens.
2/ Moreover, POLS Inscriptions can be converted into PRC20 tokens under the verification of multiple trusted indexers (relayers). This provides convenience for the listing of POLS on exchanges.
2/ For multiple Inscription transfer, calldata is used to concatenate the Inscription IDs, similar to Ethscriptions esip-5.
In-contract Inscription transfer follows esip-1 and esip-2.
(4/5) The transfer protocol will take effect on the Polygon Mainnet at block
#50140000
.
Our Index result is consistent with dune data here:
#PolsMarket
#POLS
(5/5) ๐โโ๏ธIf you're experiencing any indexing issues, please contact us immediately via Discord: .
Before and after the transaction, please verify the validity of the transaction of Inscription on multiple platforms.
#PolsMarket
#POLS
(1/5)
#POLS
does not support batch minting of inscriptions in contracts, but it supports the generation of inscriptions from transfer transactions with "From != To" and "From = To".
(2/5) The rules for transferring and batch transferring Inscriptions follow the same rules as Ethscriptions, which means transferring by Inscription ID. But contract event transfers are not supported.
Please refer to for the protocol for batch transfers.