Atlas | Powered by NodeOps
@BuildOnAtlas
Followers
16,115
Following
1
Media
39
Statuses
141
A permissionless, decentralized infrastructure orchestration layer for web3 apps, and protocols, built as an $ETH-secured AVS on @eigenlayer by @nodeops_app
Joined June 2023
Don't wanna be here?
Send us removal request.
Explore trending content on Musk Viewer
Iran
• 571141 Tweets
Washington Post
• 446042 Tweets
Judge
• 345719 Tweets
Bezos
• 245173 Tweets
Beyoncé
• 192276 Tweets
Houston
• 186001 Tweets
Tehran
• 129059 Tweets
WaPo
• 124295 Tweets
#WorldSeries
• 77432 Tweets
#Smackdown
• 40287 Tweets
レジェンド車両
• 35050 Tweets
全員最大金枠アイテム5つ
• 34714 Tweets
ワールドシリーズ
• 31094 Tweets
#طهران
• 31062 Tweets
#RepBX
• 29837 Tweets
ANIM NA TAONG SAMAHAN
• 27724 Tweets
Phil Lesh
• 23199 Tweets
Andrade
• 20573 Tweets
Stanton
• 20487 Tweets
ヤンキース
• 16622 Tweets
الهجوم الاسراييلي
• 15344 Tweets
Willie Nelson
• 10527 Tweets
Giannis
• 10523 Tweets
Pinned Tweet
Introducing Atlas by
@NodeOps_App
- a critical step in our attempt to revolutionize decentralized infrastructure! Today, we introduce you to the future of Scalable Decentralization 🚀
To get a quick overview, follow this thread.
22
77
37
Decentralized Infra
+
Economically secured Infra
+
Reliable Infra
=
Atlas
Simple, isn't? 🤷
1
2
7
How did we conceive the idea of Atlas?
✅Understand the problems in our industry
✅Find solutions in a way that promotes the values of Web3
✅And finally, design an operational framework to bring these solutions together
In our previous article, we discussed the problems with
1
2
6
What is “Verifiable SaaS?”
We all know what SaaS is. It is an acronym for Software-as-a-Service, which means software that is a service you can subscribe to and use.
Verifiable SaaS was coined by
@sreeramkannan
of
@eigenlayer
in the context of how he sees the world of Web3
1
3
11
Atlas lies at the heart of this transformation.
Bringing off chain verifiable attributes on chain w.r.t node network provisioning is what this is all about.
@eigenlayer
The background says it all
Conversion of SaaS --> DVSaaS (Decentralised Verifiable SaaS is complete)
17th September, 2024
We Present you with the private access to
@BuildOnAtlas
Inviting
DePIN Protocols
Compute Providers
Developers
Node Operators
Community
2
4
20
0
1
4
At Atlas, we are busy assembling the pieces of the puzzle that will create the best infrastructure marketplace for Web3.
To follow up on the deployment process post last week, in this post, we will share what node deployment will look like from the user’s perspective.
Note:
1
3
5
👀
0
0
1
A wonderful representation of the world of orchestration in Web3.
Atlas is the conductor when it comes to node infrastructure provisioning for blockchains and protocols using
@NodeOps_App
.
Read more about us here:
The Orchestration Layer: Intro
The blockchain world is chaotic.
From L1, L2s, to Sidechains, and other scalability solutions, the blockchain ecosystem has exploded, becoming more complex and non-interoperable.
Developing a multichain dApps is now a time-consuming nightmare.
12
18
69
1
1
3
Hello Folks 👋.
We have been in Alphanet for a week now, and it is time to share what we have achieved so far. 🧵
3
10
83
With our Alphanet, we created a platform where restaking Operators can bring compute(Providers) for basic node deployment and get rewarded in return.
But now, we want to take this to the next level⬆️.
1
12
63
Our team is working hard behind the scenes, creating the building blocks for the next-generation Web3 infra marketplace.
Operator onboarding is a crucial first step in this direction.
Let's take a peek under the hood to see how this is done in Atlas 🧵
1
3
12
A nice explanation of what we are building with Atlas.
🌐
Atlas - an Eigenlayer ecosystem project with over 1M revenue rate.. something you can’t miss..
@NodeOps_App
is becoming one of the largest DePIN project by revenue.. with launch of Atlas AVS — they are going to build an infra to bootstrap more AVSs— Atlas is the orchestration
8
16
112
0
4
19
Our first step towards bringing decentralization coupled with CE security to node networks for all manner of Web3 projects.
🍾
@BuildOnAtlas
Alphanet is here! 🍾
Atlas Network Alphanet, our private testnet, is soon going live on
@eigenlayer
testnet (Holesky).
Since the release of the Atlas litepaper in August, NodeOps has been busy creating the building blocks for its DePIN orchestration layer.
1️⃣
7
7
37
0
4
11
Absolutely!!
We want to be the best at nodesales but also go beyond.
Atlas is what will transform
@NodeOps_App
into a one-stop shop or a unified marketplace where protocols and blockchains can get the most reliable, decentralized, and secure infrastructure.
Nodesales are all the rage these days, NodeOps is addressing most of the Node infrastructure challenges with a novel consumer focused approach. This has lead to success for many projects & with the addition of
@buildonatlas
for its Node Orchestration Layer its looking pretty
13
22
149
0
4
8
Node infrastructure provisioning for Web3 is mainly done on web2 centralized cloud infrastructure providers like AWS and Google Cloud.
But this is about to change now.🌏👇
1
1
6
@NodeOps_App
is hiring!!
NodeOps is actively hiring to expand its team across each verticals.
If you come across or know any suitable candidates, please feel free to refer.
Of course there is a referral bonus for a successful hiring.
Thanks & do spread the word.
2
4
16
2. Orchestration Layer: At the heart of Atlas lies the AtlasNetwork as an AVS on EigenLayer.
The AVS coordinates all the activities related to onboarding, deployment, monitoring, incentives, and slashing on NodeOps ensuring that it runs as a well-oiled machine.
1
4
14
Atlas will “bring a new era of orchestration for infrastructure” to
@NodeOps_App
.
Let’s get a glimpse at the kind of ecosystem we want to build using Atlas 🌏 👇
1
3
9
With Atlas, we want to bring coordination between different elements of a decentralized, CE secure, & reliable infra for node networks. Thanks to
@RedactedRes
for the mention.
➍ 𝐀𝐕𝐒 𝐄𝐜𝐨𝐬𝐲𝐬𝐭𝐞𝐦 (𝟏/𝟐)
As of today, there is >30 AVS protocols being built on
@eigenlayer
.
This includes:
➤
@eigen_da
[Data Availability]
➤
@eoracle_network
[Decentralized & Slashable Oracle]
➤
@witnesschain
[DePIN Coordination Layer]
➤
@hyperlane
11
8
46
0
3
9
As part of the Alphanet, we created the essential elements of our Atlas Network.
Which included:
✅The Atlas AVS contracts on
@eigenlayer
holesky.
✅A smart operator selection logic that selects the right operator for every node deployment
✅A new Operator Onboarding process
1
0
9
So far, we have:
➡️onboarded 7 Operators
➡️with 121 providers
➡️running 116 individual node clients
1
0
9
Here is a glimpse of the new Operator Dashboard.
This is what every Operator gets to see once they complete the onboarding process.
It shows the provider machines they added to the pool and which run node clients (workload) on them.
1
0
8
Details of individual provider machines are also available, and here is one such example.
This particular provider runs four workloads and has accrued certain rewards in USDC and NodePoints.
Uptime and monitoring information is also available for Operators.
1
0
8
Last time, we shared the design details for Operator onboarding.
This post will look into node deployment and its interaction with Atlas.
Let's lift the hood.👇
1
3
8
These Operators have been awarded 13.5k USDC and 14k NodePoints for providing the hardware resources.
NOTE: These rewards are just indicative and for testing and are not a representation of future rewards distribution.
1
0
8
Like the existing
@NodeOps
Console, Node Operators get rewarded with NodePoints for deployments.
1
0
7
In a nutshell, with Alphanet, we have:
✅demonstrated the onboarding of new Operators and provider machines to the Atlas network
✅ performed deployment based on a scheduling logic that selects the best Operator available
✅and a reward mechanism for Operators who join in and get
1
0
7
The team is already working behind the scenes on version 2.0 of the Atlas network.
We have taken the feedback and will continue to share details of these changes in upcoming posts, so stay tuned. 🚀🌐
0
0
6
Shout out to all Scribblers 📢.
and a hearty congratulations to the winners 🥳
Three masked geniuses just walked out of
@NodeOps_App
HQ with bags full of grants! 💰
Security footage reveals they used nothing but keyboards and big brains.
Witnesses report hearing: 'It's not theft if it's open source!'
Suspects at large: 🧵
12
6
31
0
27
159
Great to see
@naman_307
part of this amazing line up. 👍
🇸🇬 THE ROLLUP DAY 2024 AGENDA IS OUT! 🇸🇬
Our 20 Sep event, co-hosted with
@eigenlayer
, has got a STACKED speaker roster 🔥
See it to believe it ↓ 🧵
3
20
113
0
2
5
4. Infrastructure Providers can provide compute and hardwares for creating a truly decentralized permissionless marketplace for developers and Node Operators.
5. Contribute to the growth of NodeOps by becoming a Node watcher and earn rewards doing so.
1
1
5
Atlas elevates NodeOps from an infrastructure provider to a permissionless marketplace, catering to all Web3 infra and security needs, and addresses the challenges we see with current infrastructure provisioning.
Truly a huge win for our industry! Join us at
@buildonatlas
🚀
0
1
5
NodeOps Today delivers the following:
1. One-click node deployment across multiple blockchain protocols.
2. Support for various node types: validator, full, light, RPC, and archive nodes.
1
1
4
First, to those unfamiliar -
@NodeOps_App
simplifies the deployment & management of nodes for blockchains and protocols. Our mission is to empower developers & operators with AI-powered tools, reducing complexity and boosting productivity.
1
1
4
What can you expect from Atlas?
1. Blockchains can now create proposals for bootstrapping their network.
2. dApps can create proposals to bootstrap their liquidity needs.
3. Amazing yield-generating opportunities for liquidity and infrastructure providers.
1
1
4
With such a strong positioning, it is time for
@NodeOps_App
to take the next step in its evolution i.e. moving from being a SaaS to a truly Decentralized Verifiable SaaS (DVSaaS).
And this is the purpose of Atlas.
2
0
3
But there are challenges Web3 projects face:
1. Creating a decentralized & secure node network is hard.
2. The trustworthiness of the infrastructure provider is not transparent.
3. A fragmented node infrastructure tooling ecosystem fails to provide a unified experience.
1
0
4
Once the provider is selected for deployment, the deployment is triggered.
The deployer deploys the deployment to the provider and is responsible for deployment.
In parallel, the reconciler consistently enforces the database state to the provider pool.
1
0
4
To overcome these challenges, we introduce Atlas:
Atlas is our new permissionless, decentralized infrastructure orchestration layer designed to address these challenges.
1
0
4
It transforms NodeOps into a marketplace for blockchains, protocols, & dApps to bootstrap their node networks & economic security.
Operationally Atlas is a multi-layered protocol consisting of:
1. Permissionless Marketplace
2. Orchestration Layer
3. Sustainable Economy
1
0
4
3. AI-enhanced infrastructure for automated deployment & error handling.
4. Comprehensive monitoring tools for real-time analytics & vulnerability tracking.
1
1
4
The backend talks to the Scheduler to find the best provider for this particular deployment.
In parallel, a new AVS task is also created, which records the result of the payment process.
1
0
4
And this wraps up the high-level view of our new deployment process.
We will continue to share engineering/tech/design information in easy-to-read posts, so follow us.
0
0
4
The lite paper provides the overall architecture of Atlas along with aspects of the Atlas AVS and the new NodeWatch network crucial to the security and stability of the node infrastructure.
1
1
4
Atlas brings together the decentralization and economic security present within the Ethereum network to other node networks.
And it does this in a way that is sustainable via a value creation and distribution economic model that is hyper focused on inclusive growth.
1
0
3
6. 24/7 Consistent Monitoring: of nodes & provider infrastructure.
7. Scalability and Decentralization: For better blockchain security and reliability.
1
1
4
Node deployment begins with the Console on
@NodeOps_App
.
Users select the node they want to deploy, which triggers the payment module.
Once the payment is successful, a deployment task is sent to the backend, triggering the deployment.
1
0
3
Operational frameworks are an essential part of system or solution design. Simply put, they provide a picture of how a system works as a unit.
In our case, this framework consists of three main aspects or layers that work together to implement our solution stack effectively and
1
0
3
Atlas Key Features:
1. Modular: Decentralized onboarding & resource provision without dependencies.
2. Permissionless: Community-led decision-making via on-chain voting.
3. Quality-Focused Onboarding: Ensures robust & reliable infrastructure providers.
1
0
3
In the end, the operator needs only run a setup command provided on the UI, to complete the registration process and adding the machine to the existing pool of infrastructure compute ready to receive deployment workloads.
And this is how Operator onboarding works in Atlas.
0
0
3
If the human body is a system, then the marketplace is the body where all the organs come together and interact, the orchestration layer is the nervous system, and the economy is the blood that flows through it.
Read about the details in our latest blog 👇
0
0
3
Machine registration happens via the AddMachine method of the ProviderRegistry contract. The first step is to check whether the machine is registered with the Atlas AVS.
Once the machine is registered with our AVS, it will show up as “Pending,” which means it is ready for setup.
1
0
3
The following diagram shows the entire flow between the operator, the Atlas AVS, various smart contracts and what these interactions mean.
The Atlas Operator UI is where operators go to register and deregister the infrastructure (machine) they intend to use for node deployments.
1
0
3
@NodeOps_App
does node infrastructure provisioning really well.
It has successfully built the most powerful consumer Infrastructure SaaS via its current offerings in form of NodeOps Console & NodePad.
It supports 35+ Protocols, 34000+ Nodes, 18k+ Active Node Folios & a wide
1
0
3
3. Sustainable Economy: A sustainable value capture and distribution policy drives the economy with Atlas. All stakeholders are incentivized to ensure the robustness and reliability of our services.
1
0
3
Follow us, join us in this journey and read more about what we are building:
0
0
2
It starts with creating a web front end, where operators willing to contribute their hardware resources for node deployments can register with our Atlas AVS.
Currently, these operators are whitelisted to ensure a smooth lift-off, but in the future, onboarding will be open to any
1
0
3
The idea is quite simple but powerful. Suppose you are designing a dApp or infrastructure in Web3, what if you could reuse existing components created by other projects as services by simply subscribing to them?
These services would be verifiable because they run on a
1
0
3
1. Permissionless Marketplace: Blockchains, dApps, & protocols bootstrapping their node network or economic security can now create proposals for the NodeOps community to vote on.
On-chain governance decentralizes decision-making by empowering the community to take action.
1
0
3
In this frame of reference,
@eigenlayer
is the cloud that houses all these services, which are intermingled, coexist, and create their own ecosystem—a “verifiable digital commons,” as Sreeram puts it.
So the question now arises, what service can
@NodeOps_App
provide to Web3?
1
0
3
Thanks to the innovative Atlas AVS on
@eigenlayer
, Ethereum validators (solo/DVT/Operators) can now be utilized for node deployments.
3
0
2
An operator can have multiple units of hardware resources, such as multiple solo validators in a cluster.
1
0
3
This brings decentralization and economic security to protocols and chains, resulting in a much more robust and resilient node network for them.
@NodeOps_App
Read 👇 to learn more.
0
0
2
4. On-chain Incentivization: Rewards active participation & investment in network growth.
5. Operational Integrity: Efficiently coordinates provider matchmaking, deployment, & monitoring.
1
0
3
Earlier, we shared the design flow of how Operator onboarding will work behind the scenes with Atlas.
This post will share how it will look from the Operator's perspective.
This is the testnet version of the UI, and the final version will look different.
Let’s dive in.👇
1
2
3
Vital to this ecosystem is our integration with
@eigenlayer
which plays a crucial role in:
✅Providing access to a diversified and decentralized set of Operators.
✅Allowing easy onboarding of solo/DVT validators as providers.
✅Bringing economic security to protocols.
1
0
2
This is not just a solution but a win-win situation for all stakeholders involved.
✅A node operator gets reliability, decentralization, and economic security
✅The Ethereum validator gets rewarded for running the node
✅And the blockchain network grows more robust and better
0
0
2
Node sales may promote decentralization by controlling the distribution of the rights to promote physical decentralization; however, this could come at the cost of reliability.
For example, an individual might get the right to host a node given their geographical location, but
1
0
2
With Atlas, we bring the demand for reliable, decentralized, and secure node infrastructure from protocols together with a diversified supply of compute resources in a manner that is open and transparent.
1
0
2
Step3:
Once the transaction is verified, a confirmation screen will appear, and the user will see the node under “My Nodes.”
And the new node appears under My Nodes.
1
0
2
Step 1:
The node operator gets a list of nodes they can deploy on the Console, as shown.
Upon selecting a node for deployment, the payment process kicks in.
1
0
2
How reliable can a recently launched node network be if it is community-driven? More importantly, is there a solution?
1
0
2
Yes!
Imagine the potential of allowing node operators to run their nodes on an Ethereum validator. This could be the key to achieving the reliability a new node network needs.
Not only will such a cohort of infrastructure providers be reliable from a hardware resource pov, but
1
0
2
Finally, once the configuration is complete, the machine is successfully added to the provider pool for node deployment workloads.
At this stage, the Operator can click on the machine to see its details.
1
0
2
Step2:
The user clicks on Pay and confirms the transaction in the wallet.
And waits for the transaction to complete.
1
0
2
It's time for our weekly update, folks.📢
The team has been working hard to move from a proof of concept stage (shared earlier in several posts) to something more concrete.
To recap, this is what we covered in the POC:
➡️Operator & Provider onboarding module
➡️Node
1
0
2
As part of the Alphanet, we created the essential elements of our Atlas Network.
Which included:
✅The Atlas AVS contracts on
@eigenlayer
holesky
✅A node deployment mechanism to select the best Operator for every new deployment
✅A new Operator Onboarding process to get
1
0
2
Expect to see more protocols, more operators and more AVS integrations.
Read more about Atlas here:
0
0
2
So far, we have
➡️onboarded 7 Operators
➡️with 121 providers
➡️ running a total of 116 individual node clients on these providers
1
0
1
The current design is limited to the hardware resources that restaking Operators bring with them, but we want an open, more decentralized, and diverse pool of infrastructure providers.
For this, it is essential that we start considering Providers as separate entities from
0
0
1
@tokenterminal
@NodeOps_App
@eigenlayer
Let me help you with this.
@NodeOps_App
is a NaaS (Node as a service) platform that primarily does node deployments for blockchains.
We are creating a new AVS called Atlas
@buildonatlas
that will allow us to onboard the existing Ethereum validators via EigenLayer into our pool
1
0
1
@tokenterminal
@NodeOps_App
@eigenlayer
Another way to look at
@buildonatlas
is to think of it as an orchestration layer that will bring together the demand for decentralized node network and economic security and the supply of compute resources locked within existing Operators on EigenLayer.
0
0
1
As we march towards our vision, we are ready to implement the next crucial element of our plan: separating Operator and Provider roles.
1
0
1
This is why we are building Atlas.
We anticipated this massive growth in DePIN projects and node sales and the need of an orchestration layer that is designed to be:
➡️Flexible: in order to adapt to this growing demand for node sales
➡️Decentralized: Make these DePIN projects
0
24
39
Just 8 days left!⌛
NodeOps is all set for
@token2049
in Singapore! 🇸🇬
Grab your tickets with our exclusive promo code NODEOPS15 and enjoy a 15% discount 🙌
See you there!
0
1
1
Like the existing
@NodeOps_App
Console, Node Operators got their rewards in NodePoints for every deployment they completed.
1
0
1
@tokenterminal
@eigenlayer
@buildonatlas
We are bringing decentralization and economic security to node infrastructure provisioning.
Here is our litepaper released last week.
1
1
1