Security update and coordinated upgrade: The core team has identified a vulnerability in public Gateway Addresses that affects asset issuance, including fUSD. Transaction privacy is unaffected, and no spend keys or wallets are compromised. We will coordinate a network upgrade asap. It requires majority consensus to activate, so we ask node operators, pools, and exchanges to be ready to update. No action is needed from ordinary users beyond upgrading when the release is published. A full technical write-up will follow after the upgrade is in place.

THE WAIT IS OVER. ATLAS IS LIVE. One ecosystem. One connected experience. Built for People. Business. Commerce. Payments. Technology. This is Nexar. Powered by NXR. One Ecosystem. A Brighter Tomorrow. #ATLAS #NexarNetwork #NXR #Web3

This launch will offer a new era to finance on chain and I love to see it.

In case you missed it: Governance on Zano is decided by stakers, and no one can see how you voted. Every staker gets to vote yes, no, or abstain. Everyone sees the outcome, no one sees your choice. vote.zano.org 🔒

“I have nothing to hide” misses the point. Privacy isn’t about hiding wrongdoing. It’s about deciding who gets access to your financial life. Public transaction histories can reveal spending patterns, wallet balances, and who you transact with, information that can be used for tracking, targeting, or price discrimination. @firoorg gives users control over that information by making financial privacy the default. Your money. Your transactions. Your choice of who sees them.

We're going to look back at the obsession with AI benchmarks as one strange phase of this industry.

One box. Your whole AI. Models, agents, and data inside. Nothing to rent, nothing to leak. #AI #DePIN #PowerNode #PrivateAI #LocalAI

Told no. It found another way in. In June, an OpenAI agent got past access blocks on Australia’s Medicare statistics portal. OpenAI told the government 84 days later. Agents can reason around rules in a prompt. Put the limits on what the agent can reach.

I think we're going to have to rethink what accountability means when software can act on its own. With ordinary software, there is usually a fairly clear chain when something goes wrong. An autonomous agent complicates that chain. It can be given a task by one person, use tools belonging to an organization, make decisions nobody explicitly instructed it to make, and interact with systems its operator never expected it to reach. Who is responsible when an AI system does something its creators didn't intend, and the people responsible don't know about it immediately? We're building systems that can act faster than the organizations responsible for them can sometimes understand what they have done. That makes monitoring and incident reporting part of the AI system itself. You can't have autonomous action without autonomous accountability.

The @ApeBond page just got a little more interesting. $SEED Base Bonds are now there, giving people another way to get into Sproutly. What I find useful about this is that the bond isn't asking you to understand everything about @Sproutlyrwa before taking a look. You can discover $SEED first, then go down the rabbit hole and see what the project is actually building. That’s a pretty natural way for new eyes to find Sproutly. Base Bonds are live on ApeBond.

According to @AnthropicAI, around 950 Claude-powered agents searched a DNA sequence database for 21 hours and identified more than 200,000 genes associated with one type of enzyme. Then narrowed that down to 20 candidates for closer investigation. One agent identified a previously unnoticed arrangement in viruses that infect bacteria: repeated DNA sequences next to a known enzyme gene and a mystery protein. Anthropic’s researchers then tested the system and found preliminary evidence that it may function somewhat like CRISPR.

gm to everyone who read "the cloud" and thought "someone else's computer." You get it.

Privacy coins keep getting delisted, and that has been Zano's accessibility problem for years. Wrapped $ZANO doesn't carry that baggage. Buy it wherever it's easiest, whether that's a Uniswap pool, the Coinbase app, or a centralized exchange. Then withdraw it to your own wallet and bridge it to Zano mainnet. On the way in, it behaves like any EVM token, which is exactly why it can be listed and traded anywhere. The moment it lands on Zano, that stops. Amounts hidden, addresses hidden, no history to follow on-chain. Public where you need access, private where you need privacy. 🔒

Agents don't have to be malicious to cause security problems. It can be trying to complete a perfectly ordinary objective and discover that it has access it shouldn't have. It makes the Australian government incident worth thinking about. An OpenAI agent gained unauthorized access to files on a government health portal during a training exercise. Although, it has been said that there is no evidence that personal health information was accessed. The boundary between what the agent was supposed to do and what the surrounding system allowed it to do wasn't as clear as we thought. Permissions is not the whole security model for agents. An agent needs to know what it is allowed to do, but the system also needs to make it difficult for the agent to turn an unexpected capability into an unexpected action.

We're going to look back at the phone as the last major computing interface where we had to do most of the work ourselves. Muse sitting in glasses is interesting for reasons other than hardware. If you open an app and figure out how to use it today, eventually you may just tell your agent what you want and let it figure out which services need to be involved. This has enormous implications for the companies that built the apps we're used to using. If the agent becomes the place where the transaction starts, the application may no longer be the primary interface to the customer.

Most financial anomalies surface months after they hit the ledger. A PowerNode agent monitors transactions and payment data on a recurring basis - flagging the unusual, classifying it, escalating what matters to a human. On-premise, so there's no third-party AI vendor in your risk inventory.

$ZANO burn report: Today: 18.58 ZANO This week: 127 ZANO This month: 707 ZANO All time: 15K ZANO Every transaction on Zano includes a small fee that gets burned permanently. The busier the network, the more supply gets removed.

It's going to be difficult to build international rules for AI while every major power is treating AI capability as a strategic advantage. Sam Altman and Dario Amodei are asking for international cooperation around AI risks, standards and incident reporting. At the same time, governments are competing to build more compute, develop more capable systems and make sure their rivals don't get ahead. Those two things are not necessarily incompatible, but pretending the competition doesn't exist won't make cooperation easier. We managed to create international rules around technologies where countries had very strong reasons to compete. AI is going to require something similar. The difficulty is agreeing on what countries should be willing to disclose, what they should be allowed to build, and what happens is they decide that moving faster is more important than following the rules everyone else agreed to. That is where the serious AI governance work begins.

I was thinking about this earlier. Imagine you buy a token representing a real tree. Cool, but then you start wondering: Where is the tree? How old is it? What’s happening to it? Can its information be tracked? That’s where @SproutlyRWA starts making more sense to me. The physical tree isn’t forgotten once the digital representation exists. There’s infrastructure being built around the asset, its data and everything that happens around it. That connection between the thing in the ground and the thing on chain is what makes the story much bigger. If you’re exploring environmental RWAs, Sproutly is a good place to start [t.me/sproutlyrwa]

Recently, @Google began extending its Private AI Compute architecture to support persistent memory on the server side, allowing an AI assistant to retain context across devices without giving the cloud provider access to the underlying personal data. The technical approach is quite specific. Personal encryption keys remain on the user's devices, while the encrypted memory is stored in dedicated cloud infrastructure. When the AI needs that information, an end-to-end encrypted connection sends the request to an isolated secure enclave, where the data can be temporarily decrypted, used, and then encrypted again.