Decentralised Compute Infrastructure For The Onchain Economy 2,500+ nodes live | Scaling towards 40,000 Powered by $AVT
Aventus Cloud ☁️
Joined November 2016
- Tweets12.9K
- Following662
- Followers21.2K
- Likes13.6K
Pinned Tweet
Today, we put our year one on the record.
The Aventus DAO Annual Review is now live.
Inside: the network, the numbers, the decisions, the changes in strategy, what we learned, and where we go next.
Read the full report ↓
aventus.io/insights/aventus-…
Having worked on enterprise blockchain infrastructure at Aventus since 2017, one thing we’ve learned is that businesses need flexibility over how their applications operate.
Not every business needs a completely separate blockchain.
But not every business can operate under exactly the same rules either.
@HyperliquidX is showing how both approaches could coexist.
Payward, the parent company of Kraken, announced its intention to be the first CFTC-regulated deployer on HIP-3* markets. Payward will use Hyperliquid as the infrastructure layer to deploy perpetual futures markets for US clients. Subject to regulatory approval, Bitnomial, Payward’s CFTC-regulated DCM and DCO, would act as the HIP-3* deployer: creating, owning, and administering the markets and clearing and settling the contracts. If approved, NinjaTrader Clearing, Payward’s CFTC-registered FCM, would carry client accounts.
HIP-3 will support optional deployer configuration for permissioned markets in a future network upgrade. This set of additional deployer functionality is collectively called HIP-3*. At its core, HIP-3* activation involves an onchain allowlist managed by the deployer or its sub-deployers. The functionality is strictly additive to HIP-3; its use is optional and up to the deployer. Existing markets remain unchanged. The initial release is available on testnet, where specifications are preliminary and subject to change based on feedback.
Hyperliquid is a neutral infrastructure layer with the goal of supporting large parts of the financial system. HIP-3* gives deployers additional functionality to operate deployments consistent with the requirements applicable to them. As with HIP-3, HIP-3* deployers are independent operators who use Hyperliquid as the onchain infrastructure layer for their own markets, while retaining control and responsibility over their deployment.
Interesting development from Tether.
We’re approaching decentralised infrastructure through Aventus Cloud, with over 2,500 community-operated nodes.
Different use cases, but a familiar challenge: making independently operated infrastructure useful, reliable and manageable at scale.
Tether’s MDK Gains Broad Industry Backing to Accelerate the Next Generation of Bitcoin Mining Automation
Learn more: tether.io/news/tethers-mdk-g…
The Aventus DAO Council has published its decision on the bridge recovery, AVT supply and the AvN Mainnet v10.0.3 upgrade.
The statement sets out the recovery plan, the one-time replacement issuance, the new permanent transaction fee burn and the next steps for restoring the bridge.
Read the full Council decision ↓
aventus.io/insights/bridge-r…
Circle’s expansion into AI agent payments is particularly interesting for us at Aventus.
We’re developing community-operated compute and verification infrastructure through Aventus Cloud.
As agents begin purchasing services autonomously, independently verifying the work those services perform becomes increasingly valuable.
cirBTC and EURC join @USDC on Circle Gateway, expanding Circle Interop.
→ One unified balance per asset
→ Crosschain access in under 500ms after deposit finalization
→ The same Gateway integration and experience
More assets available where your app needs them.
circle.com/blog/circle-gatew…
The growing resistance to OKXICE is interesting.
Having spent years building enterprise blockchain infrastructure at Aventus, we’ve seen how important confidence in the underlying systems is to adoption.
Companies want to understand the risks and who is accountable.
Those are reasonable expectations.
🚨 HUGE: Wells Fargo, Arm and Intuit just joined the "please don't tokenize my stock" club, taking OKXICE's rejection list to 22 of the 63 companies it wanted to list.
cointelegraph.com/news/nasda…
China has put blockchain alongside AI and 6G in its national infrastructure plans.
That's quite a statement about where the technology is heading.
We've spent nearly a decade building enterprise blockchain infrastructure at Aventus.
It's encouraging to see serious attention being given to its practical applications.
🇨🇳 BIG: China targets 2030 to largely complete its national blockchain network, with plans to expand blockchain use in trade, finance, manufacturing and agriculture.
ct.com/news/china-2030-natio…
Grayscale highlighting blockchain’s role in the AI infrastructure economy is encouraging.
At Aventus, we’ve spent years working on decentralised infrastructure, and one question keeps becoming more relevant.
How do you coordinate independent participants, verify their contributions and build an economic model that works for everyone involved?
That’s where some of the most interesting innovation is happening.
Frontier tech and crypto are converging.
Crypto projects part of the AI buildout:
$DATA → Licensing and verifying AI training data.
$CHIP → Financing GPU hardware through onchain loans.
$PEARL → Merging proof-of-work with AI compute, letting miners earn rewards while powering compute.
Read more on The Stack by @willhamilogden: grayscale.com/the-stack/bloc…
Interesting development from Ethereum.
At Aventus, we’ve recently strengthened our network’s software build and release processes as part of our latest mainnet upgrade.
The Glamsterdam delay is a reminder of just how important careful testing, independent security research and responsible deployment decisions are for blockchain infrastructure.
The PHP security crisis is a reminder of how much responsibility comes with operating critical infrastructure.
For community-operated networks like Aventus Cloud, that responsibility extends across governance, software releases and independent node operators.
Building the network is one challenge. Keeping it secure and sustainable for years is another.
The FBI continues to warn about two critical security flaws in PHP, a programming language used to build many websites and online services. Attackers could exploit these vulnerabilities to break into systems, putting sensitive information and business operations at risk. Security updates are available and should be applied immediately.
If you are a business owner or website operator, check whether your systems are affected. Contact your IT support team, website developer, or hosting provider for help identifying vulnerable systems and applying the necessary updates.
The FBI urges organizations to take the following steps now:
➡️ If an immediate update is not feasible it is recommended that organizations take the system offline until it can be fully mitigated.
➡️ Immediately update affected PHP installations following the guidance on php.net. Inventory where PHP runs in your environment, prioritizing internet-facing systems and vendor products that bundle PHP.
➡️ Monitor web servers for suspicious activity, including PHP processes unexpectedly launching command shells or downloading files. Ensure appropriate process-monitoring capabilities are in place to help identify potential exploitation.
➡️ If you find signs of compromise, isolate affected systems, preserve your web server and PHP logs, and report it to your local FBI field office or ic3.gov. Those reports help us identify the actors involved and warn other organizations before they become victims.
For the latest information on these vulnerabilities (CVE-2026-109618 and CVE-2026-109619), follow PHP’s announcements on php.net, CERT-EU Security Advisory 2026-018, and CISA’s Known Exploited Vulnerabilities catalog.
ALT Critical vulnerability alert for PHP Core with CVE-2026-109618 and CVE-2026-109619, CVSS score 9.2, urgent patch required.
A useful example from another ecosystem
One feature we like in @NEARProtocol's Chain Signatures: a single operator cannot sign a transaction alone.
Independent participants have to cooperate to produce the signature.
It is a useful example of decentralisation doing a specific job: distributing the authority to act.
When assessing any network, look at what an operator can do independently and what requires agreement from others.
That tells you something a node count cannot explain on its own.
For us, an important part of infrastructure design is making those boundaries explicit.
People should know where the power sits
One thing we’ve learned building infrastructure at Aventus since 2017 is how important node economics are!
Everyone’s talking about @Solana’s 150ms finality target.
We're equally interested in the changes to validator operating costs.
Making decentralised networks faster and more economical to operate is good for the entire industry.
Alpenglow is now live on Solana mainnet. ⛰️
Finality just went from ~12.8 seconds to ~150ms.
The biggest consensus upgrade in Solana’s history, built by @anza_xyz.
Infrastructure rarely gets the spotlight.
It gets the workload!
As more businesses move onchain, they need infrastructure behind them that can handle real demand.
That is where Aventus comes in.
And our community of decentralised node operators is a big part of what makes it work.
Find out more at: aventus.io
A power failure in London
Millions of banking customers affected.
That’s how interconnected our infrastructure has become.
At Aventus, we’re building community-operated decentralised compute and verification infrastructure.
Check us out at: aventus.io
BREAKING: Multiple online services are down or 'experiencing issues.'
Google Cloud has reported "issues" in its western Europe region affecting dozens of websites, including; Revolut, Royal Mail and HSBC.
Latest updates ➡️ trib.al/M16q5UZ
📺 Sky 501
Aventus Cloud, beyond your own nodes.
The upcoming dashboard will give operators a view of the wider network, including a map of operator locations and the total number of registered nodes.
From there, a more detailed dashboard will show the computers, operating systems, client versions and connection types represented across the network.
For a community helping to build and run this infrastructure, access to that information should be part of the experience.
This is an early preview. More coming soon!
Interesting to see @Microsoft putting greater emphasis on operational independence, auditability and customer control.
These are increasingly important requirements for enterprise infrastructure.
At Aventus, we’ve spent years exploring how decentralised technology can provide greater transparency and independent verification.
Exciting times ahead 🥳
Today in Paris, we announced new capabilities across Microsoft Sovereign Cloud, expanding choice and control for organizations running their most sensitive workloads across public and private cloud, and our growing partner ecosystem. blogs.microsoft.com/blog/202…
Aventus connects the businesses building onchain with the community running the infrastructure.
Appchains bring the applications.
Our community of node operators runs Aventus Cloud, carrying out the compute work those applications send to the network.
AVT is used for transaction fees on Aventus Network and rewards for active node operators.
Through governance, holders also have a say in how the ecosystem develops.
We’re building more reasons to use AVT across Aventus Cloud and appchains.
Our ambition is straightforward: as the ecosystem grows, AVT should have more work to do.
World wants banks to know who’s behind an AI agent.
Good.
But knowing who authorised an agent tells you very little about the quality of the work it performs.
Independent verification will become increasingly important as autonomous systems take on greater responsibilities.
Something we’re actively developing through Aventus Cloud.
Microsoft’s reported withdrawal from Nscale’s UK data centre is worth following.
Imagine announcing an AI data centre with 23,000 GPUs, only to discover that sufficient electricity might not arrive for another five years.
Across the compute industry, there’s an enormous difference between projected capacity and infrastructure that’s actually delivering services.
Something every cloud provider, including decentralised networks like Aventus Cloud, should be measured against.
Imagine someone creates a 24/7 market for your company’s shares without your involvement.
Who’s responsible when pricing diverges from the underlying stock?
Who manages investor expectations?
The companies objecting to OKXICE have opened up a conversation the tokenisation industry needs to have.
After nearly a decade building Aventus, we’ve learned that businesses need confidence in the rules, clear accountability and trust in the infrastructure they’re being asked to adopt.
