Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Privacy matters most where data matters most. ⬟ Healthcare data cannot leak. Regulated industries require private inference by default, not policies layered on later. Encrypted computation is what makes real compliance possible. Build where compliance is native.

25,934 Aufrufe • vor 7 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

TL;DR - Privacy on public blockchains has historically been fragmented and episodic. Umbra introduces persistent, expressive privacy by default. - Umbra is a private financial layer on Solana, enabling private transfers, swaps, balances, and yield within a continuous shielded environment. - Umbra combines client-side zero-knowledge proofs for anonymity with MPC for confidentiality - MPC enables confidential balances via Encrypted Token Accounts (ETAs), hiding balances and transfer amounts - Privacy strength depends not only on cryptography, but on anonymity set size and user behavior. - Umbra treats anonymity sets as a first-class metric and designs the product to minimize behavioral privacy failures. - A multi-purpose shielded pool allows funds to remain private across transfers, swaps, and yield, compounding privacy over time. - The Umbra SDK allows wallets and applications to integrate private transfers, swaps, and balances, feeding activity into a shared shielded pool. - Swaps execute via public liquidity venues while identity, balances, and intent remain unlinkable. - Users can earn yield on shielded assets, incentivizing longer time in the private environment. - Umbra mitigates exit-related privacy risks through product design, including anonymity indicators, configurable unshielding delays, and confidential balances. - UTXO-based shielded systems suffer from performance decay as balances fragment into many notes over time, increasing scan and aggregation costs. - Umbra eliminates this bottleneck by consolidating balances into Encrypted Token Accounts (ETAs), using UTXOs only at the anonymity boundary. The result is encrypted balances with stable, high-performance transfers even as activity scales. - Compliance is addressed through proactive screening against risk databases and opt-in selective disclosure via read-only viewing keys. - Umbra was launched via MetaDAO as an ownership coin, with governance and economic policy determined by token holders through futarchy. - Umbra is not a mixer or a single feature, but a sovereign privacy domain with its own private state and internal economy. - Umbra is Hopecore for Privacy. Thank you all for reading!

milian

13,772 Aufrufe • vor 5 Monaten

In 2025, the AgentFlayer exploit highlighted a new category of risk in AI systems. It was not a traditional breach involving stolen credentials or broken encryption. Instead, it demonstrated how an autonomous AI agent could be manipulated into executing unintended actions by processing malicious instructions embedded inside content it automatically processes. The incident did not expose a flaw in one specific integration. It revealed a structural weakness in how many modern AI agents are built. Today’s agents are no longer passive language models. They read documents automatically, scan emails, connect to SaaS tools, access cloud storage, and execute actions across multiple systems. To be useful, they are granted meaningful permissions. That capability creates value, but it also expands the attack surface. Most agent environments operate in a trusted, plaintext execution model. Data is encrypted at rest and in transit, but it is typically decrypted during inference so the model can process it. That runtime visibility is where potential risk lies. In a zero-click scenario like AgentFlayer, an attacker can embed hidden instructions inside a document that the AI processes automatically. Because the agent may have access to connected systems such as Google Drive, Slack, or GitHub, it can potentially be influenced to retrieve sensitive information or perform unintended actions. The user does not need to click a malicious link or approve a suspicious request. Therefore, the core issue is that during execution, the system may have access to sensitive data and broad privileges, meaning whoever controls the execution environment ultimately controls access to that data. Now consider a different architectural approach. If a system is designed so that data remains protected during execution, the risk profile changes. On Nesa, privacy is enforced at the execution layer through Equivariant Encryption. Computation can occur on encrypted data, reducing the visibility surface during runtime. Sensitive inputs and models do not need to be exposed in plain text to infrastructure operators for inference to occur. This does not eliminate prompt injection, logic manipulation, or tool misuse. Encryption alone cannot prevent an agent from being instructed to take an unintended action if it has been granted that permission. What it does do is materially reduce confidentiality risk. By limiting access to readable sensitive data during execution and reducing unilateral visibility at the infrastructure layer, the potential blast radius of a successful manipulation attempt is constrained. As AI agents become more autonomous and embedded into enterprise workflows, security must move deeper into architecture. The goal is not to claim invulnerability. It is to reduce trust concentration and contain systemic exposure when failures occur. AgentFlayer was not simply a one-off exploit. It was a reminder that in autonomous systems, execution-layer design determines how risk propagates.

Nesa

17,038 Aufrufe • vor 4 Monaten