kai retweetledi
@ClaimScanXYZ First tech to see claimed fees in realtime like this, looks good
4dLTJCnsosUfhYMdzrFjWhuVN6Fo7eJ7nLmH72appump
English
kai
228 posts
kai
@KaiRayden
lover of art & math artist^ - ^software🦀
Katılım Eylül 2021
416 Takip Edilen1.2K Takipçiler
.@Pumpfun x GitHub Fee Dashboard:@ClaimScanXYZ
🛠 Monitor every claim, every token, and every accumulated fee in one place.
Check it out: claimscan.xyz
TOKEN IS NOW LIVE 🔻
CA:4dLTJCnsosUfhYMdzrFjWhuVN6Fo7eJ7nLmH72appump
English
@openclaw has 370~ $SOL claimable in creator fees; fee share structure is locked and immutable👌
check on @ClaimScanXYZ
English
kai@KaiRayden
748 SOL gone from a @Pumpfun fee shareholder's claimable balance. Not a hack. The token creator just removed the shareholder, collected all the fees, and added them back, one transaction through a Squads multisig. 1- Reset the fee sharing config -> removed the shareholder, made himself the sole recipient 2- Updated fee shares to add the shareholder back but this instruction automatically distributes all pending fees first. Since the shareholder was already removed, all 748 SOL went straight to the creator/auth That's it. Two calls. The second one is designed to distribute fees before updating, it's probably a safety feature. The Squads multisig was closed right after. The creator just used it against the shareholder. Dashboard still shows the shareholder with the right percentage. Vault is empty. Found this while building @ClaimScanXYZ . Now you know what to watch for. Permissions should be locked on creator fees
QME
🚨 @pumpdotfun approved a fake CTO for my token and a scammer stole 748 SOL of fees.
🧵👇
English
748 SOL gone from a @Pumpfun fee shareholder's claimable balance.
Not a hack. The token creator just removed the shareholder, collected all the fees, and added them back, one transaction through a Squads multisig.
1- Reset the fee sharing config -> removed the shareholder, made himself the sole recipient
2- Updated fee shares to add the shareholder back but this instruction automatically distributes all pending fees first. Since the shareholder was already removed, all 748 SOL went straight to the creator/auth
That's it. Two calls. The second one is designed to distribute fees before updating, it's probably a safety feature.
The Squads multisig was closed right after.
The creator just used it against the shareholder.
Dashboard still shows the shareholder with the right percentage. Vault is empty.
Found this while building @ClaimScanXYZ . Now you know what to watch for. Permissions should be locked on creator fees
English
Agent Hackathon starts today from @solana and @colosseum
AI agents compete to build on Solana. Humans vote. Agents win prizes.
$100,000 in prizes for the top four submissions 👇
English
@KaiRayden will you keep working on this project or one time launch you think?
English
Hey @jhorikawa_err , glad you're checking out the our Houdini MCP repo! :D I want to share an update on this. We're integrating our Opus API into the Houdini MCP. Opus is an #houdini powered API we developed at Capoom that generates 3D models by controlling parameters. Sneakpeek:
Junichiro Horikawa@jhorikawa_err
I wanted to check what you can do with Houdini MCP. Looks promising. github.com/capoomgit/houd… #Houdini
English
@JackHiddeG @jhorikawa_err Kinda, LLM controls Houdini over Model Context Protocol
Català
I wanted to check what you can do with Houdini MCP. Looks promising.
github.com/capoomgit/houd…
#Houdini
English
kai retweetledi
A lil thing that popped in my head. Not sure, but most likely inspired by @sixnfive Flow piece.
#houdini #flipsim #redshift #simulation
English
