IERC Document
  • 📜IERC Protocol
    • Overview
    • Why use IERC 20?
    • Use Cases and Features
    • Roadmap
  • 🌠User's Guide
    • Explore IERC-20
    • How To Mine
    • How To Deploy
    • How To Transfer
    • Market
      • How To Buy
      • How To List
      • How To Bulk Buy
  • 🔁IERC Swap
    • How to IERC Swap
    • How to add Liquidity
    • Liquidity providers (LPs)
    • FAQ
  • 🔥New Features
    • PoW&DPoS
    • 🔨How to PoW&DPoS Mining
    • IERC PoW
      • Phrase I: PoW - Base
      • ⛏️How to Mine
      • Phase II: PoW - Advanced
      • 🤝How to Participate
    • IERC DPoS
      • 📒Staking Rules
      • 💦How to Stake
      • 🎁Rewards Program
    • Tokenomics
    • FAQ
  • 💻Devs
    • IERC-20
      • Deploy
      • Mint
      • Transfer
      • Freeze Sell
      • Proxy Transfer
      • Stake
      • Unstake
      • More
    • DINX EVM (beta)
      • RPC
      • Add Token
      • Explorer
      • API
  • 🤵Ambassador Program
  • ❓FAQ
Powered by GitBook
On this page
  • Workc & MintHash
  • Deploy & Mint
  1. New Features
  2. IERC PoW

Phrase I: PoW - Base

PreviousIERC PoWNextHow to Mine

Last updated 1 year ago

Workc & MintHash

IERC PoW builds upon the IERC native protocol by introducing the "workc" field to describe the mining output difficulty. Only Mint Transaction Hashes that meet the workc format are recognized by indexers. All indexers strictly adhere to this rule.

Apart from workc, no other complex or unreasonable concepts or changes have been introduced.

Workc: Describes the mining output difficulty. Only transactions with hash headers meeting this rule will be included.

MintHash: Refers to the transaction hash that complies with the .

For instance, if you want to mine ierc-m4 inscriptions, your Mint Transaction Hash must start with "0x0000".

const regex = /^0x0000[a-fA-F0-9]{36}$/;
const isValidity = regex.test(mintHash)

// isValidity => true : 0x0000edd685500ca4c1c261e15a3267d364a4a9548966d45a70085c2cfba534b
// isValidity => false : 0xe6cc5edd685500ca4c1c261e15a3267d364a4a9548966d45a70085c2cfba534b
// isValidity => true : 0x0000000685500ca4c1c261e15a3267d364a4a9548966d45a70085c2cfba534b

Deploy & Mint

Before proceeding, you need to understand the deployment mechanism of IERC20 inscriptions through the documentation.

Based on IERC20, you need to add a field called workc in the methods to explain the mining difficulty.

Like this:

// deploy; send 0eth from self to 0x0000000000000000000000000000000000000000;
{    
	"p":"ierc-20", //protocol name: ierc20 | terc-20    
	"op":"deploy", //operation: deploy/mint/transfer/freeze_sell/proxy_transfer    
	"tick":"ierc-m4", //token tick, can't be repeatable, case insensitive.    
	"workc":"0x0000",    
	"max":"21000000", //max supply    
	"lim":"1000", //limit for each mint    
	"wlim":"10000", //limit for each address can maximum mint, address balance < deploy.wlim (Before mint, please do not receive transfers from others, transfers are also counted as balance)    
	"dec":"8", //decimal for minimum divie    
	"nonce":"0", //increasing interger
}

If you want to mint inscriptions, the data format follows the same mechanism as regular IERC20 inscriptions. Just ensure that your mintHash complies with workc.

We have deployed two sets of PoW experience inscriptions on the Ethereum mainnet:

⚠️ Notice: These inscriptions are not official targets in any form, and any market activities associated with them are unrelated to the official project.

  • ierc-m4: Requires a mining threshold difficulty of "0x0000".

  • Ierc-m5: Requires a mining threshold difficulty of "0x00000".

🔥
Mint operation in IERC Protocols