daistats VS besu

For more accurate stats check out: - https://daistats.com/ - https://makerburn.com/ - https://maker.defiexplore.com/

On daistats.com you can see that DAI is currently collaterized with USDC for 28.6%. Combine this with the fact that DAI has an overcollaterization ratio of 137.58%. This means that DAI could survive a complete USDC crash much better than you'd think, possibly not even depegging from $1.00 at all.

Looking at https://daistats.com/.. have never seen unhealtier numbers..

USDC & USDP (both centralized) account for 70% of DAI collateral. https://daistats.com/

It's not the thing propping up crypto prices. DAI is relatively small ($6.5B mcap), DAI is also partly backed by USDC [1], which is backed by cash and US government bonds (held at Circle) so it would be extremely difficult for DAI to lose collateral backing faster than keepers could liquidate positions. Does DAI have an influence on the $1T crypto industry? Of course, but its liquidity pales in comparison to USDC, USDT, and BUSD (~$100B between them). If the market is crashing, it's doubtful DAI is the culprit (as it's actually a solid, battle-tested protocol that already lived through the Covid crash and '18 and '19 severe drawdown and many other trying market scenarios).

But what you say is true of all debt markets. Debt has an inflating effect on the price, and when those debts get wiped off from liquidations, it can have a cascading affect in the opposite direction from that on the way up. That is precisely what happened to the real estate market in '08. People didn't think the real estate market could go down in terms of price. And yet, it did, and we had a major financial crisis as a result as real estate prices drew down 50% or more in some areas and foreclosure supply flooded the market.

[1] https://daistats.com/#/

It's not an algo stable, otherwise your post is solid. It is overcollateralized by mainly USDC and ETH (see https://daistats.com/) and only when that collateral fails to make the protocol whole would it even begin to consider using MKR as a backstop. The centralized aspect of course coming from the fact that it is heavily collateralized by USDC. This was done to keep DAI firmly on peg, for now. There are plans in motion to reduce reliance on USDC.

Daily Goerli: I've been testing this PR for besu for the past several days, and the stability of nimbus-besu has improved substantially. Looking forward to it getting merged into main.

Check out the Layered TX pool PR for more details and benchmarks - https://github.com/hyperledger/besu/pull/5290

you can check this spreadsheet for a comparison https://github.com/hyperledger/besu/files/11137473/Layered.Transaction.Pool.metrics.ods

Yes, it's gotten better. I don't recommend pairing with nimbus until this issue gets fixed or prysm until something is done to reduce the amount of time it takes to recover from being offline for a day or more.

Daily Goerli: On Friday, I reported a RocksDB issue that was causing besu to error and exit immediately. The bad commit has been identified and a fix has been issued. lodestar-nethermind somehow ended up on an invalid fork which isn't resolved by restarting either client. Waiting to see how each client team responds and if they need more info, but might need to do a resync.

https://github.com/hyperledger/besu 148 contributors

Download links and release notes here: https://github.com/hyperledger/besu/releases/tag/23.1.2

Now running into this error on my freshly synced Besu 23.1.0. 😔️