Octez RPC (Octez 1111.0~rc2+dev (958bc09e))

Aggregate BLS proofs. Return null if the provided proofs cannot be aggregated, or if their aggregation is not a valid proof for the provided public key.

Aggregate BLS public keys after checking their BLS proofs

Aggregate BLS signatures. Return null if the signatures cannot be aggregated, or if their aggregation is not a valid signature for the provided public key and message.

Check a BLS proof

Threshold BLS signatures

Forcefully set the bootstrapped flag of the node

The heads of all active peers

Lists block hashes from '', up to the last checkpoint, sorted with decreasing fitness. Without arguments it returns the head of the chain. Optional arguments allow to return the list of predecessors of a given block or of a set of blocks.

The chain unique identifier.

A breakdown of all the contributions to the delegation portion of the baking power of the given delegate for the given cycle.

Lists blocks that have been declared invalid along with the errors that led to them being declared invalid.

The errors that appears during the block (in)validation.

Remove an invalid block for the tezos storage

The bootstrap status of a chain

The current caboose for this chain.

The current checkpoint for this chain.

The current savepoint for this chain.

Lists protocols of the chain.

Information about a protocol of the chain.

Return the runtime node configuration (this takes into account the command-line arguments and the on-disk configuration file)

Returns the history mode of the node's underlying storage. In full or rolling mode, it provides the values of additional_cycles and blocks_preservation_cycles. The sum of these values is the total number of stored cycles.

Replace the logging configuration of the node.

Configuration for the DAL

List of protocols which replace other protocols

List of protocols to switch to at given levels

Schema for all the RPC errors from the shell

Fetch a protocol from the network.

Returns whether or not the node is ready to answer to requests.

Inject a block in the node and broadcast it. The operations embedded in blockHeader might be pre-validated using a contextual RPCs from the latest block (e.g. '/blocks/head/context/preapply'). Returns the ID of the block. By default, the RPC will wait for the block to be validated before answering. If ?async is true, the function returns immediately. Otherwise, the block will be validated before the result is returned. If ?force is true, it will be injected even on non strictly increasing fitness. An optional ?chain parameter can be used to specify whether to inject on the test chain or the main chain.

Inject an operation in node and broadcast it. Returns the ID of the operation. The signedOperationContents should be constructed using contextual RPCs from the latest block and signed by the client. The injection of the operation will apply it on the current mempool context. This context may change at each operation injection or operation reception from peers. By default, the RPC will wait for the operation to be (pre-)validated before returning. However, if ?async is true, the function returns immediately. The optional ?chain parameter can be used to specify whether to inject on the test chain or the main chain.

Inject a protocol in node. Returns the ID of the protocol. If ?async is true, the function returns immediately. Otherwise, the protocol will be validated before the result is returned.

Monitor every chain creation and destruction. Currently active chains will be given as first elements

Monitor all blocks that are successfully applied and stored by the node, disregarding whether they were selected as the new head or not.

Wait for the node to have synchronized its chain with a few peers (configured by the node's administrator), streaming head updates that happen during the bootstrapping process, and closing the stream at the end. If the node was already bootstrapped, returns the current head immediately.

Monitor all blocks that are successfully validated and applied by the node and selected as the new head of the given chain.

Monitor all economic protocols that are retrieved and successfully loaded and compiled by the node.

Monitor all newly received blocks that are not yet known by the store.

Monitor all blocks that were successfully validated by the node but are not applied nor stored yet, disregarding whether they are going to be selected as the new head or not.

List the running P2P connection.

Details about the current P2P connection to the given peer.

Forced close of the current P2P connection to the given peer.

Full network statistics.

Clear all greylists tables. This will unban all addresses and peers automatically greylisted by the system.

Returns an object that contains a list of IP and the field "not_reliable_since". If the field "not_reliable_since" is None then the list contains the currently greylisted IP addresses. If the field "not_reliable_since" Contains a date, this means that the greylist has been overflowed and it is no more possible to obtain the exact list of greylisted IPs. Since the greylist of IP addresses has been design to work whatever his size, there is no security issue related to this overflow. Reinitialize the ACL structure by calling "delete /network/greylist" to get back this list reliable.

List of the last greylisted peers.

Stream of all network events

List the peers the node ever met.

Details about a given peer.

Change the permissions of a given peer. With {acl: ban}: blacklist the given peer and remove it from the whitelist if present. With {acl: open}: removes the peer from the blacklist and whitelist. With {acl: trust}: trust the given peer permanently and remove it from the blacklist if present. The peer cannot be blocked (but its host IP still can).