On Tech, Business, Society.

Category: Blockchain Page 1 of 7

Re-Thinking DAOs as an Evolution of Coops

We should stop trying to force DAOs to exist based on their current path of evolution if they want to be a positive part of the blockchain future.

There is no doubt that most DAOs from the cohort that mushroomed during the 2020-2022 period are floundering, or being very loosely successful. 

Yet, some pundits continue to profess a type of analysis that obscures instead of enlightens. Machiavelli for DAOs: Designing Effective Decentralized Governance struck me as a very unrealistic opinion about how to design decentralized governance by espousing Machiavellian principles. 

One of the biggest problems is when we see DAOs as a lever to eliminate the need for human management. This is a naive and misguided assumption. No organization can run on autopilot, and DAOs are no exception. Even when you inject the strong community component that is always part of DAOs, communities also need to be managed with human intellect. In fact, DAOs can be even more difficult to manage than traditional organizations, due to their decentralized nature and the diversity of their shot-gun stakeholders.

We need to stop trying to force decentralized organizations as a panacea for something that doesn’t need it. And we need to be realistic about what’s viable. 

There is validity in rethinking the way we design and implement DAOs towards more simplicity, not complexity. We need to move away from the idea of DAOs as completely autonomous organizations, and instead think of using DAO constructs as a complement that espouses the novelties of blockchain and cryptocurrency. Maybe DAOs are meant to be a complement to something else but not an entirely standalone thing. 

I don’t mean that we need to throw the whole concept away. There are some very good embedded ideas, at the high levels:

  1. Decentralization is a good anti-single point of failure.
  2. Automation with embedded smart contracts does bring operational efficiency. 
  3. Community/user voices with decision-making influence have their benefits. 
  4. Giving back parts of the economic gains to participants that contributed to wealth creation is the right thing to do.

The “autonomous” part in the DAO vocabulary is perhaps the most misleading, misguided, and certainly the weakest part of the equation. 

Management by committee, delegation, or populist votes is a terrible idea. Conflating blockchain consensus mechanisms with human decision-making is blasphemy against human intelligence and decades of sound management practices. 

Voting on decisions, when you have an economic or ideological stake, is not a bad idea, even if it’s only a directional vote that could influence a future decision, but thinking that this is sufficient for running organizations or projects is a naive assumption. 

On the regulatory side, being “autonomous” doesn’t absolve an organization (or its instigators) from the rule of law as set by governments or regulatory authorities. 

Maybe DAOs could be applied when there is predictable repeatability, no issues, no surprises, and when a given system is stable. These difficult simultaneous conditions narrow DAO’s applicability field tremendously. 

The cooperative (Coop) corporate business model is the closest to the DAO concept. I think the industry should work more diligently to extend and adapt the Coop model instead of trying to push DAOs as we know them today. 


Source: https://coopcreator.ca 

Platform cooperatism is a concept that was recently introduced. It is described as “businesses that sell goods or services primarily through a website, mobile app, or protocol.”

This article, ‘Staking’ Identities: Looking at the Practicalities of Transforming DAOs Into Co-ops looks at the similarities between DAOs and Platform Cooperatives.

We can draw a lot of inspiration from the cooperative Coop model. At their core, coops are businesses that are owned and democratically controlled by their members. That happens to be the primary goal of DAOs, which is why the match is worth exploring seriously.

By combining the best of DAOs and the best of coops, we can create a new type of organization that is democratic, equitable, and resilient.

12 Things the Crypto Industry Needs to Get Right

It’s going to take a long time to get back on track

It’s the end of summer and return to work or school for many people. Crypto has had a boring summer, no matter how you cut it. In terms of prices, we’re pretty much where we were 90 days ago, roughly. (See chart below)

However, beyond that quantitative metric, the industry malaise will continue as long as we have a hostile US regular (the SEC). Sadly, the crypto industry has a lot of headwinds to fight through. Every bit of good news is quickly tempered by regulatory realities.

The non-US market that wants to shrug off the SEC is not so immune to what happens in the US. The US is still that locomotive engine that needs to go full speed to power the rest of the industry. So, we can’t just depend on the rest of the world to pave the way on its own.

What could lift things permanently is a lot of things:

1. SEC change of regime and / or change of rhetoric

2. US Congress passing some law(s)

3. Bridges working seamlessly between L2s & from Ethereum to non EVM chains (eventually it should be just “VM”,- the blockchain as one virtual machine)

