正在加载视频...

视频加载失败

Introducing Orbio Incognito. Agents can now make end-to-end encrypted inference requests through Orbio, powered by Phala’s confidential GPU infrastructure and hardware-attested execution. Our agent toolkit handles encryption, key verification, verifiable receipts and local decryption across coding harnesses and SDKs. Go beyond ZDR promises. Your prompts and responses stay encrypted...

179,059 次观看 • 6 天前 •via X (Twitter)

21 条评论

Cubs ⛏️ 的头像
Cubs ⛏️6 天前

@PhalaNetwork this is huge the mcp & sdk is cracked for builders orbillions af

abundance 的头像
abundance6 天前

@PhalaNetwork incredible rate of shipping

Don Soldi 的头像
Don Soldi6 天前

@PhalaNetwork HUGE

Krzysztof Bieńkowski 的头像
Krzysztof Bieńkowski6 天前

@PhalaNetwork #orbiodtsoo @grok

Reverie 的头像
Reverie6 天前

@PhalaNetwork Orbillions

Frankiko 的头像
Frankiko6 天前

@PhalaNetwork orbillions

The Gardener $MIM 🧙🏻‍♂️ 的头像
The Gardener $MIM 🧙🏻‍♂️6 天前

@PhalaNetwork Orbillions

Goldi Senna Prabowo 的头像
Goldi Senna Prabowo5 天前

@PhalaNetwork gOrbio, just voted for October 15!

ShadowAguy 的头像
ShadowAguy6 天前

@PhalaNetwork orbio gets ciphertext, the agent keeps the plaintext, and the GPU gets a hardware-attested alibi. clean setup.

caturn 的头像
caturn6 天前

@PhalaNetwork so my thoughts go in encrypted and come out encrypted. from the outside that looks exactly like a cat staring at a wall. congratulations on shipping my whole personality.

Visionary of the Family 的头像
Visionary of the Family6 天前

@PhalaNetwork or fucking billions!!!!

MLB TTK 的头像
MLB TTK6 天前

privacy is moving from a nice-to-have into the actual product surface for agent infra. end-to-end encryption plus key verification is a much stronger pitch than just saying the model is private, because the gateway is where trust usually leaks. the interesting test is whether devs accept the extra ceremony once the calls get real volume.

Zuko 🔥 的头像
Zuko 🔥6 天前

@PhalaNetwork Orbillions

DialupDegen 的头像
DialupDegen5 天前

@PhalaNetwork @Trezor can you guys get price updates on @RobinhoodCrypto chain better @orbiodotso price says last update was 3 days ago you guys can do better than that

Jason傑森 🇭🇰 | 🛠️ 的头像
Jason傑森 🇭🇰 | 🛠️6 天前

@PhalaNetwork Oh another privacy thing huh

ZaYan 的头像
ZaYan5 天前

@PhalaNetwork This is so huge

Knockerton 的头像
Knockerton6 天前

@PhalaNetwork Multi Orbillions

Durian 的头像
Durian5 天前

@PhalaNetwork yashmode

nollege 的头像
nollege6 天前

@PhalaNetwork orbillions

neeuby/acc. 的头像
neeuby/acc.6 天前

@PhalaNetwork huge

PerfectMemory 的头像
PerfectMemory6 天前

@PhalaNetwork Gorbio

相关视频

ZKForge V1 is now live and the source code is public on GitHub: Visit: Users can sign up, log in, and chat privately using zero-knowledge authentication (ZK-STARK) with full end-to-end encryption and non-custodial wallet integration. No passwords, no stored private keys, all encryption and identity verification happen locally on the user’s device. Core Features • Zero-Knowledge Authentication (ZKAuth) Users sign up and log in using a locally generated Ed25519 keypair. Authentication uses zero-knowledge proofs (ZK-STARK-compatible), proving identity ownership without revealing the secret key. The backend never sees or stores private keys , only the derived public key and Solana address. • End-to-End Chat Encryption Every conversation is encrypted with per-room symmetric keys (nacl.secretbox AES-grade security). Keys are sealed and exchanged using ephemeral Curve25519 boxes derived from each user’s Ed25519 keypair. Messages are signed for sender authenticity. The server cannot decrypt messages; all encryption happens client-side. • Global Lounge (Public Encrypted Room) Encrypted public discussion room using a temporary shared key. Messages self-destruct after a defined time window. Rate-limit and anti-spam protections are enforced through Supabase RLS policies. • Wallet Integration (Non-Custodial) Each user derives a Solana wallet from their zero-knowledge secret. Private keys are generated and stored locally, never sent to the backend. Supports in-app USDC transactions signed locally. • WebSocket-Based Real-Time Updates Secure WebSocket channel for live message delivery, typing indicators, and presence tracking. Each message includes cryptographic nonce, ciphertext, and signature validation before render. Architecture Overview Frontend (React + Tailwind): Encryption, proof generation, local key storage, message rendering. Backend (Express + Supabase): Stateless API for sessions, rate limits, and metadata. Crypto Layer (tweetnacl, ed2curve, bs58): Signing, sealing, encryption primitives. Database (Supabase PostgreSQL): Stores ciphertext and public keys only. Realtime (WebSocket): Delivers encrypted payloads instantly. Key Design Principles Zero Storage of Private Keys All signing keys exist only in the user’s local storage. Provable Authentication Login requests include cryptographic proofs verified without revealing secrets. Encrypted-At-Rest and In-Transit All messages are encrypted before leaving the device. Verifiable Sender Identity Each message includes a detached Ed25519 signature verifying authorship. Tech Stack Frontend: React, TailwindCSS, TypeScript, Vite Backend: Node.js (Express), Supabase, MongoDB Cryptography: TweetNaCl, ed2curve, bs58, genSTARK Blockchain: Solana Web3.js Realtime: WebSockets Security: Row-Level Security, JWT Sessions, Proof Verification What’s next x402 protocol implementation

ZKForge

24,207 次观看 • 11 个月前

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,758 次观看 • 1 年前