GOFER is a Solana operations desk with three bounded workers: Observe reads public account records, Reconcile compares expected payments with transaction evidence, and Prepare assembles a SOL batch for the wallet owner to review.
The desk executes deterministic checks against Solana RPC. It does not impersonate an LLM, invent jobs or show simulated payments as real. The optional eve reasoning agent uses the same read-only tools when an operator configures a model provider.
GOFER is an independent project. It is not operated by Solana, Pump.fun or your wallet provider. No token contract or token reward is configured.
Observation reads a finalized SOL balance, account owner, executable flag and up to 12 recent transaction signatures. Each report identifies its network, slot and observation time. The on-curve check describes the address, not the safety of its owner.
When refresh is enabled, the desk rechecks the selected account every 60 seconds while this browser tab is visible. Closing the tab stops this monitoring. There is no claim of unattended server monitoring in this release.
A history lookup can fail independently of a balance lookup. GOFER retains that distinction. Missing data is not replaced by invented activity or a zero balance.
Solana RPC: getSignaturesForAddress
A campaign contains 1 to 8 distinct on-curve recipient addresses and positive SOL amounts. CSV columns are label,address,sol,signature; label and signature are optional. Amounts support at most 9 decimal places. Duplicate recipients must be combined.
The worker checks supplied signatures and, for rows without one, up to 8 recent payer signatures. Only successful finalized direct System Program SOL transfers with the exact payer, recipient and amount qualify. An instruction cannot satisfy two rows in the same report.
Unverified does not mean unpaid. Older, inner-instruction, split and token transfers are outside this check. A matching transfer is evidence of movement, not proof that a particular off-chain invoice was fulfilled. Inspect the explorer record before deciding to pay.
Reconciliation never automatically selects unpaid recipients or sends funds.
GOFER prepares a single transaction containing at most 8 direct SOL transfers and a job-bound memo. The total batch limit is 10 SOL. SPL tokens, swaps, recurring transfers and unattended spending are not included.
The review shows the full payer and recipient addresses, network, exact amounts, total, RPC network fee, estimated signer SOL change and simulation result. GOFER adds no service fee. A simulation can pass and execution can still fail when state changes.
The browser checks that the transaction matches the displayed batch. The wallet must sign exactly that message. GOFER verifies the returned signatures and persists the signature and message before requesting broadcast. If saving fails, no broadcast is requested. An uncertain response remains pending; there is no automatic replacement payment.
A successful finalized chain transaction must match the stored message before a record is marked finalized. A signature alone is not completion. Unresolved jobs block another preparation of the same job identifier.
This release has not had an independent security audit or a funded mainnet acceptance test. Use devnet and a separate wallet for testing. Never share a recovery phrase. GOFER does not hold keys or guarantee recoverability of browser-local records.
Saved jobs and run records are stored in this browser, not in a shared public database. Export JSON to keep a copy. Clearing browser storage removes local records and pending-operation protection. Do not clear it while a payment is unresolved.
JSON exports are records, not cryptographic certificates of application provenance. Local storage can be modified. The transaction signature and the chain are the authority for a transfer.
Public addresses and transaction signatures are sent to the configured Solana RPC through the GOFER server. Recipient batches reach that server for preparation and verification; there is no intentional application database retention. Hosting and RPC providers may retain request logs.
Never place private keys, seed phrases or confidential personal information in labels. Labels are local metadata; the on-chain memo contains only the GOFER job identifier.
The optional reasoning service is built with eve. Its authored tools can inspect wallets and reconcile payment evidence. Shell access, file tools and other default tools are disabled. The reasoning agent has no signing or broadcast tool.
The public desk's operational workers run without model credits. Natural-language reasoning requires a separately configured AI Gateway provider and protected operator access. No provider key is copied from another project.
Model output is interpretation, not transaction authority. The app's deterministic amount, network, message and signature checks remain outside the model.
MotionSites is connected to the development workflow for design references. It is not connected to user wallets and does not receive payment data.