PonsShare

The creator fee sharing layer for @ponsdotfamily. Launch tokens and share creator fee through a wallet, X, or GitHub account.

[PonsShare @PonsShare]

@ponsdotfamily makes launching tokens simple.

But there's still one thing missing.

You can route creator fees to a wallet... but not to someone through their X or GitHub account before they even have one.

What if you want to launch a token for a creator, contributor, or project and let them claim their fees later?

That's what PonsShare solves.

https://t.co/RfjM8WYsyO

[Pepe by Matt Furie - HOOD Chain 💚 @PepeonHood]

How it feels holding $PEPE on $HOOD 🪶 💚

[PonsShare @PonsShare]

@cryptocune @ponsdotfamily No miscommunication anymore, buybacks of token will be done in the next update aswel with 50% of the fees.

[PonsShare @PonsShare]

Whats next,

Better UI, quicker launch options.
More fee sharing

Token distribution (airdrop mechanism for ALL @ponsdotfamily launched tokens.

BUYBACK and burn if the creator doesnt claim the fees in 7 days.

Flywheel / distribution to holders option on launch.

Updates will be live later today.

[PonsShare @PonsShare]

@Sol_Shrimp Noted

[PonsShare @PonsShare]

Which new features would u like to see on @PonsShare let us know in the comments and we build it.

https://t.co/MV4zbnqPWJ

[PonsShare @PonsShare]

@PepeonHood @Matt_Furie I blurred the Privy user ID because it’s private, but this should still be sufficient proof that he made the claim.

This is through https://t.co/mQ20zxF7aA

[PonsShare @PonsShare]

@MEADGod Hey @MEADGod, I have nothing to report about something breaking but since @ponsdotfamily allow integrations is there any plan to publish and document the IPFS upload endpoint for third-party launch UIs.

[PonsShare @PonsShare]

@Apelifesavings @Capt_diamondntz @PepeonHood @pepeonrhood @Matt_Furie It isn't a part of the UI error i have just checked it.

[PonsShare @PonsShare]

Transparency is important to us, so here's what happened.

For a short period, our database was compromised. As soon as we discovered the issue, we secured it and fixed the vulnerability.

The incident was LIMITED to database access only.

Nobody ever had access to any wallets or private keys, and no on-chain funds were at risk.

Creator fee wallets remained unchanged, and no unauthorized party is receiving creator fees.

[PonsShare @PonsShare]

The issue has now been resolved.

It was only a UI issue. Creator fees were always being routed correctly on-chain, and no funds were ever at risk.

We apologize to the PEPE community for the confusion and appreciate everyone's patience while we resolved it.

@PepeonHood @pepeonrhood @capt_diamondntz

[PonsShare @PonsShare]

We made a mistake while restoring some database values.

Creator fees are still being routed correctly to @Matt_Furie on-chain, so there's nothing to worry about.

The issue is only with the UI display and the Privy mapping. We're fixing it now, and it should be updated within the next few minutes.

Thanks for your patience.

[PonsShare @PonsShare]

@Capt_diamondntz @PepeonHood @pepeonrhood It already is and was.

[PonsShare @PonsShare]

THE sharing layer of pons.

https://t.co/MV4zbnqPWJ

[PonsShare @PonsShare]

@fern @nikil When is the next CCM meta on RH?

[PonsShare @PonsShare]

@Matt_Furie Check PEPE on @RobinhoodCrypto.

Pepe belongs to Hood.

[PonsShare @PonsShare]

@Matt_Furie Check PEPE on @RobinhoodCrypto.

Pepe belongs to Hood.

[Achi @AchillesXBT]

WEBSITE IS LIVE!

https://t.co/UaobOcb5tr

TWITTER IS LIVE!

@pepeonhood

0xC79234A9918B15605a456c71D433879600420450

[PonsShare @PonsShare]

@vladtenev @chrisontesla @ponsdotfamily & @PonsShare is the best place for family finance.

[PonsShare @PonsShare]

@vladtenev Imagine if a token was created and a agent could trade with the fees.

only on @ponsdotfamily !

[PonsShare @PonsShare]

@vladtenev Imagine if a token was created and a agent could trade with the fees.

only on @ponsdotfamily !

[Achi @AchillesXBT]

All fees to @matt_furie

You are not bullish enough anon

@RobinhoodCrypto got all the volume now