Do these three things well to get rid of the Crypto Trust Crisis easily
Original article by Ria Bhutoria
The DeFi way
In 2022, the Crypto industry faced catastrophic events due to excessive risk-taking and apparent fraud, leading many to question whether what we are doing is good for society. Opaque, exploitative, and corrupt platforms reached enormous proportions before collapsing, harming innocent bystanders, much like the failure of traditional market participants.
However, these events do not represent what would be possible if we optimized the crypto network specific properties. Members who remain today still believe there is an opportunity to build monetary, financial and technological systems that provide fair, resilient and sustainable alternatives to existing platforms and systems that wrongly extract value from participants.
In order to move forward, we must, of course, identify where we have failed. But we also have to acknowledge what works and rearticulate the attributes we want our new system to have:
Sovereignty gives control to the individual
Accountability, checks and balances on intermediaries
Credible neutrality to participate in the crypto economy without permission
Self-sovereignty -- the ability to control our assets, data and identity -- is one of the most powerful attributes the crypto network offers and has never been more important. When users have ownership of their assets and data, they don't have to rely on third-party providers or trust intermediaries to do no evil. They can't do evil.
However, today's self-custody puts excessive demands on the end user. It has no safety net. That's why users cede control to centralized providers that feel familiar and secure but fail them time and time again. Users will eventually want to be freed from this, where a few centralized providers control (and sometimes abuse) access to user assets and data.
A major obstacle to self-hosting is that most L1 wallets (such as Bitcoin and Ethereum) are configured as private key accounts (formally known as externally owned accounts, EOAs). For private key accounts (whether "hot" - online - or "cold" - offline), the individual is responsible for keeping the private key and mnemonics associated with his or her account. This private key and mnemonic combination has a single point of failure: if lost or leaked, all assets associated with the key are lost.
In fact, Coinbase found that key loss was one of the most frequent support requests from its unmanaged wallet users, confirming that most users were unprepared to secure and manage their keys. Analysts also estimate that the loss of assets due to the failure to secure keys is significant.
Until now, users have had to choose between accessibility and control. There are two different approaches to resolving this tradeoff -- multi-party computation and account abstraction. Both approaches have the benefit of eliminating a single point of failure and making self-hosting more convenient.
Today, one way to support autonomous hosting is multi-party computing. At a high level, the MPC protocol facilitates distributed key generation and transaction signature through a threshold of down-chain parties. Different entities (or devices owned by a single entity) hold separate "shares" that collectively represent a separate private key, and all devices do not hold the full key.
Because the computation is done off-chain, the MPC wallet transaction looks the same as the private key wallet transaction and is cheaper than the multi-signature transaction. MPC wallets are chain-agnostic and can support different signature schemes (as opposed to multi-signature -- and smart contract wallets more broadly -- they are not chain-agnostic). In addition, given that key shares are distributed and can be rotated, the MPC wallet has no single point of failure, provides enhanced security and seedless recovery, and harmonizes previously conflicting features of convenience and control.
Last year, Coinbase used MPCS (where Coinbase and users hold key shares) to overhaul the infrastructure behind its retail app in order to give users more flexibility to access decentralized apps (DApps) directly through the Coinbase app, while maintaining strong security guarantees. The use of MPC technology for digital asset hosting is also common among institutional providers such as Fordefi and Fireblocks.
Lit Protocol and Entropy are on-chain protocols that use MPCS in interesting ways to unlock distributed and programmable access control and key management. Recent proof of concept on Lit includes using the protocol to validate transactions initiated from web2 (e.g., Google) accounts, suggesting that MPCS can generate wallets and recovery mechanisms similar to web2.
Account abstraction is another way to improve autonomous hosting, but at a deeper level in the stack. Account abstraction proposes to embed smart contract functionality into a contract account in a user's account, which is the default account type on the chain. In the process, it seeks to maintain the benefits of self-hosting while enabling greater functionality, flexibility, and customization.
Contract accounts are not generic accounts operated by a single private key, but are controlled by code that can be customized to meet the needs of different users. They provide user-friendly recovery mechanisms, such as social recovery, where, similar to MPCS, users can designate multiple transaction signers and designate a third party as one of those signers to assist in account recovery. They also covered the ability to adopt different signature schemes, define transaction parameters (for example, set spending limits, delegate fraud monitoring), and enable "multi-party invocation" atomic transactions (bundling multiple operations into a single transaction).
Introducing account abstraction at the base layer has been on Ethereum's roadmap since 2016. A recent proposal (ERC-4337) aims to mimic the account abstraction on L1 without changing the consensus layer protocol (although the timing and feasibility of this proposal are still under discussion). Even faster, L2's like Starknet and zksync are rolling out native integrated account abstractions. This is a positive development, especially as user activity and interaction with on-chain applications shifts from L1 to L2. In December, Visa outlined in the article it how to use native account on Starknet abstract to implement automatic (pull) to pay.
I look forward to seeing continued experimentation and development of MPCS, making the MPC library more open, battle-tested and standardized, and establishing account abstractions into on-chain specifications. As we achieve this goal, I would like to see the use of more technologies, either independently or in combination, to address the possible shortcomings of one after the other.
Autonomy may be one of the industry's most important long-term goals. However, it will take time to level the playing field between unmanaged and managed experiences, and we may never completely close the convenience gap between managed and unmanaged systems.
There will probably always be users who prefer to use cryptocurrencies through a centralized platform. In addition, certain stakeholders (institutions) are legally required to proxy escrow and will always rely on third party providers. Recognizing this, we have a responsibility to direct users -- retail and institutional -- to responsible platforms.
In our favor, auditing chain balances and activity is a breeze using encryption techniques for encrypted networks. Transparency and auditability are inherent properties of encrypted networks and are often discussed in the context of decentralized applications and protocols. With some effort, cryptocurrency transparency guarantees could be extended to centralised trading platforms and custodians involved in operations on the chain -- in particular through proof of reserves.
Proof of Reserves Proof of matching platform assets (digital asset balances) with outstanding liabilities (customer deposits) using a cryptographic mechanism. This process allows stakeholders to verify that the entity holding the digital assets on behalf of the customer actually owns the funds to which the customer is entitled. Relevant technical details, I recommend the Nic Carter , etc and Vitalik Buterin articles and ZK podcast about this topic.
Not all proof-of-stockpile procedures are created equal, and poor implementation may reveal sensitive information or contain attack surfaces that do not provide the assurance we seek. However, best practices over the years have enabled platforms to provide reasonable assurance to stakeholders that they are solvent, while maintaining platform and customer confidentiality in an automated manner.
Service providers have avoided using these tools in the past, mainly because stakeholders (e.g., customers, investors, regulators) did not demand it. However, we are now at a stage where trust in crypto institutions is broken. Increasingly, the crypto industry does not enjoy the industry standards and regulatory clarity of traditional finance. In response, several trading platforms have pledged to conduct reserve certification, although the rationality of individual implementation plans needs to be studied.
Through self-regulation and standardised reserve certification, we can not only rebuild trust, but also provide a consistent level of transparency and assurance not available in traditional asset classes. Moreover, as the unmanaged initiatives discussed above evolve and mature, I would like to see the requirement for centralized platforms go beyond just publishing proof of reserves and offer hybrid hosting models that shift power to the user side.
At the same time, we should also try to strengthen DeFi and make it easier to use. DeFi replaces intermediaries with smart contracts that enforce rules along the chain, making them inherently auditable and corruption-proof. The collapse of the irresponsible CeFi agency last year reminds us why the (carefully designed) DeFi agreement is valuable - because transparency is intrinsic to it.
In addressing these issues, we need to stay true to crypto's core values of credible neutrality. The new system we are building needs to be open, unrestricted, empowered and resistant to censorship.
Concerns about Ethereum censorship arose when OFAC (Office of Foreign Assets Control of the U.S. Treasury Department) decided to sanction smart contracts linked to Tornado Cash, a privacy-protecting hybrid. To avoid the consequences of compliance issues, many ecosystem participants began to censor the address transactions that interacted with the coin-mixing tool, leading many to question Ethereum's trusted neutrality. If one entity can decide who gets to use Ethereum and how, then what's left of the system we're building other than another set of centralized and easily censored databases?
At the same time, mergers (Ethereum's transition to proof of interest) change the power dynamics among protocol participants. Block construction and proposal are separated, known as proposer-builder separation (PBS), by out-of-protocol software (relays) located between the verifier and block builder, allowing verifiers large and small to capture MEVs (maximum extractable value) and preventing verifier centralization by transferring economies of scale from the MEVs to the block builders.
Note: James Prestwich & have spent A succinct description of today's MEV supply chain is "Users create MEVs, searchers extract them. Searchers pay builders; builders pay proposers."
Although the verifiers did not perform the review directly, after the merger they began to receive fully built blocks rather than transaction packages. Thus, the verifier proposing blocks from the review relay/builder is the default review because they can no longer attach transactions that these entities may have excluded, delaying the inclusion of the transaction. Concerns are heightened by the fact that the largest relays and builders are sharing the blocks under review.
The community responded quickly to implement interim measures to improve the resilience of the network, including:
Flashbots is open source to encourage and support the development of a diverse and healthy relay market.
Neutral Repeaters such as Gnosis's Agnostic Relay, ultrasoundmoney's Ultrasound Relay, Relayooor and Aestus came into being.
Flashbots open-source its builders to lower the barriers to developing competitive builders.
Flashbots introduced min-bid (a new parameter in its successor software) that allows validators to specify a threshold below which they will build blocks locally.
The verifier consciously connects to the non-vetting relay to reduce de facto vetting.
Those efforts are beginning to pay off. After peaking at nearly 80% in November 2022, the proportion of blocks under review (or "compliance") has fallen to 67%, according to data last week (as of January 5). In addition, while Flashbots' dominance in the relay block is still high, it has declined over the past few months. Ultimately, Ethereum plans to further strengthen the network's censorship resistance by building relay functionality into the protocol through the proposer-builder separation (PBS) within the protocol.
The centralization of the builder market remains, with the top five entities controlling about 85% of the blocks in the past week, but the distribution among these entities has improved now compared to a few months ago when a single entity dominated. Still, there are no initiatives actively pushing builders to be accountable for neutrality, and this needs to change.
We need to introduce checks and balances at the protocol layer on builders (for example, through transaction inclusion lists) and proposers (for example, through repledge on Eigenlayer) to decentralize the builder market and avoid situations where a single entity dominates block production and imposes arbitrary preferences on users. Regarding builder decentralization, Flashbots announced SUAVE (Single Unified Auction for Value Expression), a new approach to isolate and decentralize block building, while also building a mechanism to return extracted value to the creator (user).
Such protocol-level solutions: (1) adjust incentives rather than relying purely on the benevolence of the community to provide strong safeguards against censorship; (2) A more equitable distribution of acquired value to those who produce it is necessary. But early progress should inspire optimism and confidence that the community will continue to prioritize and strengthen the credible neutrality of our foundation.
"Only when you've been on fire can you really listen to advice about fire." -- J. R. R. Tolkien
Last year, we had to learn the hard way because some bad actors strayed from the ideals on which this industry lives. This unfortunate sequence of events reminds us that we need to leverage crypto's core attributes into the centralized and decentralized products we're building, rather than abstracting them. If we return to the core values that united us in the first place, I believe crypto's original vision can be realized.
Original link
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia