mi-cho-coq VS vercel

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/

Frontend: Developed with Remix, hosted on Vercel

Choosing Vercel was a natural decision as it has become the default method for launching apps that are accessible to a wide audience. The simplicity of configuring environment variables, domains, and other settings facilitated this choice. We have implemented feature branch deployment to guarantee that the code is operational and prepared for peer review.

Next, we'll deploy our ecommerce website to Vercel (which is a great choice to host your Next.js website). Other hosting options include Netlify and Render.

This approach has seen a proliferation of platforms that offer this as a service(Netlify, Vercel, Cloudflare etc.) and also a proliferation of frameworks with different strengths and weaknesses(list of frameworks supported cloudflare).

Next.js: Highly optimized for production from the start, with features tailored for performance in real-world scenarios, including extensive support for SEO and server-side capabilities. Note: With deployment to Vercel is free and comes with additional free tooling such as website analytics and more.

Easily deploy your Next.js app with Vercel by clicking the button below:

Now go to https://vercel.com, sign up for an account, and click "New Project". Connect your GitHub account and give Vercel permission to access your repositories.

Next.js has become a standard choice for developing React applications, offering various deployment options across different platforms. While Vercel is a popular choice for building and deployment, specific project requirements may require deployment to GitLab. In this guide, I'll illustrate the process of deploying a Next.js application to GitLab Pages.

I hosted my portfolio in Vercel. The main reason why I chose it is the hosting has great support for NextJS and IMPORTANT THING, it is total FREE 🤑 (with my usage). And I have use GitHub Action for deploy it automatically when I make or merge change into main branch.

To do this just head over to Vercel and log in if you're not already logged in. If this is your first project, you'll be seeing something like this.