Project Handover Agreement
Parties
This document is made between regulate.fun, styled the Memecoin Exchange Commission (the "Commission"), and the holder of the Solana wallet Dc7GWonCzvmwgdorP2puaq6uggKU54GMUhK8AbJPHfVE (the "Developer") in case RF-2026-0048. PUP FUEL ($PUPFUEL), token mint AzJdTPbo9jo2xgZLdVbkEpC7Yv8WXtSGadzHGesEpump, together with everything listed in Schedule A, is the "Project".
Background
A. The Commission is an independent, community-run reputation registry. It is not a government agency, regulator, court or law-enforcement body, and nothing in this document is a government order, a court judgment, or legal or financial advice.
B. The on-chain record in RF-2026-0048 shows the following:
(1) The wallet Dc7GWonCzvmwgdorP2puaq6uggKU54GMUhK8AbJPHfVE created and deployed PUP FUEL ($PUPFUEL), token mint AzJdTPbo9jo2xgZLdVbkEpC7Yv8WXtSGadzHGesEpump.
(2) On 2026-10-20 the wallet registered $PUPFUEL on the commission's Regulated list.
(3) On 2026-10-26 the wallet sold 17,000,000 $PUPFUEL: 1.73% of total supply and 100% of its holding, for about 6.55 SOL ($670.27). Transaction: 2cvKPeHXQX26rhtAWk1vZq9pBJoM7TNZUVAbiCswAF8DzMWQuSVHhvKFuKTMhzpe7haKVMxpJLxNRLdLjbsmt6pp.
(4) On 2026-10-26 the commission suspended $PUPFUEL's regulation.
(5) On 2026-10-26 the commission charged the wallet in RF-2026-0048 with a fine of $166.
(6) On 2026-10-27 the fine of $166 was paid and the case settled.
C. The Commission has published the findings and allegations set out in Schedule B. By entering this agreement the Developer neither admits nor denies them.
D. The Developer has chosen to hand the Project over to the Commission, so that it can be run in holders' interest and its proceeds can pay the outstanding fines in the cases listed in Schedule C and fund restitution to victims.
1. A voluntary agreement
1.1 The Developer enters this agreement voluntarily. The Developer was free to decline it, and declining would not have added any charge, fine or other penalty to the case.
1.2 The Developer accepts this agreement by signing its SHA-256 fingerprint with the wallet named above, from the case hub at regulate.fun/hub. That signature is the Developer's signature on this agreement.
2. The handover
2.1 Within 7 days of signing, the Developer transfers to the Commission sole control of every asset in Schedule A, including logins, recovery email addresses and phone numbers, two-factor devices and backup codes.
2.2 Credentials and keys are delivered privately through the case hub or another channel the Commission names, never in public. The Commission replaces every credential when it receives it.
2.3 The Commission confirms each asset on the public outcome record when it holds sole control of it. The handover is complete when every asset in Schedule A is confirmed.
3. Undertakings of the Developer
3.1 The Developer has disclosed every account, domain, server and wallet used for the Project, and has or will obtain control of each asset in Schedule A.
3.2 After the handover the Developer keeps no copy of any credential or key, and does not access, recover or try to recover any transferred asset.
3.3 The Developer does not present itself as the developer, operator or representative of the Project, or as affiliated with regulate.fun, and does not launch or promote any token presented as the Project or its successor.
3.4 The Developer cooperates with the reasonable steps a registrar or platform requires to complete a transfer.
4. Undertakings of the Commission
4.1 The Commission runs the Project in good faith, in the interest of its holders.
4.2 Proceeds the Commission receives from the Project, including creator fees, are applied first to the fines charged in the cases listed in Schedule C, in the order listed. Each fine is paid in full once the proceeds held cover it, and that case is then settled as paid; 90% of each such fine goes to that case's verified victims under Commission Policy §7. A case in Schedule C that is dismissed, or whose fine its own defendant pays, is passed over. Once every case in Schedule C is closed, 90% of further net proceeds is paid into the victims' fund and the rest covers the cost of running the Project and the Commission. All proceeds are published on the outcome record.
4.3 The Commission publishes this agreement and its performance on the public outcome record, and records the Developer's cooperation in RF-2026-0048.
4.4 Once the handover is complete, the Commission does not open a new case against the Developer over the conduct described in RF-2026-0048 and Schedule B. New conduct may be the subject of a new case.
4.5 Once the handover is complete, the Commission lifts the suspension of $PUPFUEL's regulation, and the Project is regulated under the Commission's administration. The Developer's own standing is restored: the Developer may publish on regulate.fun and apply to register other coins under the Regulated Standard, screened in the usual way with this agreement on its record.
4.6 Where the Commission has reported the Developer's wallets to exchanges or wallet providers, it informs them of this agreement and its completion on request. The Commission makes no representation about how any third party will act.
5. The public record
5.1 The record of RF-2026-0048, including its findings and allegations, remains public. It is updated to show this agreement, and allegations remain marked as allegations.
5.2 The Commission does not publish credentials, private keys or personal information received under this agreement.
6. Non-performance
6.1 If the handover is not complete within 7 days of signing, or the Developer takes back control of any transferred asset, the Commission may record this agreement as breached on the public outcome record and give notice on its channels. Sections 4.4 and 4.5 then no longer apply.
7. General
7.1 This is the whole agreement between the parties about the Project. Its text is fixed by its SHA-256 fingerprint; any change needs a new agreement.
7.2 If any part of this agreement cannot be enforced, the rest still applies.
7.3 The Developer may take independent legal advice before signing.
Schedule A
| # | Item | Status |
|---|---|---|
| A1 | Creator wallet and creator fees. The $PUPFUEL creator fees redirected to a wallet the Commission designates or, where that cannot be done, sole control of the creator wallet Dc7GWonCzvmwgdorP2puaq6uggKU54GMUhK8AbJPHfVE. Any $PUPFUEL tokens or fees that reach a Developer-controlled wallet after signing are sent on to the Commission. | outstanding |
| A2 | Domains. Every domain used for PUP FUEL, transferred to a registrar account the Commission controls. | outstanding |
| A3 | Servers, hosting and code. Every server, hosting account, website, bot and code repository used for PUP FUEL, with all credentials. | outstanding |
| A4 | Social media accounts. Every social media account used for PUP FUEL (including X, TikTok, Instagram and YouTube), with ownership, login email and two-factor control. | outstanding |
| A5 | Community channels. The owner role in every Telegram, Discord or other community group and channel for PUP FUEL. | outstanding |
| A6 | Brand assets. Logos, artwork, source files, and any brand or trademark registrations for PUP FUEL. | outstanding |
Schedule C · Cases whose fines the proceeds pay
| # | Case | Status |
|---|---|---|
| C1 | RF-2026-0049: Regulate Fun v. HatRaDb7hhenHCkKJyXNzc9Adm95oRJDtHvAx7tLUUN4 | under investigation |
| C2 | RF-2026-0050: Regulate Fun v. Dz9kKkXGBTkp7cAbdfwL9Rcm8K6fAAShcAvf4gYnMJ7U | under investigation |
| C3 | RF-2026-0053: Regulate Fun v. 3Y8jEq5JKQdxSPLsEnwh1KyR6XUG6YddhgPfmtKoRyVd | fine $689 outstanding |
| C4 | RF-2026-0054: Regulate Fun v. 5YApab7q92dwGWWc5xuALaKhtMHy7GyPwAQvnVMWGFRS | under investigation |
| C5 | RF-2026-0056: Regulate Fun v. 5YApab7qq2dwGWWc5xuALaKhtMHy7GyPwAQvnVMWGFRS | under investigation |
Schedule B · Findings and allegations on the case record
- Evidence, 2026-10-26. Pup Fuel, and its dev, are associated with another token under investigation, Barking Puppy RF-2026-0022. A serial social media hacker further investigated for a number of pump-and-dumps from February 2026. regulate.fun/cases/22
- Finding, 2026-10-26. Pup Fuel and its developer allegedly misrepresented their affiliation with regulate.fun in an attempt to coordinate a rug pull targeting the token. The Commission regards these allegations with the utmost seriousness and maintains a zero-tolerance policy toward misrepresentation, market manipulation, and violations of the regulatory standards applicable to entities operating under its oversight.
- Finding, 2026-10-27. 91.7% of content posted by, and associated with, Pup Fuel is deemed AI.
Message signed by the defendant wallet
regulate.fun: signature on RF-2026-0048-A2 I, the holder of this wallet, sign the Project Handover Agreement in case RF-2026-0048. Wallet: Dc7GWonCzvmwgdorP2puaq6uggKU54GMUhK8AbJPHfVE Document SHA-256: 2948b88277c5dccc1ef50f3474f6a2c200f3be8e0bf5fbaab5f86f44c7a7de03 I have read the full text and I enter it voluntarily. This signature does not trigger a transaction or cost any fees. Nonce: d401dc401727018eae23d12a1455bc60
The fingerprint is the SHA-256 of the exact text at regulate.fun/outcomes/RF-2026-0048-A2.txt. The signature is an ed25519 signature by the defendant wallet over the message above, which names this fingerprint, and can be checked with any Solana signature tool.
regulate.fun is an independent, community-run reputation registry. It is not a government agency, regulator, court or law-enforcement body, and nothing in this record is a government order, a court judgment, or legal or financial advice.