4. Many more consumer apps with a dead-easy mainstream user experience, leading to millions of committed users that use these apps daily

5. Spot ETF products for Bitcoin & Ethereum (a few of them)

6. Lower gaps between promise and reality for any new / existing blockchain projects (ie lower the hype)

7. No extraordinary bad actors for a full year (ie no significant scams or security exploits)

8. Moving the conversations away from the technical realm that currently dominates (speeds & feeds won’t matter much, but interoperability & user experience will matter). Degrees of decentralization debates are overdone.

9. Players consolidation at the L1 level which is Ground zero (there are far too many competing & non-interoperable L1’s & that works directly against much needed network effects) [related to #3 & #9]

10. Established companies adoption of blockchain / crypto not in an opportunistic way, but more fundamentally

11. Emergence of better / newer / more (human) role models in the crypto space

12. Crypto techies that can better explain the business aspects and applications of what they are building; less tinkering, more useful tech. We also need more no-code tools to put in the hands of non-tech users.

Of course, all these points are being worked on. That’s the good news.

The bad news is that it will take a while to get there as these aren’t going to be realized overnight.

A Critical Perspective on Ethereum: Too Much Tinkering 

The tinkering ratio of output can be improved to yield more mainstream products

I’m writing this critique with a deep and long historical perspective on Ethereum because I want Ethereum to succeed better. I’d like its ecosystem to get stronger. I’d like its apps and services to be more useful. I’d like its end-user experiences to be on par with what the mainstream consumer expects. 

At a time when many other L1 blockchain infrastructures are struggling for growth, Ethereum has a chance to clean up and solidify its position as the preeminent blockchain infrastructure. 

Whether changes happen or not depends to a great extent on what the Ethereum community does or doesn’t do. There is a limit to what the market can do to pick up the pieces and innovate on top of what is handed to them.

This comes at a time when a large part of the Ethereum community is getting ready to re-assemble in Waterloo where the first ETH Global event took place six years ago. I participated in that event, wrote From Waterloo to Zug, Retracing Ethereum’s Journey and made a presentation chronicling the then-emerging Ethereum ecosystem.

I’d like to talk about what Ethereum can do better. So, I’m going to focus on some parts that could be improved, in order to maximize Ethereum’s potential. 

There is no need to extol Ethereum’s strengths, as you all know them. But sometimes your strengths create a weakness. So we can start there. 

One of Ethereum’s strengths is the diversity of its ecosystem and how much development activity there is around it. It is undoubtedly the most vibrant laboratory for blockchain innovation. 

However, that strength has become a weakness because there is too much TINKERING in that ecosystem. 

Tinkering is not bad because it can lead to great things as you iterate. But when I said “too much tinkering”, I meant on a relative basis. 

Tinkering as a ratio of output can be improved. This means that we don’t necessarily need less tinkering, but we need more tinkering that results in fully deployable and usable solutions. And not just at the technical level. We need more end-user applications with user-friendly, mainstream-appeal types of applications.

If your tinkering doesn’t produce an end result, do you know what happens?

Other chains take your half-baked ideas and they add the last mile to it, and they deliver something usable. Sounds familiar?

One of the drawbacks of too much tinkering is that we tend to forget about tuning the end-user experience. 

Of course, the first level of the Ethereum ecosystem is mostly comprised of developers, and that’s a great thing. Developers typically work on infrastructure or they work on services for other developers to build applications on, or they work directly on applications.

The part that needs the most improvement is the last part, the part that touches the end user.

If Ethereum wants to be in the hands of one billion users, it needs to think more about the importance of mainstream user experiences. The mainstream user wants SIMPLICITY first, and two or three clicks to get impressed and hooked. That challenge, by the way, doesn’t only apply to the Ethereum community. It does also matter for the entire blockchain industry. I recently wrote, What The Blockchain Industry Can Learn From the Popularity of Artificial Intelligence pertaining specifically to the user experience.

Here are two related parts where Ethereum can improve.

First, the Ethereum development ecosystem needs more product managers. Product managers focus on getting the product to the market in its most usable form. Sadly, sometimes, they are the ones who realize that at one point, you need to shoot the engineers in order to get the product out. Product managers obsess about the user experience, user flows and user interactions. Product managers understand how to lay out a roadmap and prioritize features rollout accordingly. 

Second, the L2 layers fragmentation is another strength-turned-weakness. L2’s have been undoubtedly beneficial to Ethereum’s scalability, but from a user perspective, the experience is not ideal, because of the switching friction. As a user, imagine if you had to switch browsers to access different parts of the web. It would be unthinkable, yet we ask Ethereum users to decide which L2 to choose from. Furthermore, we make them jump through hoops and take security risks to bridge from one network to another if they seek to move assets across L2’s. 

I don’t have a solution for this fragmentation, and some believe it’s not an issue, but I do think it is. Therefore, I’m just laying out the challenge to elevate its visibility and importance. When there is less friction, there is more adoption.

I realize that the Ethereum ecosystem is obsessed with an extreme form of decentralization at all levels of the stack. But that also creates challenges, because as you unbundle various pieces in order to decentralize the system, you then need to re-bundle everything to properly assemble a solution. Then, you need a lot of coordination and making sure that many parts work together at the same level of readiness and response, and that’s not always so easily achieved. 

This challenge was validated in Vitalik’s last essay, The Three Transitions where he advocates there are three essential capabilities that need to work together in Ethereum: L2 scaling, wallet security, and privacy. There is nothing new with these individual features as they were part of the early vision of the Ethereum blockchain. However, with increased decentralization, there are increasing degrees of complexity that compound when you start to implement these three prongs simultaneously. 

Ethereum is approaching its ten-year mark on its original inception. It’s time that we polish the ongoing tinkering in its base infrastructure and services so that apps can prosper on top of it. 

I’m looking forward to seeing more product managers and entrepreneurs drive the Ethereum ecosystem in addition to the base technology developers who are obsessed with technology tinkering. 

What The Blockchain Industry Can Learn From the Popularity of Artificial Intelligence

The A.I. industry’s approach to user adoption could prove instructive in the area of user friendliness

Image generated by DALL-E

In my third Fortune Crypto column, What Blockchain Can Learn from A.I., I contrast and compare how artificial intelligence burst onto the scene and is being adopted by end-users a lot faster than blockchain products have.

A primary reason is that A.I. has nailed the user experience, especially on a relative basis while blockchain products continue to miss their appeal to mainstream users.

A.I. refrained from overhyping itself prematurely, allowing ample time for development and refinement over the past decade, before it was ready for prime time. During that gestation period, developers dedicated themselves to fine-tuning the technology, tackling intricate challenges, and only now are we witnessing the true impact of A.I. on the average consumer.

In contrast, the blockchain industry continues to expose its tinkering to the public, resulting in a large gap between hype and reality. Several participants in that industry persist in promoting unproven products or exaggerated business models, exposing their experimental ventures to public scrutiny and inviting criticism or skepticism.

As a long-time blockchain enthusiast, this makes me incredibly jealous. I think A.I. can teach the blockchain a few lessons.

Here’s the link to the article (no paywall), A.I. exploded in popularity because it’s so easy to use. Here’s what blockchain developers can learn from that.

How Will Crypto Wallets Lead Us To The Wild World of Blockchain Apps? 

We’re a long way from the wallet becoming the next browser. But there’s more than one way to get there.

I wrote another article that was published on the week-end in Fortune, entitled The growth of Web3 depends on crypto wallets—and how we choose to use them.

The article discusses the question, Will the popularity of wallets lead users to a Web3 world, or will current web apps move more quickly in that direction by first incorporating built-in wallet functionality?

It’s a bit of a trick question because both paths will be valid, in my opinion.

Having more built-in wallets inside apps is inevitable, and that trend is going to increase. In these cases, the app itself is the main attraction, and the wallet takes a second-class position to it. In these cases, there is tight integration between the app and wallet experiences.

Then what happens when you own a variety of cryptocurrencies? You will need a multi-currency wallet to hold them. That’s where the standalone wallet comes in. In that standalone category, there is more than just holding currency. These wallets also function as a bridge to “decentralized apps”, ones that use the wallet as a user login or for authentication and pseudo-identity purposes, such as for Decentralized Finance.

Today, we have an abundance of choices in standalone wallets, while there is a shortage of useful apps that use the built-in wallet in a significant and essential way.

With that backdrop as a set-up, I invite you to click on the link and read (no paywall) the full article, The growth of Web3 depends on crypto wallets—and how we choose to use them.

P.S. The image above was generated by starryai with the prompt “A bridge depicted by cryptocurrency wallets.” I was pleasantly surprised that it also included the hamburger menu alluding to apps, although I didn’t give it that directive.

Page 1 of 7

Powered by WordPress & Theme by Anders Norén