cardano-ledger VS mi-cho-coq

The actual code implementing it is a little hard to find (as always with the quite convoluted and scarcely documented Haskell sources of IOG). I'd suspect it to be somewhere in https://github.com/input-output-hk/cardano-ledger/tree/master/eras.

That's just rubbish, you can stop trying to create a false narrative now. Minpoolcost was in the Shelley design spec and deliverables, it's not something **evil Charles** come up with because he felt like it.

See for yourselves all the commits in the source repo for the implementation, it is sooo active: https://github.com/input-output-hk/cardano-ledger/commits/master

The formula for the mid-ada-value can be found here. Which is essentially:

Blockchain - I find it's one of the few fields really investing in formal methods at the moment (my old boss recently opened a research center at Carnegie Mellon in formalizing maths actually). Two repos with specs are:

* https://github.com/input-output-hk/cardano-ledger

This is a helpful article! : https://github.com/input-output-hk/cardano-ledger/blob/master/doc/explanations/features.rst I am invested in both the ERC20 and the native token. However, there’s greater demand currently for the ERC20 tokens.

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/