You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ERC20 can be split into multiple types (Fungible Token)
bulk All tokens have the same expiration date. very straight forward
Example: Special loyalty points issued in limited amounts, which expire together under a single rule. In such cases, the
ability to mint new tokens continuously may not be suitable.
Example: All tokens expired after block x
default:granular Each token has an individual expiration date. see ERC-7818
Common loyalty points where each point can have a unique expiration, allowing more flexibility in managing user rewards.
ERC721 can be split into multiple types (Non-Fungible Token)
bulk All tokenId have the same expiration date.
Example: coupons or vouchers intended for services that affect a broad user base, where a uniform expiration is necessary.
default:granular Each tokenId has an individual expiration date.
Coupon tailored to individual users, where each voucher can expire independently.
Example:
tokenId1 minted on block a and expired at block x
tokenId2 minted on block b and expired at block y
tokenId3 minted on block c and expired at block z
Example: All tokens were minted on the different blocks but expired at block x (same block)
additional:granular Each tokenId has an individual expiration date but has the same valid period it's can be done by default:granular but adding default duration
Example: a simple coupons or vouchers
Example: Each token is valid for n blocks
Extension feature for ERC-7818 below.
Blacklist for restricting receiving and spending.
GreyList can receive but restrict spending, only to members on the list.
Exception addresses are exempt from token expiration, meaning tokens held by these addresses will not expire.
Freeze fund can only move in or out by mint and burn action.
For
ERC20
andERC721
ERC20
can be split into multiple types (Fungible Token)bulk
All tokens have the same expiration date. very straight forwardability to mint new tokens continuously may not be suitable.
default
:granular
Eachtoken
has an individual expiration date. see ERC-7818Interface for ERC-721 should be ERC-7858
ERC721
can be split into multiple types (Non-Fungible Token)bulk
AlltokenId
have the same expiration date.coupons
orvouchers
intended for services that affect a broad user base, where a uniform expiration is necessary.default
:granular
EachtokenId
has an individual expiration date.Coupon
tailored to individual users, where each voucher can expire independently.additional
:granular
EachtokenId
has an individual expiration date but has the same valid period it's can be done bydefault
:granular
but adding defaultduration
coupons
orvouchers
Extension feature for
ERC-7818
below.Blacklist
for restricting receiving and spending.GreyList
can receive but restrict spending, only to members on the list.Exception
addresses are exempt from token expiration, meaning tokens held by these addresses will not expire.Freeze
fund can only move in or out bymint
andburn
action.Permit
for support gasless approval of tokens (standardized as ERC2612) Openzeppelin Implementation.QuotaMint
is used to limit the minting of tokens, providing easier and more efficient budget management.QuotaMintSchedule
allows the periodic renewal of a minting quota, enabling budget management over specified time intervals.DailySpending
to limit daily spending amounts for all users.SpendingTier
to limit spending amounts depends on the user tier.DailyReceiving
will limit daily receiving amounts for all users.ReceivingTier
to limit receiving amounts depends on the user tier.NearestExpiryQuery
facilitates querying the nearest expiration balance for a specified account.AcceptedBefore
restricts the acceptance of tokens set to expire within a defined threshold.Extension feature for
ERC-721
below.The text was updated successfully, but these errors were encountered: