Connect with us

Decentralization

Modularity means multiple web3 developer journeys—we only need one

Published

on


Disclosure: The views and opinions expressed here belong solely to the author and do not represent the views and opinions of crypto.news’ editorial.

Modularity has made significant progress in expanding the web3 developer design space by unbundling the monolithic stack. Yet, with new capabilities comes new challenges that are our duty as protocol builders to overcome. 

As the modular ecosystem stands today, there is no single tutorial that guides builders end to end. Developers must take on multiple journeys and educate themselves about every component part before they can start building their dApp. We must create better tools to help them interact with these technologies more productively. The onus is on us to simplify the developer journey, and we must do so by working together.

The modular developer journey

Let’s paint a picture of the current developer journey. Before a developer can start building, they must determine the infrastructure that will support their dApp. In web2, this can be as simple as selecting an operating system or even no-code software tools available online. With monolithic blockchains, it comes down to selecting the layer-1 (or layer-2) that best meets their technical and business requirements. In modular web3, the technical diversity and long-term social unknowns make choosing a protocol an already overwhelming task. 

In the modular paradigm, a developer must understand how to construct the blockchain stack one layer at a time. However, many modular solutions are still in highly developmental stages, and it will take time to battle-test them for reliability and long-term relevance.  

Additionally, many technical integrations and critical bridges that make modular architecture functional are incomplete or challenging to build with. Most blockchain roadmaps evolve over time; plans and priorities change, and no promises are certain. 

This puts an immense cognitive load on developers to educate themselves about the differentiators of countless new protocols, associated security risks, trust assumptions, and overall technical readiness. And even once this is all figured out, there is a lack of shared resources that sufficiently guide developers on how to stack these technologies together. 

DApp development is, therefore, high-risk, inconvenient, and very complex in its current form. Until we think more tactically about how these pieces fit together, it will be challenging for any developer to build consumer-friendly products.

We’ve been here before

There are plenty of lessons from the evolution of web2 that can and should be applied to web3. In its earlier phases, developers would run their own servers and might build sophisticated client-server interactions to produce web2-like applications, but it was an arduous and cumbersome process. It wasn’t until significant advances in cloud computing, JavaScript, AJAX, and responsive design that developers had fertile ground to build a web2 capable of achieving mass adoption.

Once the common traits of web2 systems were abstracted away from programmers, it became simple enough for large-scale experimentation. This eventually led to the phenomenal successful consumer applications we see today. This is what we must achieve for web3.

Building on a monolithic chain has edged closer to this state. Take Ethereum (ETH) as an example. Despite its constraints, developers have a clear understanding of how to build a dApp. It created the first true generation of web3 developers who eventually moved on to experiment with other blockchains.

Now, developers’ motivations have evolved past initial curiosity and experimentation, and they want to build sophisticated products that solve problems and create impact. These products require the flexibility and agility of modular solutions to work. 

However, this flexibility introduces significantly more complexity. Exponentially, more decisions must be made when composing a modular framework. If we are to enable bolder experimentation and product development in web3, these complexities must be abstracted away in the same way they were in web2.

Building bridges, not islands

As modular protocol builders, we must acknowledge that this is a messy process but one we can systematize. We must create streamlined pathways between protocols and simplify the integration process so that any developer—web3 native or not—can build in easy steps.

There are three primary opportunities where we can collectively begin tackling these challenges.

Cross-platform networks. Core developers from different modular protocols could work together to create shared tools and interfaces that help developers build streamlined products. Developing these shared prototypes that package multiple protocols together will improve the developer experience, as they will be better able to identify the optimal setup according to their dApp’s needs, and seamlessly integrate these elements into their stack. 

Shared documentation. Create content, tutorials, and documentation that clearly illustrate how to stack various modular protocols together, express how integrations function, and how one system might complement another. It will help developers better assess their needs, make more educated choices, and ultimately build stronger dApps.

Shared experiment weeks. Coordinate partnered initiatives that bring developers across multiple modular communities together and invite them to experiment and build. This would help developers better understand the dApp-building process across the modular stack, unlock new opportunities for shared development, and catalyze dApp production through experimentation. 

