1/N After much demand, it's finally here: a proposed roadmap for AvalancheGo, or how to build the future of next-gen blockchain networks by leveraging all the best components of of monolithic and modular designs into one.
Note, this non-exhaustive and requires ACP approvals!
2/N The roadmap is divided across three major pillars:
1. Modular programmability: Making the building of permissionless, highly customizable, sovereign chains best-in-class. 2. Monolithic performance: Increasing performance of the monolithic stack to 100K+ tps / chain
...
3/N ...
3. System reliability: Improvements to time to finality and overall system reliability.
For modular programmability, it is all about upgrading subnets into powerful, sovereign chains. This includes:
Is the Twitter/X app as buggy for you as it is for me?
1. I see my own tweets twice in my own threads, even though they were posted once. Clear threading error incoming recently posted tweets.
2. Sent messages seem to go into limbo for a while, until they are posted. I tried setting that send-wait period to its lowest setting but there's still a wait period. This is probably why interactions are down -- ever since @elonmusk took over, the app has become laggy.
1/7 Sound ways to do fee isolation, a quick thread.
There are multiple ways to do fee-isolation on chain. For those that need a refresher, fee isolation is the idea of localizing fees based on some specific restriction that the protocol may want to enforce.
2/7 For example, one thing that can be done is if a smart contract is taking up a lot of traffic, then that smart contract will need to pay more than others.
One form of this is what Solana does. This is my understanding based on the code review (please correct me if I'm wrong).
3/7 Solana has 4 execution cores which process txs in parallel as long as they don't conflict. If they do, they form queues behind the core. The priority fee then executes txs in the order of the priority fee. It is not enforced by chain, just by the block-building heuristic.
While these ideas are in it's infancy, there are ways distributed ledgers can ensure intellectual property rights are preserved, and attribution can still flow back to creators.
The launch of AvaCloud addresses many challenges businesses face with blockchain technology. AvaCloud is a Web3 Launchpad and a landmark step for massive blockchain adoption.
I have spoken with businesses around the world, and one thing is clear. There is a resounding interest in blockchain technology, but primary barriers of poor user experience, scalability, and expensive start-up costs keep businesses from entering the space.
With AvaCloud, our team has automated the process of launching completely customizable, infinitely scalable blockchains using a no-code portal your parents could use. This will accelerate the opportunities for businesses of all sizes to build in Web3.
The firmware always had full access to the secret key -- the Secure Element is for passive storage, the firmware retrieves the key and uses it. Every firmware update thus requires full scrutiny. Glad to see a dangerous firmware update being rejected by the community.
The tweet from @Ledger that says that firmware *cannot* access the key seems incorrect and misleading. And Ledger's PR and Comms team have done a terrible job of explaining what's happening.
Long story short:
* Don't update your ledger firmware. Wait until Ledger withdraws and issues a new upgrade without the misfeature.
* Nano S seems not to be affected anyway.
* Your coins are infinitely safer in a hw wallet compared to a software wallet.