Garlic 10 SOL Giveaway
The first token deployed on https://t.co/bfXxrrVGfe that bonds will receive 10 SOL.
To enter, tag a friend and drop your dev wallet you deployed on in the comments below๐. We are ONLY accepting wallets that deployed tokens on Garlic.
Good luck๐ง
Just fixed a bug where images wouldn't load due to slow ipfs metadata propagation. All images will now display even on newly deployed tokens.
https://t.co/kb34V1gWKL
What would $PLTR be at if it was unvampable?
Protect your https://t.co/2pOGWdhRGF launches from vamps with https://t.co/kb34V1gWKL
HNE93e2UsB4y49FztZhzxPNPv3TWhXYzuhmM1FSQpump
GjWzsUG4U8DVSsxKKVnbigvx1vxvK33WY3WwWDQE9jV9
BuNA8LbtJSGH4NKujpwnLWrrLrWW4rAMQYHwudpypump
this shit doesn't happen if you deploy on @Pumpfun with https://t.co/kb34V1gWKL ...
just saying ๐คทโโ๏ธ
DXQ2ajNDRs82JwXchi1DSwEBeK3aGeMLXnXwDyj1pump
8gWzjCioBZC2DJz6dLX66GhgmsWwmQjBjmUfSqv1pump
$GARLIC already has 10+ more SOL in the LP than other tokens at the same market cap. This effect will compound over time as the Garlic ecosystem grows.
Bonding curve/launchpad tokens are notorious for having thin liquidity and being griefed by large sells.
Garlic fixes this.
How buybacks/LP injections work on Garlic
When tokens in the Garlic ecosystem have accrued at least 0.1 SOL + fees in creator rewards, the "claim" instruction on the Garlic Program is invoked. https://t.co/L8x50Ivnmv
This instruction does the following:
1) Verifies that the creator fee rewards pool has enough SOL in it
2) Signs using the token dev PDA created on deploy to claim the creator fees. 10% of the fees go to a designated protocol fee wallet that pays for our RPCs and infrastructure.
3) If the token hasn't bonded yet, the creator fees are used for a buyback. If the token has bonded, 50% of the creator fees are used to do a buyback and then combined that with the other 50% of the creator fees in SOL to add to the liquidity pool and burn the LP pool tokens. This adds liquidity at a 1:1 ratio, strengthening the pool and raising the floor.
Every single token deployed on https://t.co/bfXxrrVGfe is equipped with this feature (including $GARLIC). As a result, the ceilings are higher and the liquidity pools are deeper on Garlic tokens.
See the quote tweet for information on how to see these transactions onchain for a specific token.
@Jik1615898 A voting system could be a good idea. Maybe token-gated/DAO or proof-of-stake like Solana validator consensus. Would definitely help with edge cases.
It's hard to tell how https://t.co/bfXxrrVGfe would handle situations like this in the future. Kind of hard to prevent a vamp if they have different names.
Open for suggestions in the comments.
8f4wvfVpcVY2xYrTuVVYHy9hxC9q9rwQNhfHDGc4pump
ukwDnxk56MnqpCXsxNE8xpWwZ4qafjpt16KVogHpump
@Andydangy That's true. In this case some people are saying the "Billy" name might be larp so there's that to consider as well.
Sometimes market participants gotta decide
How buybacks/LP injections work on Garlic
When tokens in the Garlic ecosystem have accrued at least 0.1 SOL + fees in creator rewards, the "claim" instruction on the Garlic Program is invoked. https://t.co/L8x50Ivnmv
This instruction does the following:
1) Verifies that the creator fee rewards pool has enough SOL in it
2) Signs using the token dev PDA created on deploy to claim the creator fees. 10% of the fees go to a designated protocol fee wallet that pays for our RPCs and infrastructure.
3) If the token hasn't bonded yet, the creator fees are used for a buyback. If the token has bonded, 50% of the creator fees are used to do a buyback and then combined that with the other 50% of the creator fees in SOL to add to the liquidity pool and burn the LP pool tokens. This adds liquidity at a 1:1 ratio, strengthening the pool and raising the floor.
Every single token deployed on https://t.co/bfXxrrVGfe is equipped with this feature (including $GARLIC). As a result, the ceilings are higher and the liquidity pools are deeper on Garlic tokens.
See the quote tweet for information on how to see these transactions onchain for a specific token.
Here's how to see the TXs for buybacks/LP injections on all tokens on https://t.co/bfXxrrVGfe (including $GARLIC):
On the tokens page(https://t.co/L0vgeTPWcj), each token listing has an address next to "Buy/LP: " (see attached image). If you click on the address, ie "4Kbi...EzUb" for $YELLOW, it brings you to the Solscan link for the buyback/LP injection address: https://t.co/qabXzLYBJp.
You can do this for any token on https://t.co/bfXxrrVGfe to see when the dev fees are going into buybacks(pre bond) and liquidity injections(after bonding).
The only one that's a little different is $GARLIC, where the buybacks occur from the dev wallet (as you probably notices from the DB bubbles on the chart). All other tokens use a separate address to claim and buyback.
Made a slight edit to the site
Rearranged the tabs the tokens page (https://t.co/L0vgeTPWcj) to make it easier to find tokens.
Also added pagination. Once we reach 20 tokens you will be able to navigate through multiple pages.
Drop any site/eco feature requests in the comments.
The Garlic Onchain Program:
Most "launchpads" built on https://t.co/rmSwz2rwgg are nothing more than a https://t.co/dK90zHJIuH wrapper. What's unique about Garlic is that it has its own onchain program. https://t.co/KoQEi2BU8r
The Garlic program has 4 main instructions:
"initialize" - This instruction sets the Garlic mint that 0.25 SOL deploy fees go into. Once this is set it cannot be changed.
"claim" - This instruction claims creator fees on tokens deployed on https://t.co/bfXxrrVGfe and does buybacks prebond / liquidity injections post bond.
"claimGarlic" - This instruction claims creator fees on $GARLIC and does buybacks prebond / liquidity injections post bond.
"deploy" - This is the instruction that deploys tokens on Garlic. It makes a new PDA (Program Derived Address) for the fee claimer/dev of the token so users do not have permission to claim the fees. The name and ticker you use to deploy the token are stored onchain and "deploy" txs will automatically fail if you attempt to reuse them.
Everything happening in one transaction keeps Garlic safe from fake tokens, vamps, and keeps the ecosystem trustless and secure.
It was a technical challenge to fit all of the accounts in the transaction as you can see from the attached images. The claim instruction has 45 accounts, and the deploy instruction has 53 accounts. Solana transactions have a size limit of 1,232 bytes and the deploy transaction is just under that limit thanks to using an ALT (address lookup table) to store addresses in a compressed format.
Garlic is the first(and hopefully last) of its kind. This is not a vibecoded slop @Pumpfun wrapper. Garlic is one of the only tech projects on Solana right now that is actually building onchain.