The Cambrian explosion of modular solutions means that we see innovation in every corner, but we cannot continue to work in silos. For our protocols to achieve their fullest potential, we must move beyond the competition that consumes our time and energy at each layer and think about how we can collaborate across it. We only succeed when we reach the stage where developers can just focus on building their products, not the infrastructure we have designed to underpin them. 

Erick de Moura

Erick de Moura

Erick de Moura, co-founder of Cartesi, brings over 20 years of software industry expertise, encompassing software business, development processes, and system architecture. Prior to Cartesi, he led teams and projects in diverse sectors, including healthtech, e-commerce, and infrastructure. Currently, Erick serves as a board member and advisor to The Cartesi Foundation.



Source link

Censorship Resistance

AARON: Ocean’s DATUM Is Tackling Bitcoin’s Most Pressing Problem

Published

on


Follow Aaron on Nostr or X.

It’s difficult to find a more fundamental threat to Bitcoin’s continued existence than mining centralization. If —say— there are only a few mining pools, there is a very real possibility that these organizations face regulatory pressure of the kind that exchanges have also had to deal with: they could be forced to only include KYC’ed transactions into blocks. Since censorship resistance is arguably its core value proposition, I seriously doubt that Bitcoin would, in this scenario, have much long-term viability at all.

To that end, it was great to see Ocean launch DATUM (Decentralized Alternative Templates for Universal Mining) this weekend. Similar to Stratum V2 (implemented by Demand Pool), DATUM allows miners (or: “hashers”) to select the transactions they include in the blocks they find, while still splitting the block reward with other users of the pool. In other words, hashers get the benefit of pooled mining, without having to outsource transaction selection to the Ocean pool operators, thus making it more difficult to apply regulation. (It’s much easier to regulate a few big businesses —mining pools— in a handful of jurisdictions, than it is to regulate many smaller businesses and individuals —hashers— from around the world.)

Of course, the adversarial mindset will recognize that this doesn’t in itself solve the problem of mining centralization in its entirety. Most obviously, draconian lawmakers could ultimately just ban this type of pooled mining altogether. Besides, it’s not really clear that there is a demand from hashers to construct their own blocks in the first place– though that might of course quickly change if and when there in fact is regulatory pressure that stops pools from including certain transactions in blocks. (And Ocean is providing an incentive for hashers to select their own transactions by cutting fees for those that make use of the new feature.)

Either way, DATUM is an important step in the right direction. If nothing else, it should take away a lot of the concerns of Ocean themselves refusing to include certain “spam” transactions in their blocks: now every hasher can decide for themselves what transactions they do and do not want to include.

The more difficult it is to thwart Bitcoin’s censorship resistance, the brighter Bitcoin’s future looks.



Source link

Continue Reading

Adoption

SocialFi, web3, and UX: Cracking the trillion dollar creator economy

Published

on


Disclosure: The views and opinions expressed here belong solely to the author and do not represent the views and opinions of crypto.news’ editorial.

SocialFi is a web3 industry attempt at solving the problem of monetizing digital content—the genuine issue affecting millions of talented creators worldwide.

From the perspective of daily users, it might be hard to see creators struggling. However, despite producing quality content daily, the overwhelming majority do not make any money at all. Many SocialFi projects have been launched in the last couple of years, aiming to solve this very monetization part by rewarding every digital interaction for both creators and users. Unfortunately, most seem to have missed the mark by leaning too heavily on aspects of decentralization rather than offering real-world solutions to existing problems. 

The origins of mass interest in this space occurred during the pandemic lockdowns. With the idea of pursuing a passion-based career becoming more mainstream, the future of social monetization was catapulted into a new growth phase. This was also a time when the crypto industry saw a mass influx of retail investors, with industry narratives steering towards building pragmatic, real-world solutions. This led to significant advancement in the SocialFi movement, and plenty has been achieved since then in terms of on-chain innovation, tokenized community governance, integration of NFTs, and other DeFi products that authentically bridge issues around creator monetization and user rewards. 

Yet, as a sector claiming to be the future of the trillion-dollar creator and freelancer economy, the modest market cap of SocialFi tokens is over $2 billion. This indicates that the sector has a long way to go in establishing itself into a global financial ecosystem. Contrast this with DeFi’s market cap (around $70 billion) or even of NFTs (around $62 billion), and it’s clear that SocialFi has a long road ahead. 

