Coin Alerts

SCRT news archive

464 stories

Last checked

Refresh

Estimated news impact scores by coin. Scores are not price-change percentages.

Newest first

Check failed. Showing saved news from .

  6. Published Social post

    Secret Network (@SecretNetwork)

    Open systems still need space for private participation. From DeFi strategies and governance decisions to sensitive AI context, users should be able to act without becoming observable by default. Secret continues to build the infrastructure that makes this possible.

  8. Published Social post

    Secret Network (@SecretNetwork)

    Secret Joins Forces with Arbitrum, and $SCRT is moving to Arbitrum Six years ago, Secret released privacy-preserving smart contracts on mainnet, before "confidential compute" was even a thing. Secret was right early. Today we're making the move to be right at scale. $SCRT is joining forces with Arbitrum, one of the largest, most active ecosystems in Ethereum: deep liquidity, tooling, wallet and exchange support, and thousands of builders composing with one another, available from day one. Arbitrum has welcomed Secret and is ready to support the migration and SCRT's growth. This is a move toward where the world is going. As AI pushes more computation into closed systems run by a handful of companies, one question keeps getting louder: who gets to compute on private data, and on whose terms? Confidential AI and verifiable, secure off-chain compute is the frontier, and it's where Secret is heading. Teams on Arbitrum are already shipping AI agents, inference markets, and verifiable compute - the exact stack Secret is built for. Mark the date: September 1, 2026. A one-time snapshot of SCRT balances will be taken, and a new ERC-20 SCRT will be issued on Arbitrum. The snapshot includes native SCRT and staked SCRT (including unbonding that’s currently in-progress). Staked SCRT carries over as-is, so if you're staked, you don't need to do anything. It does not include sSCRT, SCRT in contracts or liquidity pools, SCRT bridged to other chains, or IBC-bridged tokens. Eligibility is set entirely by the snapshot. If you hold SCRT in any of those forms, convert it back to native or staked SCRT before September 1, or it can't be claimed later. Also, move IBC tokens back to their native chains before the date. After the snapshot, the SCRT contract suite goes live on Arbitrum. You claim by proving your balance against the Redeemer's Merkle root, nothing to deposit first, every claim verifiable, and no deadline. SCRT remains the governance token. We're proposing one change now, cutting inflation from 9% to 5%, and keeping the rest simple, with further refinements open to community governance later. After the migration, SCRT Labs will officially stop maintaining the Secret Network and will release all the code under a permissive license. This is a proposal, not a decision. It goes to a community governance vote, with a signaling proposal on-chain soon. Secret built something real, ahead of its time. The story continues on Arbitrum. Full announcement: [LINK]

  11. Published Social post

    The Block (@TheBlockCo)

    Secret Network’s Axelar bridge drained for $4.67 million in infinite-mint exploit that went unnoticed for seven days https://www.theblock.co/post/405459/secret-networks-axelar-bridge-drained-for-4-67-million-in-infinite-mint-exploit-that-went-unnoticed-for-seven-days?utm_source=twitter&utm_medium=social

  12. Published Social post

    GoPlus Security 🚦 (@GoPlusSecurity)

    🚨 Security Alert: An attacker exploited an infinite mint vulnerability in a modified CW20-ICS20 token contract (secret1yxj...) on Secret Network, stealing approximately $4.67 million worth of assets from Axelar. Three transactions involving WETH, USDT, and WBTC were bridged into Axelar Network. The attacker subsequently transferred the stolen assets to #ETH. The exploit occurred on June 10, while Axelar and Secret publicly disclosed the incident to the community on June 19. Attacker Addresses: https://mintscan.io/axelar/address/axelar1hzra9z4zn8q0w8f3dj2wnw0xgetu8dfdhl6ad8 https://etherscan.io/address/0x6c2eAB82bA2897A6E99FB6Af018020dA15123976 Vulnerable Contract: https://mintscan.io/secret/address/secret1yxjmepvyl2c25vnt53cr2dpn8amknwausxee83 Example Exploit Transactions: https://mintscan.io/axelar/tx/C6F4F590B36EFF5FDCDE8996D9270AC3EE2DA243A3AC88E0F152FC074F9EB0FB?height=29841952 https://mintscan.io/axelar/tx/0072DE8548F12CC530A73B69FB494B690FDD4D7EFC5988236B07C1C354AC4E54?height=29842118 https://mintscan.io/axelar/tx/9DE90F7B5EE221351F4842FBEFC3F6B0A291C1EED846693BD3FC38730EB45AD1?height=29842126 Ethereum Receiving Transactions: https://etherscan.io/tx/0x3513509c71bc8e02695fad55e136b8f21933f6a4433f4dafe471800d98ca8e05 https://etherscan.io/tx/0xe49353d3a2b87d2f8ffaea85f26452d379ab186542b0bfeb552d5659efdf8967 https://etherscan.io/tx/0xde42dd558e9ccd70978c20529afacf0a94565d04aa798d1e38c32b4959d73343

  13. Published Social post

    GoPlus Security 🚦 (@GoPlusSecurity)

    🚨 Security Alert: An attacker exploited an infinite mint vulnerability in a modified CW20-ICS20 token contract (secret1yxj...) on Secret Network, stealing approximately $4.67 million worth of assets from Axelar. Three transactions involving WETH, USDT, and WBTC were bridged into Axelar Network. The attacker subsequently transferred the stolen assets to #ETH. The exploit occurred on June 10, while Axelar and Secret publicly disclosed the incident to the community on June 19. Attacker Addresses: https://mintscan.io/axelar/address/axelar1hzra9z4zn8q0w8f3dj2wnw0xgetu8dfdhl6ad8 https://etherscan.io/address/0x6c2eAB82bA2897A6E99FB6Af018020dA15123976 Vulnerable Contract: https://mintscan.io/secret/address/secret1yxjmepvyl2c25vnt53cr2dpn8amknwausxee83 Example Exploit Transactions: https://mintscan.io/axelar/tx/C6F4F590B36EFF5FDCDE8996D9270AC3EE2DA243A3AC88E0F152FC074F9EB0FB?height=29841952 https://mintscan.io/axelar/tx/0072DE8548F12CC530A73B69FB494B690FDD4D7EFC5988236B07C1C354AC4E54?height=29842118 https://mintscan.io/axelar/tx/9DE90F7B5EE221351F4842FBEFC3F6B0A291C1EED846693BD3FC38730EB45AD1?height=29842126 Ethereum Receiving Transactions: https://etherscan.io/tx/0x3513509c71bc8e02695fad55e136b8f21933f6a4433f4dafe471800d98ca8e05 https://etherscan.io/tx/0xe49353d3a2b87d2f8ffaea85f26452d379ab186542b0bfeb552d5659efdf8967 https://etherscan.io/tx/0xde42dd558e9ccd70978c20529afacf0a94565d04aa798d1e38c32b4959d73343

  14. Published Social post

    Axelar Network (@axelar)

    Secret Network incident analysis by @CommonPrefix. Axelar's protocol was not compromised and prevented contagion from spreading to other chains. Here's the full report: https://commonprefix.com/blog/secret-network-exploit

  15. Published Social post

    CoinDesk (@CoinDesk)

    JUST IN: @Axelar discloses a $4.67M exploit targeting assets bridged to Secret Network, with the vulnerability isolated to a Secret-side smart contract. Both connections have been disabled.

  16. Published Social post

    Secret Network (@SecretNetwork)

    We have identified an incident affecting assets bridged over IBC to Secret Network from the Axelar chain, with approximately $4.67M worth of tokens taken. Based on current information, the issue is isolated to the Secret-side ICS-20 smart contract of the Cosmos IBC connection between Secret and Axelar, used for assets bridged from Axelar to Secret. Immediately upon becoming aware of the incident, the Axelar emergency committee has disabled the Secret and Secret-SNIP connections. We're reaching out to the relevant exchanges and law enforcement agencies. The incident is isolated to assets on Secret bridged over IBC from Axelar. No other IBC connections or Secret tokens appear impacted. No other Axelar integrations are affected. Axelar’s core protocol is not affected. We're preparing a detailed post-mortem.

  17. Published Social post

    Axelar Network (@axelar)

    We have identified an incident affecting assets bridged over IBC to Secret Network from the Axelar chain, with approximately $4.67M worth of tokens taken. Based on current information, the issue is isolated to the Secret-side ICS-20 smart contract of the Cosmos IBC connection between Secret and Axelar, used for assets bridged from Axelar to Secret. Immediately upon becoming aware of the incident, the Axelar emegency committee has disabled the Secret and Secret-SNIP connections. We're reaching out to the relevant exchanges and law enforcement agencies. The incident is isolated to assets on Secret bridged over IBC from Axelar. No other IBC connections or Secret tokens appear impacted. No other Axelar integrations are affected. Axelar’s core protocol is not affected. We're preparing a detailed post-mortem.

  18. Published Social post

    Secret Network (@SecretNetwork)

    We have identified an incident affecting assets bridged over IBC to Secret Network from the Axelar chain, with approximately $4.67M worth of tokens taken. Based on current information, the issue is isolated to the Secret-side ICS-20 smart contract of the Cosmos IBC connection between Secret and Axelar, used for assets bridged from Axelar to Secret. Immediately upon becoming aware of the incident, the Axelar emegency committee has disabled the Secret and Secret-SNIP connections. We're reaching out to the relevant exchanges and law enforcement agencies. The incident is isolated to assets on Secret bridged over IBC from Axelar. No other IBC connections or Secret tokens appear impacted. No other Axelar integrations are affected. Axelar’s core protocol is not affected. We're preparing a detailed post-mortem.

  19. Published Social post

    Secret Network (@SecretNetwork)

    This is how privacy becomes standard in DeFi. @TopazDex and SilentSwap are integrating private swaps directly into the trading flow, maintaining self-custody and keeping user activity private and out of public view. More private rails. Better execution. Strong partnership.

  20. Published Social post

    Secret Network (@SecretNetwork)

    DeFi expanded quickly, and surveillance expanded with it. Wallet clustering, copy trading, and automated extraction have made public activity easy to profile and exploit. Private execution changes that by keeping sensitive details out of view, making DeFi more viable for serious capital and more usable for everyone.

  21. Published Social post

    Secret Network (@SecretNetwork)

    Secret Network and PardnaFi Collaborate to Bring Confidential Computing to Digital ROSCA Infra... Secret Network, the leading provider of decentralized confidential computing, today announced a collaboration with @PardnaFi, a community-finance infrastructure platform digitising traditional ROSCAs, known across different communities as Pardna, Susu, Stokvel, Ajo, and Committee. Through this collaboration, PardnaFi is integrating SecretVM to explore privacy-preserving partner APIs, confidential orchestration workflows, and secure community-finance infrastructure for digital savings circles. Traditional ROSCAs have long helped communities save collectively, build financial discipline, and access capital through trusted group-based contribution systems. However, many of these savings circles are still managed through WhatsApp groups, spreadsheets, informal ledgers, and manual administration. This creates challenges around transparency, contribution tracking, payout coordination, privacy, trust, and auditability. PardnaFi is building a secure, non-custodial infrastructure that allows partner organisations to embed savings-circle functionality directly into their own products. This includes circle creation, contribution schedules, payout coordination, member status tracking, and operational event records. Contribution and payout events can be anchored on-chain to create a tamper-evident operational history, while customer funds remain outside PardnaFi custody. By integrating with SecretVM, PardnaFi is exploring how confidential computing can support sensitive community-finance workflows without exposing unnecessary participant data. ROSCA activity can include personal contribution behaviour, missed payments, payout order, group participation, and other sensitive financial signals. SecretVM provides a confidential computing layer that can help protect this operational data while enabling verifiable execution and stronger trust between partners, communities, and infrastructure providers. The current PardnaFi integration runs a Partner API sandbox inside a TDX-based confidential virtual machine. This sandbox demonstrates signed partner access, controlled sandbox writes, contract-backed orchestration flows, and privacy-preserving API execution without exposing production data or enabling live settlement authority. Through this integration, PardnaFi is validating several key capabilities: Confidential Partner API Runtime: Partner API requests can be processed inside a confidential computing environment, helping protect sensitive operational data from the underlying infrastructure. Signed Request Validation: Partner requests are authenticated using HMAC-signed access, supporting stronger controls for partner-facing integrations. Replay Protection: The sandbox validates request freshness and replay resistance, helping prevent repeated or unauthorized request execution. Controlled Orchestration Flows: PardnaFi can test contract-backed orchestration routes, controlled write operations, and partner workflow execution in a secure sandbox environment. Sanitized Logging: The integration is designed to prevent secret material from being exposed in logs, supporting safer operational visibility. Evidence-Based Validation: Signed reads, controlled writes, authentication failures, idempotency, and blocked routes have been tested to support auditability and runtime confidence. PardnaFi has already completed several technical milestones across its Partner API, confidential computing, and smart contract orchestration architecture. These include deploying and validating the SecretVM confidential computing integration, implementing signed request authentication and replay protection, completing controlled write orchestration flows, developing its Partner API sandbox, and establishing OpenAPI governance. PardnaFi also completed automated OpenAPI security and validation analysis using Crush42, achieving a 100/100 assessment score across documented review categories, with findings and remediation history traceable through the project's commit history. The integration is currently operating in a controlled sandbox environment. It does not execute live settlement, payouts, contributions, staking, payment rails, treasury movement, DAO actions, or production smart contract mutation. Instead, the purpose of the integration is to prove that PardnaFi can expose secure partner API functionality through Secret Network’s confidential computing layer before progressing toward production-grade partner access for digital ROSCA workflows. “Our mission with PardnaFi is to bring trusted community finance into the digital age without losing the privacy, discipline, and social trust that make traditional savings circles so powerful,” said Adrian Cross, Founder and CTO of PardnaFi. “ROSCAs have helped communities access capital for generations, but the infrastructure behind them has not kept pace. By integrating SecretVM, we can begin building partner-facing systems where sensitive contribution activity, payout coordination, and operational workflows are handled inside a confidential and verifiable environment. This gives us a strong foundation to support fintechs, credit unions, and community organisations as they bring secure digital ROSCAs to more people.” “PardnaFi is a powerful example of how confidential computing can support real-world community finance,” said Luke Bowman, COO of Secret Network. “Traditional savings circles depend on trust, coordination, and privacy. By bringing these workflows into a confidential and verifiable digital environment, PardnaFi is helping create infrastructure that can serve fintechs, credit unions, and community organisations while protecting sensitive participant data.” Looking ahead, PardnaFi is focused on onboarding ecosystem partners, strengthening privacy-preserving community-finance infrastructure, and expanding the capabilities of its digital ROSCA workflows. The team is also exploring future use cases across Secret AI, including LLM-powered financial education, better savings decisions, and community-based financial coordination. Together, Secret Network and PardnaFi are advancing a new model for privacy-preserving community finance, where traditional savings circles can become more transparent, efficient, auditable, and secure without compromising the privacy of the people who rely on them. About Secret Network Secret Network is a decentralized network of nodes that utilize Trusted Execution Environments, or TEEs, to enable confidential computing. As the privacy hub of Web3, Secret Network provides infrastructure for private smart contracts, encrypted data transfer, confidential applications, and verifiable execution across decentralized systems. scrt.network About PardnaFi PardnaFi is a community-finance infrastructure platform digitising traditional ROSCAs, known across communities as Pardna, Susu, Stokvel, Ajo, and Committee. The platform enables partner organisations to embed savings-circle functionality into their own products, including circle creation, contribution schedules, payout coordination, member status, and operational event tracking. PardnaFi is building secure, non-custodial infrastructure for trusted digital ROSCAs, with a focus on privacy, transparency, auditability, and operational efficiency. www.pardnafi.com

  22. Published Social post

    Secret Network (@SecretNetwork)

    People care about privacy. They just choose convenience first. @AnewbiZ007 says that balance is starting to shift as users see the risks of exposed data, transparent ledgers, and real-world targeting. Privacy is becoming a security priority again.

  23. Published Social post

    Secret Network (@SecretNetwork)

    It has the right ingredients: privacy people can actually use, self-custody that does not bend, and cross-chain utility tied to real flows like swaps, payments, invoicing, and payroll. That combination gives SilentSwap a real shot at becoming the privacy standard this market has been waiting for.

  24. Published Social post

    Secret Network (@SecretNetwork)

    Good news for traders, and better news for privacy. @SilentSwap going live on @TopazDex puts non-custodial privacy directly into the trading flow, where it belongs. This is how privacy expands: not as a niche feature, but as a standard part of execution.

  25. Published Social post

    Secret Network (@SecretNetwork)

    Secret Network Ecosystem Update: May 2026 Greetings, Secret Community! This article captures all the key developments in the Secret Network ecosystem for May 2026. Secret AI / SecretVM Weekly Highlight: secretvm-verify In this edition of SecretAI / SecretVM Weekly Highlight, Secret introduces secretvm-verify, an open-source SDK that enables cryptographic verification across the full confidential computing stack, supporting Intel TDX, AMD SEV-SNP, NVIDIA GPU attestations, SecretVM bindings, and ERC-8004 trustless agents. This software development kit (SDK) allows developers and users to independently verify workloads, TLS bindings, and end-to-end VM integrity before trust is established. A major advancement for confidential AI infrastructure, secretvm-verify strengthens trustless verification by making confidential workloads, autonomous agents, and compute environments provably authentic and independently auditable by default. NVIDIA GPUs are verified via NVIDIA Remote Attestation Service, and the SDK is fully open source for complete auditability on GitHub: https://github.com/scrtlabs/secretvm-verify Read more here. Secret and Corbits Launch $20K Compute Credit Campaign for Confidential AI Commerce Secret and @corbitsdev launched a builder campaign offering up to $20,000 in compute credits for selected teams deploying on SecretVM and Secret AI. The initiative enables developers to build private, verifiable, and pay-per-request AI services using confidential computing and agentic commerce. It advances infrastructure where AI agents securely discover, verify, and autonomously pay for services. The campaign focuses on enabling builders to use SecretVM and/or SecretAI to add verifiability and privacy to their existing Faremeter APIs or use them in new ways. Read more here. SecretAI / SecretVM Weekly Highlight: SecretVM Clusters In this edition of SecretAI / SecretVM Weekly Highlight, Secret introduces SecretVM Clusters alongside the new SecretVM Agent Skill, an infrastructure that enables autonomous agents to create and manage confidential infrastructure directly. With support for spinning up isolated SecretVMs, deploying workloads through docker-compose, and managing instances without human intervention, agents can now operate with fully self-sovereign confidential compute. Read more here. SilentSwap Graduates from YZiLabs EASY Residency S3 @SilentSwap has officially graduated from @yzilabs EASY Residency S3, marking a key milestone in its journey to building privacy-first cross-chain infrastructure. Over the past 10 weeks, the team refined a non-custodial swap system designed for fast, decentralized, and compliant cross-chain execution without sacrificing user control. SilentSwap will present at YZi Labs Demo Day in San Francisco, continuing its mission to make privacy a native part of crypto UX. Article on YZiLabs EASY Residency S3 here. SCRT Labs Integrates Intel® Trust Authority Into SecretVM @scrt_labs has integrated Intel® Trust Authority directly into every SecretVM, making hardware-backed attestation available by default. Developers can now prove workloads are running inside genuine Intel TDX environments with Intel-signed verification, TLS-bound attestation, and customizable policies. This unlocks stronger trust for confidential AI, finance, healthcare, and regulated applications where security must be independently verified. Read the full article here. Private AI agents that do not leak prompts, tools, or intermediate state: a builder blueprint -Article Private AI agents are moving beyond model privacy to full execution privacy. As they handle sensitive workflows, protection must cover prompts, retrieval, tool calls, secrets, logs, and intermediate state. Most systems leak through Retrieval-Augmented Generation (RAG), shared runtimes, and exposed credentials. Real privacy requires confidential execution in TEEs like SecretVM, where workloads run without host inspection. Prompts and agent state must be treated as sensitive data, while tools and retrieval remain permissioned and sealed. Secrets should only be released after attestation. With workload verification and code provenance, trust becomes provable. The goal is end-to-end confidential, verifiable AI infrastructure. Read the full Article here. Secret X space with Beldex: Building Privacy Infrastructure Luke B, Chief of Operations (COO) at Secret Network Foundation, explored the growing importance of privacy in Web3, sparked by rising data breaches like GitHub’s recent hack, with Beldex. He highlighted the gap between privacy awareness and adoption, driven by convenience over security. Secret is focused on addressing privacy breaches through privacy-preserving smart contracts, encrypting computation, not just transactions, and has expanded into cross-chain privacy and confidential AI inference via Secret AI. Secret is open to integrating with other projects already building any privacy tech out there. The need to give great user experience surpasses competition. Listen to the full space recordings here. SecretAI / SecretVM Weekly Highlight: SecretVM Skill for Agents In this edition of SecretAI / SecretVM Weekly Highlight, Secret introduces the SecretVM Agent Skill, a new capability that allows AI agents to directly create, deploy, and manage confidential virtual machines without human intervention. SecretVM Skill enables agents to spin up SecretVMs, deploy workloads via docker-compose, and control infrastructure lifecycles and end-to-end encryption. This is a key step toward self-sovereign AI, unlocking autonomous agents that own, manage, and securely execute workloads on confidential infrastructure. Go to secretai.scrtlabs.com to get started Read the full article: here. SilentSwap Rank #4 on BNBCHAIN DappBay in May SilentSwap ranked #4 on BNB Chain DappBay in May, recording 362.56K total transactions and 120.07K total users. As a privacy-focused cross-chain aggregator, SilentSwap is designed to give users full control of their assets while adding a layer of privacy to every transaction. It is fully non-custodial, trustless, and decentralized, with a routing system that analyzes liquidity across multiple networks and constructs optimal execution paths without exposing user-level metadata. Try Now Check out this article: BNB Chain Understands What Crypto Needs Next SecretAI / SecretVM Weekly Highlight: SecretVM on Google Cloud In this edition of SecretAI / SecretVM Weekly Highlight, Secret expands SecretVM to Google Cloud, enabling developers to deploy Intel TDX confidential VMs on Google’s infrastructure while maintaining the same attestation, privacy, and verification guarantees. With a unified deployment workflow across bare-metal and cloud environments, teams gain greater flexibility without sacrificing confidentiality. With this, enterprises can easily adopt cloud confidential computing using SecretVM on Google Cloud, combining hyperscaler scalability and accessibility with independently verifiable private compute. Start here: https://secretai.scrtlabs.com/ Read more here. Secret listed among Major Privacy Token Categories Zord Crypt Zord Crypt, a Web3 enthusiast and researcher on AI, DeFi, and RWA, listed Secret and others as major programmable privacy chains in the article Major Privacy Token Categories. Secret is proactive in bringing confidential computation to smart contracts, DeFi, AI, and decentralized applications through encrypted computation and TEE infrastructure. Read the full article here. May 2026 marked continued progress for the Secret Network ecosystem, driven by advances in confidential computing and autonomous AI infrastructure, including the launch of secretvm-verify, Intel® Trust Authority integration across SecretVM, and new agent capabilities for deploying and managing confidential workloads. SilentSwap expanded adoption by graduating from YZiLabs EASY Residency S3 and ranking #4 on BNB Chain DappBay with over 362K transactions and 120K users, further reinforcing Secret Network’s role in privacy-first Web3 infrastructure. Stay tuned for more developments on Secret Network in 2026.

  27. Published Social post

    Secret Network (@SecretNetwork)

    Private AI agents that do not leak prompts, tools, or intermediate state: a builder blueprint AI agents are moving from demos into systems that touch money, customer data, internal knowledge, and operational workflows. That changes what builders need to protect. It is not just the final output anymore. It is the prompt. The retrieved context. The tool calls. The API keys. The reasoning steps that become intermediate state. The logs. The workload itself. If any of that leaks, the agent is not private in any meaningful sense. A private AI agent has to protect the full execution path. That is the blueprint. 1. Start with the right threat model Most agent stacks leak in predictable places. The prompt gets sent to a third-party model endpoint. Retrieved documents are exposed through a RAG layer. Tool calls reveal internal systems and account structure. Logs capture raw prompts, responses, and secrets. Intermediate state sits in a shared runtime. Credentials are injected into machines that have not proven what they are running. The result is a system that may look polished on the surface but exposes sensitive data at every step. Builders need to think beyond model privacy. The real question is whether the whole agent pipeline is private and verifiable from end to end. 2. Isolate execution Agents handling sensitive tasks should not rely on shared infrastructure by default. They should run inside isolated environments where the host cannot inspect memory, prompts, or internal state. That is where confidential VMs matter. SecretVM gives builders a way to run general workloads inside TEE-backed Confidential VMs. That means the agent runtime, tools, orchestration layer, and supporting services can execute inside a protected environment instead of on a public, inspectable host. This is the difference between private AI as a feature and private AI as infrastructure. 3. Treat prompts and intermediate state as sensitive data A lot of teams focus on protecting training data or final outputs while ignoring the live execution path. That is a mistake. Prompts often contain user intent, business logic, internal instructions, and sensitive records. Intermediate state may include chain-of-thought-like scaffolding, planning context, partial tool outputs, memory summaries, and system decisions. Those artifacts can reveal just as much as the final answer. If the runtime leaks them through logs, metrics, dashboards, or tool responses, privacy is already broken. Builders should assume that prompts and transient agent state need the same protection level as the source data itself. 4. Protect retrieval, not just generation RAG systems create a new privacy surface. If retrieval outputs are visible to the wrong user, sensitive data can leak long before the model produces a final response. That means private agents need controlled retrieval paths, permission-aware document access, and confidential execution for the part of the stack that handles context assembly. A private agent is not just a private model call. It is a private retrieval pipeline, a private tool layer, and a private execution environment. 5. Make tool use confidential Agents are useful because they act. They query databases. Call internal APIs. Sign transactions. Move funds. Access tickets, CRMs, and knowledge bases. Trigger workflows. That means the tool layer becomes one of the highest-risk parts of the stack. If tool inputs and outputs are exposed, the agent leaks business logic and operational state even if the model itself is private. Builders need to run the tool orchestration layer inside confidential compute, keep credentials protected, and scope access tightly. Private agents require private tool use. 6. Release secrets only to verified workloads This is one of the most important design rules. Do not hand API keys, passwords, mnemonics, or database credentials to a workload just because it requests them. Only release secrets after the machine proves what it is. That is the role of attestation-bound key management. In SecretVM, a workload can prove its identity and measured environment, and only then receive secrets from a key management layer. This gives builders a way to keep sensitive material outside the VM until the workload is verified. For private agents, this matters because tools, memory systems, external services, and payment flows all depend on credentials. If those credentials are released without verification, the rest of the privacy model collapses. 7. Reduce observability leaks Observability is necessary. Data leakage through observability is optional. Private agents still need logs, metrics, and resource monitoring. But those surfaces should be designed so they do not become exfiltration channels for prompts, retrieved documents, or internal state. That means controlled access to logs. Privacy modes for sensitive environments. Clear separation between operational telemetry and application data. The option to disable public informational endpoints when full privacy is required. This is where builders need discipline. The easiest way to break a private system is to expose it through convenience tooling. 8. Make workloads verifiable Privacy without verifiability leaves users with a black box. That is not enough for agents that hold secrets, access tools, or perform actions on behalf of users. Builders need a way to prove what code is running. Attestation gives that proof. Workload verification makes it usable. Code provenance connects the deployed workload back to source, build process, and pinned image artifacts. This matters because users will increasingly ask the same questions: What code is this agent running? Did it change? Can I verify the workload before giving it access to my data or funds? Can I audit the deployment path from source to execution? If the answer is no, trust remains informal. If the answer is yes, the agent becomes inspectable infrastructure. 9. Plan for upgrades without losing trust Real agents evolve. You patch bugs. Update tools. Improve prompts. Swap models. Change dependencies. The problem is that upgrades can weaken trust unless users can see what changed and verify the new state. Builders need upgrade paths that preserve confidentiality while exposing enough history and attestation data for users to validate the change. The goal is not to freeze the system forever. The goal is to let it improve without turning verification into guesswork. 10. Design for agent autonomy carefully A serious agent stack should eventually be able to manage its own infrastructure. Spin up an isolated VM for a task. Deploy a workload. Use secrets only after attestation. Run privately. Tear itself down when the job is complete. This model is much safer than keeping long-lived sensitive workflows on shared infrastructure. It also maps well to how agents will operate in production: task-specific, scoped, verifiable, and disposable when needed. Private agents should own their execution environment, not borrow it blindly. 11. Keep the builder path practical A blueprint only matters if teams can actually use it. That means developers need clear deployment flows, templates, SDKs, CLI support, verification tools, and billing that works in production. Private infrastructure should not require heroic effort just to ship a basic workload. If private AI is going to become normal, the developer path has to be straightforward: sign up configure resources deploy a confidential workload verify it connect tools manage secrets monitor safely scale when needed That is how private agents move from concept to product. 12. What users will expect next Today, many users still accept agent systems that operate as opaque services. That will not last. Users will demand stronger guarantees around prompts, tool use, memory, and execution. Enterprises will ask where data flows and who can inspect it. Security teams will ask how secrets are released. Developers will ask how to verify workloads. Partners will ask how to audit the stack without exposing the data. The systems that can answer those questions with proofs will be the ones that earn trust. The blueprint in one line A private AI agent protects prompts, retrieval, tools, secrets, logs, and intermediate state inside a confidential and verifiable runtime. That is the standard builders should be aiming for. Not private at one layer. Private through the full execution path. That is what SecretAI and SecretVM are built for. Build here: https://secretai.scrtlabs.com/

  28. Published Social post

    Secret Network (@SecretNetwork)

    Verification by Default: SCRT Labs Integrates Intel® Trust Authority Into Every SecretVM Confidential computing has spent the last decade solving a hard problem: helping keep data protected even while it's actively being used. With Intel TDX and hardware-enforced execution environments, that battle is largely won. The harder, and ultimately more important question is the one that follows: how does the party relying on a confidential workload verify independently, without taking anyone's word for it, that the workload is actually running where it's supposed to, on hardware in the state it's supposed to be in? That is the question Intel Trust Authority answers. As of today, it's a built-in capability of every SecretVM. What's actually shipping SCRT Labs has integrated @intel Trust Authority (ITA) directly into the SecretVM platform. The integration has three properties worth highlighting, because together they define the developer experience: Attestation is on by default. Every SecretVM now exposes an /ita_jwt endpoint that returns an Intel-signed attestation token on demand. There is no separate sign-up flow, no API key to provision, no SDK to integrate. SCRT Labs ships its own ITA credentials and a Secret-defined appraisal policy bundled into the platform, so the simplest possible flow works immediately, with nothing for the developer to configure. Boot a SecretVM, fetch the token, verify it. That is it. Custom policies are a one-field addition. Operators who want their VMs attested against their own ITA accounts and policies can add API keys directly in the SecretVM configuration. The endpoint then issues tokens against each configured policy, returned as an array. Relying parties can verify against multiple independent appraisals at once, a layered defense model that maps cleanly onto regulated workloads where multiple parties (operator, auditor, customer) each need their own verification path. Tokens are bound to the TLS connection. The report_data field of each attestation token carries the fingerprint of the SecretVM's TLS certificate. A relying party that fetches a token over TLS and checks the binding has strong assurance that the channel they are talking on terminates inside the attested VM, not merely that a genuine TDX VM exists somewhere on the network. . This is designed to mitigate a category of impersonation and proxying attacks that bare attestation flows leave open. Why independent appraisal matters The shift Intel Trust Authority enables is subtle but consequential. In a conventional cloud confidential-computing setup, the same provider that hosts a workload also signs the documents asserting that the workload is genuine. The math works, but the trust model concentrates a great deal of authority in one party. ITA decouples those roles: Intel itself is the appraiser, the host is only the host, and the relying party receives a token signed by an independent third party with no operational stake in the workload. This matches a principle that has guided Secret Network from its earliest days: verification should not require trusting the operator. Embedding ITA as a default capability of SecretVM, rather than gating it behind an enterprise tier, extends that principle to every developer building on the platform. Where this unlocks new workloads Several categories of work need exactly this kind of independent, hardware-rooted verification before they can move into shared infrastructure. Confidential AI inference. Users of hosted models, particularly proprietary or sensitive ones, can verify that the node serving their requests is the genuine TEE it claims to be, with prompts and weights designed to help prevent operator access. This is foundational for the trusted-inference services that are now becoming a category in their own right, including the confidential model hosting SCRT Labs is building on top of SecretVM. Financial services. Trade execution, market-data clean rooms, cross-institutional settlement, model-driven risk and compliance, anywhere competing parties need to share computation without sharing data, attestation that auditors and counterparties can verify themselves replaces an awkward chain of contractual assurances. Healthcare and life sciences. Multi-party clinical research, federated training on patient data across institutions, and processing of PHI under HIPAA, GDPR, and equivalent regimes all benefit from being able to demonstrate, with hardware-backed cryptographic evidence, that processing occurred inside an attested environment under a known policy. Regulated and audited compute. For SOC 2, ISO 27001, and similar frameworks, an Intel-signed attestation token is something an auditor can validate without taking the platform's word for anything. That changes what is defensible, and how quickly it can be defended. A note from SCRT Labs "Confidential computing is only half the battle; verification is what enterprises actually buy. I am glad to strengthen our Intel TDX Confidential VM offering with Intel Trust Authority integration. By making Intel Trust Authority a standard feature of every Intel TDX-powered SecretVM, we’re making verifiable trust the baseline for the industry. We are proud to ship this deep integration and grateful to Intel for providing the independent attestation infrastructure this market has long required." — Alex Zaidelson, CEO, SCRT Labs What's next The current integration covers the foundation: on-demand attestation, custom policies, and TLS-bound tokens. The roadmap from here goes deeper, richer policy templates for common compliance regimes, tighter integration with our confidential AI inference layer so attestation can be requested per session rather than per VM, and additional binding modes for relying parties that need finer control over freshness requirements. If you build workloads where trust needs to be demonstrable rather than assumed in AI, in finance, in healthcare, or anywhere else, Intel Trust Authority on SecretVM is available now, with the bundled SCRT Labs credentials, at no additional cost. Get started Documentation: enabling Intel Trust Authority on SecretVM — https://docs.scrt.network/secret-network-documentation/secretvm-confidential-virtual-machines/attestation/intel-trust-authority Intel Trust Authority overview: https://www.intel.com/content/www/us/en/security/trust-authority.html The SecretVM platform: https://secretai.scrtlabs.com/

  31. Published Social post

    Secret Network (@SecretNetwork)

    Private, verifiable, pay-per-request AI is starting to take shape. Our partnership with @corbitsdev brings together SecretVM and SecretAI for confidential execution, Corbits’ Faremeter framework for agentic payments, and Solana for fast settlement. Builders can now launch a new class of AI services with up to $20,000 in compute credits to get started.

  32. Published Social post

    Secret Network (@SecretNetwork)

    Secret Network Ecosystem Update: April 2026 Greetings, Secret Community! This article captures all the key developments in the Secret Network ecosystem for April 2026. SilentSwap Expands to Avalanche SilentSwap integrates the @Avalanche chain through a multi-chain deployment, introducing privacy-preserving transaction routing at the infrastructure layer. Users can transfer assets, manage DeFi positions, and acquire RWAs without exposing wallet-level metadata or transaction graphs. Settlement remains near real-time, typically within one to three minutes, while users retain full self-custody. SilentSwap orchestrates encrypted routing and execution without assuming custody of user funds, ensuring secure and discreet interaction across the network. Trade now on the SilentSwap app Article on DeFi Without Intent Leaks DeFi often leaks intent before execution, exposing traders to MEV and exploitation. Secret enables confidential computation through its smart contracts, where inputs, outputs, and state remain encrypted while the code stays verifiable. Builders can protect order flow, collateral data, and user positions using selective disclosure. This shifts DeFi toward privacy-preserving execution without sacrificing transparency or composability across applications now and beyond today’s period. Read more SilentSwap Is Powering Privacy on BNB Chain @BNBCHAIN is integrating privacy as core infrastructure, shifting it from optional to foundational. @SilentSwap, a privacy DEX, leverages Secret’s confidential computing layer to enable private execution in DeFi flows. Privacy in DeFi will fundamentally reshape market structure by reducing MEV exploitation, protecting trading strategies, and enabling confidential capital deployment. It introduces a shift from fully transparent finance to selectively verifiable systems, where users retain control over what is revealed while still preserving auditability and compliance. Read the full article here SilentSwap recorded 107.14K users and 321.50K silent transactions this month, with millions in volume processed without on-chain traceability. Built on confidential computing, it delivers a fixed 1% fee, 1–5 minute settlement, triple-audited security, and full non-custodial execution with real privacy and real speed for BNB users. Try now Secret Partners with Praxis Secret has partnered with @Praxis_Protocol to integrate confidential computing into the agent economy, where coordination requires privacy to be complete. Secret provides infrastructure for verifiable, private execution using TEEs, enabling agents to process sensitive data, execute financial logic, and coordinate high-stakes workflows without exposing inputs or relying on centralized infrastructure. This integration allows agents to prove execution integrity without revealing underlying data. As decentralized AI grows, the partnership underscores that privacy, trust, and confidential computing infrastructure are essential for autonomous systems to operate safely at scale. Read more ChainGPT X Space with Secret: AI Agents & Privacy @azaidelson, CEO of @scrt_labs at Secret Network, joined @Chain_GPT in an AI After Dark X Space to explore why AI agents still lack real-world utility at scale. The core limitation identified is trust and data exposure, which continue to restrict production adoption despite strong market hype. The session highlighted AIVM and confidential computing as foundational infrastructure for verifiable, privacy-preserving agent execution, enabling secure computation without exposing sensitive inputs or relying on centralized systems. Alex also noted that the next 6–12 months will likely see rapid agentic expansion, especially in coding, where AI is already compressing development cycles and accelerating software creation by orders of magnitude. Listen to the full recording here Secret Partners Antseed Secret Network has partnered with @AntSeedAI to integrate confidential computing into its AI inference marketplace via SecretVM, enabling privacy-preserving, verifiable routing of AI queries. The system ranks providers by cost, latency, reputation, and Secret-powered TEE privacy, ensuring encrypted prompts and outputs stay hidden from providers. Developers connect through a local proxy while users and providers earn $ANTS. The result is open, efficient AI with hardware-level privacy and no gatekeepers. Read more here Secret Partners with QSTN Secret has partnered with @qstnus to bring confidential computing into passive data monetization through SecretVM’s integration into QSTN V2 via SecretAI. This adds a private verification layer for reward distribution, campaign validation, and audience targeting. Users can now keep control of sensitive data while businesses still receive trusted behavioral insights. Read more here April 2026 marks a strong month for the Secret Network ecosystem, focused on scaling confidential DeFi and privacy-preserving AI. Growth was driven by key partnerships with Praxis, AntSeedAI, and QSTN, integrating confidential computing into AI agents, inference, and data monetization. SilentSwap expanded to Avalanche and deepened its presence on BNB Chain, surpassing 107K users and 321K private transactions with fast, non-custodial execution. At the core, SecretVM continued enabling verifiable, encrypted computation, reinforcing Secret’s position as essential infrastructure for secure, real-world Web3 applications. Stay tuned for more developments on Secret Network in 2026.

  33. Published Social post

    Secret Network (@SecretNetwork)

    A strong step toward a more user-aligned data economy. Our partnership with QSTN brings confidential verification and attested execution to reward distribution, campaign validation, and audience insights. Users stay in control of their data. Businesses gain access to signals they can trust. Privacy-preserving infrastructure for real participation, real rewards, and real confidence.

  35. Published Social post

    Secret Network (@SecretNetwork)

    A meaningful step for private AI infrastructure. Our partnership with @AntSeedAI brings confidential computing into the open inference market, so users can route prompts through providers that deliver hardware-level privacy without giving up flexibility, price efficiency, or control. Open access. Verifiable privacy. Better inference by design.

  36. Published Social post

    Secret Network (@SecretNetwork)

    Secret Network and QSTN Partner to Bring Confidential Computing to Behavioral Data Monetization Secret Network, the leading provider of decentralized confidential computing, today announced a strategic partnership with QSTN, a passive data monetization platform that enables users to earn cryptocurrency by securely connecting their accounts and sharing anonymized behavioral data. This collaboration integrates SecretVM into QSTN V2 to provide a confidential verification layer for reward distribution and campaign validation, giving users and businesses a more private, trusted, and verifiable data economy. Through this partnership, QSTN V2 will leverage SecretVM via the SecretAI platform to process sensitive verification requests inside Trusted Execution Environments (TEEs). By securely evaluating reward claims, campaign activity, and user participation within secure enclaves, QSTN can verify legitimate actions, segment audiences, and distribute incentives without exposing the personal data behind them. This creates an attestation-backed system for privacy-preserving validation, helping ensure both trust and confidentiality across the platform. “Working with SecretVM via the SecretAI platform has been a smooth and practical experience, especially for integrating confidential compute into an existing application without major architectural changes,” said Orrin Campbell of QSTN. “It allowed us to introduce a privacy-preserving verification layer without rebuilding our core systems, while adding trust and transparency through attestation.” As businesses look beyond unreliable surveys and bot-driven engagement metrics, the need for authenticated, privacy-preserving behavioral signals becomes increasingly important. By integrating Secret Network’s technology, QSTN V2 will benefit from: Confidential Verification: Sensitive user and campaign data is processed inside secure enclaves, keeping reward distribution and validation workflows private. Attestable Execution: Remote attestation provides verifiable proof that reward and campaign decisions were executed inside a trusted environment. Authenticated Audience Intelligence: Businesses gain access to high-quality insights derived from verified, real-user activity across platforms such as Google, YouTube, LinkedIn, and X. Set-and-Forget User Experience: Users can securely connect their accounts once and passively earn crypto rewards over time without constant manual input. Modular Integration: SecretVM functions as a lightweight confidential compute layer that fits into QSTN’s existing infrastructure without requiring a full backend redesign. “QSTN is a compelling example of how confidential computing can power a more user-aligned data economy,” said Luke Bowman, COO of Secret Network. “By combining privacy-preserving infrastructure with verified behavioral insights, this partnership helps ensure users remain in control of their data while businesses gain access to trustworthy signals with greater confidence.” QSTN V2 builds on the company’s earlier traction, following QSTN V1’s growth to more than 10,000 users and 130 business campaigns. Since launching the V2 beta in November 2025, QSTN has grown to 3,500 users, secured two issued U.S. patents in blockchain-based data monetization, won two blockchain hackathons, and expanded its ecosystem through academic collaboration with the University of Illinois. Together, Secret Network and QSTN are advancing a new two-sided model in which users are not the product, but active participants in the value their data helps create. About Secret Network Secret Network is a decentralized network of nodes that utilize Trusted Execution Environments (TEEs) to enable confidential computing. As the privacy hub of Web3, Secret Network provides the infrastructure for private smart contracts and encrypted data transfer. scrt.network About QSTN QSTN is a passive data monetization platform that enables users to earn cryptocurrency by securely connecting digital accounts and sharing anonymized behavioral data. Designed as a “set-and-forget” experience, QSTN allows users to generate ongoing value from verified activity while maintaining control over their identity and data. For businesses, QSTN delivers privacy-preserving, behavior-based audience intelligence and campaign validation backed by authenticated user signals. https://data-earn.qstn.us

  39. Published Social post

    Secret Network (@SecretNetwork)

    Secret Network and Antseed Partner to Bring Confidential Computing to the Open AI Inference Market Secret Network, the leader in on-chain data privacy, today announced a partnership with @AntSeedAI, the open market for AI inference. This collaboration integrates Secret Network’s Confidential Computing into the Antseed ecosystem, allowing users to route their AI queries through verifiable, privacy-preserving nodes. Antseed disrupts the centralized AI model by allowing providers and buyers to connect peer-to-peer without gatekeepers. By running as a local proxy ,at localhost:8377. Antseed allows any tool, from Claude Code to custom scripts, to access any model via an open network. The router scores all available providers in real time against what you care about: cheapest price, lowest latency, TEE privacy, or minimum provider reputation. Through this partnership, Secret Network’s Trusted Execution Environments (TEEs) become a primary metric in the Antseed router, enabling users to prioritize verifiable privacy when selecting a provider. "Antseed is solving the gatekeeper problem for AI, and Secret Network is solving the privacy problem," said Luke Bowman, COO of Secret Network. "By integrating Secret’s confidential computing capabilities, Antseed users don't have to choose between the best price and data security. They can now automatically route their inference to providers that guarantee privacy at the hardware level." Key Integration Features: Privacy-First Routing: Antseed’s real-time router now includes Secret Network-backed TEE based privacy as a key scoring metric, alongside price and latency. Hardware-Level Security: Users can verify that their AI prompts and model outputs remain encrypted and inaccessible to the provider, powered by Secret’s TEE infrastructure. Decentralized Rewards: Providers and users of Secret-validated confidential inference can register on-chain and receive earnings automatically in $ANTS token via the Antseed protocol. Zero-Friction Adoption: Developers can access Secret’s privacy-preserving inference by simply pointing their existing AI tools to the Antseed local proxy. "Antseed’s motto is 'Everyone profits, no one controls,'" said Shahaf Antwarg, Co-Founder of Antseed. "By bringing Secret Network into our Compute Index, we are ensuring that 'no one controls' also means 'no one sees your data.' This is the final piece of the puzzle for a truly open, professional AI infrastructure." About Secret Network Secret Network is the first blockchain with data privacy by default for smart contracts, specializing in Decentralized Confidential Computing (DeCC). It provides the essential privacy layer for Web3 and AI, protecting sensitive data and enabling secure, private communication between decentralized applications and AI models. Learn more: https://scrt.network/ About Antseed Antseed is an open market for AI inference that eliminates gatekeepers and platform rent-seeking. By connecting providers and buyers peer-to-peer through a local proxy, Antseed offers a seamless, resilient, and transparent way to consume AI compute. Learn more: https://antseed.com/ | Twitter: @AntSeedAI

  41. Published Social post

    Secret Network (@SecretNetwork)

    A major step forward for decentralized AI. Our partnership with @Praxis_Protocol brings confidential, verifiable execution to autonomous agents, giving developers a secure environment for sensitive data, high-stakes decisions, and trusted coordination. Private by design. Verifiable by default. Built for what agents need next.

  43. Published Social post

    Wu Blockchain (@WuBlockchain)

    Z Protocol Co-Founder : AI Agent Era Will Make Privacy a Massive Opportunity Co- founder of Z Protocol @zprotocolxyz Kieran Dennis said human users average about 12 on-chain interactions daily, while AI agents could execute over a thousand. He warned that deploying these agents on transparent public chains will amplify data exposure risks. Even current human activity has led to real-world threats actors can track transaction times and balances to carry out "wrench attacks" (physical coercion for private keys). Kieran said as AI agents scale, these risks will grow exponentially, making built-in privacy essential. He added that embedding end-to-end privacy into AI models is a major opportunity, allowing users to truly control their data.

  44. Published Social post

    Secret Network (@SecretNetwork)

    ​Secret Network and Praxis Partner to Bring Confidential Computing to AI Agent Mesh ​Secret Network, the leading provider of decentralized confidential computing, today announced a strategic partnership with Praxis, an innovative platform building a decentralized mesh for AI agents. This collaboration integrates Secret’s technology to provide AI agents with a secure, confidential, and verifiable execution environment. ​Through this partnership, @Praxis will leverage Secret Network’s Confidential Virtual Machines (Secret VMs) to enable agents to operate within Trusted Execution Environments (TEEs). This allows users to deploy AI agents with provable integrity, ensuring that the agent’s logic remains untampered, while maintaining absolute privacy for the data being processed. ​"At Praxis, we are building the coordination layer for the next generation of autonomous agents," said Robert Brighton, CEO of Praxis Protocol. "Privacy and verifiability aren't just 'features' for AI; they are requirements for true autonomy. By integrating Secret Network’s TEE capabilities, we are ensuring that agents in our mesh can handle sensitive data and financial transactions with the highest level of trust and security." ​As AI agents move toward handling complex tasks, the need for decentralized trust and identity systems becomes critical. By integrating Secret’s technology, Praxis agents will benefit from: ​Provable Integrity: Cryptographic proof that agents are executing exactly as intended. ​Data Privacy: Confidential compute capabilities that protect sensitive user inputs from exposure. ​Decentralized Compute: An optional layer of decentralized execution to remove single points of failure. ​Seamless Integration: Full compatibility with the existing Praxis agent mesh for identity and payments. ​"The integration of Secret Network’s confidential computing stack into the Praxis ecosystem marks a significant milestone for decentralized AI," added Luke Bowman, Chief of Operations at Secret Network. "By providing a verifiable environment for agents, we are giving developers and users the tools they need to interact with AI without compromising on privacy." ​The partnership will focus on technical implementation over the coming months, allowing Praxis developers to easily opt-in to Secret-powered confidential environments for high-stakes agent operations. ​About Secret Network Secret Network is a decentralized network of nodes that utilize Trusted Execution Environments (TEEs) to enable confidential computing. As the privacy hub of Web3, Secret Network provides the infrastructure for private smart contracts and encrypted data transfer. scrt.network ​About Praxis Praxis is building the foundational mesh for the future of AI agents. By providing a framework for trust, identity, and payments, Praxis enables a seamless ecosystem where autonomous agents can collaborate and transact securely. prxs.ai

  45. Published Social post

    Secret Network (@SecretNetwork)

    DeFi Without Intent Leaks: Design Patterns You Can Implement Now Most DeFi leaks intent before it executes. A swap is visible before settlement. A position update is visible before the market reacts. A liquidation threshold becomes public long before it is tested. On public-by-default systems, order flow becomes free intelligence for bots, competitors, and attackers. That is not neutral infrastructure. It is a built-in extraction layer. Secret Network changes that execution surface. Secret Contracts keep contract input, output, and state encrypted, while the contract binary stays public and verifiable. That matters because DeFi does not need less logic. It needs less leakage. The network docs also make the boundary clear: not every field is private. Sender, sent funds, block height, chain ID, and contract hash are not encrypted. Good privacy design on Secret is not about hiding everything. It is about keeping the sensitive part of execution confidential and revealing only what the application actually needs to reveal. Keep price discovery public, keep user state private One of the cleanest patterns on Secret is selective visibility inside an AMM or swap venue. Pool balances and other market-wide values can remain readable when the protocol needs them for price formation, while individual LP balances, wallet balances, contribution history, and reward flows stay private. Secret’s own DeFi guidance describes exactly this setup: a privacy-preserving exchange can keep pool balances public while individual contributors remain anonymous, with token balances and holder data re-encrypted inside Secret Token contracts. This is the right default for builders who want transparent markets without exposing every participant. Make shared state visible only where it is necessary for pricing or solvency. Keep per-user state encrypted by default. On Secret, viewing keys and permits give users controlled ways to disclose that data when they choose to. Use private order flow for swaps, auctions, RFQs, and dark pool style execution Intent leaks start before settlement. They begin in the mempool and in the shape of the transaction itself. Secret’s docs are explicit here: encrypted mempool and encrypted state make Secret front-running resistant by default, and private DeFi designs can keep order size, placed bids, and liquidation points unknown. The DeFi docs also point to dark pools as a natural fit for this model. That gives builders a clear pattern to implement now. Accept encrypted client messages as order flow. Keep quote requests, trade size, and execution parameters private until the contract computes the outcome. Reveal only the settlement result to the entitled user or counterparty. Where metadata sensitivity matters, contracts can enforce constant-length messages through padding to reduce leakage from message shape itself. Hide collateral surfaces, not protocol rules Public risk parameters are fine. Public liquidation maps are not. Secret highlights lending protocols with private collateralization information as a core use case, and lending systems that can evaluate eligibility on encrypted financial data without exposing the user’s underlying records. The broader DeFi overview makes the same point from a trading perspective: on Secret, users can lend, borrow, and provide liquidity without revealing liquidation targets, position size, or strategy. That is the pattern builders should adopt. Keep protocol logic, rate curves, collateral factors, and liquidation rules public in the contract code. Keep account-level health, collateral composition, and exposure encrypted in state. Public logic, private balance sheet. That is how you preserve verifiability without turning every borrower into a target. Treat disclosure as a permission layer, not a data model A lot of DeFi teams still think privacy and compliance sit on opposite sides. On Secret, they do not. The network’s access model is built around selective disclosure. Viewing keys let users reveal contract-specific private data such as balances or history. Permits let users sign access to specific parts of their private data for specific dApps or parties, and this access can be granted for a specified amount of time. This is one of the most practical design patterns available on the network today. Build private state first. Add disclosure endpoints second. Do not architect the protocol around permanent public exhaust and call it transparency. Architect it around user-controlled access. Split confidential systems into modules Secret supports cross-contract communication, which means you do not need one oversized contract trying to do everything. Matching, collateral management, pricing, settlement, and permissions can be separated into modules and composed securely. That makes systems easier to reason about and easier to audit. One important design rule is that only data originating inside the enclave is inherently verifiable, and external inputs need to be verified before relying on them for execution. Data can be trusted, but sender address should not be assumed trustworthy without verification. For DeFi builders, that means confidential modules should exchange verified state transitions, not loose assumptions. Use Secret as the confidential execution layer, even if the rest of the app lives elsewhere Not every product needs to move its whole stack to Secret. Secret’s model is explicit: you can host the bulk of your application on your preferred blockchain and use Secret to handle confidential data. For teams already shipping elsewhere, that is a practical route forward. Keep public settlement or liquidity where it already exists. Route sensitive order flow, private balances, credit logic, or sealed coordination through Secret. Privacy does not have to be a full rewrite. It can be a deliberate boundary in the architecture. Start with privacy-safe defaults in development A private DeFi design can still leak if the implementation is careless. Secret’s docs flag contract migration as a privacy risk, because an admin could migrate to malicious code that reads entrusted data. They also note that iterators and raw queries are not supported across user-dedicated encrypted state, which means data access patterns should be designed explicitly rather than assumed from public-chain habits. The implementation path is already there. Secret.js handles input and output encryption and decryption for Secret Contracts on the client side. Secret provides LocalSecret as a zero-config local chain for testing, and the docs list Secret Labs crates plus secret-toolkit modules for storage, viewing keys, crypto, and utils in Rust. These are not future-facing ideas. They are the current development path. DeFi without intent leaks is not a slogan. It is an architectural choice. Keep what the market needs to know visible. Keep what extractors want to know encrypted. Let users disclose only what they need, only to whom they choose. That is the design space Secret Network opens up now, with Secret Contracts, Secret Tokens, viewing keys, permits, and confidential cross-chain patterns already documented and available to build with.

  47. Published Social post

    Secret Network (@SecretNetwork)

    Attestation for builders: what it proves and why users will demand it Privacy gets attention first. That makes sense. If you are building with confidential compute, the first question is usually about what stays hidden, who can access it, and whether the infrastructure owner can inspect the workload. But privacy is only half the job. The other half is proving what is actually running. That is where attestation matters. For builders, attestation is the mechanism that turns confidential compute into something users can verify. It provides cryptographic evidence about the machine, the environment, and the workload being executed. In SecretVM, that means a verifier can inspect whether a workload is running inside genuine TEE hardware and whether the measured software stack matches what it is supposed to run. That changes the trust model. Without attestation, a confidential VM is still a black box. Data may be protected, but users are still left trusting the operator to describe the workload honestly. They cannot independently confirm the environment, the code path, or the integrity of the deployment. With attestation, that starts to change. A SecretVM exposes attestation data that can be checked against expected measurements. Those measurements are tied to the software stack, including core artifacts and the workload definition. That means a developer can publish the relevant workload configuration, and a verifier can compare it to what the VM proves it is running. If the measurement matches, the verifier knows the workload is genuine. If one byte changes, the proof changes too. That matters more than many teams realize. Users are getting used to software that asks for trust without giving proof. In consumer apps, that may remain common. In AI, finance, infrastructure, healthcare, enterprise software, and autonomous systems, it will not be enough. Once users understand that workloads can be verified, they will start expecting it. They will want to know whether the code handling their data is the same code they reviewed. They will want to know whether an AI system is running in the environment the builder claims. They will want to know whether a service has been upgraded, whether secrets are only released to verified workloads, and whether logs, metrics, and operational surfaces reveal more than they should. They will want proof, not policy pages. This is why attestation is not just a backend detail. It is becoming part of the product surface. For builders, that means a few practical things. First, provenance matters. If users are going to verify workloads, the workload definition needs to point to something precise. That is why code provenance and pinned images matter. A docker-compose file tied to a specific image hash and linked back to source control gives verifiers something concrete to inspect. Second, upgradeability has to be visible. If a workload can change over time, users need a way to know that. An upgrade path without transparency weakens trust. An upgrade path with visible history and attestable state gives users a way to evaluate changes. Third, key management has to respect attestation. Sensitive material should not be handed to a workload just because it asks. It should only be released when the machine proves its identity and integrity. That is the logic behind attestation-bound key management. Fourth, verification needs to be usable. Raw attestation data is powerful, but most users will not parse low-level registers by hand. Builders need verification flows that are understandable, auditable, and easy to repeat. That includes UI-based verification, offline verification tools, and clear documentation. This is also where the conversation moves beyond privacy. Confidential compute protects data from the host. Attestation proves the environment to the user. Together, they give builders a way to offer systems that are both private and verifiable. That combination matters for AI in particular. Private AI cannot rely on secrecy alone. If a team is sending prompts, internal documents, customer data, or execution logic into a system, they need more than assurance that the host cannot inspect it. They need confidence that the exact workload they approved is the one receiving that data. The same applies to agents, oracles, private services, and internal enterprise tools. As these systems become more autonomous, the standard will rise. Users will not just ask whether the infrastructure is encrypted. They will ask what code is running, how it can be verified, whether it changed, and who controls the keys. Builders who can answer those questions with proofs will have an advantage. Builders who cannot will be asked to do so anyway. That is why attestation is worth understanding now. It is not a niche feature for specialists. It is how confidential compute becomes accountable. It is how trust moves from claims to evidence. And it is one of the clearest reasons SecretVM matters. Build with privacy. Ship with proof. Start here: https://secretai.scrtlabs.com/

  48. Published Social post

    Secret Network (@SecretNetwork)

    We’re excited to partner with YijingBot to bring confidential AI-powered gameplay onchain. By leveraging SecretVM and Secret AI, YijingBot runs its backend and sentiment analysis inside confidential compute, ensuring the daily “luckiest fortune” jackpot is determined in a way that’s private, verifiable, and impossible to manipulate. Bringing confidential AI inference, transparent winner selection, and provably fair gameplay to life.

  49. Published Social post

    Secret Network (@SecretNetwork)

    Something exciting is coming. We’re teaming up with @stormrae_ai to explore the future of privacy-preserving AI testing. Together, we’re working on ways to combine advanced AI red-teaming with confidential computing powered by SecretVM, helping ensure sensitive AI data and prompts remain protected. More details on the partnership dropping soon.

  50. Published Social post

    Secret Network (@SecretNetwork)

    Secret Network Partners with moonCat AI to Optimize Confidential AI Liquidity on the Superchain Secret Network, the leading platform for Web3 data privacy, today announced a strategic partnership with MoonCat AI, a Superchain-native DeFi protocol focused on AI-driven liquidity intelligence and capital efficiency. The collaboration will enable @Mooncat_ai to run sensitive components of its AI Liquidity Optimiser within a confidential virtual machine (VM) powered by SecretVM, a key component of the Secret Network ecosystem. This helps protect moonCat AI’s models while enabling verifiable execution on-chain. This partnership addresses a key challenge for advanced DeFi infrastructure: protecting AI models and decision systems while maintaining transparency and trust. moonCat AI’s Liquidity Optimiser analyses on-chain liquidity, incentives, and usage patterns to help identify more durable yield opportunities and improve capital allocation for liquidity providers. By utilizing SecretVM, moonCat AI can execute sensitive components of its AI Liquidity Optimiser in a confidential computing environment. This cryptographic isolation helps protect the models and decision logic behind the optimiser from external view or manipulation. Crucially, the integration supports cryptographic attestation and zero-knowledge verification, allowing moonCat AI to prove that computations are executed correctly without exposing the underlying code. "The future of DeFi depends on innovation that is both powerful and trustworthy," said Luke Bowman, COO of Secret Network Foundation. "Our partnership with moonCat AI is a perfect demonstration of SecretVM's value. We are providing a trustless environment where moonCat AI can secure its intellectual property while offering unprecedented, verifiable transparency to its user base. This is truly confidential DeFi in action." “We’re building AI-powered liquidity intelligence for DeFi,” said Joshua Allen-Nelson, Founder & CTO of moonCat AI. “Our Liquidity Optimiser analyses how incentives, usage, and liquidity interact across the Superchain to help identify more durable yield opportunities. Secret Network helps us bring that intelligence layer into production without compromising trust. About Secret Network Secret Network is the first blockchain with data privacy by default, allowing for the development of powerful, permissionless, and privacy-preserving applications. Secret Network’s unique technology enables decentralized applications (dApps) to leverage encrypted inputs, outputs, and state, as well as AI models to keep computation and inference confidential protecting users and IP. Website: scrt.network About moonCat AI MoonCat AI is a Superchain-native DeFi protocol (SuperchainERC20) building infrastructure for collective prosperity. Its AI Liquidity Optimiser analyses on-chain liquidity, incentives, and usage patterns to help identify more durable yield opportunities across the Superchain. Combined with fee-free staking, AI-assisted governance, and a profit-only fee model, moonCat AI aims to make DeFi more transparent, efficient, and sustainable. Website: https://www.mooncat.ai/

Showing 50 of 464 stories · Page 1 of 10. Filters apply to the full news archive.