Pundi
Pundi AIPundi X
  • 🤖Pundi AI overview
  • 🈁Pundi AI Data Platform
    • Data stakeholders
    • Data Labelling
    • Pundi AI Data Platform (Alpha Testnet) - User Guide
    • FAQ
  • 🦾Pundi AIFX Omnilayer
    • Pundi AIFX
    • Installation Pundi AIFX
    • Setup Node
      • Full node with Binaries
      • Full node with Docker
      • Snapshot Guide
      • Node Monitoring Device
    • Validators
      • Validator Overview
      • Setting Up a Validator for Pundi AIFX
      • Validator Recovery
      • Validator FAQ
      • Validator Security Notice
      • Migration Best Practices
      • Transfer Validator Permissions
    • Delegators
      • Delegators FAQ
      • Delegator CLI Guide
      • Delegator Security Notice
    • Pundi AIFX Tutorials
      • Pundi AIFX CLI Commands
      • Cloud Setup
      • Testnet faucet
      • Ledger Integration for fxcored
      • Sentry Nodes
      • Account Migration Guide (CLI)
    • Upgrade Instructions
      • Cosmovisor Upgrade Guide v8.5.x
        • Cosmovisor Integration - Binaries
        • Cosmovisor Integration - Docker
      • Manual Upgrade Guide v8.5.x
        • Binaries - Upgrading Your Node
        • Docker - Upgrading Your Node
      • Upgrade Versions
        • v2.2.0 Upgrade Instructions
        • v3.1.0 Upgrade Instructions
        • v4.2.1 Upgrade Instructions
        • v5.0.0 Upgrade Instructions
      • Upgrade FAQ
    • Deploying on Pundi AIFX EVM
      • Products
      • MetaMask
        • Download and Install MetaMask
        • Add Network
        • Configure Custom Tokens
        • Create and Import Accounts
      • Connect Wallet to Dapps
        • Connect using MetaMask
        • Connect using Pundi Wallet (Wallet Connect)
      • With Remix
      • With Truffle
      • With Hardhat
      • Cross-Chain Bridges
        • Bridging Tokens from other networks
        • Pundi Gravity Bridge
    • DApps and Infra
      • Margin X Swap
      • Pundi Wallet
      • PundiScan
      • Baklava Space
      • Safe Multisig
      • PortfolioX
      • Token Factory
    • Developers
      • Pundi AIFX Network
      • Pundi AIFX Modules
      • Pundi AIFX JSON RPC
      • Pundi AIFX REST API
      • Web3 JSON RPC
        • JSON RPC Server
        • Namespaces
        • JSON RPC Methods
        • Events
      • Support Leap
      • Third Party Price Oracles
      • Contract Deployments
      • Pundi AIFX Cross Chain
        • sendToFx
        • f(x)Core
        • ibc
        • Target
      • Precompiled Contracts
        • CrossChain Precompiled
        • Staking-V2 Precompiled
      • Pundi AIFX SDKs
        • Python SDK
        • JavaScript SDK
      • Contract Monitoring
    • Pundi X Chain (under Pundi X)
      • Getting Started
        • Install Pundi X (PundiXChain)
        • Setup Node
          • Full node with Binaries
          • Full node with Docker
          • Snapshot Guide
          • Node Monitoring Device
          • Node Peers
      • Validators
        • Validator Overview
        • Setting Up a Validator for PundiXChain
        • Validator Recovery
        • Validator FAQ
        • Validator Security
        • Sentry Nodes
      • Delegators
        • Delegator FAQ
        • Delegator Overview
        • Delegator CLI Guide
      • Pundi X Tutorials
        • Pundi X CLI Guide
        • Ledger Integration for pundixd
        • Testnet Faucet
        • Cloud Setup
      • Upgrade Instructions
        • Cosmovisor Integration - Binaries
        • Cosmovisor Integration - Docker
        • Support keplr
      • Developers
        • Pundi X Network
        • Pundi X Protobuf
        • Pundi X gRPC & REST
        • Pundi X JSON RPC
        • Pundi X Cross Chain
          • ibc
  • 👛PURSE+
    • Purse Box
      • How many NFTs can I mint?
      • Minting (Etherscan)
      • Minting (Pursetoken.com)
    • PURSE+
      • Links
    • Bridging
      • BSC -> Ethereum
    • Protocols
      • LP Restaking Farms
        • How to Use Farms
        • Contract on BscScan
      • PURSE Staking
      • PURSE Staking Rewards
        • Campaigns
      • PURSE Retroactive Rewards
        • Campaigns
    • Contracts
      • Ethereum
      • Binance
      • Function X
    • IBC
      • PUNDIX Chain
    • PURSE Token
      • Background
      • ERC404 intro
      • Accounting of Balances
      • Minting PURSE NFT(s)
      • Transferring PURSE
      • Maintaining PURSE NFT(s)
      • NFTs in Queue
      • Token IDs
  • 🎡Pundi AI MM Agent
    • Why Market Making
    • Traditional MM vs. AMM
    • AI MM Agent: Bridging the Gap
    • Use Cases
    • Train & Launch (Step 1 & 2)
    • Flywheel (Step 3)
    • How the AI MM Agent Works in Detail
    • Why This is Powerful
  • 🛍️Pundi AI Data Marketplace (soon)
  • 🥇PUNDIAI Token Overview
    • Revenue generation flywheel
    • vePUNDIAI
      • how to bribe with vePUNDIAI
    • Protocol pool
  • Governance
    • Governance Proposal Information
      • EGF Info
      • EGF Grants Program
      • Application Template
      • Successful Grant Applicants
      • Launching an EGF Proposal
  • Links
