EarnPatch.

Wallet-free evaluation · real CSV processing

One release.
Follow every side.

Use fictional roles and balances to inspect the complete commercial workflow. Historical NEAR transactions are separately verifiable. No wallet, faucet, private key or database setup is needed for local evaluation.

1. Commission and publish the source release

The main application and Studio share one workspace. A new EarnPatch session begins with an open SafeShare invitation. To write your own brief, select Merchant in Studio and confirm Reset this workspace; this deliberately starts a new draft and preserves earlier workspaces.

  1. Open Commission & delivery. Review the existing invitation or reset as Merchant and create a brief.
  2. Switch to Developer, accept the terms and submit the provided SafeShare release.
  3. Switch to Merchant, review the release and acceptance criteria, check the review box and approve.

The accepted template performs SafeShare exports. Uploaded code is identified by a hash; arbitrary uploads are not hosted or executed.

2. Choose the settlement path

Native evaluation: open Customer, buy a simulated 0.01 NEAR use, preview and redact a CSV, confirm the policy and download the actual sanitized result. Developer share is 20% until the 0.004 cap. Native earnings are visible in the main application and Studio.

Independent Paperlane integration: open Funding & integration. As Merchant, import the published release; as Developer, accept the separate token agreement (0.007 TestEPUSD/use, 25%, 0.003 cap). Use Open token-checkout Paperlane to hand off this exact workspace.

In Paperlane, purchase as the sample customer, load a CSV, review columns, select redactions, confirm the policy, process and download. Return to Finance to inspect token allocations and simulated withdrawals. Native uses are not token credits. TestEPUSD has no redemption value.

3. Inspect funding and proof separately

Finance also demonstrates conditional development grants. Grant commitments, release and refunds are separate from customer export purchases and do not create export credits.

Inspect genuine Testnet evidence: the 42 historical transaction identities retain their exact success/rejection/refund labels; the completed G45 registration has a separate record. Fresh state reads are anonymous and read-only.

Workspace and recovery rules