PARTY

Launch a V4 Pool with Friends. $PARTY live on Robinhood.

0x68dae2aab5e80dcfb379b332d9161cf0328fffab

[PARTY @LaunchPartyV4]

Getting into a token launch shouldn't be a race.

Launch a V4 Pool Together.

Up to 250 seats per party. Same entry for everyone.
No deadline. Refund anytime.

Dividend Tokens Live on Robinhood x @Uniswap V4
Next: BSC, BASE, ETH.

Join $PARTY Launch → https://t.co/OhMeLwS8Jt

[PARTY @LaunchPartyV4]

Get in before the FOMO.

0x68dae2aab5e80dcfb379b332d9161cf0328fffab

[PARTY @LaunchPartyV4]

. @fomo / @Mobulaio will surface our coins once we’re a listed launchpad. Same for @GeckoTerminal. Applying for both. Until then make sure to engage and share CA.

Bounties out for the best thesis on FOMO ↓
https://t.co/AqcH5QqUVA

[PARTY @LaunchPartyV4]

@_TJRTrades that’s true

[PARTY @LaunchPartyV4]

@seyong @fomo need that VPN

[PARTY @LaunchPartyV4]

@GeckoTerminal $PARTY

0x68DaE2aab5E80dcFb379B332D9161cF0328FffaB

[PARTY @LaunchPartyV4]

@JamesWynnReal

[PARTY @LaunchPartyV4]

Keep 90% of your trading fees on Robinhood Chain.

Our 10% platform fee goes back into ecosystem development: $PARTY buybacks, liquidity provision, and a new community incubator (TBA).

https://t.co/OhMeLwSGz1

[PARTY @LaunchPartyV4]

More chains coming to Launch Party.

community vote :

[PARTY @LaunchPartyV4]

@JR5_Crypto few

[PARTY @LaunchPartyV4]

@totalistrading hearing things

[The Watchers @WatchersLabs]

We reviewed @LaunchPartyV4.

Assessment: LEANING LEGIT ( deployed contracts, a registered token launch and a funded vesting escrow are independently observable. Successful refunds, fee distributions and the claimed liquidity restrictions remain unverified in this review )

@LaunchPartyV4 lets people pool funds before launching a token into a V4 liquidity pool on Robinhood Chain. Participants reserve seats at a fixed price and share the crew allocation according to how many seats they hold.

Website:
https://t.co/xn0TIMJVUC

How it works

A host chooses the token, seat count, seat price, crew allocation, vesting period and trading-fee settings.

The application describes refundable seats until launch succeeds. The host can launch once the minimum participation threshold is reached; anyone can launch when the room fills.

“Same entry” means the same price per seat. It does not mean equal allocations per wallet or protection against someone participating through multiple wallets.

The build

We inspected the deployed frontend and checked its configured contracts through an independent Robinhood Chain RPC.

The party factory, token launcher and trading hook all returned deployed bytecode.

Party factory:
0xDec25F5E4AaB73Ebc64601A0885E01Ae1203fc29

Token launcher:
0x8299666748f3D04531D36ea882731e7fC7576d8E

Trading hook:
0x8E75298A4fD5dccFFf16A7404d4A1acc2CcAA8CC

At the time of checking, roomCount() returned 3 rooms and coinCount() returned 2 registered coins. The factory’s launchConfiguration() returned a token supply of 1,000,000,000 and a maximum of 250 seats.

The frontend contains contract interactions for reservations, refunds, launching, vesting releases and fee-related operations. These are substantive components, although frontend code and deployed bytecode do not establish that every advertised feature works correctly.

What we verified for $PARTY

The website identifies this room as “Launch Party Official Token”:

https://t.co/KfpAP3KVTV

Independent contract reads confirmed:

• isRoom(address) recognises that address as a room belonging to the configured factory.
• seats() and totalJoined() both returned 50.
• seatPrice() returned 0.02 ETH, making the full reservation amount 1 ETH.
• host() matched the host displayed by the application.

The factory’s termsOf(address) also matched the displayed launch terms:

• 10 host seats.
• A 12.5% crew allocation.
• 3-day vesting.
• A host-launch threshold of 26 paid seats.

The official X account announced a successful launch with all 50 seats filled and published this token address:

0x68DaE2aab5E80dcFb379B332D9161cF0328FffaB

That is the same token we matched to the launcher. Its name() returned “Party” and totalSupply() returned 1,000,000,000 tokens.

The launcher’s launches(address) record links it to a pool ID and this vesting escrow:

0x3e674111d921d6410f3f67be4c6d6b5112e763cc

The escrow returned:

