Password is @unicornandmemes
FIND OUT OUR DEMOS ON https://delvesdk.fun/
DISCLOSURE STATEMENT:
CA: HBiRMz4vUyPQTGUn5MMhH1oXyMiMKGsqFGXruuKNpump
READ THIS BEFORE BUYING. By buying, you represent you read and accept this disclosure.
This disclosure is designed to reduce ambiguity in a high-speed PvP launch environment and to protect a Hackathon execution sprint; it is not designed to maximize participation, price, market cap, or community satisfaction.
A) Acknowledgment: YOU AGREE AND ACKNOWLEDGE THAT YOU READ THE DISCLOSURE ON THIS WEBSITE BEFORE BUYING.
Most buys are ineligible for any perpetual revenue-share program. You may be ineligible even if you believe you qualify. We will not explain anything individually. Everybody gets the same chance. No exceptions.
No buy or sell signal is being provided. Nothing here is investment advice. You further acknowledge that, in a high-speed launch, most humans will not reach the website during the initial ineligible window. This disclosure is intended for the subset of participants who do reach the website and choose to follow these rules.
0) TIMING WINDOWS (READ THIS FIRST)
All timing is determined by Solana blockchain confirmation time (the time your transaction lands and is confirmed on-chain). The team is not responsible for mempool/priority-fee/validator delays, timestamp display differences, RPC/UI lag, or any mismatch between what you see in a UI and on-chain confirmation time.
STEALTH LAUNCH WAS CONDUCTED 3 HOURS PRIOR TO STREAMING OCCCURED OR ACCOUNTS UNLOCKED: https://pump.fun/coin/HBiRMz4vUyPQTGUn5MMhH1oXyMiMKGsqFGXruuKNpump
CA: HBiRMz4vUyPQTGUn5MMhH1oXyMiMKGsqFGXruuKNpump
X post about stealth: https://x.com/DelveSDK/status/2019153165665399183
We exercised our rights under Clause 4.2 prior to launch. The X & Telegram were locked and this was an executive decision and none knew this would occur. The token metadata corresponds to the X post.
LAUNCH [00:00] WHEN CUSTODIAN ADDRESS CREATES A TOKEN:
HuPWr84vhtmwmTUvmEmk8MDKQ2Cx4nsjuxPUuMDr8j8Y.
THIS DISCLOSURE STATEMENT PERTAINS TO ONLY THE DLVSDK TOKEN. THERE IS ONLY ONE $DLVSDK TOKEN.
DLVSDK TOKEN:
https://pump.fun/coin/HBiRMz4vUyPQTGUn5MMhH1oXyMiMKGsqFGXruuKNpump
INELIGIBLE WINDOW OF 4 MINUTES & 20 SECONDS (260 SECONDS):
Ineligible for perpetual revenue-share.
INELIGIBLE WINDOW → Bonding Curve Completion: Eligible, subject to disqualification.
Bonding Curve Completion → POST-BONDING INELIGIBLE WINDOW 6.9 MINUTES (414 SECONDS): Ineligible.
Final POST WINDOW OF ELIGBILITY OF 69 MINUTES: Eligible, subject to disqualification.
These windows may be referenced elsewhere as “the first eligibility window” and “post-bonding eligibility window.”
THIS DISCLOSURE DOES NOT RESTRICT YOUR RIGHT TO BUY, SELL, TRANSFER, OR HOLD. IT ONLY DEFINES ELIGIBILITY CRITERIA USED FOR A SEPARATE PROGRAM TIED TO COMMUNITY CUSTODIANSHIP OF DEMOS.
1) DISQUALIFICATION
You are disqualified from perpetual revenue-share eligibility if any of the following occurs:
WALLET ADDRESS IS CONSIDERED DISQUALIFIED: 3NS1To2DJvAdRUVZmenMyfs5qfQLNTyUVPKXWTSCdo6t
ANY WALLET ADDRESS THAT BOUGHT $DLVSDK BEFORE PUBLIC LAUNCH AS ABOVE
Any sale, transfer, or movement of tokens in an eligible wallet (even partial).
Mixing eligible and ineligible tokens in the same wallet, or commingling that makes eligibility unverifiable.
Use of a sanctioned entity, restricted counterparty, or any wallet the team reasonably cannot service due to compliance risk.
Failure to complete KYC if required for revenue-share administration, only if and when required.
Recommendation for long-term participants: use a fresh wallet that holds only SOL plus the eligible purchase, so you preserve eligibility without accidental mixing.
If you are disqualified, any would-be share that would have gone to you becomes unallocated and may be reassigned as described in Section 7.5.
2) NO ADVICE OR PROMISE
This is not investment advice.
This is not a promise of profit.
This is not a buy/sell signal.
This is a rulebook for a perpetual revenue-share feature tied to community custodianship of demos built during the hackathon build period.
Eligibility is narrow and determined strictly by on-chain timing plus wallet hygiene, and then by the program rules below.
Eligible Revenue Sharing Wallets will be be published on website and DelveSDK Revenue Pool Address shall be set in stone in 24 hours of launch. First revenue payments shall begin 36 hours post launch.
3) HACKATHON PRIORITY AND BUILD FOCUS
Our first consideration is to win the Pump.fun hackathon. That is why these strict rules exist: to protect execution focus, shipping velocity, and demo quality. We are not here to promise vaporware or mislead individuals in the name of “building community.” We prioritize execution and finding custodians.
PumpFun Hackathon page (reference only):
https://hackathon.pump.fun/
“Build in public” means we will:
publish demos frequently
publish written development updates, so the public can test, break, critique, and improve
the demos through feedback on OnlyHodlers
“Build in public” does not mean we will:
explain full mechanics on demand
provide customer support
host town halls, or
provide real-time onboarding
This is a sprint. The demos are the product of the sprint.
4) LAUNCH FORMAT, CONDUCT, AND INTEGRITY
4.1 Stealth launch posture
DelveSDK may conduct a stealth launch (limited pre-announcement) to reduce spam and improve execution focus. A stealth launch is not, by itself, a promise of fairness or distribution outcomes.
4.2 No bad-faith trading conduct by the team
DelveSDK’s intent is to comply with hackathon and platform expectations regarding conduct. Team members are expected not to:
sell their own tokens at any time during the program,
engage in insider trading, or
act in bad faith toward token holders.
DelveSDK is not engaging in (and does not endorse) market manipulation, including bundling, sniping, wash trading, artificial volume, or the use of volume bots. Price is set by market participants.
4.3 Why the initial ineligible window exists
The initial ineligible window exists to give humans a chance to reach this website, read the disclosure, and decide whether they want long-term participation. The team follows the same timeline and waits through the same ineligible window.
5) LAUNCH INTEGRITY SAFEGUARD (SINGLE-LAUNCH INTENT & DISCRETIONARY ABORT/RELAUNCH)
Single-launch intent: We are not launching decoys or intentional duplicates. Our intent is to proceed with a single launch.
Discretionary safeguard: However, shortly before the first eligibility window opens, DelveSDK may, in its sole discretion, decide not to proceed with our intended dev-wallet purchase and/or decide to abort and relaunch a new token if we determine that a malicious actor has materially compromised launch integrity.
Examples of malicious action (non-exhaustive): “Malicious action” may include, without limitation:
a single actor purchasing an unusually large portion of supply before the first eligibility window with the apparent intent to prevent humans from having time to read this disclosure;
the bonding curve filling at an unusually high rate before the first eligibility window in a manner inconsistent with a fair-read window for humans;
coordinated behavior designed to exploit timing windows, overwhelm participants, or undermine the integrity of the eligibility program.
Notice mechanism: If DelveSDK determines that an abort/relaunch is necessary, DelveSDK will provide notice via Pump.fun comments shortly before the first eligibility window opens, using Solana confirmation time as the timing reference. We will make reasonable efforts to communicate clearly, but we do not guarantee that every participant will see the notice due to network, UI, or platform limitations.
Good-faith purpose: This safeguard is not intended to manipulate markets or act in bad faith. Its purpose is to preserve a fair-read window for humans, protect the integrity of the eligibility program, and remain aligned with our primary objective (the hackathon execution sprint).
Reset of timing windows: If a relaunch occurs, the timing windows reset and a new initial ineligible window applies to the new launch.
Acknowledgment: By buying or participating, you agree and acknowledge that this safeguard is a good-faith integrity mechanism (not bad faith), may be exercised at DelveSDK’s discretion, and may negatively affect participants.
6) DEMO OWNERSHIP VS. CUSTODIANSHIP
All demos, code, websites, branding, mechanics, and associated intellectual property are owned and retained by DelveSDK.
Community custodians receive custodianship only: operational responsibility and stewardship, not ownership.
Nothing in this disclosure grants equity, securities, IP ownership, or control rights over DelveSDK assets.
7) PERPETUAL REVENUE-SHARE
Perpetual revenue-share applies only to qualifying demo revenue generated by demos that:
are created and deployed before the hackathon deadlines (as determined by DelveSDK), and
remain operated under community custodianship rules (as defined below), and
generate qualifying revenue from binding/leasing/session-state monetization (or similar mechanisms), and
remain in compliance with safety, lawful-use, and custodianship requirements.
This revenue-share is non-transferable and non-assignable. It does not grant equity, securities, ownership of IP, rights in founder fees, rights to other products, or rights to any non-demo revenue streams.
8) POOL SPLIT AND ALLOCATION RULES:
8.1 Base split (per qualifying community-custodied demo)
For each community-custodied demo that produces qualifying revenue:
40% — Eligible Token Holder Pool (“Reserved Pool”)
40% — Custodian Pool (incentive for operating the demo)
20% — DelveSDK Pool (development, infrastructure, security, shipping)
8.2 What is “reserved in perpetuity”
Only the 40% Eligible Token Holder Pool is reserved in perpetuity as a category of allocation for qualifying demo revenue, subject always to eligibility, disqualification, compliance constraints, and administrative feasibility.
8.3 CUSTODIAN POOL STABILITY AND DISCRETION:
The custodian percentage will not be changed before the hackathon deadline.
After the hackathon deadline, DelveSDK may modify custodian incentive structures at its discretion (including percentages, selection rules, payout cadence, and operational requirements), provided the Reserved Pool concept remains as described above.
8.4 DELVESDK POOL USE:
DelveSDK may use its 20% at its discretion for build costs, security, infrastructure, contractor support, operational expenses, or to expand participation and custodianship.
8.5 DISQUALIFIED POOL AND REASSIGNMENT:
If an eligible participant becomes disqualified, the would-be share that would have gone to that participant becomes unallocated (“Disqualified Pool”). The Disqualified Pool may be handled as follows:
Founders’ personal share: founders may receive a share of the Disqualified Pool only to the extent stated by DelveSDK policy at the time, and not necessarily the entire amount.
Assignment discretion: founders may assign their received portion (if any) to DelveSDK, to custodians, to other eligible participants, to operational reserves, or to any other allocation at their discretion.
DelveSDK discretion: DelveSDK may also assign any portion of the Disqualified Pool it controls to expand participation, broaden custodian eligibility, fund operations, or create additional incentives.
No guarantee is made that Disqualified Pool amounts will be redistributed to remaining eligible token holders or to custodians.
8.6 ELIGIBILITY EXPANSION DISCRETION:
Co-founders may, at their discretion, expand custodian eligibility, adjust eligibility administration processes, and allocate DelveSDK-controlled pools (including DelveSDK’s 20% and any Disqualified Pool amounts under DelveSDK control) to expand participation—provided that the Reserved Pool concept remains as described above.
9) COMMUNITY CUSTODIANSHIP:
Custodianship means operating the demo and recruiting humans to use it. Custodianship is not promised developer work.
Custodians are expected to:
keep the demo active in public,
share it, recruit participants, and sustain usage,
provide practical feedback (bugs, clarity issues, misuse patterns), and
follow non-compete, safety, and lawful-use rules.
Inactivity rule: If there is 24 hours of inactivity (no meaningful use, no recruiting effort, or failure to source participants), DelveSDK may reassign custodianship to other eligible community members.
10) SUPPORT EXPECTATIONS (BEST-EFFORT, BUILD-FIRST):
These demos are shipped fast and may be rudimentary, unstable, or incomplete. DelveSDK will provide best-effort fixes as time allows while prioritizing shipping new demos and completing the hackathon sprint. Support is discretionary and depends on bandwidth and mutual trust.
11) COMMUNICATIONS AND SUPPORT BOUNDARIES (REQUIRED FORMAT)
We prioritize written updates and demo feedback loops. We do not provide individualized explanations, hand-holding, training, or private consulting. We may decline questions that are repetitive, speculative, adversarial, or unrelated to actionable demo feedback or custodianship.
WE RESPOND IN TWO PLACES ONLY:
Pump.fun livestream chat is the primary & fastest channel. This is where we are building & testing live. It is not customer support. It is for live coordination & immediate feedback while work is happening.
OnlyHodlers is for structured tickets only: https://onlyhodlers.com/
How to ask support questions (required format): Our preference is that you take all website materials made available (including patent-related materials and disclosures) and use Large Language Models (AI) to resolve your questions first. If you are still unsatisfied, post on OnlyHodlers.com:
your exact question, and
the AI’s answer you received, and
what part of the AI answer is unclear or wrong.
Support queries that do not include the AI answer are unlikely to receive a response.
No live Q&A formats. We are not going to do X spaces or town halls by request.
12) CUSTODIAN NON-COMPETE AND NON-CIRCUMVENTION
This section applies to any custodian or anyone with privileged access (private builds, credentials, unreleased links/endpoints, internal docs, or early demo access). It exists to prevent confusion, duplicated launches, brand dilution, and execution risk during the hackathon build cycle.
12.1 Restricted period
The restricted period begins when a person receives privileged access and continues until the later of:
the hackathon deadline, and
fourteen (14) days after DelveSDK publicly announces the end of the hackathon build cycle,
unless DelveSDK states otherwise in writing.
12.2 Restricted conduct
During the restricted period, custodians will not, directly or indirectly:
launch, assist, promote, coordinate, seed, or market any memecoin/token associated with any DelveSDK demo, feature, mechanic, naming, lore, demo website, or demo content (including “community,” “unofficial,” “parody,” or “derivative” launches);
use DelveSDK demos or privileged information to build, release, operate, or market a substantially similar competing demo/system/service;
exploit non-public information (mechanics, configuration values, UI flows, pricing logic, endpoints, internal links, partner conversations, sponsor discussions, roadmap notes);
approach partners, streamers, sponsors, advertisers, platforms, or service providers introduced through DelveSDK communications for the purpose of offering a competing build, deal, or launch;
create confusion about affiliation or present any independent launch as approved, endorsed, partnered, sponsored, or “officially connected” to DelveSDK.
12.3 Permission for any associated launch (post-hackathon only)
Any permission to launch an associated token is solely at DelveSDK’s discretion, must be explicit and in writing, and will not be granted before the hackathon deadline. If granted later, DelveSDK may impose conditions and may revoke permission prior to launch if risk or confusion arises.
13) ADULT / NSFW CONTENT SAFETY
Adult/NSFW streaming using DelveSDK demos requires prior written permission from DelveSDK.
No custodian or participant may create, host, feature, or facilitate NSFW/adult content involving anyone under 18 (or below the age of majority in their jurisdiction if higher). All adult/NSFW activity must comply with applicable laws and platform rules, including age verification and required recordkeeping where applicable.
Violations result in immediate removal from custodianship and loss of access.
14) BUILD STREAMS AND CONTENT BOUNDARIES
We may stream during the build cycle. These streams are primarily to demonstrate builds, show demos running, gather feedback, and recruit custodians.
The build streams will not include team faces and will not be treated as a teaching session. We may play music. We may chat for entertainment purposes only. Any technical or operational communication with custodians may occur through other channels at our discretion.
15) PATENT FILING NOTICE:
DelveSDK intends to work on filing a provisional patent application related to aspects of the system described in the demos and disclosures.
A provisional filing:
does not mean a patent has been granted,
provides no guarantee of exclusivity,
may never mature into an enforceable patent, and
may be challenged, opposed, narrowed, or rejected.
The demos and written updates are the sprint output. Patent-related materials are informational artifacts, not a promise of rights or outcomes.
16) ARG LOGS & LORE (ALTERNATE REALITY GAME)
Some aspects of branding, streams, community engagement, and story framing may be presented as an ARG (Alternate Reality Game) for entertainment (including “Logs & Lore,” character framing, jokes, and narrative elements).
ONLY posts titled “MEMO” providing development updates are intended to be non-fiction. Everything else may be fictionalized, stylized, or lore-first.
“It’s not a lie, if you believe it” is an ARG framing device.
17) CLOSING ACKNOWLEDGMENT:
By buying or participating, you acknowledge:
you read this disclosure first,
eligibility is narrow and may be lost permanently due to timing or wallet mixing,
no buy/sell signals are being provided,
custodianship is stewardship only and does not transfer demo ownership,
the Reserved Pool is subject to eligibility/disqualification and feasibility limits, and
the team’s priority is the hackathon execution sprint.
Co-founders:
Name: R.K.
Name: K.W.