ligo/src/lib_client_base/client_confirmations.mli

(**************************************************************************)
(*                                                                        *)
(*    Copyright (c) 2014 - 2018.                                          *)
(*    Dynamic Ledger Solutions, Inc. <contact@tezos.com>                  *)
(*                                                                        *)
(*    All rights reserved. No warranty, explicit or implicit, provided.   *)
(*                                                                        *)
(**************************************************************************)

val wait_for_operation_inclusion:
  #Client_context.full ->
  chain:Chain_services.chain ->
  ?predecessors:int ->
  ?confirmations:int ->
  Operation_hash.t ->
  unit tzresult Lwt.t
Client/Alpha: split module `Client_proto_context` 2018-04-22 12:50:34 +04:00			`(**************************************************************************)`
			`(* *)`
			`(* Copyright (c) 2014 - 2018. *)`
			`(* Dynamic Ledger Solutions, Inc. <contact@tezos.com> *)`
			`(* *)`
			`(* All rights reserved. No warranty, explicit or implicit, provided. *)`
			`(* *)`
			`(**************************************************************************)`

			`val wait_for_operation_inclusion:`
			`#Client_context.full ->`
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			`chain:Chain_services.chain ->`
Client/Alpha: split module `Client_proto_context` 2018-04-22 12:50:34 +04:00			`?predecessors:int ->`
			`?confirmations:int ->`
			`Operation_hash.t ->`
			`unit tzresult Lwt.t`