JLChong◼️☝️

There’s too much evidence that this is the jellyjelly team The GitHub creator is @iqramband with @lessin as a contributor Looking back at these GitHub profiles history they had worked on venmo in 2014 (iqram) and thing related to each post by (lessin) The email connected to @lessin GitHub matches the email shown in one of his Twitter posts for further confirmation The ca of $QUEST was added by iqram to the GitHub code under ‘mint’ The dev has been buying back and burning and the wallet funding the dev wallet has $18m wallet value which is connected to jelly jelly insider trades The day that this GitHub was published @lessin posted , telling @iqramband it’s time as seen in the post below At this point it is impossible for this GitHub to be anything other than @lessin and @iqramband new project We are seeing some hints being dropped gradually and their statement of making the next launch a stealthy one checks out Jellyjelly hit 460m+ and I suspect that as things unfold $quest is gonna run to 10M+ minimum The concept of quest is really cool and could be a big hit once finalised into and app E7Xfasv5CRTNc6Xb16w36BZk3HRSogh8T4ZFimSnpump

In case you’re still doubting Iqram posted this on JellyJelly 4 hours ago and it clearly shows he he has github bookmarked and he’s been posting videos of using @zocomputer to help vibecode $QUEST

QUEST belong to $jellyjelly @lessin and @iqramband. This is traceback of gemini . Make your choice. $Quest E7Xfasv5CRTNc6Xb16w36BZk3HRSogh8T4ZFimSnpump Technical Evidence: The Link Between the Repo and $QUEST CA Evidence 1: Shared Wallet Signature (The Smoking Gun)The "Treasury Address" defined in the packages/sdk/src/constants.ts file and the wallet that deployed theE7Xfasv5CRTNc6Xb16w36BZk3HRSogh8T4ZFimSnpump token share a direct financial trail. Finding: The token deployer received its initial SOL funding from the same source as the project's "Treasury" or the same identified Binance Hot Wallet exit point. Conclusion: The financial backing originates from a single entity (linked to the Sam Lessin/Finman team). Evidence 2: Hardcoded "Test Mint" VariableA deep dive into apps/web/.env.example and scripts/test-payout.ts reveals a direct link: Code Line: const MINT_ADDRESS = process.env.NEXT_PUBLIC_QUEST_MINT || "E7Xfasv5CRTNc6Xb16w36BZk3HRSogh8T4ZFimSnpump"; Analysis: The developer didn't choose a random coin for testing. They embedded this specific token into the system as the default reward unit. Evidence 3: Metadata and Identity Alignment Repo Definition: Throughout the entire codebase, the protocol is referred to as "Quest." Token Identity: The metadata for the E7Xfas... address confirms the ticker is $QUEST. Match: Project name, codebase name, and token ticker are a 100% match. Evidence 4: API and Bot IntegrationThe file packages/api/src/verify.ts uses GPT-5 mini to verify video submissions. When a verification is successful, the payout function specifically calls this CA to execute the transfer.

MCP wrapper for e-commerce links with all payments served via x402 and USDC. @openclaw @USDC @arc @base @solana Can’t vouch for the service but amazing to see this stuff emerging so fast!