Thankfully, there are signs that SocialFi platforms and the utility tokens that power them have a bright future. This is seen in the significant volume of new users willing to join a newly launched SocialFi platform. Sure, many of these users are only there for the free rewards, but that’s the current norm for web3, whether they like it or not.

The benefits of SocialFi

To benefit from such early user traction, builders in SocialFi must be real with themselves when designing a product. The reality is that very few creators care about (or will even benefit from) decentralized content ownership or on-chain proof of IP rights. Although this is a USP widely marketed in web3, it only benefits the top 1% of celebrity creators in the world. 

What about the masses? What USP will win their attention and loyalty? The answer to this holds the solution for how SocialFi platforms can finally win market share from Big Tech’s platforms, and central to this is building hybrid ecosystems. This means fusing blockchain features (such as tokenization) with non-blockchain architecture, providing an intuitive and seamless user experience for the masses. 

While DeFi and blockchain technologies have a variety of clear benefits and value, mass adoption won’t happen if web2 users are required to get past the web3 wall of creating a digital wallet, store a 20-word seed phrase, and interact with an unfamiliar user experience. If creating an account is harder than starting an Instagram account, you’ve already lost 95% of all potential users. From a user experience standpoint, people cannot be held back by the intimidating web3 gates. 

Appealing to the masses

The winners in this space will focus on the narrative that appeals to the masses, building a community of real creators, empowering them with web3 education, and implementing real-world token utility into a seamless user experience. That’s the formula for SocialFi’s success. 

Without a doubt, the SocialFi community is tackling these challenges, and 2024 remains a crucial year for projects in this space. The current wave of innovation is the most exciting one, as projects roll out user-centric features that focus on user experience and build upon the value that traditional platforms have already created for the creator community. Tokens matter, but as a secondary driver of growth, and should only exist as a medium to enhance the user experience. This realization will shape the sector moving forward.

Dave Catudal

Dave Catudal

Dave Catudal, co-founder of Lyvely, is an accomplished entrepreneur in tech and wellness with an extensive background in product innovation and e-commerce. Credited with founding several successful wellness ventures, Dave is building the future of SocialFi at Lyvely, integrating various aspects of web3 to deliver transparent monetization and engagement tools for the creator and freelance economy. Dave previously founded one of the GCC region’s fastest-growing D2C health supplement brands. He also holds a patent for his best-selling fitness machine and online program in the US.



Source link

Continue Reading

crypto custody

Centralizing SaaS wallets: Killing autonomy for the sake of convenience?

Published

on


Disclosure: The views and opinions expressed here belong solely to the author and do not represent the views and opinions of crypto.news’ editorial.

Traditional software-as-a-service-based multi-party computation custodians are often seen as the “convenient” solution in the crypto universe, managing a staggering portion of decentralized assets. But the reality is that the convenience quickly wears off, revealing a host of limitations, unexpected risks, and challenges as you dive deeper into the technological aspects of protecting digital currency. 

Regardless of your decentralization versus centralization stance, it is essential to recognize that the appearance of private key control can be skewered by a lack of control in policy governance and infrastructure you do not run yourself.

The rise and risks of SaaS-based MPC wallets 

The emergence of SaaS-based MPC wallets has significantly impacted the crypto landscape, allowing businesses to manage digital assets with convenience and perceived security. These wallets are typically provided by tech companies that are currently positioning themselves more and more as non-custodial service providers. However, despite this label, these solutions still require users to trust a centralized party to coordinate signing and key generation securely, placing them high on the custody spectrum in terms of control over assets. 

This reliance on a centralized service provider creates a situation where control and security are not entirely in the hands of the institution using the service. While these tech providers do not operate as traditional third-party custodians, such as BitGo or Anchorage—highly regulated and offer fully managed custodial services—they still introduce a central point of control and potential vulnerability. As used by both SaaS-based providers and traditional custodians, MPC technology involves splitting cryptographic keys required for transactions into multiple parts distributed among various parties to enhance security. 

However, in the case of SaaS-based solutions, the centralization of these services within a few dominant players introduces new risks. One of them is that these providers become attractive targets for hackers due to their significant control over many clients’ assets, creating a vulnerability similar to that of centralized exchanges. Two, the concentration of control in these SaaS-based models not only increases security risks but indirectly limits the autonomy of crypto businesses.

