Skip to main content
The admin API gives access to several non-standard RPC methods, which allows fine grained control over an Parallax client instance, including but not limited to network peer and RPC endpoint management.

admin_addnode

Ingests an address into the addrbook with source=manual. Manual entries persist across restarts, are exempt from source-aware bucket eviction, and are heavily weighted in dial selection (a 4x chance multiplier over other sources, not a strict front-of-queue guarantee). Accepts either plain ip:port (v2.0-native peers, KeyType=0x00) or the legacy enode://<nodeID>@ip:port form (v1.x peers, KeyType=0x01). Returns true if the entry was inserted or updated, false otherwise.

Example

admin_addPeer

The addPeer administrative method requests adding a new remote node to the list of tracked static nodes. The node will try to maintain connectivity to these nodes at all times, reconnecting every once in a while if the remote connection goes down. The method accepts a single argument, the enode URL of the remote peer to start tracking and returns a BOOL indicating whether the peer was accepted for tracking or some error occurred.

Example

admin_addrbookResetKey

Regenerates the addrbook’s per-node secret nKey and clears the tried table atomically. Use after a credible nKey leak — without a fresh key, an attacker who learned the old one can predict which buckets future peers will land in and skew the address selection. Destructive: every entry currently in the tried table is moved back to the new table or evicted. Returns true on success.

admin_addrbookStatus

Returns a read-only snapshot of the addrbook: total entry count, the new/tried split, and per-source counts (manual, dns_seed, tcp_gossip, legacy_udp, plus self_advertised when present).

Example

admin_addTrustedPeer

Adds the given node to a reserved trusted list which allows the node to always connect, even if the slots are full. It returns a BOOL to indicate whether the peer was successfully added to the list.

admin_clearbanned

Removes every entry from the persistent ban list (<datadir>/banlist.json). Does not touch the in-memory discourage filter, which is restart-cleared by design. Returns true on success.

admin_datadir

The datadir administrative property can be queried for the absolute path the running the Parallax node currently uses to store all its databases.

Example

admin_dialV2

Directly opens a BIP324-style v2 RLPx connection to the given ip:port. Bypasses the addrman routability filter, so it can target loopback / RFC1918 addresses for testing. Operator-testing entry point — peers established via admin_dialV2 are still subject to all the normal post-handshake checks (peer cap, ban list, self-endpoint guard). Returns true if the dial was launched, false otherwise.

Example

admin_exportChain

Exports the current blockchain into a local file. It optionally takes a first and last block number, in which case it exports only that range of blocks. It returns a boolean indicating whether the operation succeeded.

admin_importChain

Imports an exported list of blocks from a local file. Importing involves processing the blocks and inserting them into the canonical chain. The state from the parent block of this range is required. It returns a boolean indicating whether the operation succeeded.

admin_listbanned

Returns the active (non-expired) entries from the persistent ban list as a JSON array, matching Bitcoin Core’s listbanned output shape. Each entry has the CIDR-formatted subnet, the Unix-second timestamps for ban_created and banned_until, plus the derived ban_duration and time_remaining in seconds. Expired entries are pruned lazily on each call.

Example

admin_nodeInfo

The nodeInfo administrative property can be queried for all the information known about the running the Parallax node at the networking granularity. These include general information about the node itself as a participant of the ÐΞVp2p P2P overlay protocol, as well as specialized information added by each of the running application protocols (e.g. eth).

Example

admin_peerEvents

PeerEvents creates an RPC subscription which receives peer events from the node’s p2p server. The type of events emitted by the server are as follows:
  • add: emitted when a peer is added
  • drop: emitted when a peer is dropped
  • msgsend: emitted when a message is successfully sent to a peer
  • msgrecv: emitted when a message is received from a peer

admin_peers

The peers administrative property can be queried for all the information known about the connected remote nodes at the networking granularity. These include general information about the nodes themselves as participants of the ÐΞVp2p P2P overlay protocol, as well as specialized information added by each of the running application protocols (e.g. eth).

