PENNYSTOCK / DOCUMENTATION
Follow the treasury.
Launch around a penny stock. Set the creator-fee allocations once. Follow stock accumulation, eligible holder rewards and verified burns through finalized receipts.
Launch Penny Fund. Build its stock treasury.
Choose an eligible stock whose underlying exchange share trades below $5, name your memecoin and review the launch in your wallet. “Penny Fund” is an example name, not an existing launched coin. The token trades against SOL on Pump.fun. Its creator fees are received by the declared custody treasury and accounted for under the coin’s locked stock-treasury, holder-reward and buyback allocations.
Pairing describes the treasury strategy. It is not a stock-quoted liquidity pair, a price peg or a claim on shares. Only admitted, issuer-verified Solana stock tokens are supported; entering an arbitrary ticker does not make its shares available onchain.
At the suggested 70 / 20 / 10 preset, 1 SOL in collected creator fees funds 0.7 SOL of retained stock, 0.2 SOL of stock-token holder rewards and 0.1 SOL of launched-coin buybacks. Separately funded reserves cover network fees and account rent. The eventual token quantity comes from the executed market price and finalized receipt. Unspent budgets remain assigned to their original stock.
One coin. One selected stock.
The launch flow creates a SOL-quoted coin on Pump.fun and assigns all of its creator fees to the declared treasury. A memo binds the network, coin mint, stock mint, treasury and canonical version-2 fee-policy hash to the launch receipt. The allocation, weekly calendar, weighting, exclusions and minimum payout are locked at finalization. The wallet reviews and signs the transaction after simulation.
A lookup-table setup transaction keeps the subsequent coin creation and treasury fee assignment within Solana’s transaction size limit. Account rent and network fees are shown separately; PennyStock adds no launch charge. The worker verifies the finalized fee-sharing account before registering the coin.
Fresh installations default to devnet; the service panel below reports this deployment’s network. Test assets are identified explicitly. Mainnet admission checks independent underlying-share pricing, current issuer eligibility, exact mint identity and DEX liquidity. Public spending remains disabled until hosting, signing and funded acceptance are complete.
Automatic claims. Automatic purchases.
The worker checks for creator fees, claims them and waits for finalization. Only verified fee credits become a purchase budget. Unrelated SOL deposits stay outside that budget. Once the minimum purchase size is reached, the worker requests an exact-input route into the coin’s selected stock token.
Before signing, it checks the treasury, output mint, minimum received, slippage, price impact and operating reserve. It simulates the exact transaction and checks for unrelated treasury asset changes. A user-controlled signer authorizes the operation. The signed transaction is saved to persistent storage before broadcast.
A timeout leaves the transaction pending. The worker follows its existing signature rather than issuing another purchase. Confirmed receipts update the budget exactly once. Failed transactions leave the purchase budget intact; an unverifiable receipt pauses execution.
Real stock routing uses Jupiter on Solana mainnet. Devnet uses an explicitly configured Pump test-token curve, representing no shares. The full cycle passes against Pump’s unmodified deployed programs in a local devnet fork, including automatic claiming, token delivery and restart recovery. A separate mainnet-fork test executes a live Jupiter SOL-to-AMC route and verifies the exact delivered stock-token balance. Both use local funds; neither is a public mainnet stock purchase. The worker accepts only direct SOL-to-stock legs. If the best quote uses another token, it tries bounded venue filters; an unavailable acceptable route leaves the budget waiting. Simulation still enforces the full cost cap.
A funded public-devnet cycle has now finalized with zero dev buy at launch, a separate test trade, an automatic fee claim and an automatic test-asset purchase. The worker spent exactly the verified 296,297-lamport fee credit and recovered the pending purchase after reopening its journal. This used test tokens and a local worker, not a public mainnet stock purchase.
Devnet launch receipt ↗ · Fee claim ↗ · Test-asset purchase ↗
Mainnet creation, verified.
The operator's PennyStock Test / PNYTEST launch finalized on Solana mainnet with zero developer buy and zero creator holdings. Its creator fees are assigned immutably, 100% to the declared test treasury. Setup and creation cost 0.01450316 SOL. No stock purchase was included; this operator test does not enable public launches or certify the hosted stock-purchase pipeline.
One fee stream. Three separate budgets.
Creators choose percentages totaling exactly 100%. The suggested preset is 70% stock treasury, 20% holder rewards and 10% buybacks and burns. The allocation applies only to collected creator fees, not trading volume or every fee charged by Pump.fun.
The retained-stock budget buys and keeps the selected stock token. The reward budget buys that stock token for eligible holders of this launched coin. The buyback budget buys this launched memecoin; a separate verified SPL burn destroys the purchased tokens. A buyback alone is not a burn.
Each finalized claim credits the three budgets with integer accounting. Up to two lamports of allocation rounding remain reserved until later claims. Unrelated deposits never become fee income. No worker withdrawal endpoint or cross-budget spending is provided. Network fees and account rent require a separately funded operating reserve. Swap spread, venue fees, slippage and price impact affect delivered tokens; receipts disclose actual input, output and network fees.
Existing version-1 launches retain their original 100% selected-stock treasury terms, including the published PNYTEST receipts. New launches cannot alter them. Creator fees still enter a single declared custody wallet on Pump.fun; the allocation hash is committed onchain and enforced by the worker and signer, rather than by a new escrow smart contract. Wallet custody remains an operator trust assumption.
Weekly, funded stock-token rewards.
Weeks run Monday 00:00 UTC to Monday 00:00 UTC. Each eligible wallet’s weight is the sum of its launched-coin balances multiplied by the seconds held during that week, across all of its token accounts. The first period begins at launch. Purchases enter the week of their finalized onchain block time. No PENNY holding is required or substituted for holding that launched coin.
The indexer replays every produced finalized block from the verified creation slot. Token-balance changes, block parents and hashes must match the durable checkpoint. Block timestamps are clamped to the preceding indexed timestamp if they move backwards. Missing history, missing token metadata or a pruned archive pauses settlement; current snapshots never substitute for complete history.
Under ordinary-system-wallet-v1, liquidity and program vaults represented by off-curve authorities or program-owned accounts are excluded. The custody treasury, burn addresses and the additional exclusion list committed at launch are excluded as well. Recipients must be ordinary on-curve system wallets with current issuer-specific distribution eligibility. Additional custodial or pool wallets must be identified in the published exclusions before launch. Issuer review is not a promise of permissionless stock-token transfers.
At week end, funded stock tokens are divided in proportion to eligible balance-seconds, with integer rounding held for the following week. The minimum distribution shown at launch is a per-holder amount in selected stock tokens. Smaller entitlements accumulate across weeks until that threshold is reached; this is not a token-price or SOL threshold. No qualifying weight means funding rolls forward. Outstanding entitlement, retained treasury inventory and other coins’ inventory cannot fund a different recipient or buyback.
A missing recipient eligibility review pauses that period for review. Eligibility is checked again before transfer. Only supported token programs and extensions can execute: fee-on-transfer, transfer hooks or other unsupported issuer extensions leave funds pending with an explicit reason. A completed distribution requires the exact recipient’s finalized token credit; completed periods and individual delivery receipts are shown in the treasury ledger. Yield, token quantity and distribution frequency are not guaranteed.
PENNY’s own creator fees.
Creator fees generated by the PENNY token are separate from the fees of coins launched through the platform. Each launched coin retains its own immutable fee policy; version-1 launches keep their 100% selected-stock treasury terms. PENNY’s own proceeds can fund developer incentives, trader rewards, PENNY buybacks and burns, and additional stock-token purchases for selected leading launches.
These ecosystem programs are intended policy, not active distributions. Allocation weights, qualifying activity, anti-abuse controls, launch selection and payment schedules must be configured and published before execution. Launch-level holder rewards and coin burns do not activate PENNY ecosystem spending. PENNY’s separate ecosystem execution remains disabled until its policy is approved, configured and verified funded. Only confirmed transfers and burns may appear as completed activity.
Know what the stock token represents.
The directory combines OTC Desks discovery, an independent Pump QuoteControl read and DexScreener market quotes. The directory’s under-$5 filter is a stock-token unit quote. Mainnet launch admission separately requires a fresh Alpaca IEX trade and available recent ask below $5 for the mapped underlying share. Rebasing, multipliers and shallow pools can create differences.
Backed products are tracker certificates; Backpack publishes separate tokenized-security terms. A memecoin holder does not receive shares, voting rights, redemption rights or ownership of treasury assets simply by holding the coin. Stock-token eligibility and regional restrictions still apply.
The treasury signer controls its assets. A verified fee assignment does not make the stock-buying policy itself enforceable by a PennyStock smart contract. Do not describe the treasury as trustless.
Check the running service.
These checks read the deployed settings, RPC network and authenticated worker readiness. A connected configuration does not establish a completed public-chain acceptance test.
Checking the deployment.
Reading the deployed configuration and authenticated worker response.
Where each service runs.
Vercel hosts the website and wallet transaction endpoints. Railway hosts the persistent automation worker, with one replica and a mounted data volume. The worker database must not run inside Vercel’s ephemeral filesystem.
Set the RPC and network separately on both services. Keep the treasury address public. Operator signing can run inside the persistent worker using its protected secret, or through an existing managed signing service. The worker verifies the key’s public address, network, registered market and spending budget. No private key belongs in Vercel, the browser, a NEXT_PUBLIC variable, GitHub or chat.
The repository’s automation guide lists every variable and deployment command. The mainnet runbook separates operator setup, execution acceptance and public activation. Configuration alone is not a completed transaction test.