• coin(): the same PARTY token address.
• totalGranted(): 125,000,000 tokens, matching 12.5% of supply.
• duration(): 259,200 seconds, or 3 days.
• start(): September 29, 2026, at 00:26:23 UTC.

The token’s balanceOf(escrow) returned approximately 124,992,785.49 PARTY when checked.

These are independently retrieved contract-state observations. We have not matched the difference between the granted allocation and remaining balance to individual claim receipts.

The earlier X announcement specified 50 seats at 0.02 ETH each, which also matches the room’s state.

The addresses and function names above identify the reads used in this review. The independent RPC endpoint was:

https://t.co/MWItoplgJh

Does holding PARTY earn platform revenue?

That has not been established.

The frontend describes a configurable fee model: 10% of each trading fee goes to the protocol, while the remaining 90% is divided between holders and the creator’s destination according to launch settings.

0x68dae2aab5e80dcfb379b332d9161cf0328fffab

[PARTY @LaunchPartyV4]

@Jaspeeroo 0x68DaE2aab5E80dcFb379B332D9161cF0328FffaB

[PARTY @LaunchPartyV4]

@RobinHubHB @RobinhoodCrypto 0x68dae2aab5e80dcfb379b332d9161cf0328fffab

[PARTY @LaunchPartyV4]

0x68dae2aab5e80dcfb379b332d9161cf0328fffab

[PARTY @LaunchPartyV4]

. @fomo / @Mobulaio will surface our coins once we’re a listed launchpad. Same for @GeckoTerminal. Applying for both. Until then make sure to engage and share CA.

Bounties out for the best thesis on FOMO ↓
https://t.co/AqcH5QqUVA

[PARTY @LaunchPartyV4]

@mauritsneo being early together.

[PARTY @LaunchPartyV4]

the party just started.

[PARTY @LaunchPartyV4]

@ddivixx assemble

[PARTY @LaunchPartyV4]

@WatchersLabs 🙏 willing to open source once we get some runway

[The Watchers @WatchersLabs]

Update on @LaunchPartyV4.

The team provided specific LP and testnet reward receipts. We checked them independently, and there are findings to add to our review.

The $PARTY LP positions are held at the dead address.

The successful mainnet launch transaction shows PositionManager 0x58daec3116aae6D93017bAAea7749052E8a04fA7 minting positions 3400392 and 3400393 directly to:

0x000000000000000000000000000000000000dEaD

Both IDs match the supply and floor positions in PARTY’s launch record. Current ownerOf() reads also returned the dead address for both.

This resolves the specific LP-position ownership question we raised. The precise description is that the position NFTs were minted directly to the dead address; the liquidity itself was not destroyed.

Mainnet launch receipt:
https://t.co/8jhreZVzCn

We also verified the supplied testnet sweep-and-claim receipts.

Both transactions succeeded on Robinhood Chain testnet, chain ID 46630.

The first called sweep(bytes32). Its Swept event recorded:

• Total: 3,552,947,069,941 units.
• Holder allocation: 3,197,652,362,947 units, approximately 90%.
• Platform allocation: 355,294,706,994 units, approximately 10%.
• Creator allocation: 0.

The same transaction emitted a reward-funding event from the contract subsequently used for the claim. This records funding for holder rewards, rather than immediate payment to every holder.

Sweep receipt:
https://t.co/Jr9AGYdbb9

The second transaction called claimFor(address) on that reward contract and emitted RewardPaid for:

0xb781c0e1d36b1048fd2d38f33566f5042d472ecb

The recorded reward was 12,535,113 units. The transaction sender was different from the recipient, demonstrating a claim submitted on the holder’s behalf.

Claim receipt:
https://t.co/tLKgnREhO1

We matched transaction inputs, successful receipts and emitted events. We could not separately trace the internal native-asset transfers because the endpoint did not provide the required tracing or historical balances.

The team also clarified the fee wording.

“Reflections up to 3%” refers to the total trading fee. Hosts choose 0%, 1% or 3%, and can allocate up to 90% of that fee to holders. The maximum holder portion is therefore 2.7% of a trade.

$PARTY itself is configured with a 1% trading fee and 0% allocated to holders. That matches our independent contract reads.

According to the team, no launched mainnet coin has enabled a holder share yet, so there is no mainnet holder-payout receipt to show. The examples above are testnet evidence and should be described that way.

Assessment remains LEANING LEGIT, with stronger evidence than our initial review: $PARTY 2 LP positions are confirmed at the dead address, and the supplied testnet sweep-and-claim transactions are corroborated.

We’re updating the findings where the evidence has changed.

[PARTY @LaunchPartyV4]

@ddivixx GOING TO BE A PARTY