Gives 100 Reddit Coins and a week of r/lounge access and ad-free browsing.

When you come across a feel-good thing.

  1. Nothing serious. There are enough pools outside of AWS which can take the load of block validation.

  2. 75% is not a requirement - it's just a target set by IOG. The more nodes are running on the new version the smoother the hardfork.

  3. Now with the data visualized one can easily see that Cardano network is not solely dependent on AWS. I.e., even if AWS completely fails, the Cardano network can continue to work.

  4. Cloud infra is by far WAY better for the network health then non cloud infra. It’s by design faster and more redundant and scalable.

  5. Now that over 56% of the pools have upgraded to the Vasil ready node software, the hard fork will happen rather soon now. Can even be by the end of this epoch. IOG's target distribution is 75%.

  6. Epoch changes are no longer something special for SPOs. They are only relevant for snapshots of stake delegation. So, no there's no point in waiting for epoch changes.

  7. That's not entirely true, nodes tend to behave differently at epoch transition. My BP only misses leader checks at the epoch transition, all other times it operates flawlessly.

  8. The point is, that epoch changes have no influence on deciding the time of the upgrade. Missing leader checks is normal and has no effect on operation - except, when your pool has to produce block exactly on that very specific slot.

  9. The miner ETH will only sustain some value of the merge goes bad. But even then - consider 190 B$ disappears just with it. IMO this would cause more than just a ripple in the crypto world.

  10. Honestly if it all goes tits up, which I don't imagine it will, people will likely vote to roll the chain back to a pre-merge snapshot. This would of course cause eth to absolutely tank but its be better than a catastrophic failure.

  11. Its just about 200B$ at stake. Terra/Luna was just a peep compared to that one.

  12. Yes, because they know what to do and have done so in the past. If you look at the intensive testing and even a change in the testing setup that has been done and the huge community that was involved during that test phase then it is obvious that there is a serious effort to make Vasil a success story.

  13. First - your calculation of fees is only for simple transactions. dApp transactions have additional cost factors. However with Vasil hardfork and Babbage era references to dApps will become available, thus reducing fees for dApps by lowering the size of the transactions (a reference to a piece of of code is massively less than the code itself).

  14. Thanks for your input. Agreed on the balance between affordability and incentives for SPO. But let's hope IOG has a plan to lower fees on the future, as it is critical from a user pov.

  15. One has also to distinguish between transaction fees for the chain and - in the case of dApps fees for processing the swap (or whatever the dApp actually does). Transaction fees for the chain will become significantly lower once references (Vasil HF, but also the dApp code must be adopted) can be used. It is up to the DEX (or others) to define the cost for a swap (etc.). They have, e.g., their own processors which get some incentive and probably want to cover operational and development costs as well.

  16. Why are you not using one of the light wallets like eternl, nami, etc.?

  17. I just get a picture of George RR Martin in South Park saying "Oh its coming....just wait!"

  18. Why is such a response not a surprise here? Anyways if you would have had a look at the list of issues on github you would have seen, that the list of bugs - and especially those of Vasil blockers is shrinking with every 1.35.x release. And the announcement says it very clearly 1.35.3 is supposed to be the one ready for mainnet.

  19. Sounds like a weird answer, and I, for myself cannot believe that I'll give someone that exact answer - but your questions are wrong;

  20. Actually, 1.35.2 was just tagged - and IMO this is going to be the final version before the hard fork. I.e., all real blockers have been ironed out.

  21. That's true. As a matter of fact IOG advises SPOs to downgrade from pre-1.35.2 versions to 1.34.1. They just want to be on the save side and avoid bugs in previous 1.35.x releases. This also indicates that 1.35.2 will be the hardfork version.

  22. Marsian population is massively shorting crypto markets because they are smarter than robots :-)

  23. But we all know that TA means nothing. Everybody can provide a chart that show exact the opposite.

  24. TA? Bah. I sacrifice chickens and cast bones for my market predictions.

  25. Sure works as well as TA! However, there's a bit less mess afterwards with TA I'll have to admit

  26. After checking their github, it reveals, that there's only a few bugs open on their must have list. And IMO there's no big one on that list of open bugs.

  27. P2P is part of the hardfork? I missed that.

  28. With p2p I meant network topology discovery to be precise. This functionality is already in the node software for quite some time but not generally enabled on mainnet. People still want to test how it works before enabling it.

  29. With references to smart contracts, i.e. Plutus 2.0, I don't see a problem referencing a dApp on L1 chain that happened to be there before the head started.

  30. Wow, that article is so bad. It's not even worth reading. Haven't seen any worse article about Cardano yet. Best thing is to forget everything said there and start from scratch with some more serious information.

  31. Not only I fully agree - I'm also running one of these single pools. Single pools can and do provide the same rewards as exchange pools (given that they have the same amount of delegated ADA). This is the case because the selection of block producing pools and the distribution of rewards is driven by algorithm and not by mining power.

  32. First - before we go deeper into your question - being a node needs further definition. With Cardano there are different types of nodes; one being a relay or block producer of a pool - and the other one is part of the Daedalus wallet. And - of course one can just run a node for fun. The biggest difference between the block producers and the rest of nodes in the network: only block producers (registered as such on the chain) can actually mint new blocks. All others are just listeners (relays are also part of block diffusion - but that's another story.

  33. Interesting distinction thank you for the answer. So if you can read from the chain as just a listener what’s all this hooplah about mithril and verifying the state of the chain?

  34. It is the idea behind Mithril (actually just one of many more), to make it possible to validate blocks and submit transactions without having a full node. Instead of current light wallets, which use a remote (from the wallets point-of-view) node or an API like blockfrost (which also uses a full node for processing), Mithril technology will allow checking the validity of a partial blockchain.

  35. I've been into Cardano since the Mary HF. Upgrade of pools was never a problem. But it's very important that the node software is well tested and stable.

Leave a Reply

Your email address will not be published. Required fields are marked *