Show newer

Don't get me wrong. I like EIP-1559 Fee Market. Besides, nearly all -based chains (Polkadot, Kusama, Kulupu, etc) already implement fee market in production. However, for Ethereum, a good specification does not do much itself without the community agreeing on it. (6/8)

Show thread

The lack of self-consistency primarily hurts community trust. A pressing question is -- how do you expect the mining community to trust ACD's decisions on EIP-1559 Fee Market, when ACD often contradicts itself? (5/8)

Show thread

This was not the only example. Similar thing happened in EIP-1344, which was included despite some technical objections in its design. On the other hand, many of us thought EIP-2315 was doing well addressing its technical issues, until the last minute when it was rejected. (4/8)

Show thread

Probably the most worrying thing is self-conflicting ACD decision makings. Remember ProgPoW? It was rejected nearly purely because many devs think it's controversial. While in EIP-1559 Fee Market, it's included despite its controversy in the miner community. (3/8)

Show thread

It's really hard to point at a clean example on an ACD decision where I can say -- the governance process is working really well. It's really easy to find many many examples on ACD decisions where people can easily say -- the governance process is broken. (2/8)

Show thread

I can't help but echo the comments from greg_colvin, peter_szilagyi and others, regarding the "nastiness" of ACD decision making on EIP-2315. (1/8)

We're not there yet, but close. There are still some framework-level code to be written. If successful, we may be able to generalize this to be suitable for other types of blockchains, besides -like ones!

Show thread

I'm actually quite excited about this. Right now, most users utilize the EVM execution and RPC compatibility layer, but not so much the wrapper block layer. This proposal will be the first time we try wrapper block in production. github.com/ellaism/meta/discus

Really happy to see NEARProtocol using SputnikVM for its execution engine!

New unified EVM runner for Frontier!

In the past, users of Frontier have to compromise between compliance (the "stack" runner), and interoperability (the "builtin" runner). The compromise is no more!

github.com/paritytech/frontier

Basic documentation for Frontier is up. The Ethereum compatibility layer for Substrate! paritytech.github.io/frontier/

There will always be a tendency towards centralization, as shown in the real world. Kulupu cannot succeed if it does not have resistance towards that tendency. A blockchain should keep being leaderless and decentralized.

Show thread

has so many methods and ways that you can easily climb up the "voice ladder" and get yourself heard. You can join the Kulupu council, post democracy referendums, and even, our kulupunetwork official Twitter account is shared. Not many have used them at all.

Show thread

We should also post more educational materials on what "decentralization" means. It's a bad sign if people still ask permissions when doing anything, if there is no autonomy other than from developers in the community, and if people feel surprised by the openness of marketing.

Show thread

This leaderless community cannot function without a rational user base. So this is the first thing that has to be done -- promote fact-checking and transparency. and correct any misinformation posts (especially those ones that are positive) from now on.

Show thread

The project must now learn how to form a leaderless community. It has been so long that nearly all burdens of marketing, community building and governance tasks being on just a handful of individuals. This is not sustainable.

Show older
Mastodon

Wei's Mastodon server, at That World!