Balance Checker
Last updated
Last updated
The PiGET Balance Checker is a powerful tool crafted to confirm if a given card possesses a specific ERC-20, ERC-1155, or ERC-721 token.
Put simply, it's a tool to check whether that PiGET card holds a particular type of token or NFT.
The Balance Checker application is particularly valuable for ticket verification purposes.
For example:
Consider an exclusive event that admits only individuals with invitations or tickets, which essentially serve as one or more types of NFTs. Upon arrival at the event, attendees must demonstrate ownership of the requisite NFT. This is where the PiGET Balance Checker proves its utility.
Through a simple scanning process, organizers can promptly verify whether an individual possesses the necessary NFT or not. Thus, the Balance Checker emerges as an indispensable tool for events that require invitation or ticket validation.
In addition to NFTs, the Balance Checker can also verify ERC-20 tokens. For instance, to participate in an event, one might need to hold ETH.
To best serve PiGET users, we empower them with the freedom to customize the features of the Balance Checker application.
Currently, we offer four settings for our users. The setup process may vary slightly depending on the specifics of each feature, but generally, the procedure remains quite similar.
This setting is intended for cases where you simply need to verify whether the scanned cards contain the required token type. Anyone possessing a token that meets your criteria will be deemed valid.
For this setup, you'll utilize the following URL format:
Where [chain ID] represents the ID of the blockchain on which the token you wish to configure resides.
For the convenience of PiGET users, here are 5 blockchains supported by our Balance Checker feature along with their corresponding Chain IDs:
Ethereum - 1
Binance Smart Chain (BNB) - 56
Avalanche - 43114
Polygon - 137
Optimism - 10
As for the [token contract], since you can check both ERC-20 tokens and NFTs (ERC-1155 and ERC-721), we'll divide them into two cases:
ERC-20:
Finding the contract address for ERC-20 tokens is actually pretty simple!
You can easily locate it on popular cryptocurrency websites like CoinMarketCap or CoinGecko. These sites are trusted by many and make it super easy to find the contract address you're looking for.
If you prefer using search engines like Google or Bing, it's just as easy. Just type in the name of the token and the blockchain it's on, and you'll have the contract address right at your fingertips.
For example:
USDC token contract on Polygon is: 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359.
Whereas its contract on Ethereum is: 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48.
NFTs (ERC-1155, ERC-721):
For ERC-1155 or ERC-721 tokens, or simply put, NFT tokens, finding their contract addresses isn't difficult at all, thanks to the KEYRING NFT Viewer.
Through the KEYRING NFT Viewer website, you can quickly locate the contract of a specific NFT and even its ID.
One of the unique features of the KEYRING NFT Viewer is that you don't need to connect a wallet to view NFTs on a particular wallet address.
Here's how it works:
Go to the KEYRING NFT Viewer website.
Choose the blockchain and enter the wallet address where you want to view the NFT.
Click the search icon.
Select the NFT you want to view information about.
Voilà! You can now see the NFT address, Token ID, and Token standard without any hassle.
The URL for this feature will be:
Simply put, users just need to add [list-contained/] before [chain ID] to activate the list-checking feature.
This setup operates similarly to the General Verification mentioned earlier, but with some added features, of course.
The key difference here is that with this setup, you get additional functionalities:
Viewing a list of approved addresses.
The Balance checker users can see a list of cards that have been approved. Note that only valid cards will appear on this list.
This feature makes it easier for users to keep track of the number of participants.
Tracking how many times approved cards have been scanned.
This feature helps users gather information on how many times a card from a particular address has been scanned.
It can help limit the misuse of cards being passed around multiple individuals and scanned multiple times (Well, if that goes against the rules of your group, otherwise, having this information might still be useful, right?).
Sending the list via email.
To further enhance user-friendliness, we've integrated the capability to send the list via email, with just a simple sharing action.
To access the list, you simply need to tap on the "List" icon on the screen.
With this setting, users will have limited access only to cards belonging to a specific group to pass through.
This means that even if a person possesses a designated token, if they are not part of the authorized group, their card will still be denied.
The URL format for this feature will be as follows:
The [chain ID] and [token contract] will be similar as the instruction above, with the distinction lying in the [group name], which will be the key determinant of whether the card is approved or not.
The [group name] is the name of the company or the user's private group, which will filter out only the cards belonging to this company or group that can pass through the checking process.
To create a company or group card, users can refer to the FAQ section.
How to UseWell, this also means that outsiders granted permission won't get a free pass. Just owning the right token doesn't magically open the gates, you know!
The URL for this feature is:
Users simply need to add [list-contained/] right before [group name] to utilize the list-checking feature for Group Verification.
This feature will be identical to the Group Verification feature mentioned right above, except you can view reports on:
The total number of addresses scanned.
How many times each address was scanned.
Sending the list via email.
These additional functionalities work similarly to the "General Verification with Report" feature explained earlier.
