Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Vault Zero (VZ) token information #30165

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

VaultZeroAI
Copy link

This request provides the info.json file for Vault Zero, a gamified multi-agent AI platform on Web3. It includes essential details such as the platform’s name, description, contract address, and links for accurate representation on the designated platform.

The description highlights Vault Zero’s unique blend of AI, strategy, and decentralized rewards. Tags like “defi,” “vaults,” “AI,” and “gamified” are included for categorization. The provided contract address is in checksum format, and all links (website, explorer, research, Twitter, Discord) are verified for accuracy.

This update ensures compliance with listing requirements and enhances visibility across blockchain platforms.

Verified holder count: 1,348. Source: BscScan

This request provides the info.json file for Vault Zero, a gamified multi-agent AI platform on Web3. It includes essential details such as the platform’s name, description, contract address, and links for accurate representation on the designated platform.

The description highlights Vault Zero’s unique blend of AI, strategy, and decentralized rewards. Tags like “defi,” “vaults,” “AI,” and “gamified” are included for categorization. The provided contract address is in checksum format, and all links (website, explorer, research, Twitter, Discord) are verified for accuracy.

This update ensures compliance with listing requirements and enhances visibility across blockchain platforms.
@merge-fee-bot
Copy link

merge-fee-bot bot commented Jan 24, 2025

PR Summary

Files OK: 2
Token in PR: BEP2 0x910F42f204BD998fA271cA8aa07ce359c733b898
Symbol: VZ decimals: 18
Links: Logo Info Website ExplorerFromInfo ExplorerFromID
Tags: defi, dapp
Token check error:
❌ number of holders not checked: please, check it manually

@merge-fee-bot
Copy link

merge-fee-bot bot commented Jan 24, 2025

Hi! In order to compensate for the efforts of processing PRs, we kindly ask for a contribution.
💀 As there is no refund, before paying the fee, make sure new tokens fulfill the minimum circulation and other acceptance criteria.
See also the PR Fee FAQ.

Please pay 500 TWT to the BEP20 (Binance Smartchain) address 0x485EC1fCAaad17401770149d8ad37119e46157c7.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet

TWT Acquiring:

Notes:

  • New tokens without significant usage are rejected, see criteria mentioned above.
  • One PR should be for a single project; PR's with more than 10 logos will be rejected.
  • Payment evaluation happens automatically, but with a few minutes delay. When payment is detected, an Accept Review is automatically placed on the PR, which is a condition for merge.
  • Evaluating the PR is done manually, and it is merged only if all conditions are satisfied.
    There will be a fee to process this request. None of it goes to the developers.
    Before paying the fee, make sure new tokens fulfill the minimum circulation and other acceptance criteria.
    If you are paying TWT for the submission, this will be burned automatically. There will be no refunds.

@merge-fee-bot
Copy link

merge-fee-bot bot commented Jan 24, 2025

@VaultZeroAI, kind reminder: please pay fee: 500 TWT to the address 0x485EC1fCAaad17401770149d8ad37119e46157c7.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet
See the Pull Request Fee FAQ.

Copy link

@merge-fee-bot merge-fee-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fee is PAID, fantastic! Thanks! Review added.

The PR will be evaluated soon by a maintainer, and if merged, the new logos should be visible in Trust Wallet.
Please note that the app caches logos (up to several days; if you want to see changes immediately, use a new installation). See the assets FAQ.
@Cryptocool1, @cryptomanz1: please take note.

(500.00 TWT)

@merge-fee-bot merge-fee-bot bot added the Payment Status: Paid Fee completely paid for PR label Jan 24, 2025
@merge-fee-bot
Copy link

merge-fee-bot bot commented Jan 24, 2025

500.00 TWT have been successfully burned.

@VaultZeroAI
Copy link
Author

Additional Information:

What is the purpose of this token? How will it benefit Trust Wallet users?

The purpose of the Vault Zero (VZ) token is to serve as the core utility and governance token for the Vault Zero platform. It will provide users different use cases and rewards. The token aligns with the platform's vision to combine AI and gamification.

Providing the token to Trust Wallets users allows easy verification and security for those taking part in token transactions. It also allows users to prioritize Trust Wallet as the wallet choice for anyone utilizing the Vault Zero platform.

How is the token being distributed? Are you conducting an airdrop?

The token has a fixed supply go 6 Billion with renounced contract. It is not being airdropped but some users have migrated from a prior contract. Any team allocations are bought at market price (no minted tokens for team), any additional migrated tokens are burned, and tokens are distributed on Decentralized exchanges.

Did you sold the tokens at an Initial Coin Offering (ICO) or a token presale?

No

Is the token listed on a centralized/decentralized exchange?

Yes, Pancakeswap with future listing potential Cross Chain and CEX

Is a Smart Contract audit completed? Where can we find this information?

No, the contract is a simple Bep20 token with the exact same features and code as the OpenZepplin library which is already audited.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants