mi-cho-coq VS hub-feedback

There are similarities between the promises made by Cardano and what you find in Tezos: * proof-of-stake L1s * on-chain voting: Voltaire for Cardano vs periodic elections on Tezos (already 8 important upgrades of the protocol that were voted for, with the Foundation abstaining!) * formal verification of contracts and the chain itself: mentioned here for Cardano vs several projects in Tezos (Mi-Cho-Coq, foobar.land, both using the Coq proof assistant) * ongoing work on L2s: Hydra for Cardano vs Deku, zkRollups and optimistic rollups as well (a bit similar to Arbitrum IIRC).

We are not working with LIGO to verify smart contracts, more with Mi-Cho-Coq which aims to verify smart contracts directly at the Michelson level. Using Mi-Cho-Coq it is possible to verify the Michelson output of LIGO or SmartPy. I heard LIGO people also have projects to do verification directly at the LIGO's level or verify the implementation of the LIGO compiler.

Formal verification for smart contracts. Many (Not all) categories of vulnerabilities can be avoided that way. See fe: https://medium.com/coinmonks/verify-a-smart-contract-with-archetype-6e0ea548e2da or https://gitlab.com/nomadic-labs/mi-cho-coq which can be used on any michelson code.

The link to the Coq formalization of Michelson, to formally verify smart-contracts: https://gitlab.com/nomadic-labs/mi-cho-coq

Web assembly is stack-based and there are tools like KWasm for formal verification - so a move to WASM is a more likely candidate... but Michelson is a very capable and verifiable stack based low-level language too. https://gitlab.com/nomadic-labs/mi-cho-coq/

image: this key specifies the image this container is based on to be created. It can be a local image or an image from the Docker hub.

Finally, we can upload our application to Docker Hub so that other people can use the image we created. To do this, follow the steps below:

Pull the official Docker distribution of pgAdmin 4 from the Docker Hub repository with the following command:

To use Docker Scout, you'll first have to have a Docker Hub account. Follow the installation instructions for Docker Scout on GitHub. Once Docker Scout is installed, you can sign in to Docker Hub on the command line with the docker login command.

Go to Docker Hub, sign up, and log in to your account's overview page.

Login to Docker [Create an account with https://hub.docker.com/]

Docker Hub

Dockerhub account

There are a lot of docker-compatible registries almost every cloud provider has its registry but for this article, we will use the docker registry called docker hub. Go to the website create a new account and sign in then you can push or pull images.