Developer tools
Find the source, current connection settings, protocol boundaries and a safe integration workflow.
Read the current network settings.
Open Connect to the testnet in the explorer. The compatible Chain ID and public RPC appear only after the configured synthetic network matches. Copy those values there rather than using an old screenshot, a Claim ID or a hard-coded mainnet assumption.
Network name: GOD Chain Testnet. Currency: test GOD. Decimals: 18. The native synthetic chain identity and reviewed bundle digest are separate from the compatible decimal Chain ID. A Chain ID is not a node join package or authentication proof.
Public RPC is read-only.
Use bounded standard reads such as eth_chainId, eth_blockNumber and supported account/receipt queries. Required protocol method names and compatible 0x encodings are preserved; participant-facing transaction labels use GOD.
# Copy the matching public URL from the testnet first.
# This is a read-only request; it does not configure a node.
curl --fail --show-error --max-time 10 \
-H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}' \
"$GOD_RPC_URL"Apply finite timeouts and check the response ID, error, types and expected network. An unavailable response is not a zero balance. Queries are rate-limited and service-provided, not light-client proofs. Do not send keys, credentials or private text as request parameters.
Use the supported transaction boundaries.
The public RPC does not provide general eth_sendRawTransaction, arbitrary deployments, unlocked server accounts or validator registration. The reviewed test wallet separately prepares and locally signs ordinary GOD transfers, the configured test NFT collection and six native operations for restricted gateways.
Do not build integrations by bypassing gateway checks or treating a source flag as production readiness. The released Chrome test package does not offer arbitrary external website signing. Candidate provider work is not a production provider release.
Native god1 and compatible 0x addresses encode the same raw account identity. Validate checksums and account roles; an operator godvaloper1 identifier is not an ordinary payment recipient.
A safe application workflow.
- Read the pinned release and supported interfaces. Public source can lag local development; check the reviewed revision.
- Verify the network and supported method before displaying a balance or enabling an action. Keep read services replaceable.
- Prepare an unsigned review with exact recipient, amount, operation, sequence, network and fee limit. Never ask a service to custody a user's key.
- Sign only after local approval. Retain the known TX ID before one bounded submission.
- Confirm the exact committed result and relevant resulting state. On timeout, look up the same ID instead of automatically creating a replacement.
- Exercise refusal, restart, stale state and reset cases with synthetic assets. Do not log passphrases, private keys or private faith text.
God EVM + God SDK + GodCometBFT.
God EVM provides compatible smart-contract execution; God SDK connects state, staking, rewards and protocol accounting; GodCometBFT coordinates validator agreement. These are project branding names for established open-source foundations, not claims of independent invention. Dependency identifiers, interoperability fields, licenses and attribution remain intact.
A wallet RPC is not a peer protocol. Operators also need reviewed software, the exact genesis/runtime bundle, its independently trusted digest, their own identity and reachable P2P peers.
Contribute without exposing private material.
Report the action, expected result, browser version and whether the network check matched. Review any diagnostic attachment first. Never attach an encrypted wallet backup, passphrase, private key, recovery phrase or private faith text. Public addresses and transaction IDs can still reveal your activity; share them only deliberately.