ouroboros-network VS plutus

I'm one of the consensus team members at IOG. We maintain and extend the consensus layer of the Cardano blockchain, which provides a rich set of challenges related to distributed computing, type level programming, networking, concurrency, among others.

According to a document on pipelining I saw on Github they might be building a whole new Ouroboros protocol called Leios (https://github.com/input-output-hk/ouroboros-network/pull/3579/files) so there might be something we don't know yet

• cardano-node - top level integration code • ouroboros-network & ouroboros-consensus - network code & consensus (which integrates network, consensus and the ledger) • ledger - ledger(s) specifications and implementation • plutus - the smart contract language and related infrastructure

Check out cardano-ping.

This is non trivial, you can check an example how we generate valid subset of Haskell to check that our implementation of orElse is corect: https://github.com/input-output-hk/ouroboros-network/blob/master/io-sim/test/Test/STM.hs

So from what I gather the transaction fee is a fixed protocol parameter. I like how fees are distributed amongst the epoch, If I had to design a blockchain system I'd also have chosen this approach TBH. It addresses some of the issues and misaligned incentives if you only have to rely on fees for block rewards. However if the demand for transactions constantly outweighs the available space you get into other issues. I tried to find details on how Cardano handles transactions and manages its mempool. I believe somewhere here is the code? (https://github.com/input-output-hk/ouroboros-network/blob/master/ouroboros-consensus/src/Ouroboros/Consensus/Mempool/Impl.hs)

Ouroboros(the consensus algorithm's formal specification): https://github.com/input-output-hk/ouroboros-network

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

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.

* 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 :)

PR for Improved Rational for on-chain size was merged into Plutus: https://github.com/input-output-hk/plutus/commit/6d8d25d1e84b2a4278da1036aab23da4161b8df8

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.

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

There is a discussion on GitHub about this. The second solution in MPJs reply is what you are suggesting.

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