By relying on an external provider to manage critical aspects of digital asset security, institutions may find themselves constrained in managing policies, procedures, and the overall governance of their assets. This centralization stands in contrast to the decentralized ethos of the crypto industry, where individual sovereignty over digital assets is paramount.

The challenges of dependency and trust in MPC custodians 

While MPC wallets often claim to be non-custodial because the institution holds part of the key, the reality is far more complex: the heavy dependency on third-party vendors for day-to-day operations, security, and service availability introduces significant risks. Despite the customer institution holding a key share, all other components affecting the use or potential misuse of key shares remain under the vendor’s control. This setup creates vulnerabilities around key signing integrity but, even more importantly, introduces friction into the customer experience, an operational risk that should be accounted for.  For instance, any policy change can take up to a few weeks if it is not prioritized by the vendor, posing significant delays and operational inefficiencies​.

Analyze this potential impact further. MPC wallets can have longer transaction times, and their reliance on vendors for routine account changes and maintenance can be problematic. If a team member leaves, revoking their access is done at the vendor’s tempo. It can take considerable time, resulting in a period where the security of assets may be compromised. Additionally, service downtimes for maintenance during business hours can disrupt operations. Plus, in disaster scenarios, asset recovery can take up to 48 hours—a period that is far too long for any organization dealing with high-value transactions. These operational dependencies can be highly inconvenient. Ultimately, they pose security risks that contradict what decentralization stands for—namely, running your own wallet infrastructure.

For regulated financial institutions or firms with stringent security requirements, these dependencies are deal-breakers. That’s because the operational risks and costs associated with relying on third-party MPC wallet solutions are often unacceptable to internal risk teams. These teams are unable to get comfortable with the inherent uncertainties and potential for delayed response times that these products entail. Consequently, many MPC wallet solutions fail to pass the rigorous scrutiny of risk assessments, preventing them from being adopted by institutions that require the highest levels of security and operational control​.

A new paradigm for crypto custody

If the incumbent SaaS solutions represent the ‘trust us’ model, the ideal solution should transition towards a ‘trust but verify’ approach and, ultimately, a ‘never trust, always verify’ model. This shift empowers customers to partially or fully host the software, granting them control and ownership of critical IT infrastructure. By eliminating the opaque operations inherent in black box SaaS solutions, institutions not only mitigate operational risks hidden in the friction of operating in a third party’s sandbox but also enable more agile and flexible infrastructure management.

This enhanced control supports better risk management and allows institutions to adapt quickly to market demands, ultimately driving revenue growth and positively impacting the bottom line.

A practical solution integrates critical management and policy controls into a comprehensive platform, allowing institutions to manage their digital assets within a zero-trust security framework. This architecture continuously validates every interaction, eliminating implicit trust and enhancing security. By adopting a service-oriented architecture, institutions can tailor the system to their unique requirements, ensuring scalability, high performance, and robust security. 

Current market offerings, which rely entirely on SaaS-based MPC wallets, place undue trust in vendors who control all components, including cryptographic processes, keys, policies, and transaction data. By moving towards solutions that enable institutions to own and control critical parts of their digital asset infrastructure, the industry can mitigate risks and reduce vulnerabilities while operating more closely to the principles of decentralization. Such a transformation is essential for fostering trust and security in the rapidly evolving crypto landscape​.

Now is the time for institutions to take control of their policies. By adopting models that provide partial or complete control over key management and policy enforcement, institutions can better align with the correct treatment and oversight of service providers or outsourcing arrangements. This paradigm shift is essential for the industry’s future, and it’s something that is poised to safeguard crypto’s core values while paving the way for continued innovation and trust.

Haden Patrick

Haden Patrick

Haden Patrick is the director of business operations of Cordial Systems, a provider of institutional-grade self-custody software using a zero-trust security model.  Haden has executive experience in team leadership, engineering, and education originating from his 24-year career as a Naval Officer. After co-founding SoloKeys, the first open-source security key company, he managed projects connecting web3 to traditional finance at a cryptocurrency trading firm before joining Cordial Systems.



Source link

Continue Reading
Advertisement [ethereumads]

Trending

    wpChatIcon