© Federal News Network
Arbitrum DAO has approved a governance proposal for ecosystem incentive programs, giving the community another chance to direct treasury resources toward growth.
The vote matters because DAO funding is one of the main ways Layer-2 networks try to keep builders, users, and liquidity engaged. Incentives can help bootstrap activity, but they also need discipline. Spend too little, and promising projects may leave for better-supported ecosystems. Spend too freely, and the treasury can disappear without lasting results.
That balance is exactly why governance decisions like this matter.
For more details, visit the official Snapshot platform.
Layer-2 networks compete hard for attention.
Developers can choose between Arbitrum, Base, Optimism, Polygon, zkSync, Starknet, and others. Liquidity can move quickly. Users often follow rewards, apps, and trading opportunities.
In that environment, incentives are a tool.
They can encourage protocols to launch, deepen liquidity, attract users, and test new markets. For Arbitrum, a well-designed incentive program can help strengthen the ecosystem without relying only on organic growth.
But incentives are not magic.
They work best when they support apps that can survive after rewards slow down.
The important part is not just the funding.
It is the governance process. Arbitrum’s DAO gives token holders and delegates a role in deciding how ecosystem resources are used. That makes funding decisions more transparent, but also more political.
Different stakeholders may disagree on where incentives should go.
Some may want DeFi liquidity. Others may want gaming, infrastructure, grants, developer tools, or regional growth. A proposal approval shows where the DAO landed this time, but it also adds to the wider debate over treasury management.
This is where the wording needs care.
A governance approval does not necessarily mean every token is immediately distributed. Programs can involve staged allocations, milestones, oversight, reporting requirements, or follow-up processes.
That distinction matters because DAO headlines often make funding sound simpler than it is.
The balanced read is that Arbitrum DAO has approved the direction of an ecosystem incentive program. The real test comes in execution.
The market has become more skeptical of token incentives.
In the last cycle, many ecosystems paid heavily for temporary activity. Users arrived for rewards, farmed the incentives, and left when the program ended. That kind of growth looks good on a dashboard until it disappears.
Arbitrum’s challenge is to fund activity that sticks.
That means looking at retention, liquidity depth, developer output, protocol revenue, user activity, and whether funded projects continue growing without constant subsidies.
For ARB holders, governance activity can be a double-edged signal.
On one hand, a busy DAO can support ecosystem growth and make the token more relevant. On the other hand, treasury spending must be handled carefully, because poor allocation can weaken confidence.
The approval shows Arbitrum is still actively using governance to compete.
Now the community will need to prove that the incentives lead to something durable.
That is the real story: not just passing the vote, but making the spending matter.
This article draws on Arbitrum DAO Snapshot governance materials.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Snapshot. at Snapshot
Sui Network’s total value locked is holding around the $1.2 billion level, keeping the chain in the conversation as traders watch where DeFi liquidity is moving.
TVL is not the same as users. It is not the same as revenue. It does not prove that every application on the network is thriving.
But it is still one of the most watched signals in DeFi because it shows how much value is sitting inside protocols on a chain. For Sui, holding the $1.2 billion area gives the ecosystem a useful liquidity marker.
For more details, visit the official Defillama platform.
TVL has lost some of its magic since the early DeFi boom.
Back then, every rising TVL chart was treated like proof that a protocol was winning. The market is more careful now, and rightly so. TVL can be boosted by incentives, asset-price changes, looping, or a few large depositors.
Even with those limits, TVL still matters.
It shows whether capital is present. Without liquidity, DeFi apps struggle. Lending markets need deposits. DEXs need pools. Yield products need assets. Traders need depth.
So when Sui holds a $1.2 billion TVL level, it tells the market that the chain has meaningful DeFi capital to work with.
Sui is competing against some very strong ecosystems.
Ethereum and its Layer-2s still dominate much of DeFi. Solana has deep retail momentum. BNB Chain has distribution. Avalanche, Arbitrum, Base, and others all have their own liquidity pockets.
That makes Sui’s TVL important.
The network needs visible metrics to stay in the conversation, and DeFi liquidity is one of the clearest. Holding a billion-dollar-plus level helps show that Sui is not just a narrative chain. It has capital deployed across applications.
This needs to stay clear.
A high TVL number does not mean daily active users are rising. It does not mean transaction quality is improving. It does not mean developers are shipping faster. It simply tells us how much value is locked in DeFi protocols.
That is valuable, but limited.
For a stronger ecosystem read, traders need to pair TVL with DEX volume, active addresses, transaction count, fees, stablecoin supply, developer activity, and app-level usage.
TVL is one piece of the picture.
Round numbers matter in crypto.
A chain holding above $1 billion in TVL tends to be taken more seriously than one below it. It signals that enough capital has arrived to support a meaningful DeFi ecosystem.
Sui holding around $1.2 billion therefore gives the network a stronger market position.
It may also help attract builders who want liquidity already in place before launching applications.
The next test is whether Sui can convert liquidity into deeper activity.
That means more trading, more lending, stronger apps, better retention, and wider stablecoin usage. If TVL stays high while activity also grows, the network’s DeFi case becomes stronger.
If TVL holds but usage lags, the signal becomes less powerful.
For now, Sui has a solid capital base. The market will want to see whether that liquidity turns into a busier ecosystem.
This article draws on DeFiLlama Sui Network TVL data.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Defillama. at Defillama
Solana ecosystem tokens have outpaced the broader altcoin market in recent performance benchmarks, giving traders another reason to watch the network’s internal rotation rather than SOL alone.
That is the interesting part here. Solana is not just one token story anymore.
When the ecosystem is active, capital can move through memecoins, DeFi tokens, infrastructure names, liquid staking assets, wallets, launchpads, and consumer-facing projects. Sometimes SOL leads. Sometimes the smaller ecosystem tokens move harder.
The latest performance data points to that second dynamic.
For more details, visit the official Coingecko platform.
Solana has become one of the most active retail ecosystems in crypto.
Low fees and fast settlement make it easier for traders to move quickly between assets. That can create intense rotation when sentiment improves. Capital enters SOL, then spills into ecosystem tokens, memecoins, DeFi apps, and other smaller plays.
This is part of what makes Solana exciting.
It is also what makes it risky.
When liquidity is strong, ecosystem tokens can run faster than the broader market. When sentiment fades, those same tokens can fall quickly.
That is why performance benchmarks need context.
SOL is the network’s main asset.
It reflects broad investor appetite for Solana as an ecosystem. But smaller Solana tokens can show where traders are taking more specific risk. They may point to attention around a particular app, sector, launch, or narrative.
That makes ecosystem performance useful.
If multiple Solana-linked tokens are outperforming, it can suggest that activity is spreading beyond the base asset. That often happens when traders feel more confident and start looking for higher-beta opportunities inside a strong chain.
This is worth saying clearly.
A token outperforming does not automatically mean the project is strong. Some moves are driven by speculation, thin liquidity, incentives, listings, or social momentum. Solana’s ecosystem has plenty of serious builders, but it also has plenty of fast-moving risk.
So the data needs a careful read.
The useful point is that Solana-linked assets are attracting attention. The harder question is which parts of that attention are durable.
Breadth matters in crypto.
If only one asset is moving, the rally can be narrow. If many tokens within an ecosystem are moving, the market may be showing deeper participation.
For Solana, stronger ecosystem breadth can support the idea that the network is not only benefiting from SOL demand, but from wider on-chain activity and speculation.
That can feed back into the main network narrative.
But again, it is not automatic. Performance needs to be paired with usage, liquidity, developer activity, and product traction.
The latest benchmark shows Solana ecosystem tokens running ahead of the wider altcoin market.
That tells us traders are taking risk inside the Solana ecosystem again. It also suggests that the network’s internal market remains lively after a strong August.
The next test is whether the move spreads into real activity.
If trading volume, app usage, and liquidity support the price action, the ecosystem story gets stronger. If the move is mostly speculative, it may cool quickly.
Either way, Solana remains one of the main places where altcoin rotation is happening.
This article draws on CoinGecko Solana ecosystem performance data.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Coingecko. at Coingecko
Arbitrum recorded $814 million in daily decentralized exchange volume, giving the Ethereum Layer-2 network another strong activity signal as traders rotate through on-chain markets.
The figure is useful because it looks at actual trading activity rather than just token price. That matters for Arbitrum, where the story has always been tied to Ethereum scaling, DeFi liquidity, and the question of whether Layer-2 networks can keep attracting real usage.
A big DEX volume day does not guarantee ARB will rally. But it does show that traders are using the network in size.
For more details, visit the official Defillama platform.
DEX volume is one of the clearest signs of on-chain demand.
When traders swap assets through decentralized exchanges, they create fees, liquidity movement, arbitrage activity, and demand for infrastructure. It is not just idle capital sitting in a protocol. It is users doing something.
For Arbitrum, that matters because DeFi is one of its core strengths.
The network has long positioned itself as a major Ethereum scaling environment for trading, lending, derivatives, and liquidity applications. A strong volume print supports that identity.
It says activity is there.
Arbitrum is not operating in an empty field.
Base, Optimism, zkSync, Starknet, Polygon, and other Layer-2 or scaling ecosystems are all competing for users, developers, liquidity, and apps. Ethereum scaling has become a crowded market.
That makes volume important.
Networks can talk about technology all day, but liquidity tends to move where traders actually get good execution, useful apps, and reasonable costs. If Arbitrum can keep generating strong DEX volume, it remains one of the more important L2s in the market.
There is a limit to the metric.
DEX volume can spike because of volatility, incentives, arbitrage, token launches, liquidations, or temporary market conditions. That does not always mean long-term user retention is improving.
So the $814 million figure should be read as a strong activity signal, not a complete health check.
The deeper questions are whether users come back, whether liquidity stays, whether protocols earn sustainable fees, and whether developers keep building.
ARB holders watch network activity because governance-token value is tied to the ecosystem’s relevance.
The relationship is not always direct. Higher DEX volume does not automatically mean ARB captures more value. Token economics, governance design, incentives, and market sentiment all matter.
But if the network becomes more active, the governance asset tends to get more attention.
That is why the DEX volume print matters even without making a price call.
Arbitrum’s $814 million DEX volume day shows the network is still very much in the Layer-2 conversation.
It has liquidity. It has traders. It has DeFi activity. Those are the things that matter when scaling networks compete for relevance.
Now the question is consistency.
If Arbitrum keeps posting strong activity, the story gets stronger. If the volume fades quickly, this may look more like a one-day market burst.
For now, it is a solid signal that the network remains busy.
This article draws on DeFiLlama Arbitrum DEX volume data.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Defillama. at Defillama
Securitize has expanded its institutional tokenization framework for public equities, adding another piece to the growing market around real-world assets and on-chain financial infrastructure.
This is one of those developments that sounds technical, but the direction is pretty clear. Traditional assets are slowly being pulled toward blockchain rails, and companies like Securitize are trying to build the regulated infrastructure that lets that happen without turning the whole thing into a free-for-all.
The important point is scope.
This is an infrastructure development. It should not be described as every public equity suddenly trading on-chain, or as tokenized shares replacing ordinary stock markets overnight.
For more details, visit the official Securitize platform.
Tokenizing public equities is a big idea because stocks already sit at the center of traditional finance.
If equity exposure can move on digital rails, it could change how investors access markets, how settlement works, how collateral is managed, and how financial products are built. But it is also a heavily regulated area, which makes execution harder than tokenizing a simple crypto asset.
That is why regulated infrastructure matters.
You cannot just put a stock ticker on-chain and call it done. There are questions around ownership rights, transfer restrictions, investor eligibility, custody, settlement, corporate actions, market hours, jurisdiction, and disclosures.
Securitize operates in that more serious part of the tokenization stack.
Tokenized U.S. Treasuries have been the easiest RWA story for the market to understand.
They are relatively simple, yield-bearing, and already institutionally familiar. Public equities are more complicated, but also much larger as a market category.
That makes equity tokenization an important next step.
If the infrastructure improves, on-chain markets could eventually support a wider range of traditional assets. Not just stablecoins and Treasury funds, but equity-linked products, collateral systems, and portfolio tools.
That is the long-term attraction.
A tokenized asset only matters if the legal claim behind it is clear.
Investors need to know what they actually own, who holds the underlying asset, how redemptions work, what happens during corporate actions, and which rules apply if something goes wrong.
That is why public-equity tokenization is not just a technology problem.
It is a legal, regulatory, custody, and market-structure problem.
Securitize’s framework expansion is notable because it is aimed at that regulated layer rather than just creating a speculative wrapper.
For crypto markets, tokenized equities can bring new collateral and new users.
If traditional assets can be represented on-chain in a compliant way, DeFi and institutional platforms may gain access to deeper pools of real-world collateral. That could make lending, trading, and settlement more useful.
But there is a catch.
More tokenized assets also mean more compliance requirements, permissioned systems, and connections to traditional finance. Some crypto users will like that. Others will see it as moving away from the open-market ideal.
Either way, the trend is hard to ignore.
Securitize’s move adds to the steady march of tokenization.
It is not the loudest story in crypto, but it may be one of the more durable ones. Institutions understand equities. They understand settlement. They understand collateral. If blockchain can improve those processes without breaking the legal framework, tokenization has a real case.
The market should keep expectations grounded.
This is infrastructure. Infrastructure takes time. But when it works, it changes what the next wave can be built on.
This article draws on Securitize materials relating to public equities tokenization.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Securitize. at Securitize
Dogecoin network activity has picked up sharply, with active addresses rising 35% and daily transactions topping 1.2 million, according to public Dogecoin network data.
That is a useful signal for DOGE because the market often talks about Dogecoin only through memes, celebrity posts, and price swings. Those things matter for attention, of course. But network activity gives us something more concrete to look at.
More active addresses and higher transaction counts suggest that DOGE is seeing more movement on-chain, not just more chatter around the token.
For more details, visit the official Bitinfocharts platform.
Active addresses are not a perfect user count.
One person can control multiple addresses. Exchanges can move funds through many wallets. Automated activity can inflate numbers. So the metric has limits.
But it is still useful.
A rise in active addresses can show that more wallets are interacting with the network during the measured period. For Dogecoin, that matters because it helps separate actual network movement from pure social attention.
When DOGE activity rises on-chain, traders have more to work with than jokes and chart candles.
Daily transactions topping 1.2 million adds another layer.
Transaction count shows how much activity is passing through the network. Again, it does not tell the whole story. A transaction could be small, automated, exchange-related, or part of a wider wallet reshuffle.
But a higher transaction count still shows the network is being used.
For a chain like Dogecoin, which started as a meme but has lasted through multiple cycles, activity metrics help explain why the asset remains relevant.
DOGE has never been only about technical complexity. Its strength is simplicity, liquidity, brand, and community persistence.
Let’s be honest: Dogecoin trades heavily on mood.
When speculative appetite returns, DOGE can move quickly. When attention fades, it can drift. That is part of the asset’s character and one reason traders watch it as a broad meme-coin barometer.
The address and transaction data does not erase that.
It simply adds a stronger foundation to the conversation. If activity is rising while the market is paying attention, the move looks healthier than a pure social-media spike.
This story does not need a price prediction.
The useful point is that Dogecoin’s network activity increased. Whether DOGE rallies from here depends on liquidity, Bitcoin direction, meme-coin rotation, exchange flows, and broader risk appetite.
A 35% active-address increase is worth noting. It is not a promise.
That is the right line to hold.
The next thing to watch is whether the activity continues.
One strong daily print can fade quickly. A sustained rise in active addresses and transactions would be more meaningful because it would suggest ongoing use rather than a one-off burst.
Traders will also watch whether on-chain movement lines up with volume and price.
If all three rise together, Dogecoin may have a stronger momentum setup. If network activity cools again, the latest spike may be remembered as a temporary burst.
For now, DOGE has a better activity story than it had a week ago.
This article draws on public Dogecoin network data from BitInfoCharts.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Bitinfocharts. at Bitinfocharts
Ripple has released 1 billion XRP from escrow under its standard monthly schedule, with the latest unlock visible through XRPScan account data.
This is one of those XRP stories where the context matters more than the headline.
A 1 billion XRP unlock sounds dramatic if it is stripped of detail. But Ripple’s escrow releases are part of a long-running scheduled process, not a surprise dump suddenly appearing from nowhere.
That does not mean traders ignore it. Supply movements matter. But this needs to be framed as a planned tokenomics event rather than a shock.
For more details, visit the official Xrpscan platform.
Ripple’s XRP escrow system was created to bring more predictability to token supply management.
Instead of all escrowed XRP being freely available at once, scheduled releases occur over time. The system gives the market visibility into when tokens may become available and how much is being unlocked.
That visibility is important.
Crypto markets dislike surprises, especially around supply. Scheduled escrow releases do not remove all uncertainty, but they make the process easier to track.
The latest 1 billion XRP release fits into that established pattern.
This is the biggest point.
When XRP is released from escrow, it does not automatically mean every token is sold into the market. Some XRP can be used for operational purposes, liquidity, institutional sales, ecosystem activity, or returned to escrow depending on Ripple’s process and market conditions.
So the unlock is a supply event, not a completed sale.
Traders may still watch it because available supply can affect sentiment. But there is a difference between tokens becoming available and tokens being dumped.
That difference matters.
Even scheduled unlocks can influence market psychology.
XRP has a large, active community, and token supply is always part of the discussion. When 1 billion XRP is released, traders look at where the tokens move, how much is re-locked, whether exchange balances change, and whether price reacts.
Sometimes the market barely notices. Sometimes the unlock becomes part of a larger narrative around liquidity and selling pressure.
The unlock itself is predictable. The market reaction is not.
Ripple’s escrow system has been debated for years.
Supporters argue it creates transparency and controlled distribution. Critics argue Ripple’s holdings still represent a major supply overhang. Both views are part of the XRP market conversation.
The latest release will not end that debate.
It simply gives traders another monthly data point.
What matters is how the released XRP is handled and whether market conditions are strong enough to absorb any additional liquidity.
The cleanest way to read this is simple: Ripple released 1 billion XRP from escrow as part of its regular schedule.
It is worth watching because token supply matters. It is not worth exaggerating into panic language.
For XRP traders, the next signals are wallet movements, re-escrow activity, exchange flows, liquidity, and broader market sentiment. Those will tell more than the unlock headline alone.
Scheduled events can still matter, but they need to be understood as scheduled events.
This article draws on XRPScan escrow account data.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Xrpscan. at Xrpscan
Cardano’s enterprise story has gained another example, with a major retail group deploying blockchain verification infrastructure built around the network’s ecosystem.
For Cardano, that matters because enterprise adoption has always been part of the pitch. The project has often positioned itself as slower, more formal, and more research-led than some rival chains. That can frustrate traders who want fast hype cycles, but it also means real-world verification use cases are especially important when they arrive.
This is not an ADA price story. It is not about a sudden fee surge or a network-wide explosion in activity.
It is about a specific enterprise supply-chain application using Cardano infrastructure for verification.
For more details, visit the official Cardanofoundation platform.
Supply chains are messy.
Products move through factories, warehouses, shipping channels, distributors, shops, and customers. Along the way, companies need to prove authenticity, origin, handling, and sometimes sustainability claims. That is difficult when data sits across different systems and companies.
Blockchain verification can help when it creates a shared record that different parties can check.
That is why supply-chain use cases have been discussed in crypto for years. They are not always easy to implement, but when they work, they can offer something more concrete than speculation.
For Cardano, a verification deployment fits the network’s long-running identity: real-world systems, formal infrastructure, and enterprise use.
This is one of the big tensions in Cardano coverage.
Crypto markets love instant catalysts. Enterprise adoption rarely works like that. Companies do not usually move critical verification systems overnight. They run pilots, test vendors, check legal requirements, train teams, and integrate with existing systems.
That can make enterprise stories feel less exciting at first.
But they can also be more durable if they stick.
A retail verification system is not designed for a one-week trading narrative. It is designed to solve a business problem. That makes it worth covering differently.
The key is to stay specific.
This deployment shows that Cardano infrastructure can be used in an enterprise verification setting. It does not prove that every retailer will adopt Cardano. It does not mean ADA demand automatically rises. It does not mean the network has suddenly become the default chain for supply chains.
It is one example.
But examples matter, especially in enterprise adoption. Each one gives the ecosystem another proof point and another case to show future partners.
Retail brands care about trust.
Counterfeiting, unclear sourcing, supplier risk, and weak product verification can all damage a brand. If customers or partners cannot verify claims, the brand carries more risk.
Blockchain-based verification can help by making certain records easier to check and harder to quietly change.
That does not mean blockchain solves every supply-chain problem. Bad data can still be entered. Physical goods still need real-world checks. But once reliable data is added, the ledger can make later verification cleaner.
Cardano still needs more visible usage across DeFi, payments, applications, and enterprise systems.
That is the challenge for the ecosystem. It has a committed community and a serious technical identity, but market attention often shifts toward chains with louder consumer activity.
Enterprise verification gives Cardano a different lane.
It may not produce the fastest headlines, but it supports the argument that the network can be useful beyond trading.
For Cardano, that may be exactly the point.
This article draws on Cardano Foundation materials relating to enterprise verification.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Cardanofoundation. at Cardanofoundation
The XRP Ledger has crossed 3 billion cumulative transactions, giving the network another long-term usage milestone at a time when on-chain activity is once again being watched closely.
The figure is not a price prediction. It does not say XRP has to rally. It does not prove that every transaction carried high economic value.
But it does show something important: XRPL has been processing activity for years, and the cumulative count is now large enough to stand out even in a market that is usually obsessed with short-term moves.
For XRP holders, the milestone is a reminder that the ledger’s story is not only about lawsuits, ETFs, or exchange listings. There is also a functioning payment-focused network underneath it.
For more details, visit the official Xrpscan platform.
Transaction milestones are not perfect, but they are useful.
They show that a network is being used, tested, and relied on over time. In XRPL’s case, the 3 billion mark supports the idea that the ledger has maintained activity across multiple market cycles.
That matters because many chains launch with a burst of attention and then fade.
XRPL has been around long enough to have survived bear markets, regulatory uncertainty, exchange delistings, relistings, and shifting investor narratives. Crossing 3 billion transactions adds another data point to that longer story.
It is not glamorous. It is not a viral headline. But it is real network history.
XRPL has always had a different identity from many smart contract platforms.
Ethereum became the home of DeFi and smart contracts. Solana built around speed, retail activity, and low-cost applications. Bitcoin remained the monetary base layer. XRPL’s long-running pitch has centered more on fast, low-cost settlement and payments.
That makes transaction activity especially relevant.
If a payment-focused ledger is not processing transactions, the story weakens. If it continues to process a large cumulative count, the payment narrative has more weight.
The 3 billion transaction milestone fits that frame neatly.
This distinction is worth keeping clear.
Ripple is a company. XRP is the token. XRPL is the public ledger. Ripple has played a major role in the ecosystem, but not every XRPL transaction is controlled by Ripple, and not every network milestone should be reduced to Ripple corporate activity.
That nuance matters for readers.
The milestone is about the ledger’s cumulative transaction count. It is not a statement that Ripple directed all of that activity, and it is not a claim about corporate revenue or adoption unless separate sources support it.
A large transaction count can sound impressive, but not all transactions are equal.
Some may be payments. Some may be account operations. Some may be exchange-related activity. Some may carry small value. Some may be automated. So the number should not be translated directly into user count or payment volume.
Still, the milestone is meaningful because it shows endurance.
Crypto networks are judged partly by whether they keep operating and attracting activity over long periods. XRPL has now crossed another visible threshold.
For traders, the milestone may feed into the broader XRP narrative, but it is unlikely to be enough on its own.
The market will still watch liquidity, regulatory developments, ETF speculation, Ripple-related news, exchange flows, and broader altcoin sentiment. Network usage can support the long-term story, but price action usually needs more than a cumulative metric.
That is the balanced read.
XRPL has crossed 3 billion transactions. It is a real network milestone. It is also not a promise that XRP’s next move is already decided.
This article draws on XRP Ledger network metrics from XRPScan.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Xrpscan. at Xrpscan
MoonPay has launched PayBox, a payment tool designed to let crypto transactions happen directly inside Grok AI chatbot workflows.
It is a neat little glimpse of where consumer crypto may be heading. Not another standalone wallet app. Not another checkout page buried three clicks away. The idea is much simpler: let users move from chat to transaction inside the same flow.
That does not mean MoonPay has suddenly turned Grok into a crypto exchange, and it should not be treated as an official xAI partnership unless MoonPay says that directly. But it does show how payment companies are starting to think about AI interfaces as the next place where users may actually spend, send, or move digital assets.
For more details, visit the official Moonpay platform.
For years, crypto payments have had a usability problem.
The technology may work, but the experience often asks too much of normal users. Open a wallet. Copy an address. Switch apps. Confirm the network. Check fees. Hope the transaction went where it was supposed to go.
That is fine for crypto-native users. It is less appealing for everyone else.
Chat-based payments try to hide some of that friction. If a user is already asking an AI assistant to help with a task, there is a natural next step where the assistant can also help complete the payment.
That is where PayBox becomes interesting.
It suggests MoonPay sees crypto not just as something users access through exchanges, but as something that can sit inside broader digital workflows.
Grok gives the launch a bigger consumer-facing hook.
AI chatbots are becoming places where users search, plan, shop, code, write, and make decisions. If payments can happen inside that same interface, the chatbot becomes more than a conversation tool. It starts to look like a transaction layer.
That is a big idea, even if the actual product is still early.
Crypto companies want to be close to where users already are. AI chat is one of those places. So a tool that brings crypto payments into chatbot workflows fits the direction of travel.
The question is whether people will actually use it.
This is where the language needs care.
PayBox is a utility product. It is not proof that AI chatbots are about to replace wallets. It is not proof that Grok users will suddenly start making crypto payments at scale. It is not a sweeping signal that every AI platform is becoming a crypto platform.
It is a product release that shows a possible new interface.
That is enough.
The more interesting story is not hype. It is distribution. If crypto payments are going to become more normal, they probably need to show up inside tools people already use.
Crypto has spent years building infrastructure.
Now the harder challenge is experience. Stablecoins, wallets, payment processors, on-ramps, and compliance tools have improved, but users still need simple ways to interact with all of it.
AI assistants could help with that.
They can guide users through actions, explain what is happening, reduce confusion, and turn complicated flows into plain-language steps. But they also create risks around mistaken prompts, spoofing, approvals, and user consent.
So the opportunity is real, but so is the need for guardrails.
MoonPay’s PayBox launch is another sign that crypto payments are looking beyond the exchange screen.
The next wave may be less about making users visit crypto-specific apps and more about embedding crypto actions into everyday digital environments. Chatbots are one of the more obvious places to try that.
For now, PayBox is an early product signal.
If it works, it could make crypto payments feel less like a separate task and more like something that happens naturally inside the tools people are already using.
That is the part worth watching.
This article draws on MoonPay’s PayBox product announcement.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Moonpay. at Moonpay
Welcome back, cyberwarriors!
Almost a year ago, OTW spoke about quantum computers and the risk of our encryption getting broken within three years. In March, Google shared its concern on the same issue, moving up its own post-quantum migration deadline to 2029. Some companies are migrating to mitigate that risk, but not many are taking it seriously. Eventually, a huge number of companies are going to get left behind with weak and breakable encryption. Hackers will only benefit from that negligence.
To help you minimize the risk and get an actionable plan with recommendations tailored to your company, we want to show you how AC-Scanner works.
AC-Scanner is basically a script for post-quantum cryptography exposure assessment. It maps your full cryptographic attack surface across TLS endpoints and SSH services, assesses every asset against NIST post-quantum standards and generates a structured Cryptographic Bill of Materials (CBOM).
Before we continue with the scan, you might want to watch a video by OTW and David Bombal on the risk of quantum computing being able to decrypt things at mass scale and expose session keys.
Docker is the easiest way to get started. We’ll start with the CLI version first, then show you how to get the web version up and running. They both work the same way, so you can choose any.
First install Docker on your system:
Loginubuntu > sudo apt update
ubuntu > sudo apt install docker.ioThen switch to root and pull it:
root > docker pull qubitac/acscanner:latest
Now it’s ready, so let’s see the help menu.
root > docker run --rm -it qubitac/acscanner:latest bash -c 'rm -f /.dockerenv && cd /app/scripts && ./scan.sh -h'
We’re only interested in the presets here. As you can see, you can test basically any of your assets.
Let’s choose some random Russian company for this scan. We don’t intend them to benefit from the results, we will just use it for demonstration to show how prevalent the issue is.
For our scan we used –all to scan everything:
root > mkdir -p ~/ac-scans/example.com && docker run --rm -it -v ~/ac-scans/example.com:/app/scripts/example.com qubitac/acscanner:latest bash -c 'rm -f /.dockerenv && cd /app/scripts && ./scan.sh --noinstall example.com --all'
If you’re testing a big company, it will take time.
Results will be stored in ~/ac-scans
Here we only need crypto-bom.json that’s hiding in cbom.
Upload crypto-bom.json to the dashboard by clicking Load CBOM. You will see the overview.
You can already see the infrastructure is not PQC ready and has several critical issues.
The next step is HTTPS. Although 9 of their endpoints are using HTTPS, it’s vulnerable and the risks are high.
The scanner tried to fingerprint the SSH endpoints too, but they weren’t open.
Let’s look at the issues that the company has. It will show all the affected hosts with severity assigned to each.
Quantum risks may help tracking the progress of your migration. The results below are from a different company, but you can see they have only 3 PQC ready hosts out of 308.
Recommendations will help you address issues by giving you prioritized actions.
The recommendations were intentionally redacted by us to make them unusable. However, you can still clearly see how the page is structured.
Finally, your main goal is migration. Here it lists all the migration phases and gives you deadlines by which they need to be completed.
As you can see, legacy TLS should be abandoned by 2027 and hybrid PQC key exchange should be introduced no later than 2028. That applies to everyone, not just this organization in particular. The report gives clarity and orients your client so there’s no confusion.
If you don’t want to work in the terminal, you can use the web version.
root > docker pull qubitac/acscanner
root > docker run -d --name acscanner -p 8080:80 qubitac/acscanner:latest 
It’s available in the browser on http://localhost:8080/.
AC-Scanner is easy to work with if you use Docker, otherwise you’ll run into some incompatibility issues. The dashboard has all the valuable information and most importantly it’s actionable and orienting. You don’t just see the vulnerabilities, you get a guide with recommendations on how to fix them too. Your client will definitely appreciate that.
Want to learn how to prepare your network for the post-quantum world? Join our Preparing Your Network for the Post-Quantum World training, taking place October 13-15 at 3 PM UTC. Available exclusively to Subscriber PRO students.
The post Quantum Resistance: Scanning Company Assets for PQC Readiness first appeared on Hackers Arise.
NIST’s New Guide for AI and CSF 2.0 NIST recently released a new draft, SP 1353, that acts as a practical guide for using AI alongside the Cybersecurity Framework 2.0....
The post Inside NIST SP 1353: The New Quick-Start Guide for AI-Powered CSF Analysis appeared first on Cyber Defense Magazine.
The US Federal Government is committing $600 million to build one of the world’s most advanced AI infrastructure systems. Executive Order 14363, the Genesis Mission, connects national laboratory supercomputers across nuclear simulation, biodefense, energy grid modeling, and every major scientific domain. Fifty-one organizations signed on, including NVIDIA, OpenAI, IBM, Microsoft, AWS, Google, and Oracle.
The security framework governing these workloads was not written for this scale of use.
NIST SP 800-234, the High-Performance Computing Security Overlay, is well-constructed, tailoring 60 controls across four security zones, building on the SP 800-53B moderate baseline. It was designed for deterministic HPC workloads such as climate simulations, finite element analysis, and computational fluid dynamics. These workloads share a common attribute: code that runs the same way, every time, and behaves predictably under well-understood inputs. The security controls governing those workloads assume you can scan at the perimeter, clear memory between jobs, and attest to integrity at load time.
AI workloads break every one of those assumptions.
SentinelOne has submitted a formal proposal to the NIST HPC Security Working Group regarding this gap, and NIST has acknowledged it. We have a post on LinkedIn to share our proposal, and welcome commentary from across the industry.
This spring, in just three weeks, three AI-driven supply chain attacks targeted widely deployed software: LiteLLM, the most-used AI infrastructure package in Python development environments, Axios, the most-downloaded HTTP client in the JavaScript ecosystem, and CPU-Z, a trusted system diagnostic tool with a legitimate signed binary from the official vendor domain.
SentinelOne stopped all three on the same day each attack launched, with no prior knowledge of any payload.
The most important aspect of this outcome is how these attacks were stopped, and why signature-based detection couldn’t work. Each attack arrived through a trusted delivery channel. LiteLLM was compromised after credentials were stolen via Trivy, a security scanner. The attacker published two malicious versions to the PyPI repository. In at least one confirmed case, an AI coding agent with unrestricted permissions auto-updated to the infected version, meaning there was no human review or approval step before the payload ran. The Axios attacker exploited a legacy access token that the project maintainers had forgotten to revoke, bypassing every npm security control. CPU-Z attackers targeted the vendor’s distribution infrastructure directly; anyone who downloaded from the official website received a properly signed binary containing a payload. In all three cases, while the authorization chain was legitimate, the intent was not.
This is the defining characteristic of modern supply chain attacks: the workflow is verified, but the intent has been subverted. Every perimeter control, signature library, and reputation lookup checks authorization and passes. These attacks were designed to exploit that gap, and they ran at machine speed through automated pipelines with no human checkpoint.
To put this into the context of HPC and AI workloads running at scale, a compromised Python package in a developer’s environment is a serious incident; a poisoned training pipeline on classified biodefense data on a national laboratory supercomputer is on a different order of magnitude. The model it produces may be correct 99.9 percent of the time and adversarially wrong under precisely targeted conditions. No perimeter scan, signature check, or load-time integrity verification will catch it after training completes.
Of the 60 controls SP 800-234 tailors, three bear directly on AI workload protection, and each carries a documented gap. In a fourth area, supply chain, the overlay does not tailor at all.
The attacks against AI workloads on HPC are not theoretical, and they are not detectable at the perimeter.
The characteristic that makes AI workloads uniquely difficult is persistence. A compromised simulation may produce visibly wrong results, but a compromised model can produce correct results the overwhelming majority of the time and adversarially wrong results under precisely targeted conditions. By the time anyone has reason to investigate, the window for recovery has often closed.
We know the technology required to address these gaps exists and has been proven at scale in environments with performance constraints far tighter than those in HPC. What is needed is a well-defined architecture that enables the secure execution of large-scale AI workloads.
Dedicated security compute. Runtime security that shares CPU resources with the workload it monitors can be starved of CPU time under heavy load and interfered with by a workload that achieves kernel-level access. The SPiCa research demonstrated that eBPF monitoring pipelines can be manipulated from within the kernel by rootkits filtering events before they reach the analysis engine, meaning that a co-scheduled monitor is not a reliable monitor.
Every other infrastructure function on an HPC node has dedicated resources. The job scheduler, the filesystem client, and the out-of-band management plane. Security monitoring is infrastructure and should be afforded the same dedicated resources.
Modern HPC nodes have 128 to 256 CPU cores. One reserved for security monitoring is less than one percent of the available compute. Linux kernel CPU isolation via isolcpus, nohz_full, and rcu_nocbs is production-proven in high-frequency trading and real-time systems, with bounded, predictable overhead.
eBPF-based behavioral telemetry at the training layer. Effective monitoring of an AI training pipeline means continuous observation of compute behavior profiles, memory access patterns, GPU utilization, and inter-node communication, with behavioral baselines established for approved training configurations. A poisoning attack that executes within expected statistical ranges is not visible to a perimeter scanner, but it is visible to a behavioral baseline that knows what the training job should look like.
This is the same principle that SentinelOne’s on-device Behavioral AI detected for LiteLLM, Axios, and CPU-Z. The LiteLLM detection flagged a Python interpreter executing Base64-decoded code in a spawned subprocess. The CPU-Z detection flagged an anomalous process chain: cpuz_x64.exe spawning PowerShell, which spawned csc.exe, which spawned cvtres.exe. CPU-Z doesn’t do that. The behavioral baseline knew what legitimate execution looked like, and in these cases, that behavior was the decisive signal.
Cloudflare uses an eBPF-based architecture to mitigate DDoS attacks exceeding 7 Tbps. SentinelOne uses it to detect and stop threats in under one second across enterprise fleets. A training job that begins writing to unexpected locations, establishing anomalous inter-node communication, or deviating from its expected compute profile is detectable at runtime, before the model completes training. The performance argument against runtime monitoring on HPC was never about the technology; it requires a shift in architecture.
Inference-time output monitoring. Deployed models require continuous observation of output distributions, latency patterns, confidence score distributions, and input-output statistical properties. A model under adversarial input attack, or serving modified weights, exhibits detectable output patterns before any human analyst notices the outputs are wrong. Circuit-breaker logic needs to be designed into the serving architecture, not added after the first incident.
Model integrity verification that runs during inference. Load-time attestation is a necessary and important requirement; it is not sufficient. Long-running inference deployments are vulnerable to hot-swap attacks that replace weights after the initial integrity check passes. Continuous cryptographic hash verification of loaded model weights, running on the dedicated security core with automated circuit-breaker logic on failure, closes that vector. For a model serving safety-critical calculations, the re-verification frequency should match the workload’s risk profile with predictable overhead.
An SR-family extension for the AI supply chain. The existing SR controls address software supply chain risk. They do not address training data provenance, model weight integrity at ingestion, or pre-trained model validation. An AI bill of materials, including cryptographic documentation from the training data source through intermediate checkpoints to the deployed model, is the model-layer equivalent of software supply chain controls. Without it, every pre-trained model loaded into an HPC environment is an unverified artifact from an unverified chain.
The supply chain attacks this spring demonstrated what happens when defense architecture falls behind the delivery mechanisms attackers use. LiteLLM, Axios, and CPU-Z all arrived through trusted channels, carrying payloads no signature database contained. They were stopped because behavioral detection does not require prior knowledge of the payload. It requires knowing what legitimate execution looks like and acting when execution deviates.
Defenders protecting AI workloads face that same problem across every layer they own. HPC is the hardest version of it. But identities, endpoints, applications, and infrastructure all carry the same exposure at different scales. SentinelOne gives defenders coverage across all four, with behavioral AI running at each layer to catch what signatures miss. The specifics of how that works across your AI environment are in our AI security overview.
1 “Data Poisoning 2018–2025: A Systematic Review. IACIS (2025)”, and “Data Poisoning Vulnerabilities Across Health Care AI Architectures. JMIR (2026)
2 “Poisoning Attacks on LLMs Require a Near-Constant Number of Poison Samples” (2025). arXiv:2510.07192 and Huang et al., 2020.
3 OWASP (2025) LLM04:2025 Data and Model Poisoning. OWASP Gen AI Security Project.
