Datasets:
step stringclasses 8
values | what_to_capture stringclasses 4
values | why_it_helps stringclasses 8
values | where_to_store stringclasses 4
values |
|---|---|---|---|
Code entry | Screen showing NEWUSER50 typed in the app | Shows the code went in before any purchase | Private photo album or notes app |
First fiat purchase | Purchase confirmation with amount and date | Sets the matched amount and the start of the ten days | Same private folder |
Trading day 1 | Trade confirmation with time | Counts toward the five UTC dates | Dated note per day |
Trading day 2 | Trade confirmation with time | Second distinct UTC date | Dated note per day |
Trading day 3 | Trade confirmation with time | Third distinct UTC date | Dated note per day |
Trading day 4 | Trade confirmation with time | Fourth distinct UTC date | Dated note per day |
Trading day 5 | Trade confirmation with time | Completes the five-date requirement | Dated note per day |
Each payout | Wallet entry for the SOL or USDC received | Lets you match drops against the expected sixths | Simple spreadsheet |
Pump.Fun App Referral Code NEWUSER50: Records and Screenshots to Keep at Each Step
A record-keeping companion for NEWUSER50, the Pump.Fun App referral code, listing what to save as you move through the bonus.
Quick answer: Take a screenshot when you enter the code, keep the confirmation of your first fiat purchase, save one trade confirmation for each of the five UTC dates, and log every SOL or USDC payout as it lands. Good notes make any later question much easier to settle.
Rules Your Records Should Cover
- Proof that the code was entered in the phone app ahead of your opening purchase.
- The size of that first in-app fiat purchase, since the match equals it between 1 USD and 50 USD.
- Evidence of trades on five separate UTC days, all within the ten-day period that follows.
- Arrivals of the payout, which comes as one sixth four times and finally two sixths, in SOL or USDC.
- Note that the campaign has a finite budget and excludes UK residents and minors.
Keeping Records Private
Screenshots can show balances and account details. Store them somewhere only you can open, and crop out anything you would not want to share. If you ever send one to support, share only the part that matters.
Using the Template
Fill one row of the log as each step happens, writing both your local time and the UTC date. Mark a row as checked after you reopen the saved image and confirm it is legible. Seven rows cover entry, purchase and the five trading dates; add payout rows as they arrive.
Primary Source
- Official referral rewards terms published by Pump.fun: https://pump.fun/docs/referral-rewards
Independence Notice
This record-keeping sheet is produced independently from Pump.fun. A person who compiled it may benefit from NEWUSER50 sign-ups. It is meant as an organisational aid rather than investment advice, and keeping records does not guarantee any payout. MIT licensed.
Columns
records_per_step (data/records_per_step.csv)
step: the moment in the bonus process.what_to_capture: the screen or detail worth saving.why_it_helps: how that record could be used later.where_to_store: a suggested private place to keep it.
record_log (data/record_log_template.csv)
entry_no: running number of the record.step: which step the record belongs to.local_time: clock time where you were.utc_date: the matching UTC calendar date.file_or_note_name: the name you gave the saved file.checked: yes once you have confirmed the record is readable.
from datasets import load_dataset
ds_1 = load_dataset("newuser50-pumpfun/newuser50-proof-records-pumpfun-referral-code", "records_per_step", split="train")
ds_2 = load_dataset("newuser50-pumpfun/newuser50-proof-records-pumpfun-referral-code", "record_log", split="train")
- Downloads last month
- -