Devnet Funding

Read balance and obtain devnet funding

A funded development account lets a user test transaction fees and a tiny SOL transfer without using mainnet funds. Devnet SOL is a testing resource, not an earning. Funding does not establish wallet ownership inside EdgeORE, and a public account balance does not establish authorization. The address provided in the project session can be queried publicly, but the app must use the account actually returned by the wallet for signing.

Read the correct cluster

Always name devnet beside the RPC endpoint and explorer link. Solana accounts can have different balances on different clusters. A mainnet explorer page for a development account is not a devnet funding result. Preserve the exact endpoint, request and observation time because balance is a time-dependent value. A screenshot without a cluster label is weak evidence.

curl --fail-with-body --max-time 30 https://api.devnet.solana.com \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"getBalance","params":["73Cc84sjGtk3RNSVoEres4PLMcZZtg4n46kQUzJnR93n",{"commitment":"confirmed"}]}'

This is a public read. It changes no account and asks for no signing key. If the connection fails, save the failure as Unavailable — connection failed. Do not convert a missing response into a zero balance. If the RPC returns a structured error, retain that error separately from a successful response whose value is actually zero. Those cases lead to different next steps.

Handle units exactly

RPC balances are expressed in lamports. One SOL is one billion lamports. Display conversion should preserve the fractional precision rather than using integer division that truncates a small balance. If constructing a textual fractional part manually, pad it to nine decimal places before trimming trailing zeros. For transfer input, use the existing exact decimal parser rather than a floating-point multiplication.

A balance is not a spend authorization. Fees, reservations and other pending operations can reduce what is safely available. EdgeORE's daily budget is another independent policy bound. A user can have sufficient balance but still be blocked by budget or blockhash validity. Explain the specific gate rather than replacing every refusal with Insufficient funds.

Fund through a development channel

Use a legitimate devnet faucet and follow its limits. Confirm the account you fund matches the intended test wallet. Faucet availability and rate limits vary; do not promise a fixed amount or instant success in documentation. After funding, query again and preserve the actual result. If a wallet screenshot is used as supplemental evidence, identify its cluster and time and avoid presenting it as an RPC observation.

Do not import a production wallet into a hosted development environment merely to obtain a known address. Create or use a development-only account appropriate for the test. The public address may appear in evidence, but the private material must remain within the test wallet's security boundary. A funded account from someone else is not yours to sign with.

Close only the funding check

The acceptance criterion is a successful devnet observation that the intended account has enough test lamports for the reviewed transfer and fees. This closes funding, not MWA connection or transaction confirmation. If public RPC is blocked from one machine, another legitimate environment can read it; record that environment. A failed network path should never become a fabricated balance or a claim that the account is unfunded.

---

Wiki home · Qualification updates · Sources and credits