balsoft/ligo
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
a5cec8fca0
ligo/src/lib_shell/chain_directory.mli

16 lines
869 B
OCaml
Raw Normal View History

First public release
2016-09-08 21:13:10 +04:00
(**************************************************************************)
(* *)
Update copyright notice (2018)
2018-02-06 00:17:03 +04:00
(* Copyright (c) 2014 - 2018. *)
First public release
2016-09-08 21:13:10 +04:00
(* Dynamic Ledger Solutions, Inc. <contact@tezos.com> *)
(* *)
(* All rights reserved. No warranty, explicit or implicit, provided. *)
(* *)
(**************************************************************************)
Shell/RPC: rework `/blocks` - start using `GET` and query parameters instead of `POST` when meaningful - inline parsed protocol data and metadata in block headers - inline parsed protocol data and metadata in operations - split the RPC in four categories: - static data, available explicitly in block headers and operations - static "metadata", information that were computed while validating a block or an operation, but which are not explicit in the block header (e.g. the baker of a block, the list of internal transfer... (currently not implemented, but that's WIP)) - "context" all the static data we may read in the context (contracts balance, list of delegates, ...) - "helpers" are some RPC that may perform some computation.
2018-04-16 02:44:24 +04:00
val get_chain_id: State.t -> Chain_services.chain -> Chain_id.t Lwt.t
val get_chain: State.t -> Chain_services.chain -> State.Chain.t Lwt.t
Resto: lift the lwt monad into Resto.
2018-04-23 03:21:33 +04:00
val rpc_directory: State.Chain.t RPC_directory.t
Shell/RPC: rework `/blocks` - start using `GET` and query parameters instead of `POST` when meaningful - inline parsed protocol data and metadata in block headers - inline parsed protocol data and metadata in operations - split the RPC in four categories: - static data, available explicitly in block headers and operations - static "metadata", information that were computed while validating a block or an operation, but which are not explicit in the block header (e.g. the baker of a block, the list of internal transfer... (currently not implemented, but that's WIP)) - "context" all the static data we may read in the context (contracts balance, list of delegates, ...) - "helpers" are some RPC that may perform some computation.
2018-04-16 02:44:24 +04:00
Shell/RPC: split out `Monitor_services`
2018-04-21 14:57:30 +04:00
val build_rpc_directory: Validator.t -> unit RPC_directory.t
Reference in New Issue Copy Permalink