Example

admin_removePeer

Disconnects from a remote node if the connection exists. It returns a boolean indicating validations succeeded. Note a true value doesn’t necessarily mean that there was a connection which was disconnected.

admin_removenode

Drops an address from the addrbook regardless of which table holds it. Inverse of admin_addnode. Returns true if the entry was removed, false if it was not present.

admin_removeTrustedPeer

Removes a remote node from the trusted peer set, but it does not disconnect it automatically. It returns a boolean indicating validations succeeded.

admin_setban

Adds or removes an entry in the persistent ban list. Banned IPs are hard-rejected at the listener for every inbound, with no trusted-peer exemption — the rejection happens before the handshake, so the node cannot yet know whether the remote is trusted. If a banned range must reach a trusted peer, unban it rather than working around the check. Arguments:
  • subnet — IP or CIDR string. "1.2.3.4" is treated as /32; "10.0.0.0/24" as a CIDR. IPv6 supported similarly.
  • command"add" or "remove".
  • bantime — seconds. Honored only on "add". Omitted, 0, or negative falls back to the daemon’s DefaultBanDuration (24 h) — relative form only.
  • absolute — when true, bantime is interpreted as a Unix timestamp instead of an offset from now and must lie in the future (0 is an error in this form). Defaults to false.
On "add" any currently-connected peer whose remote address matches the subnet is also disconnected, and re-adding a currently-active ban is an error (IP/subnet already banned) unless the new expiry extends the old one. On "remove" the call returns an error if the subnet was not previously banned. Note for the interactive console: admin.setban requires all four positional arguments there — pass null for the optional ones, e.g. admin.setban("1.2.3.4", "add", null, null). The JSON-RPC and parallax-cli surfaces accept omitted optionals. Returns true on success.

Example

admin_startHTTP

The startHTTP administrative method starts an HTTP based JSON-RPC API webserver to handle client requests. All the parameters are optional:
  • host: network interface to open the listener socket on (defaults to “localhost”)
  • port: network port to open the listener socket on (defaults to 8545)
  • cors: cross-origin resource sharing header to use (defaults to "")
  • apis: API modules to offer over this interface (defaults to “eth,net,web3”)
The method returns a boolean flag specifying whether the HTTP RPC listener was opened or not. Please note, only one HTTP endpoint is allowed to be active at any time.

Example

admin_startWS

The startWS administrative method starts an WebSocket based JSON RPC API webserver to handle client requests. All the parameters are optional:
  • host: network interface to open the listener socket on (defaults to “localhost”)
  • port: network port to open the listener socket on (defaults to 8546)
  • cors: cross-origin resource sharing header to use (defaults to "")
  • apis: API modules to offer over this interface (defaults to “eth,net,web3”)
The method returns a boolean flag specifying whether the WebSocket RPC listener was opened or not. Please note, only one WebSocket endpoint is allowed to be active at any time.

Example

admin_uptime

Returns the number of seconds the node has been running since its most recent Start. Returns 0 if the node is not yet fully started. Mirrors Bitcoin Core’s uptime command and backs the parallax-cli uptime command-line helper.

Example

admin_stop

Gracefully shuts down the running node. The method schedules the shutdown on a short delay (about 100 ms) and returns immediately so the RPC response can be delivered before the RPC server itself tears down. Client callers should therefore tolerate the RPC connection being closed without a final response — that outcome still indicates a successful shutdown. This is the underlying method used by the parallax-cli stop command-line helper, analogous to bitcoin-cli stop in Bitcoin Core.

Example

admin_stopHTTP

The stopHTTP administrative method closes the currently open HTTP RPC endpoint. As the node can only have a single HTTP endpoint running, this method takes no parameters, returning a boolean whether the endpoint was closed or not.

Example

admin_stopWS

The stopWS administrative method closes the currently open WebSocket RPC endpoint. As the node can only have a single WebSocket endpoint running, this method takes no parameters, returning a boolean whether the endpoint was closed or not.

Example