Skip to main content

SAFU Contract

Overview​

This guide explains the PinkSale SAFU Developer Badge – what it means, how to get it, and who can help. A SAFU badge adds significant trust to your project. After reading this, you will understand:

  • What the SAFU Developer Badge represents: It signifies enhanced project security and limits the developer's ability to manipulate the contract unfairly.
  • The strict criteria required: Learn the specific rules for KYC, doxxing, owner privileges, tokenomics, and contract features needed to qualify.
  • Why an approved developer is necessary: Understand that working with a listed SAFU Developer who manages initial ownership is key to getting the badge.
  • Who the approved SAFU Developers are: Get a list of developers recognized by PinkSale to help implement SAFU standards.
  • How to potentially get a discount: Learn about mentioning "Saul Pink" when contacting these developers.
  • Answers to common questions: Find clarity on the benefits, requirements, and process for the SAFU badge.

What is the SAFU Developer Badge?​

The SAFU Developer Badge signifies that a project has taken extra steps to ensure it cannot be easily manipulated by the developer to harm investors. It shows a commitment to safety and transparency. This badge will be given to KYCed projects that meet the below specifications and whose contract ownership is managed by an approved SAFU Developer during the critical early stages.

Criteria for the SAFU Badge​

To qualify for the SAFU Developer Badge, a project must meet the following strict requirements:

  • KYC with PinkSale: Projects must do KYC with PinkSale.
  • Doxxing: Projects must doxx (team identities must be public).

Owner Privileges (Managed by SAFU Developer)​

  • SAFU developer shouldn't ask for the private key of clients.
  • SAFU developer must hold the contract ownership for a minimum of 7 days.
  • SAFU developer must pause trading until the official listing time.
  • SAFU developer must own the staking contract ownership (if applicable). The staking dapp must be audited.
  • Owner cannot be able to mint new tokens.
  • Owner cannot be able to pause trading after launch.
  • Owner cannot be able to set the max transaction limit lower than 0.1% of the circulating supply.
  • Only the SAFU dev may blacklist snipers during the 7 days of holding ownership. After 7 days or when ownership is transferred, the blacklist function must be non-functioning.
  • Owner cannot be able to claim the contract’s balance of its own native tokens.
  • Owner cannot be able to set the max wallet limit lower than 1% of the circulating supply.
  • Owner cannot increase taxes in the first 7 days from listing.
  • Anything that can be changed by the owner cannot limit or stop trading for the investors (e.g., Anti-bot without time limit, Transaction time lock without limit, sell limit based on holder balance, etc.).

Tokenomics Rules​

  • Tax cannot be higher than 10% buy or sell (max 10% each side).
  • No unlock tokens (team, private, etc.) in the first 30 days from listing.
  • Liquidity lockup time shouldn’t be less than 365 days.
  • Liquidity percentage must be 60% at least.
  • Private sale bonus shouldn't be greater than 10% from the presale/fair launch rate.
  • Private sale tokens can be sent starting at launch, with limits: The first send cannot exceed 20% of the liquidity's value (in BNB equivalent) in tokens. The next two days, 50% of the remainder of the private sale tokens can be sent each day.
  • Listing rate should be equal to the presale/fair-launch/subscription rate.
  • SAFU developer must control unlock tokens (SAFU developer will help projects distribute seed, private sale tokens).
  • SAFU developer needs to confirm if the project had a private sale. If there was a real private sale, the SAFU developer can distribute tokens for private sale investors according to the rules.
  • No airdrop tokens (giveaways, contest tokens) in the first 30 days from listing.
  • For migration from old contracts, new tokens may not be distributed to old holders until 30 days from listing.

Smart Contract Requirements​

  • Contract must be audited by a trusted PinkSale partner.
  • Buybacks should be automated within the contract.
  • Burns should be automated within the contract.
  • Auto-liquidity should go to an unreachable address (e.g., Dead address).
  • Contract should not malfunction in any circumstances.
  • No proxy contracts.

Common Problems That Cause Contracts to Crash​

(Contracts seeking the SAFU badge must avoid these issues)

  • Failed transactions that are caused by mathematical errors.
  • Swap settings and parameters should always be in a safe range.
  • BNB transfers from the contract should not revert in any circumstances.

Approved SAFU Developers​

Your project can receive the SAFU badge if you collaborate with one of these approved developers who will manage the contract according to the SAFU criteria.

Note: Tell developers you got contact from Saul Pink, you will get better discount.

Q&A (FAQs)​

  • Q1: What's the main benefit of the SAFU Developer Badge?

    • A: It significantly increases investor trust by showing the project meets high safety standards and limits the developer's ability to perform malicious actions (like rug pulls).

  • Q2: Does my project have to get the SAFU badge?

    • A: No, it's not mandatory for launching on PinkSale, but it's highly recommended as it makes your project more attractive and trustworthy to investors.

  • Q3: Can I get the SAFU badge if I deploy the contract myself?

    • A: No, based on the criteria, the contract ownership must be held initially by one of the approved SAFU Developers listed in this document. They ensure the SAFU rules are followed during the critical launch phase.

  • Q4: Does getting KYC and an Audit automatically grant the SAFU badge?

    • A: No. While KYC (with PinkSale) and an Audit (from a PinkSale partner) are requirements for the SAFU badge, you must also meet all the other criteria related to Owner Privileges, Tokenomics, and Contract features, and work with an approved SAFU Developer.

  • Q5: Who holds the contract ownership after the initial 7-day period managed by the SAFU Developer?

    • A: Typically, the ownership would be transferred back to the project team or potentially renounced (sent to a dead address) after the 7-day period, depending on the agreement and project structure. The SAFU Developer ensures specific harmful functions are disabled before transfer.

  • Q6: How does the 'Saul Pink' referral work for these developers?

    • A: When you contact one of the listed SAFU Developers, mention that "Saul Pink referred me." As the note indicates, this might help you get a discount on their development or management services.

Troubleshooting​

  • Q: I don't understand some of the technical criteria (e.g., proxy contracts, swap settings).

    • A: The approved SAFU Developers are experts in these areas. When you work with one, they will handle the technical implementation to ensure the contract meets all SAFU requirements. You can ask them to explain specific aspects if needed.

  • Q: A link for one of the SAFU Developers isn't working.

    • A: Double-check the link. Try their associated channel link if available. If a contact is definitely broken, try reaching out to another developer on the list.

  • Q: How do I choose which SAFU Developer to work with?

    • A: Contact a few developers from the list. Discuss your project's specific needs, their process, timelines, and costs (remember the Saul Pink referral). Choose the one you feel most comfortable with and who communicates clearly. Some may also be associated with audit firms, potentially streamlining the process.