24 posts tagged with "Ethereum"

Maximal Extractable Value (MEV) is not just a trader’s bogeyman—it’s the economic engine quietly shaping how blocks get built, how wallets route orders, and how protocols design markets. Here’s a pragmatic guide for founders, engineers, traders, and validators.

TL;DR​

• What MEV is: Extra value a block producer (validator/sequencer) or their partners can extract by reordering, inserting, or excluding transactions beyond base rewards and gas.
• Why it exists: Public mempools, deterministic execution, and transaction-order dependencies (e.g., AMM slippage) create profitable ordering games.
• How modern MEV works: A supply chain—wallets & orderflow auctions → searchers → builders → relays → proposers—formalized by Proposer-Builder Separation (PBS) and MEV-Boost.
• User protections today: Private transaction submission and Order Flow Auctions (OFAs) can reduce sandwich risk and share price improvement with users.
• What’s next (as of September 2025): Enshrined PBS, inclusion lists, MEV-burn, SUAVE, and shared sequencers for L2s—all aimed at fairness and resilience.

The Five-Minute Mental Model​

Think of blockspace as a scarce resource sold every 12 seconds on Ethereum. When you send a transaction, it lands in a public waiting area called the mempool. Some transactions, particularly DEX swaps, liquidations, and arbitrage opportunities, have ordering-dependent payoffs. Their outcome and profitability change based on where they land in a block relative to other transactions. This creates a high-stakes game for whoever controls the ordering.

The maximum potential profit from this game is Maximal Extractable Value (MEV). A clean, canonical definition is:

“The maximum value extractable from block production in excess of the standard block reward and gas fees by including, excluding, and changing the order of transactions.”

This phenomenon was first formalized in the 2019 academic paper “Flash Boys 2.0,” which documented the chaotic "priority gas auctions" (where bots would bid up gas fees to get their transaction included first) and highlighted the risks this posed to consensus stability.

A Quick Taxonomy (With Examples)​

MEV isn't a single activity but a category of strategies. Here are the most common ones:

• DEX Arbitrage (Backrunning): Imagine a large swap on Uniswap causes the price of ETH to drop relative to its price on Curve. An arbitrageur can buy the cheap ETH on Uniswap and sell it on Curve for an instant profit. This is a "backrun" because it happens immediately after the price-moving transaction. This form of MEV is generally considered beneficial as it helps keep prices consistent across markets.
• Sandwiching: This is the most infamous and directly harmful form of MEV. An attacker spots a user's large buy order in the mempool. They frontrun the user by buying the same asset just before them, pushing the price up. The victim's trade then executes at this worse, higher price. The attacker then immediately backruns the victim by selling the asset, capturing the price difference. This exploits the user's specified slippage tolerance.
• Liquidations: In lending protocols like Aave or Compound, positions become under-collateralized if the value of their collateral drops. These protocols offer a bonus to whoever is first to liquidate the position. This creates a race among bots to be the first to call the liquidation function and claim the reward.
• NFT Mint “Gas Wars” (Legacy Pattern): In hyped NFT mints, a race ensues to secure a limited-supply token. Bots would compete fiercely for the earliest slots in a block, often bidding up gas prices to astronomical levels for the entire network.
• Cross-Domain MEV: As activity fragments across Layer 1s, Layer 2s, and different rollups, opportunities arise to profit from price differences between these isolated environments. This is a rapidly growing and complex area of MEV extraction.

The Modern MEV Supply Chain (Post-Merge)​

Before the Merge, miners controlled transaction ordering. Now, validators do. To prevent validators from becoming overly centralized and specialized, the Ethereum community developed Proposer-Builder Separation (PBS). This principle splits the job of proposing a block for the chain from the complex job of building the most profitable block.

In practice today, most validators use middleware called MEV-Boost. This software lets them outsource block building to a competitive market. The high-level flow looks like this:

