This is a notice to announce that we have been made aware that a bug has been identified in Fairmoon smart contract. Funds are currently safe, but this will impact the price in the coming next weeks/months. Read more below and how we will help Fairmoon team remedy this issue.
Just like in all Safemoon forks, Fairmoon have a tax to help build a better price floor. 1% tax is collected by the contract, and once the contract have enough tokens it will sell half to add permanently burned liquidity.
The problem is that the contract will add liquidity every 500M tokens in the contract as kept originally from SafeMoon code but unlike SafeMoon with its extremely high supply, Fairmoon supply is just 5 billion with at least 2.5B permanently locked.
While adding liquidity is good, selling 250M tokens at once on the market to add liquidity will create a drop in price with an impact of at least 50%.
This will result in a major drop in price when this happens. This effectively turns a feature to help raise the price floor into a ticking bomb and since ownership is renounced on the contract, there is no way to disable the liquidity fee.
A snapshot will be taken in the next days so investors can move to the bug-free contract. We are currently discussing with the team on the best strategy to move forward from this unfortunate situation.
Rest assured that the token is still tradable at this point and nobody at any point can take funds from liquidity other than selling. We do not recommend panic selling, as the snapshot is not taken yet.
You can watch this video which explains what is going on in details:
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The biggest rug pull of all time of 31M USD #Meerkat was done with a proxy upgrade a few hours ago. Who said ruggers were not using proxy contracts to rug pull?
For example, notorious tokens using proxies that we strongly recommend to avoid are:
- Zoracles
- Core
- Base Protocol
- Paid
- Ampleforth
- DSD/ESD
- Daiq
Well, turns out after Chapo KYC’d UnionCapital back then (Yanni project) and “deleted the documents”, he also KYC’d Leverage X (another Yanni project), screenshot reveals (and also deleted the documents). Safe to say @DeFi_Owl have obviously been fooled here and not responsible.
✅ We audited ShareDeFi Protocol $SHADE 0x9E1C8EF68a378DdCfd6607956c289FEDBfB56991 and found no issue.
- Staking contract no longer allow withdrawal of tokens
- Team have 2% tokens unlocked
- Team have locked 10K tokens for staking for one year
- No backdoors or DoS possible from the owner perspective
- Team tokens (18% total supply) have been gradually locked over the next 12 months
- Owner can pull the BNB stored in the main contract to distribute staking rewards
ℹ️ This tweet isn’t an endorsement or financial advice of any kind. We’re only publishing the results of our findings.
👉 Owner can mint token instantly through the addAllocation() function with vesting type 4 (0 Days 100 Percent)
👉 The presale is a totally opaque process as the developer is the one who is minting tokens manually to token holders, which most of them are fresh (see screenshots)
ℹ️ Transaction example where 11,089,470 tokens have been printed to a fresh wallet and forwarded some of the tokens to another one which recently dumped its tokens: etherscan.io/tx/0xc8226147c…