chainweb-node VS ouroboros-network

Most of your questions could be answered if you read the white paper. https://docs.kadena.io/basics/whitepapers/overview

You'll problably need to be familiar with Linux and Docker, but most of what you need to do is documented elsewhere (e.g. https://github.com/kadena-io/chainweb-node or https://hub.docker.com/r/kadena/chainweb-node).

Official release: https://github.com/kadena-io/chainweb-node/releases/tag/2.14 For full details refer to the Changelog: https://github.com/kadena-io/chainweb-node/blob/master/CHANGELOG.md

Not true. https://github.com/kadena-io/chainweb-node/blob/master/rewards/miner_rewards.csv

Not worth it it still a 2% fee just look up either how to mine kda solo on youtube or run this https://github.com/kadena-io/chainweb-node/releases/tag/2.12

Per KDA discord the following. Can ANYone translate as in what may or may not be effected (like wallets?) "This version replaces all previous versions. Any prior version will stop working on 2022-01-13T00:00:00Z. Node administrators must upgrade to this version before that date. " https://github.com/kadena-io/chainweb-node/releases/tag/2.12

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