1. User/Wallet: A user initiates a transaction, either sending it to the public mempool or to a private RPC endpoint that offers protection.
2. Searchers/Solvers: These are sophisticated actors who constantly monitor the mempool for MEV opportunities. They create "bundles" of transactions (e.g., a frontrun, a victim's trade, and a backrun) to capture this value.
3. Builders: These are highly specialized entities that aggregate bundles from searchers and other transactions to construct the most profitable block possible. They compete against each other to create the highest-value block.
4. Relays: These act as trusted middlemen. Builders submit their blocks to relays, which check them for validity and hide the contents from the proposer until it's signed. This prevents the proposer from stealing the builder's hard work.
5. Proposer/Validator: The validator running MEV-Boost queries multiple relays and simply chooses the most profitable block header offered. They sign it blindly, without seeing the contents, and collect the payment from the winning builder.

While PBS has successfully broadened access to block building, it has also led to centralization among a small set of high-performance builders and relays. Recent studies show that a handful of builders produce the vast majority of blocks on Ethereum, which is an ongoing concern for the network's long-term decentralization and censorship resistance.

Why MEV Can Be Harmful​

• Direct User Cost: Sandwich attacks and other forms of frontrunning result in worse execution quality for users. You pay more for an asset or receive less than you should have, with the difference being captured by a searcher.
• Consensus Risk: In extreme cases, MEV can threaten the stability of the blockchain itself. Before the Merge, "time-bandit" attacks were a theoretical concern where miners could be incentivized to re-organize the blockchain to capture a past MEV opportunity, undermining finality.
• Market Structure Risk: The MEV supply chain can create powerful incumbents. Exclusive order flow deals between wallets and builders can create paywalls for user transactions, entrenching builder/relay oligopolies and threatening the core principles of neutrality and censorship resistance.

What Actually Works Today (Practical Mitigations)​

You are not powerless against harmful MEV. A suite of tools and best practices has emerged to protect users and align the ecosystem.

For Users and Traders​

• Use a Private Submission Path: Services like Flashbots Protect offer a "protect" RPC endpoint for your wallet. Sending your transaction through it keeps it out of the public mempool, making it invisible to sandwich bots. Some services can even refund you a portion of the MEV extracted from your trade.
• Prefer OFA-Backed Routers: Order Flow Auctions (OFAs) are a powerful defense. Instead of sending your swap to the mempool, routers like CoW Swap or UniswapX send your intent to a competitive marketplace of solvers. These solvers compete to give you the best possible price, effectively returning any potential MEV back to you as price improvement.
• Tighten Slippage: For illiquid pairs, manually set a low slippage tolerance (e.g., 0.1%) to limit the maximum profit a sandwich attacker can extract. Breaking large trades into smaller chunks can also help.

For Wallets & Dapps​

• Integrate an OFA: By default, route user transactions through an Order Flow Auction. This is the most effective way to protect users from sandwich attacks and provide them with superior execution quality.
• Offer Private RPC as Default: Make protected RPCs the default setting in your wallet or dapp. Allow power users to configure their builder and relay preferences to fine-tune the trade-off between privacy and inclusion speed.
• Measure Execution Quality: Don't just assume your routing is optimal. Benchmark your execution against public mempool routing and quantify the price improvement gained from OFAs and private submission.

For Validators​

• Run MEV-Boost: Participate in the PBS market to maximize your staking rewards.
• Diversify: Connect to a diverse set of relays and builders to avoid dependence on a single provider and enhance network resilience. Monitor your rewards and block inclusion rates to ensure you are well-connected.

L2s & the Rise of SEV (Sequencer Extractable Value)​

Layer 2 rollups don't eliminate MEV; they just change its name. Rollups concentrate ordering power in a single entity called the sequencer, creating Sequencer Extractable Value (SEV). Empirical research shows that MEV is widespread on L2s, though often with lower profit margins than on L1.

To combat the centralization risk of a single sequencer per rollup, concepts like shared sequencers are emerging. These are decentralized marketplaces that allow multiple rollups to share a single, neutral entity for transaction ordering, aiming to arbitrate cross-rollup MEV more fairly.

What’s Coming Next (And Why It Matters)​

The work to tame MEV is far from over. Several major protocol-level upgrades are on the horizon:

• Enshrined PBS (ePBS): This aims to move Proposer-Builder Separation directly into the Ethereum protocol itself, reducing the reliance on trusted, centralized relays and hardening the network's security guarantees.
• Inclusion Lists (EIP-7547): This proposal gives proposers a way to force a builder to include a specific set of transactions. It's a powerful tool to combat censorship, ensuring that even transactions with low fees can eventually make it onto the chain.
• MEV-Burn: Similar to how EIP-1559 burns a portion of the base gas fee, MEV-burn proposes to burn a portion of builder payments. This would smooth out MEV revenue spikes, reduce incentives for destabilizing behavior, and redistribute value back to all ETH holders.
• SUAVE (Single Unifying Auction for Value Expression): A project by Flashbots to create a decentralized, privacy-preserving auction layer for orderflow. The goal is to create a more open and fair market for block building and combat the trend toward exclusive, centralized deals.
• OFA Standardization: As auctions become the norm, work is underway to create formal metrics and open tooling to quantify and compare the price improvement offered by different routers, raising the bar for execution quality across the entire ecosystem.

A Founder’s Checklist (Ship MEV-Aware Products)​

• Default to Privacy: Route user flow through private submission or encrypted intents-based systems.
• Design for Auctions, Not Races: Avoid "first-come, first-served" mechanics that create latency games. Leverage batch auctions or OFAs to create fair and efficient markets.
• Instrument Everything: Log slippage, effective price versus oracle price, and the opportunity cost of your routing decisions. Be transparent with your users about their execution quality.
• Diversify Dependencies: Rely on multiple builders and relays today. Prepare your infrastructure for the transition to enshrined PBS tomorrow.
• Plan for L2s: If you're building a multichain application, account for SEV and cross-domain MEV in your design.

Developer FAQ​

• Is MEV “bad” or “illegal”? MEV is an unavoidable byproduct of open, deterministic blockchain markets. Some forms, like arbitrage and liquidations, are essential for market efficiency. Others, like sandwiching, are purely extractive and harmful to users. The goal isn't to eliminate MEV but to design mechanisms that minimize the harm and align extraction with user benefit and network security. Its legal status is complex and varies by jurisdiction.
• Does private transaction submission guarantee no sandwiches? It significantly reduces your exposure by keeping your transaction out of the public mempool where most bots are looking. When combined with an OFA, it's a very strong defense. However, no system is perfect, and guarantees depend on the specific policies of the private relay and builders you use.
• Why not just “turn MEV off”? You can't. As long as there are on-chain markets with price inefficiencies (which is always), there will be profit in correcting them. Trying to eliminate it entirely would likely break useful economic functions. The more productive path is to manage and redistribute it through better mechanism design like ePBS, inclusion lists, and MEV-burn.

Further Reading​

• Canonical definition & overview: Ethereum.org—MEV docs
• Origins & risks: Flash Boys 2.0 (Daian et al., 2019)
• PBS/MEV-Boost primer: Flashbots docs and MEV-Boost in a Nutshell
• OFA research: Uniswap Labs—Quantifying Price Improvement in Order Flow Auctions
• ePBS & MEV-burn: Ethereum Research forum discussions
• L2 MEV evidence: Empirical analyses across major rollups (e.g., "Analyzing the Extraction of MEV Across Layer-2 Rollups")

Bottom Line​

MEV isn’t a glitch; it’s an incentive gradient inherent to blockchains. The winning approach is not denial—it’s mechanism design. The goal is to make value extraction contestable, transparent, and user-aligned. If you’re building, bake this awareness into your product from day one. If you’re trading, insist your tools do it for you. The ecosystem is rapidly converging on this more mature, resilient future—now is the time to design for it.

Ethereum, the world's most adopted blockchain platform for smart contracts, is known for its regular upgrades, each bringing forth new features, parameter adjustments, or enhanced security. These upgrades, driven by both proactive innovation and the need to mitigate potential security threats, have punctuated Ethereum's evolution over the years.

Before the Ethereum merge last September, the platform had seen 14 upgrades. Notably, a reactive upgrade occurred in 2016 after the DAO Fork incident when Ethereum Classic (ETC) emerged following a cyber-attack that jeopardized the DAO project's ETH funding.

Over the past few years, significant upgrades have taken place. The London upgrade in August 2020 introduced EIP-1599, introducing ETH burning and dynamic adjustment of the Base Fee for every transaction. In September 2022, the Paris upgrade transitioned Ethereum's consensus mechanism from Proof of Work (POW) to Proof of Stake (POS), signaling the end of the machine mining era.

After the Shanghai upgrade, Ethereum's core development team announced that the most important update this year would be the Cancun upgrade, expected to occur later this year.

Cancun Upgrade: What Is It and Why Does It Matter?​

Named after the city that hosted the Ethereum Developer Conference (Devcon), the upcoming Cancun upgrade will implement crucial improvements to the Ethereum network.

The star of the upgrade, EIP-4844, aims to allow Ethereum nodes to temporarily store and retrieve off-chain data, fulfilling the data and storage needs of blockchain applications. If successfully implemented, EIP-4844 is expected to reduce the costs of Layer 2 (L2) rollup solutions. Reportedly, EIP-4844 has already been tested on four development networks, with a fifth testing network about to launch.

Originally intended for completion during the Shanghai upgrade, EIP-4844 was postponed to the Cancun upgrade. Developers have also agreed to include EIP-6780 (preparing for future application of Verkle Trees), EIP-6475 (providing improved readability and compact serialization), and EIP-1153 (introducing transient storage opcode) in the upgrade.

The Principle Behind the Upgrade​

The essence of Ethereum's scalability efforts lies in increasing data processing volume and speed. Two directions are pursued concurrently – Layer 2 rollups and sharding on the mainnet. The implementation of EIP-4844 is the first step towards complete sharding.

Prior to the Cancun upgrade, L2 information was stored in the Calldata of L1 information. This method was costly and limited due to Calldata's limited space.

With the Cancun upgrade, L1 will be stored in a new location called "Blob". Blob storage is more affordable and offers more space, allowing Ethereum to host more data, increase its transactions per second (TPS), and reduce costs. As Blob is a temporary data package cleaned up every 30 days, nodes only need to download a fixed amount of data per month, decreasing node burden.

In essence, the Cancun upgrade will make L2 cheaper and faster. This will not only benefit L2 protocols but will also foster rapid development for ecosystems built on L2.

In conclusion, the upcoming Ethereum Cancun upgrade promises to be an important milestone, heralding a new era of efficient, affordable, and scalable blockchain applications. Stay tuned for further updates as the Ethereum community continues its pioneering work in advancing decentralized technologies.

Hello and welcome back to our blockchain blog! Today, we will be diving into an exciting new proposal called ERC-4337, which introduces account abstraction to Ethereum without requiring any consensus-layer protocol changes. Instead, this proposal relies on higher-layer infrastructure to achieve its goals. Let's explore what ERC-4337 has to offer and how it addresses the limitations of the current Ethereum ecosystem.

What is ERC-4337?​

ERC-4337 is a proposal that introduces account abstraction to Ethereum through the use of a separate mempool and a new type of pseudo-transaction object called a UserOperation. Users send UserOperation objects into the alternative mempool, where a special class of actors called bundlers package them into a transaction making a handleOps call to a dedicated contract. These transactions are then included in a block.

The proposal aims to achieve several goals:

1. Enable users to use smart contract wallets with arbitrary verification logic as their primary accounts.
2. Completely remove the need for users to have externally owned accounts (EOAs).
3. Ensure decentralization by allowing any bundler to participate in the process of including account-abstracted user operations.
4. Enable all activity to happen over a public mempool, eliminating the need for users to know direct communication addresses of specific actors.
5. Avoid trust assumptions on bundlers.
6. Avoid requiring any Ethereum consensus changes for faster adoption.
7. Support other use cases such as privacy-preserving applications, atomic multi-operations, paying transaction fees with ERC-20 tokens, and developer-sponsored transactions.

Backwards Compatibility​

Since ERC-4337 does not change the consensus layer, there are no direct backwards compatibility issues for Ethereum. However, pre-ERC-4337 accounts are not easily compatible with the new system because they lack the necessary validateUserOp function. This can be addressed by creating an ERC-4337 compatible account that re-implements the verification logic as a wrapper and setting it as the original account’s trusted op submitter.

Reference Implementation​

For those interested in diving deeper into the technical details of ERC-4337, a reference implementation is available at https://github.com/eth-infinitism/account-abstraction/tree/main/contracts.

Security Considerations​

The entry point contract for ERC-4337 must be heavily audited and formally verified, as it serves as a central trust point for the entire system. While this approach reduces the auditing and formal verification load for individual accounts, it does concentrate security risk in the entry point contract, which must be robustly verified.

Verification should cover two primary claims:

1. Safety against arbitrary hijacking: The entry point only calls an account generically if validateUserOp to that specific account has passed.
2. Safety against fee draining: If the entry point calls validateUserOp and passes, it must also make the generic call with calldata equal to op.calldata.

Conclusion​

ERC-4337 is an exciting proposal that aims to introduce account abstraction to Ethereum without requiring consensus-layer protocol changes. By using higher-layer infrastructure, it opens up new possibilities for decentralization, flexibility, and various use cases. While there are security considerations to address, this proposal has the potential to greatly improve the Ethereum ecosystem and user experience.

Withdrawals, gas tweaks, and what came next—without the hype.

The Short Version​

The Shapella upgrade, a portmanteau of Shanghai (for the execution layer) and Capella (for the consensus layer), went live on Ethereum on April 12, 2023. Its landmark feature was enabling staking withdrawals for the first time since the Beacon Chain's launch.

The headline change, EIP-4895, introduced a system where validator withdrawals are automatically "pushed" from the consensus layer to the execution layer, requiring no user transaction or gas fees. Alongside this, four smaller EIPs shipped to fine-tune the EVM, including gas cost reductions (Warm COINBASE), bytecode optimizations (PUSH0), and contract creation limits (Initcode metering). The upgrade also served as a final warning to developers that the SELFDESTRUCT opcode was on its way out.

Shapella effectively closed the loop on the Merge, and the next major upgrade, Dencun, followed on March 13, 2024, shifting the network's focus to scalability with EIP-4844 "blobs."

Why Shapella Was a Critical Milestone​

From the Beacon Chain's inception until April 2023, staking ETH was a one-way street. You could deposit 32 ETH to help secure the network and earn rewards, but you couldn't get your principal or those consensus-layer rewards back out. This locked liquidity was a significant commitment and a barrier for many potential stakers.

Shapella changed everything by opening the exit door.

The upgrade's core was EIP-4895, which ingeniously designed a system-level "withdrawal operation." Instead of requiring stakers to craft a transaction and pay gas to withdraw, the protocol itself now automatically sweeps eligible funds from the consensus layer and pushes them into the execution layer. This clean, push-based design minimized complexity and risk, making the change much easier to test and deploy safely.

What Actually Changed: The EIPs in Plain English​

Shapella was a bundle of five key Ethereum Improvement Proposals (EIPs):

• EIP-4895 — Beacon Chain Withdrawals (Push-based) This was the main event. It enabled both partial (rewards) and full (principal + rewards) withdrawals to flow from the consensus layer to a staker's specified withdrawal address. The key innovation is that these are not user-initiated transactions; they are automatic operations embedded in proposed blocks.

• EIP-3651 — “Warm COINBASE” This EIP made a small but important gas optimization. In the EVM, COINBASE refers to the address of the block producer (the validator), not the exchange. Before Shapella, the first time a smart contract accessed this address within a transaction, it incurred a higher gas cost. EIP-3651 made the COINBASE address "warm" by default, reducing the gas cost for protocols that frequently interact with it, such as those paying MEV tips directly to the block builder.

• EIP-3855 — PUSH0 Opcode A simple but elegant addition to the EVM. This new opcode, PUSH0, does exactly what it says: it pushes the value zero onto the stack. Previously, developers had to use heavier, more expensive opcodes to achieve this. PUSH0 makes bytecode slightly smaller and more gas-efficient, especially for the numerous contracts that initialize variables to zero.

• EIP-3860 — Limit & Meter initcode This change introduced two rules for the code used to create a smart contract (initcode). First, it capped the maximum size of initcode at 49,152 bytes. Second, it added a small gas fee for every 32-byte chunk of this code. This prevents denial-of-service attacks involving overly large contracts and makes contract creation costs more predictable.

• EIP-6049 — Deprecate SELFDESTRUCT (Warning) This wasn't a code change but a formal warning to the developer community. It signaled that the SELFDESTRUCT opcode, which allows a contract to delete itself and send its ETH to a target address, would have its functionality drastically changed in a future upgrade. This gave developers time to phase out their reliance on it before the Dencun upgrade later altered its behavior with EIP-6780.

Withdrawals 101: Partial vs. Full​

Shapella introduced two types of automatic withdrawals, each with its own rules.

• Partial Withdrawals These are automatic rewards sweeps. If a validator's balance grows above 32 ETH from consensus-layer rewards, the protocol automatically "skims" the excess amount and sends it to the designated withdrawal address. The validator remains active and continues its duties. This happens with no action required from the staker.

• Full Withdrawals (Exiting) This is for stakers who want to stop validating and retrieve their entire balance. The staker must first broadcast a voluntary exit message. After a waiting period, the validator becomes eligible for a full withdrawal. Once processed in the sweep, the entire balance is sent to the withdrawal address, and the validator is no longer part of the active set.

Throughput and Cadence​

The network is designed to process withdrawals smoothly without causing instability.

• Up to 16 withdrawals can be included in each block (every 12 seconds), allowing for a maximum of approximately 115,200 withdrawals per day.
• The block proposer scans the list of active validators and includes the first 16 eligible withdrawals. The next block proposer picks up where the last one left off, ensuring every validator gets a turn in the queue.
• To prevent a mass exodus from destabilizing the network, the number of validators that can exit per epoch (every ~6.4 minutes) is limited by a churn limit. This limit is dynamic based on the total number of active validators, smoothing out exit waves.

It's also important to note that consensus-layer rewards are handled by this EIP-4895 withdrawal mechanism, while execution-layer rewards (priority fees and MEV) are sent directly to a validator's configured fee recipient address and are available immediately.

What Came Next: Dencun and the Road to Scalability​

Shapella marked the successful completion of the "Merge era." With staking now a fully liquid, two-way process, developers turned their attention to Ethereum's next big challenge: scalability.

The very next major upgrade, Dencun (Deneb + Cancun), arrived on March 13, 2024. Its centerpiece was EIP-4844, which introduced "blobs"—a new, cheaper way for Layer 2 rollups to post transaction data to the Ethereum mainnet. This dramatically lowered transaction fees on L2s and was a massive step forward on the rollup-centric roadmap. Dencun also delivered on the promise of EIP-6049 by implementing EIP-6780, which significantly curtailed the power of the SELFDESTRUCT opcode.

The Big Picture​

Shapella was the essential confidence milestone for Ethereum's Proof-of-Stake consensus. By enabling withdrawals, it de-risked staking, restored liquidity, and affirmed the network's ability to execute complex, coordinated upgrades. It also delivered a handful of pragmatic EVM improvements that cleaned up technical debt and paved the way for future optimizations.

In short, Shapella didn't just open the exit door for stakers—it solidified the foundation of the post-Merge era and cleared the runway for Ethereum to focus on its next frontier: mass scalability.

We are on a mission to build and accelerate the web3 industry of tomorrow. We obsess about developer experience and strive towards constant innovation. And that's why now we are offering a decentralized file store, powered by EthStorage. dStore is a managed storage solution for creators and developers from any blockchain. It's user-friendly, EVM-compatible, low-cost, and petabyte-level scale, all powered by EthStorage.

What is EthStorage?​

EthStorage is a layer 2 solution that provides programmable dynamic storage based on Ethereum's data availability. It will greatly reduce the storage cost of storing a large amount of data on Ethereum, saving the cost from 1% to 0.1%. The low cost of storing large data by EthStorage can better enable a fully decentralized network in the future. EthStorage is highly integrated with EVM and is compatible with Solidity, Remix, Hardhat, and MetaMask. The team received a research grant from the Ethereum Foundation for data availability research.

EthStorage is invented by Dr. Qi Zhou, the founder of QuarkChain and author of EIP-4804/4972/5018/5027/5478. You can track EthStorage's statuses from the following sources:

• Website: http://ethstorage.io/
• Twitter: https://twitter.com/EthStorage
• Medium: https://ethstorage.medium.com/
• Telegram: https://t.me/ethstorage
• Discord: https://discord.gg/mZqqUZxjed

Why does decentralized storage matter?​

Decentralized storage is important because it allows for data to be stored in a distributed manner rather than being stored in a single location. This has several advantages, such as increased security and reliability, as well as improved accessibility. For example, because decentralized storage systems are distributed, they are less vulnerable to attacks, censorship, or failure and can continue to function even if some of the individual components fail. Additionally, because the data is stored on multiple devices, it can be accessed from multiple locations, making it more convenient for users.

What is BlockEden. xyz's dStore offering?​

We strongly believe Dr. Zhou's vision to bring more cost-effective storage to the decentralized web and would like to collaborate with his team to democratize this innovation to every web3 developer on the planet.

More specifically, we will apply EthStorage as the underlying vendor of our blob store. Our developers can develop upon it to build their DApps faster and scale instantly.

Web portal for file management

Developers and creators can drag and drop their static assets to this file store and easily manage them. We free them from the hassles of managing private keys, paying transaction fees, and maintaining files with blockchains.

To ensure the decentralization of the storage, developers could eject the managed store to their own address anytime. Furthermore, we will open source the backend of the file store so that developers or other developer-facing providers can easily host file management services.

Unlocking new business possibilities through strategic partnerships​

There are also future integration opportunities between EthStorage and BlockEden.xyz, in addition to the dStore launched today.

CDN to speed up the read

Most Internet services are read-intensive and take time to serve a large number of resources from a decentralized store. With our CDN service, developers can enjoy both the decentralization of the source files and the blazing-fast speed that we can achieve with a CDN.

Node service and API gateway to EthStorage

We will provide API access to EthStorage testnet and mainnet blockchain nodes after EthStorage mainnet launch for developers and businesses. Here are a few reasons why developers should choose us instead of their own or the official nodes:

1. Easy Access to blockchain Nodes: BlockEden.xyz ChainPlus API provides easy access to EthStorage nodes, which can be used to interact with these blockchain networks. Starts to build in 10s, instead of spending 20 hours to start, countless hours to maintain!

2. Scalability: BlockEden.xyz provides highly scalable nodes that can handle high levels of traffic and transactions. This can be important for businesses and projects requiring large amounts of data or user activity.

3. Reliability: BlockEden.xyz nodes are highly reliable, with an uptime of 99.9%. This can be important for businesses and projects that need to ensure that their applications or services are always available to users.

How to use dStore with EthStorage?​

Step 1. Go to https://BlockEden.xyz/dash/dstore and then drag and drop your files to the window.

Step 2. After the file is uploaded to the EthStorage successfully, you will see the item in the table, then right-click the row and select "Copy URL" to get the link. You can also delete a file by selecting "Delete".

Admittedly, the current version of dStore has some limitations. We don't support uploading directories and large files (size > 2MB). It may take tens of seconds to upload mid-sized images. However, this is just an initial version, and we will keep improving the product in the long run.

Dr. Qi Zhou, founder of EthStorage, share his praise on twitter -

Introducing dStore @BlockEdenHQ!

dStore makes it super easy for devs and creators to manage files on @EthStorage with web3:// protocol without their own keys. We expect to see more integrations from it and more early teams like the capable @BlockEdenHQ to build our ecosystem.

— Qi Zhou (@qc_qizhou) February 20, 2023

Mike Thrift, BD at BlockEden.xyz, commented, "dStore enriched our bundled offering to the creators and developers and laid a solid foundation for our aggregated function API services to blockchains. It made us an active contributor to the Ethereum ecosystem and gave our Aptos and Sui developers a more cost-effective and flexible choice than IPFS or Arweave."

BlockEden.xyz is committed to providing the best developer experiences to web3 developers, which does not limit to Blockchain RPCs. The decentralized storage opens new doors for developers to manage their NFT assets and files in our one-stop shop. Get started today for free at https://blockeden.xyz/dstore

• Twitter: https://twitter.com/BlockEdenHQ
• Discord: https://discord.gg/eWZvE4RSBw
• Source Link: https://blockeden.xyz/blog/2023/03/15/boost-your-web3-development-with-blockeden-xyz-chat/

Back to a month ago, we made a public incognito Ethereum mainnet RPC endpoint available to Metamask users (blog post), which attracted and was used by a few users. Now we decided to expand the benefit to our developer customers too!

How to get started?​

Step 1. Go to https://blockeden.xyz/dash/. Please sign up if you haven’t done so.

Step 2. Input your name for the API key, select ETH Mainnet, and then click + Create key.

Step 3. Grab your access URL by clicking it and copying it to the clipboard.

Step 4. Use the access URL in your project like the following. Remember to replace <access_key> with your own key.

To test it, using curl to connect ETH mainnet

curl --location --request POST 'https://eth-mainnet.blockeden.xyz/<access_key>' \
--header 'Content-Type: application/json' \
--data-raw '{
        "jsonrpc":"2.0",
        "method":"eth_blockNumber",
        "params":[],
        "id":73
}'

Why Ethereum Network?​

Ethereum network has the biggest developer ecosystem, and there are so many great innovations accumulated over years. Supporting it is going to create significant synergy with Move ecosystem. Many of our customers are not exclusive Move developers. Building a single stop for all needed services makes their life easier.

Enjoy our new service and happy holidays!