this repo has no description
1opam-version: "2.0"
2maintainer: "contact@tezos.com"
3authors: ["Tezos devteam"]
4homepage: "https://www.tezos.com/"
5bug-reports: "https://gitlab.com/tezos/tezos/issues"
6dev-repo: "git+https://gitlab.com/tezos/tezos.git"
7license: "MIT"
8depends: [
9 "dune" { >= "3.0" }
10 "ocaml" { >= "4.14.0" & < "4.15" }
11 "tezos-stdlib" { = version }
12 "tezos-crypto" { = version }
13 "tezos-lwt-result-stdlib" { = version }
14 "tezos-scoru-wasm" { = version }
15 "data-encoding" { >= "0.7.1" & < "1.0.0" }
16 "bls12-381" { >= "6.1.0" & < "6.2.0" }
17 "octez-plonk" { = version }
18 "zarith" { >= "1.12" & < "1.13" }
19 "zarith_stubs_js"
20 "tezos-crypto-dal" { = version }
21 "class_group_vdf" { >= "0.0.4" }
22 "aches" { >= "1.0.0" }
23 "aches-lwt" { >= "1.0.0" }
24 "tezos-base" { = version }
25 "tezos-sapling" { = version }
26 "tezos-micheline" { = version }
27 "tezos-context" { = version }
28 "tezos-event-logging" { = version }
29 "tezt" { with-test & >= "3.1.0" }
30 "octez-alcotezt" { with-test & = version }
31 "tezos-test-helpers" { with-test & = version }
32 "qcheck-alcotest" { with-test & >= "0.20" }
33 "lwt" { with-test & >= "5.6.0" }
34]
35build: [
36 ["rm" "-r" "vendors"]
37 ["dune" "build" "-p" name "-j" jobs]
38 ["dune" "runtest" "-p" name "-j" jobs] { with-test & ocaml:native }
39]
40synopsis: "Interface layer between the protocols and the shell"
41url {
42 src: "https://gitlab.com/tezos/tezos/-/archive/v17.3/tezos-17.3.tar.gz"
43 checksum: [
44 "sha256=7062cd57addd452852598a2214ade393130efa087b99068d53713bdf912b3680"
45 "sha512=08e4091144a03ce3c107fb91a66501bd8b65ca3278917c455a2eaac6df3e108ade63f6ab8340a4bb152d60f404326e464d0ec95d26cafe8e82f870465d24a5fc"
46 ]
47}
48description: "The protocol-environment is a two-sided component sitting between the shell and
49the protocols.
50
51On one side, it provides a restricted typing environment to compile the
52protocols against. This is a series of modules which replace the standard
53library of OCaml. These modules purposefully omit many functionalities, thus
54preventing the protocols from, say, directly writing to disk.
55
56On the other side, it provides the shell with specific call-sites in the
57protocols. These are the only entry-points into the otherwise black-box
58protocols."