nimbus-eth2/beacon_chain/spec/eth2_apis/rpc_nimbus_calls.nim

import
  rpc_types

export rpc_types

proc getBeaconHead(): Slot
proc getChainHead(): JsonNode
proc getSyncing(): bool
proc getNetworkPeerId(): string
proc getNetworkPeers(): seq[string]
proc getNodeVersion(): string
proc peers(): JsonNode
proc setLogLevel(level: string)
proc getEth1Chain(): JsonNode
proc getEth1ProposalData(): JsonNode
proc getChronosFutures(): JsonNode
proc getGossipSubPeers(): JsonNode
more callsigs! (#2302) 2021-02-09 09:23:26 +00:00			`import`
REST API client, JSON-RPC cleanups (#2756) This refactoring puts the JSON-RPC and REST APIs on more equal footing by renaming and moving things around, creating a separation between client and server, and documenting what they are - the aim is to have a simple-to-use base to start from when developing API clients, as well as make it easier to navigate the code when looking for the legacy JSON-RPC interface vs the new REST API. * move REST client, serialization and supporting types to spec/eth2_apis * REST stuff now starts with `rest_`, JSON-RPC stuff starts with `rpc_`, more or less * simplify imports such that there's a simple module to import for both server and client * map REST type and proc names to yaml spec more closely - in particular, reuse operation and type names in `rest_types` to make comparisons against spec more easy * cleaner separation between client and server modules - modules common between server and client such as `rest_types` and serialization move to the spec folder - this allows the client to be built with less knowledge about server internals 2021-08-03 15:17:11 +00:00			`rpc_types`
more callsigs! (#2302) 2021-02-09 09:23:26 +00:00
REST API client, JSON-RPC cleanups (#2756) This refactoring puts the JSON-RPC and REST APIs on more equal footing by renaming and moving things around, creating a separation between client and server, and documenting what they are - the aim is to have a simple-to-use base to start from when developing API clients, as well as make it easier to navigate the code when looking for the legacy JSON-RPC interface vs the new REST API. * move REST client, serialization and supporting types to spec/eth2_apis * REST stuff now starts with `rest_`, JSON-RPC stuff starts with `rpc_`, more or less * simplify imports such that there's a simple module to import for both server and client * map REST type and proc names to yaml spec more closely - in particular, reuse operation and type names in `rest_types` to make comparisons against spec more easy * cleaner separation between client and server modules - modules common between server and client such as `rest_types` and serialization move to the spec folder - this allows the client to be built with less knowledge about server internals 2021-08-03 15:17:11 +00:00			`export rpc_types`
json cleanups (#2456) * move json-rpc specific marshalling to rpc * serialize Epoch/Slot with cast to avoid Defect * avoid a few eth1 deps * simplify imports 2021-03-26 14:11:06 +00:00
more callsigs! (#2302) 2021-02-09 09:23:26 +00:00			`proc getBeaconHead(): Slot`
			`proc getChainHead(): JsonNode`
			`proc getSyncing(): bool`
			`proc getNetworkPeerId(): string`
			`proc getNetworkPeers(): seq[string]`
			`proc getNodeVersion(): string`
			`proc peers(): JsonNode`
			`proc setLogLevel(level: string)`
			`proc getEth1Chain(): JsonNode`
			`proc getEth1ProposalData(): JsonNode`
			`proc getChronosFutures(): JsonNode`
			`proc getGossipSubPeers(): JsonNode`