Whitepaper

What this is

Cashed is a launchpad shaped like a map. Named businesses come from OpenStreetMap: the café on the corner, the barber two doors down. A storefront can be associated with one verified community coin created through this application on Pump.fun.

The OpenStreetMap node, way or relation is the storefront’s identity. This registry rule is enforced by the application; it does not prevent someone creating other tokens elsewhere with a similar name.

Opening a storefront

Pick a business, customize its name, ticker, description and sign, and optionally add a first buy. The server verifies the business with OpenStreetMap, reserves its registry entry, pins the image and metadata to IPFS, and creates a transaction using Pump’s official SDK.

Your wallet pays in SOL and approves the transaction. Token creation and any first buy happen atomically. First buys allow up to 1% slippage. Network fees, account rent and Pump’s current protocol terms apply. The app adds no launch fee.

A coin is listed only after the exact transaction is finalized and its Pump bonding curve, mint and business fee recipient are verified. The original Pons/Robinhood Chain coins are not migrated or represented as Solana launches.

Where the fees go

Each business has a dedicated fee-recipient wallet controlled by Cashed. Creator fees accrue in Pump’s protocol vaults, including the relevant PumpSwap vault after graduation. A wallet balance and protocol-vault balance are distinct; both appear on the token panel when live data is available.

Pump sets its fee schedule. This application does not promise the original platform’s 0.7% rate. Market figures are indicative reserve-based prices in SOL, not guaranteed execution quotes.

Claiming fees

Connect a Solana wallet and sign in. Administrators can authorize that wallet to claim for specific businesses. An authorized wallet uses Claim Fees on the business page. Administrators can claim for any business, including hidden listings.

The backend checks the signed session and business-specific authorization, constructs the collection and payout, and checks permission again before signing with the encrypted business key. The payout destination is always the authenticated claimant’s wallet. The browser cannot supply another destination or modify the transaction.

Fees from Pump and PumpSwap are collected, wrapped SOL is unwrapped where needed, and the approved SOL amount is transferred in one transaction. The claimant pays network fees and any required temporary account rent. A small rent-exempt reserve remains in the business wallet. Newly accrued fees after preparation remain available for a later claim.

Claims are serialized per business and recorded for recovery. Revocation blocks future authorization; it cannot undo a transaction already signed and broadcast. Cashed retains custody. No private key or ownership transfer occurs.

Owner verification and removal

Business owners can submit an access or removal request from the storefront panel with their role, contact details and evidence. A human administrator reviews the request. Approval of a request does not automatically grant fee permissions; permissions are an explicit, separate administrative action.

An approved removal hides the listing from public discovery. It cannot delete a public blockchain token. Administrators retain the ability to manage fees for hidden listings. Long-term unclaimed-fee policy must be established by the operator.

Trust and limitations

These tokens are memes, not equity, revenue shares, ownership rights or an endorsement by a business. They may lose all value. OpenStreetMap identity does not prove business ownership.

Traders retain control of their own wallets. Business fee wallets are custodial: the platform operator controls their keys and withdrawal authorization. Administrators can redirect available fees to their own connected wallets, as reflected in the audit log. This is not a trustless on-chain whitelist.

Database records and encryption keys require separate protected backups. Service availability, RPC accuracy, map data, storage retention and administrator decisions remain operational dependencies.

Protocol references

Official Pump protocol documentation ↗

Map data © OpenStreetMap contributors · OpenFreeMap. Application token addresses and fee-recipient addresses appear on each verified storefront.