mi-cho-coq
plutus
mi-cho-coq | plutus | |
---|---|---|
7 | 89 | |
- | 1,529 | |
- | 0.1% | |
- | 9.8 | |
- | 7 days ago | |
Haskell | ||
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mi-cho-coq
- Every link DEVs interested on Tezos should know
-
12 reasons Cardano can't scale in 2022
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).
-
Formal Verification: Tezos’s Feature Nobody Talks About
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.
-
Front running and general architecture?
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.
- About Michelson design
-
ELI5 This “superior tech” Tezos has
The link to the Coq formalization of Michelson, to formally verify smart-contracts: https://gitlab.com/nomadic-labs/mi-cho-coq
-
Supporting EVM, WASM Bitcoin Script, etc.
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/
plutus
-
Are you disappointed/happy with current daps?
Plutus-related issues in Plutus repo https://github.com/input-output-hk/plutus/issues Cardano node-related issues in the Cardano node repo https://github.com/input-output-hk/cardano-node
-
A Comprehensive Guide on Web3 Programming Languages and Tools
Plutus (Haskell) is a statically typed programming language wired for writing reliable smart contracts on the Cardano blockchain. It is also a functional programming language, which means programs are composed as sets of mathematical functions for execution.
-
Software Development Languages: Haskell
* https://github.com/input-output-hk/plutus
There's quite a few recent Isabelle repos such as https://github.com/input-output-hk/high-assurance-legacy
I haven't worked there for a year or so and don't remember specifics like KLOCs, just that they're dotted around internal and public repos :)
-
Liqwid Labs: Technical Status Update #51
PR for Improved Rational for on-chain size was merged into Plutus: https://github.com/input-output-hk/plutus/commit/6d8d25d1e84b2a4278da1036aab23da4161b8df8
-
Cardano vs. Ethereum: Can Ada Solve Ether’s Problems?
Cardano also suffers from the issue of the size of Plutus script being too big. One script can eat up to 20% of block which renders the overall efficiency even worse.
- Cardano: "Slow and Steady wins the... Annnnnd it's gone." Plutus auditor publicly announces that most Cardano smart contracts have an exploit.
-
Why Cardano smart contract transactions are so big.
They're working on script libraries where you can reference a script in another UTXO rather than having to reinclude it every time. This is mentioned in some videos (I think in November's mid month update and Cardano 360), if you don't have time to watch those it's mentioned in michaelpj's comment here along with some other optimisations they're working on https://github.com/input-output-hk/plutus/issues/4174
-
Why does the same smart contract need to be included with every utxo?
There is a discussion on GitHub about this. The second solution in MPJs reply is what you are suggesting.
- PAB release date?
-
Why all the hate?
About to say that lol. Here are more info.https://plutus-apps.readthedocs.io/en/latest/index.htmlhttps://github.com/input-output-hk/plutushttps://docs.cardano.org/plutus/learn-about-plutus
What are some alternatives?
juvix - Juvix empowers developers to write code in a high-level, functional language, compile it to gas-efficient output VM instructions, and formally verify the safety of their contracts prior to deployment and execution.
marlowe - Prototype implementation of domain-specific language for the design of smart-contracts over cryptocurrencies
cardano-ledger - The ledger implementation and specifications of the Cardano blockchain.
reach-lang - Reach: The Safest and Smartest DApp Programming Language
hicdex
cardano-node - The core component that is used to participate in a Cardano decentralised blockchain.
CIPs
plutus-pioneer-program - This repository hosts the lectures of the Plutus Pioneers Program. This program is a training course that the IOG Education Team provides to recruit and train software developers in Plutus, the native smart contract language for the Cardano ecosystem.
tzkt - 😼 Awesome Tezos blockchain indexer and API
plutus-starter - A starter project for Plutus apps
Conseil - Query API and indexer for Tezos and other decentralized platforms.
openzeppelin-contracts - OpenZeppelin Contracts is a library for secure smart contract development.