Powered by GitBook
On this page
  • Example
  • Scenario 6
  1. PURSE+
  2. PURSE Token

Maintaining PURSE NFT(s)

As with any 404 token, it is each user’s responsibility to ensure that they have sufficient balance to preserve any 404 NFT they have in their address. PURSE is no exception to this rule. Different 404 tokens will enforce this rule differently. In some 404 tokens, once an address does not have sufficient balance to maintain its NFTs, the NFTs get burned from the address; but in others, the address’s NFTs might get transferred out from the address and are stored somewhere temporarily. In most cases, it is an address’s most recent NFT(s) that gets affected by this rule, and the minimum balance required to maintain any 404 NFT in an address simply follows the following equation:

minimum balance required = number of NFTs ∗ ERC20 equivalent amount for 1 NFT\small minimum \ balance \ required \ = \ number \ of \ NFTs \ * \ ERC20 \ equivalent \ amount \ for \ 1 \ NFTminimum balance required = number of NFTs ∗ ERC20 equivalent amount for 1 NFT

In PURSE, 1 PURSE NFT requires 1,000,000 PURSE ERC20 to be maintained in an address. And if this condition cannot be maintained, then the address would lose that PURSE NFT. When this PURSE NFT is transferred out of the address, it does not get burned, instead it gets transferred back to the PURSE contract and is available for minting; and anyone who successfully mints a PURSE NFT thereafter will obtain the PURSE NFT that is stored in the contract. PURSE NFTs that get sent back to the contract as a result of an address having insufficient balance to maintain them are stored in a queue-like structure, this will be highlighted in the next section after the following example.

Example

Scenario 6

Bob’s Total Balance (TB) of PURSE is now at 4,000,000 PURSE, where his Inactive Balance (IB) = 1,000,000 PURSE and his Active Balance (AB) = 3,000,000 PURSE. This means Bob has 3 PURSE NFTs in his address, and his NFT token ids - in the order of oldest to newest, are: 7, 8, 9 (actual PURSE NFT token ids start at a much larger number, this is just an example).

Bob is an extremely busy person and he momentarily forgets that PURSE is now a 404 token and he is required to maintain a minimum balance of 3,000,000 PURSE in order to preserve his 3 PURSE NFTs. He proceeds to transfer 2,800,000 PURSE to Alice, and he finds that his TB is now at 1,200,000 PURSE, where IB = 200,000 PURSE, AB = 1,000,000 PURSE; and he only has token id 7 left in his address.

Initially, when Bob transfers 2,800,000 PURSE out of his address, the PURSE in his IB will be used first to carry out the transfer. Since Bob only had 1,000,000 PURSE in his IB, this amount will be depleted and his IB will be 0; next, because 1,800,000 PURSE is still needed for the transfer and Bob has 3,000,000 PURSE available in his AB, two of Bob’s most recent NFTs are removed from his address to offset the remaining 1,800,000 PURSE required for the transfer. The removal of Bob’s 2 most recent NFTs (token id 9 first and then token id 8) will reduce his AB by 2,000,000 PURSE, but increase his IB by the same amount; and the transfer transaction will be carried out successfully, leaving Bob’s new TB as 1,200,000 PURSE (IB = 200,000 PURSE & AB = 1,000,000 PURSE).

PreviousTransferring PURSENextNFTs in Queue

Last updated 8 months ago

👛