Skip to content

Conversation

@twarkham
Copy link

@merge-fee-bot
Copy link

merge-fee-bot bot commented Nov 14, 2025

PR Summary

Files OK: 2
Token in PR: SPL BBKPiLM9KjdJW7oQSKt99RVWcZdhF6sEHRKnwqeBGHST
Symbol: GHOST decimals: 9
Links: Logo Info Website Explorer
Tags: nft
Token check error:
❌ invalid value for links.name filed, allowed only: facebook, reddit, telegram, discord, coingecko, docs, twitter, youtube, coinmarketcap, blog, source_code, telegram_news, whitepaper, medium, forum, github
❌ number of holders not checked: please, check it manually

@merge-fee-bot
Copy link

merge-fee-bot bot commented Nov 14, 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 0xA18BAb7c4995Dd70065c4C229333f9784901d0D9.
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.

@tw-jt tw-jt closed this Nov 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants