JSON-RPC
Ayrıca şöyle anılır JSON-RPC 2.0
Origin:
composes: an open, pre-existing wire format Solidus uses as-is. Solidus status:shipped, the live public interface into the testnet today.
JSON-RPC is a simple convention for calling a remote function and getting a JSON answer back. A client sends a small JSON object naming a method and its parameters; the server sends back a JSON object with either a result or an error. It doesn't care what transport carries it (HTTP, WebSockets, raw TCP) and doesn't assume anything about what the "remote procedure" actually does, which is exactly why it's a popular choice for blockchain nodes: a wallet, an explorer, or a script can all talk to a node the same simple way, regardless of what's happening inside the chain.
Where it comes from
JSON-RPC 2.0, published in 2010, is maintained as an open community specification at jsonrpc.org, no company owns it, and no blockchain invented it. It happens to be the exact format Ethereum clients use for their eth_* methods (eth_getBalance, eth_sendRawTransaction, and so on), which is part of why it became the default choice for chain APIs generally. Solidus adopts the spec as-is; the innovation, if any, is only in which methods it exposes, not in the wire format itself.
What Solidus exposes today
rpc.solidus.network is the live JSON-RPC endpoint into the public testnet. Its methods are Solidus-native, resolving a did:solidus DID document, querying credential-anchoring and revocation status, submitting a transaction, not the Ethereum eth_* namespace. That distinction matters: an Ethereum-tooling-compatible eth_* JSON-RPC surface (the kind MetaMask, ethers.js, or Foundry expect) is planned specifically for the EVM Subnet, which is its own, separate, not-yet-deployed piece of the system, not something the base L1's endpoint provides today.
Check it yourself
rpc.solidus.network is confirmed live and publicly reachable. Any standard JSON-RPC 2.0 client, curl, a browser fetch, a scripting language's HTTP library, can send it a well-formed request over HTTP and inspect the response, with no account or API key required.
Related terms: libp2p · EVM Subnet · HotStuff · Finality
Nereden geliyor
Bunu başkası belirtti. Solidus bir araya getiriyor.
JSON-RPC is a lightweight, transport-agnostic remote-procedure-call specification. Version 2.0 (2010) is maintained as an open community spec at jsonrpc.org and is not owned by any single company or blockchain project, it's the same wire format Ethereum clients expose as their `eth_*` methods. Solidus uses JSON-RPC as-is for its node's read/write API; it did not design a new wire protocol.
Bunu nasıl doğrularsınız
Bugün üretimde çalışıyor.
rpc.solidus.network is documented as the live public JSON-RPC endpoint into the testnet. Any standard JSON-RPC 2.0 client can send it a request over HTTP and inspect the response envelope without an account or special access.