💙 Maximizing endpoint availability with the Next-Gen RPC Node 🛠 Public RPC endpoints often face lower uptime, higher latency, and lack customizable logic due to infrastructure limitations. To help combat this, our award-winning Next-Gen RPC Node, presented at ETHGlobal Istanbul, aggregates endpoints from multiple providers, geos, and clouds to maintain service availability. Here’s what made it a favorite in the eyes of the jury, earning it two prizes from Filecoin and one from Arbitrum: 💙 Broad compatibility: The Next-Gen RPC Node is designed to work with a wide range of EVM-compatible chains, including Ethereum, Polygon, Scroll, Starknet, and Filecoin. 💙 No single-point of failure: The Next-Gen RPC Node aggregates RPC endpoints from diverse providers, regions, and cloud services, verifying they are operational and at the latest block height. 💙 Intelligent load-balancing: The service dynamically reroutes to the optimal node based on performance and data accuracy for the best possible results. 💙 Greater control: The highly customizable logic enables you to implement access-list capabilities, such as IP and HTTP Referrer origin whitelisting, along with custom rate-limiting and throttling. 💙 Deployment-ready: The Next-Gen RPC Node is ready for immediate use and is fully open-source, allowing you to get started quickly and conveniently at just a click of a button. So, don't let traditional RPC endpoint limitations hold you back. Unlock the full potential of your public blockchain infrastructure with the Next-Gen RPC Node. Find all the details 👇 bit.ly/3Gr1MEW

💙 Chainstack returns from Devconnect 🛠 And what a time it has been! It was a real pleasure for our Product Director Vasily (@cyberwider) to meet with all you leaders and builders to talk Web3. More about our award later this week. Great connections were made, with many new exciting opportunities on the horizon. Thanks to everyone who made it memorable! So, come meet us at a blockchain event near you. Let’s shape the Web3 landscape together.

🎉 Scroll Mainnet integration is now LIVE on Chainstack 🚀 Explore with unparalleled speed, security, and scalability via our Global Elastic Scroll Mainnet Nodes: shorturl.at/cwO69 Access the Mainnet for free with our public endpoint: shorturl.at/ptvxO Get a head start on @Scroll_ZKP Mainnet today 💙🛠

2X the difference: Why the right node deployment matters Considering running an Ethereum archive node? The significant investment required, both in terms of financial and hardware, is not to be underestimated. Let's take apart the hardware requirements and associated costs in detail, using a sample configuration as we explore the topic further… But before reading the mammoth post, we're gonna cut a long story short and provide you with the quick answer. Yes, you can save anywhere from 60% to 99% of your infrastructure costs by using a Node-as-a-Service provider, instead of an on-premise setup. ⚙ Hardware configuration: Each component of the server rig needs to be carefully considered to fully support an Ethereum archive node. This includes: An 8-core CPU, ensuring your system has the computational power to manage the intensive tasks involved. A substantive 32GB of RAM, providing the capacity to handle complex operations simultaneously. A 3.5TB+ HDD. For more efficient performance, an SSD is recommended, though the substantial storage requirement remains the same. At present an Ethereum mainnet archive node running Erigon takes up 3.5TB of space according to chainstats.org 🖥️ Hardware costs: Once you tally up the costs of the above components, you will get an estimate of the financial outlay. Based on the minimum hardware requirements mentioned above, we have devised the following sample server rig to fit the criteria, while still adhering to a realistic current market perspective: 🔌 Recurring utility costs: Beyond the initial investment, running a Ethernet archive node involves ongoing utility costs, specifically electricity and internet: ⚡ Electricity: For a single server, anticipate about $330 per month. Remember, computation-heavy operations can consume a significant amount of power. 📡 Internet: You'll also need a steady, high-speed Gigabit internet connection to ensure seamless operations. This expense stands at roughly $80 per month, irrespective of whether you're running one server or twelve. 👥 Manpower costs: Men and machines are both part of the equation when it comes to running an Ethereum archive node. We've drilled into the machinery costs, now let's understand the manpower aspect, specifically staffing your operation and the associated wage costs. Here's a breakdown of approximate wages for various levels of cloud engineers: Senior Cloud Engineer: This role often involves managing the overall architecture and overseeing operations. Given the level of responsibility and expertise demanded, a senior cloud engineer commands a high salary—around $192,000 annually. Mid-level Cloud Engineer: This position generally involves a fair bit of hands-on work, with a good amount of responsibility. The average salary for a mid-level engineer sits at $120,000 per annum. Junior Cloud Engineers: Junior engineers are pivotal in supporting the team's work and maintaining the systems. In a larger operation, you may need a couple of engineers in junior roles, contributing an additional $144,000 annually) to the total wage bill. 💵 Now, onto the total costs: For this case study we drafted a set of 3 main scenarios—staffless, one-man-army with a senior cloud engineer to make things balanced, and a fully staffed one. For the latter scenario, we have put together a team of four to realistically fit a 24/7 timeframe: 1x Senior, 1x Mid-Level, And 2x Juniors. What do we get when we crunch the numbers down for a monthly, yearly, and a five-year timeframe for each of the scenarios we defined above? Let’s find out... Now isn’t that absolutely bonkers?! Yes it is, which is why we couldn’t help ourselves to benchmark these numbers against two of our subscription plans: Growth, the minimum viable option to run Ethereum archive nodes, And Business, which lets you deploy the dozen-node-operation we are using in this example. Let’s start with a breakdown of the two plans, with the 16% annual payment discount in mind, as well: Growth plan: Up to 10 nodes, $49/mo and $588/yr, or just $40/mo and $480/yr with a 16% discount. Business plan: Up to 20 nodes, $349/mo and $4,188/yr, or alternatively $290/mo and $3,480/yr with a 16% off. With that taken care of it is indeed time for… ⚖ The final judgement: Comparing on-premise vs service provider costs. Let's dive into the operational costs (including optional staffing), whether it's monthly, yearly or over a span of five years and see how they fare against service provider fees: 🎁 Wrapping up: Operating an Ethereum archive node is no small financial endeavor, so being well-informed can help navigate this journey. Our detailed exploration into on-premise node operation costs—from hardware, utilities, to staffing – and juxtaposing them with costs of using a node service provider like Chainstack paints a striking picture. Wanna see all the details? Take a closer look at the full case study below 👇 shorturl.at/aouKY

Now on @BuildOnBase! Index & query blockchain data fast and reliably 💙🛠️ From today, @ChainstackHQ Subgraphs supports Base Mainnet & Tesnet 🔥 Subgraphs are an incredibly powerful technology that can revolutionize data management in #Web3 bit.ly/3PBpILp

1/🎉 We heard you. And that is why we’re thrilled to introduce the new standard of @ChainstackHQ services — 🌐 Global Elastic Nodes: The world’s most resilient Web3 API so you can experience efficiency & responsiveness like never before. Find out more 👇