Execution conditions#

In this exercise, the entry point may only be called by the admin address; it also requires:

  • that the argument value v be between 10 (included) and 20 (strictly)
  • be even

If not even, it must fail with this following message : Expected even value:

archetype exec_condition
variable value : nat = 0
constant admin : address = @tz1MZrh8CvYkp7BfLQMcm6mg5FvL5HRZfACw
entry main(v : nat) {
called by admin
require {
r1: 10 <= v < 20;
r2 otherwise "EXPECTED EVEN VALUE": value % 2 = 0
effect {
value := v;

It is also possible to establish execution conditions with a failif section. Execution conditions have identifiers (here r1 and r2) used for fail message when no otherwise is established, and to name the property in contract formal verification.

One of the key requirements of a smart contract's entry point is to establish execution conditions:

  • Who can call the contract?
  • Under which logical conditions?

Archetype provides dedicated syntax to make execution conditions very explicit and non ambiguous.


The following Completium CLI command deploys the contract on the Tezos network:

completium-cli deploy 2-exec_condition.arl

Call entry point#

The following command calls the unique entry point with the argument 14 using the --with option:

completium-cli call 2-exec-condition --with '14'

View contract#

The following command generates the URL to view the contract in Better call Dev:

completium-cli show contract 2-exec-condition


Open '3-rat_transfer.arl' and click on "Next: Rationals & transfers" below.