
binoua retweeted
This is a project we built internally to prevent agents from going rogue. Think of it as a governance layer for AI agents inside your org! We decides to spin it out as its own project as we want it to be completely free, open source and owned by the community!
We are open sourcing Umbra, an isolated cloud environment for AI agents.
github.com/concrete-security…
Umbra came from a internal need at Zama where we wanted to use agents across the company without giving them more access than they actually needed.
Agents can write code, install software, read internal data, use credentials and interact with production systems. As they get more capable, it becomes unrealistic to review everything they do step by step.
So the idea behind Umbra is simple: put the agent in a box. Give it a machine, let it work inside, and focus on what happens at the boundary.
The VM is theirs. The edge is ours.
Anything that touches github, slack, notion, internet, production or any other external system goes through a controlled proxy. That is where we apply policy.
Can this agent access this repo? Is github read-only? Can it push code? Can it reach production? Which credential does it need?
We grant access only when needed, and secrets are injected only for the operation being authorized.
The same applies to what comes out. Code, data or actions can be checked before they leave the environment.
Umbra is still experimental, but the key idea is: give agents enough freedom to be useful, assume they will sometimes make mistakes, and keep tight control over the boundary.
Agents can be unpredictable and most likely will always be. Boundary shouldn't be.
binoua retweeted
We are open sourcing Umbra, an isolated cloud environment for AI agents.
github.com/concrete-security…
Umbra came from a internal need at Zama where we wanted to use agents across the company without giving them more access than they actually needed.
Agents can write code, install software, read internal data, use credentials and interact with production systems. As they get more capable, it becomes unrealistic to review everything they do step by step.
So the idea behind Umbra is simple: put the agent in a box. Give it a machine, let it work inside, and focus on what happens at the boundary.
The VM is theirs. The edge is ours.
Anything that touches github, slack, notion, internet, production or any other external system goes through a controlled proxy. That is where we apply policy.
Can this agent access this repo? Is github read-only? Can it push code? Can it reach production? Which credential does it need?
We grant access only when needed, and secrets are injected only for the operation being authorized.
The same applies to what comes out. Code, data or actions can be checked before they leave the environment.
Umbra is still experimental, but the key idea is: give agents enough freedom to be useful, assume they will sometimes make mistakes, and keep tight control over the boundary.
Agents can be unpredictable and most likely will always be. Boundary shouldn't be.
The Call for Presentations for the 6th Annual FHE.org Conference on Fully Homomorphic Encryption, to be held in Seattle on April 4, 2027, is now online!
Just under 3 months left (November 1st) to submit a 2–4 page PDF on your FHE project, use-case, or demo.
Work already presented at other conferences, and any interesting presentations, demos, or tutorials, are welcome!
Full instructions: fhe.org/2027/cfp
#FHE
binoua retweeted
Anthropic used to release models their own teams had used for weeks. With fable, nobody inside has any incentive to use anything less. Now mid-tier models ship based on benchmark only.
Using your own product internally, is the best foundation for a successful model.
Any developer working with Opus 5 day to day would have caught the problem.
binoua retweeted
There’s NO Chance Trillions Move Onchain Until We Solve This | @randhindi from @zama
00:00 Why Crypto Needs Privacy
01:24 The Biggest Problem with Public Blockchains
02:34 HTTPS for Crypto
05:38 How Zama Brings Privacy to Ethereum & Solana
06:34 Why Privacy Is Making a Comeback
08:18 Building One Privacy Layer for Every Blockchain
10:11 How Confidential Transactions Work for Users
12:17 Will Privacy Become the Default?
13:00 Confidential USDC and Private DeFi Yields
14:07 Why Institutions Can't Adopt Blockchains Yet
16:11 Zama's Story: From AI Privacy to Blockchain
19:22 The Apex/T-Rex Partnership
21:13 How Shielded Assets Actually Work
23:07 Compliance, KYC, and Preventing Illicit Activity
26:53 Zama's Goal: Encrypt 95% of On-Chain Finance
28:20 Why This Is a Winner-Takes-All Market
29:00 Zama vs. Canton Explained
30:06 Final Thoughts
🤝 Paid partnership
binoua retweeted
Appreciate the S/O 🙂
Track everything Zama and let me know if you need a specific feature.
Always building!
Here is a dashboard for those who want to follow the @zama protocol metrics, in particular TVS: zamadashboard.org/tvs . Shoutout to @realchriswilder for this great tool!
Circle's compliance system flagged an external depositor's wallet. Because that wallet held funds in the cUSDC contract, the entire contract was swept into a standard holding freeze.
This is collateral damage, not a sanction against the Zama Protocol.
Our legal team is already engaged to isolate the flagged address and restore access for all unaffected participants as quickly as possible.
binoua retweeted
Thanks to @zachxbt, we found the root cause and will be taking the appropriate actions to unblock the situation. Tldr; this has nothing to do with Zama, or privacy.
The issue stems from an address related to the Overnight Finance hack, which deposited over ~$12.5m USDC into our confidential USDC wrapper contract. Back when they did, their address wasn't on any sanctions list and was not flagged by our KYT tools. However, a court order yesterday night placed a restraining order on various wallets linked to the hacker.
Since there wasn't much utility yet for the cUSDC wrapper, there were very little funds in it, and as a result the vast majority (>99%) of funds in the cUSDC contract came from that single hacker's deposit. Because of this, the court order asked to freeze our wrapper contract to freeze the hacker's fund.
So the sanction was not against Zama, or against privacy. It was a classic restraining order as we see often in DeFi, and we should have been notified so we could have taken the appropriate actions on our side.
I want to be very clear about something: our posture has always been compliant confidentiality, and we will not tolerate any illicit behavior in our protocol. It's also really useless for hackers to try to use Zama to hide their trail as we are precisely not a mixer and we do not obfuscate the sender and recipient, only balances and amounts. Eg you can see the hacker's cUSDC transactions here: eth.blockscout.com/address/0…
We are in touch with the various people involved to resolve the situation asap. In the meantime, we will pause the cUSDC, cUSDT and cWETH contracts until we have finished our investigation, identified all addresses linked to this case and taken appropriate action.
I will share a more detailed post-mortem and how we plan to deal with such requests in the future.
binoua retweeted
Congrats to the winners of @Zama Developer Program Mainnet Season 2. 👏
234 submissions across 3 tracks. 15 winners. Confidential finance, prediction markets, consumer apps, AI agent tooling were built on the Zama Protocol.
Thanks to everyone who participated. Let's take a look at what the community has built 🧵
binoua retweeted
Doing an AMA today with @eth_apple. We will talk about some big upcoming things for Zama and about our TokenOps acquisition !
nitter.cf/i/spaces/1yxBeMXzNAkJN
binoua retweeted
I am very excited to announce that @zama has acquired @TokenOps_xyz, a full-stack solution for token distribution and vesting that has been used to distribute over $2b so far. Here is why we made the deal and what it means for the Zama Protocol.
# The problem TokenOps is solving
When a company or foundation launches a token, they typically distribute a large portion to their team, early investors and treasury. The issue with doing this on public chains is that every allocation and wallet is visible to everyone. This is a lose-lose situation for everyone involved:
- long-term holders who believe in the project get penalized by bots who front-run token unlocks and push the price down
- team members become targets for hackers and criminals who use tools like Arkham to check how much they hold in their wallets. France alone had 60 kidnappings of crypto founders, employees and family members since the start of the year!
- early investors get flagged on social media and front-run by bots the instant they move tokens to exchanges, leading them to lose a lot of upside. And if investors don't make good returns, they'll imply stop investing and you won't anyone funding new projects in the future.
- treasuries and foundations cannot effectively manage their assets, and often have to split holdings across hundreds of wallets, creating massive operational overhead
TokenOps solves exactly this. By using the Zama Protocol, they enable token issuers to distribute, vest and manage allocations privately, while remaining fully onchain and self-custodial. Each team member and investor can have a single wallet receiving an encrypted amount of tokens. From the outside, you only see that the wallet received tokens and what the vesting terms are, but you no longer know the amount itself.
Beyond confidential distribution and vesting, we are also working on enabling confidential swaps directly within TokenOps, so that anyone receiving an allocation can buy and sell tokens seamlessly without anyone knowing the size or direction. This turns vesting from a static product into an active venue for OTC, treasury management and hedging on compliant rails.
And just like we used our own technology to run our token sale, we will of course use it to distribute allocations to our team and investors. In the coming months, we will shield the entire supply earmarked for team and investors, and distribute it through TokenOps' confidential onchain vesting contracts.
# How this benefits the Zama Protocol
1. it's a great use case of the technology, and it solves a real problem in the market that no transparent solution can address.
2. it creates extremely sticky TVS (Total Value Shielded) for the protocol. Whenever someone gets a vested allocation, they become a user of the Zama Protocol for the duration of their lockup, which is typically 2-4 years. That gives us 2-4 years to build utility for them so they never have to unshield their tokens and leave Zama.
3. it generates real revenue for the Zama Protocol. Every distribution, every claim, every confidential swap generates onchain fees, and all of these fees accrue directly to the protocol and are used to buy back and burn $ZAMA.
Over the next few months, we will turn TokenOps from a SaaS product into a fully onchain platform, owned entirely by the Zama Protocol. Anyone will be able to permissionlessly build on top of it and add confidential distribution and vesting features to their own apps.
If you plan to issue a token, take it for a spin at tokenops.xyz!
binoua retweeted
JUST IN 🧵
1/TokenOps is joining @zama, to roll out confidential and fully compliant token distributions, airdrops and vesting across public blockchains.
Public blockchains just became viable for institutional capital.
The future of onchain finance will not run on fully transparent infrastructure.
It requires programmable confidentiality at the protocol level. Zama is building the Confidential Protocol that makes public blockchains the default environment for sovereign and institutional capital.
Read the full announcement: zama.org/post/zama-acquires-…
binoua retweeted
I built a tiny free site where Janet (yes, the one from The Good Place) teaches the basics of online security through short interactive chats.
Passwords, phishing, scam texts, 2FA — bilingual French/English, no signup, no tracking.
Made for moms, friends, and you. 👇
janet.youngteam.net/
Zama is the HTTPS moment for blockchain. Execution is what makes it real.
Read the full details in the blog post ⬇️ zama.org/post/zama-protocol-…
binoua retweeted
Me in 2022: we need to encrypt the money onchain, its not safe to let people see how much money you have
People in 2022: nah, the only people who get mugged are influencers who show off their wealth on social
Today: 1 crypto-related kidnapping in France every 3 days, most of which are random people you never heard about.
Encrypt your money -> portfolio.zama.org
binoua retweeted
We're launching Shielded — Zama's quarterly institutional report covering confidential onchain finance. Each quarter, we'll share a comprehensive update on the @zama Protocol and our emerging ecosystem.
Most crypto projects don't publish quarterly reports. Fewer still do it with the rigor you'd expect from a finance-oriented industry. We think that needs to change — especially if we're asking institutions to trust us with trillions.
Q1 covers protocol adoption, TVS growth, the confidential token ecosystem, institutional use cases, and the infrastructure underpinning it all. We just wrapped a preview with partners, key stakeholders and builders ahead of the release.
The full report drops Thursday, April 30th.
→ Sign up to receive Shielded the moment it's live.
zama.org/shielded














