To our Blackbit community:
We want to make it easier for you to get started. That’s why we’ve lowered our minimum spend from $100 to $50.
If you signed up but haven’t taken the next step, we’d love to welcome you back →
blackbit.sh/?utm_source=orga…
Yaser retweeted
Replying to @GergelyOrosz
Funny having the same name... 😆
btw if you don't want your code to train AI, just use the local mode on ORGN's IDE (The CDE), and choose TEE models specifically. You're welcome ;)
(Cloud mode does give you access to Intel TDX sandboxes though, worth exploring too)
Yaser retweeted
ORGN: Why TEE Matters for AI Coding
Encrypting code while it is stored is important.
Encrypting it while it is being sent over the internet is also important.
But there is still one moment where sensitive data can become exposed: while it is being processed.
This is where Trusted Execution Environments, or TEE, become important.
When an AI coding agent works on a repository, it may need access to source code, configuration files, internal documentation, credentials, or other sensitive information.
In a traditional cloud environment, that workload still depends heavily on trusting the infrastructure provider.
ORGN takes a different approach.
Its confidential environments are designed around hardware-based isolation, including Intel TDX, which creates protected virtual machines where workloads can run separately from the underlying host infrastructure.
The idea is simple:
Your code should remain protected even while the AI is actively working with it.
This matters because encryption at rest and encryption in transit only protect data before and after computation.
TEE focuses on the part in the middle.
The execution itself.
For developers, that means an AI agent can analyze code, run commands, modify files, or work inside a development environment without treating the entire cloud infrastructure as a trusted party.
But ORGN goes one step further.
TEE alone still leaves an important question:
How do you know the workload actually ran inside the protected environment you were promised?
That is where attestation comes in.
Hardware attestation provides cryptographic evidence about the environment where a workload was executed.
Instead of relying only on a provider saying:
“Your code was protected.”
Users can verify evidence tied to the actual execution environment.
This is especially important for companies working with proprietary code, regulated data, internal infrastructure, or systems where exposure could create serious security risks.
As AI agents gain more access to real production systems, the security model around them becomes just as important as the model itself.
The future of AI coding will not only be about how capable the agent is.
It will also be about where it runs, what it can access, and whether that environment can be verified.
That is the role TEE plays inside ORGN. @orgn_official
Yaser retweeted
We’re heading to SF for @stepconference.
AI is moving fast. Sensitive data and code should not have to move with it.
If you’re navigating privacy, security, or regulated data in AI, let’s talk 🤝
Yaser retweeted
If Mythos and Fable are sensitive enough to be export‑controlled and used by CISA to audit gov code, but a small team like ours can beat it on offensive cyber benchmarks in weeks at a fraction of the cost…
Maybe “frontier AI” is more narrative than scarcity.
We built a cyber-capable AI model that, based on benchmarking and real-world testing, is perhaps the most capable offensive-security LLM we have seen
It scores 95% on Cybench, solving 38/40 tasks
But benchmarks only go so far, so we pointed it at real systems
Through authorized programs, we tested it against a Fortune-500 technology company, a major global telecom, and leading Web3 protocols.
The result: a 100% success rate - it found a viable path into every authorized target in our test set.
It adapts, reasons, and finds routes that aren’t obvious, even in systems that already passed audits and security reviews.
If this holds at scale, most current security assumptions break.
Yaser retweeted
We built a cyber-capable AI model that, based on benchmarking and real-world testing, is perhaps the most capable offensive-security LLM we have seen
It scores 95% on Cybench, solving 38/40 tasks
But benchmarks only go so far, so we pointed it at real systems
Through authorized programs, we tested it against a Fortune-500 technology company, a major global telecom, and leading Web3 protocols.
The result: a 100% success rate - it found a viable path into every authorized target in our test set.
It adapts, reasons, and finds routes that aren’t obvious, even in systems that already passed audits and security reviews.
If this holds at scale, most current security assumptions break.
Yaser retweeted
Not all private AI is the same, so we make that distinction very clear.
When choosing your AI model in the IDE, you will see tags: ZDR or TEE
ZDR = Policy. The provider contractually commits to not retaining or train on your data.
TEE = Silicon. The model is deployed on Intel TDX & NVIDIA TEEs. Privacy is enforced by the hardware itself.
Yaser retweeted
We shipped cryptographic attestation before the AI IDE.
Most people would think it's backwards. The logical sequence would be to build the product first, then layer in the compliance later.
But we couldn't have retrofitted it later.
It had to be the foundation.
Yaser retweeted
POV: when they ask how it feels to build with ORGN while others still use Cursor.
@orgn_official @blackbit
Yaser retweeted
Introducing Origin: The world's first confidential dev environment
After months in stealth, Origin is live! Now, devs never have to choose between building and security.
Enterprise-grade encryption keeps your IP safe from start to finish
Origin scales from startup to enterprise, so you can innovate without limits
Join the confidential coding revolution at orgn.com/
Build Everything. Expose Nothing.
#Origin #ConfidentialCoding
Yaser retweeted
We've been building something big behind closed doors.
Tomorrow, we reveal it.
Introducing ORGN, the world's first confidential coding platform.
Your code stays yours. Always.
Build Everything. Expose Nothing.
→ orgn.com
#ORGN #ConfidentialCoding
Yaser retweeted
Certificates don't protect your code
ORGN is different:
• Confidential compute for total code isolation
• Cryptographic proof your code ran in isolation
• No retention or cross-use of your IP
Build Everything, Expose Nothing.
Yaser retweeted
Just created a complete analysis of AI infrastructure opportunities covering chip manufacturers, power companies and system integrators.
I shared this analysis with my 20,000+ students.
For 24 hours, it's yours for FREE.
Like, RT & Comment "AI" and I'll DM it to you.
Yaser retweeted
Announcement: Today the Bitwise Bitcoin ETF (BITB) becomes the first U.S. bitcoin ETF to publish the bitcoin addresses of its holdings.
Now anyone can verify BITB's holdings and flows directly on the blockchain.
Onchain transparency is core to Bitcoin's ethos. We're proud to walk the walk with BITB.
[BITB disclosures & prospectus: bitbetf.com/welcome]


![The AI Cyber Defence Readiness Index [ a global wake-up call ]](https://pbs.twimg.com/media/HVdf-J3XcAEfzvR.jpg)

















