Secret Network: A Privacy-Preserving Secret Contract & Decentralized Application Platform

Disclaimer: This page is an educational summary and analysis of a technical paper. It is not a verbatim reproduction, and it is not investment or financial advice. Read the source and current project documentation before relying on technical or operational details.

The paper’s cover credits Carter Woetzel and gives the title Secret Network: A Privacy-Preserving Secret Contract & Decentralized Application Platform. It describes a 2020-era design for programmable privacy on a public blockchain. It is a historical architecture paper, not a current specification of the network’s software, economics, or governance.

Paper Details

Author Carter Woetzel
Year 2020-era; the cover has no publication date, and the references extend through December 2020
Project Secret Network
License Not stated in the document
Paper copy PDF copy hosted by Securities.io

The paper’s previously listed official address, scrt.network/graypaper, returned a 404 during this review. The linked PDF is a third-party hosted copy; its cover names Woetzel and its pages carry the www.scrt.network footer. Current official operator documentation is cited separately below.

What the Paper Proposes

The paper describes Secret Network as a Cosmos-based layer 1 using Tendermint consensus, with smart contracts built around CosmWasm. Its central idea is to let a contract process selected data privately while the wider chain remains public. Secret Contracts use a trusted execution environment (TEE), identified in this paper as Intel Software Guard Extensions (SGX), to execute code and handle encrypted information on validator hardware.

In the paper’s model, clients encrypt contract messages before sending them; contract state is encrypted when stored; and a contract can encrypt output for the intended recipient. Validators still agree on the same state transition, but the host operating system is not supposed to read data processed inside the enclave. The design also uses key-management and remote-attestation steps to identify approved enclave code and distribute the material needed for private execution.

This is application-level or programmable privacy, not blanket anonymity. The paper distinguishes public SCRT, used for network fees and consensus, from SNIP-20 Secret Tokens, whose contract design can keep token balances and transfers private. Interoperability through IBC can bring assets and applications into the ecosystem, but IBC by itself does not make data private. Privacy depends on the receiving contract and the information it exposes.

How Privacy Is Scoped

A useful way to read the design is to ask which fields are encrypted and who can later reveal them. A contract may keep its internal state private and use a viewing key to let a user or an authorized party query selected information. That can support selective disclosure, but a viewing key is still a credential: sharing or mishandling it can expose the data it controls.

The paper explicitly notes that some transaction context remains public, including the sender, chain information, sent funds, and contract-related metadata. Timing, gas use, message sizes, and application behavior can also reveal clues. A private contract therefore does not automatically hide a user’s identity, every transaction relationship, or all activity around an application. Developers have to decide what is private, what is intentionally visible, and what could be inferred from the visible parts.

Trust Assumptions and Limits

SGX changes the trust model: users rely less on each server operator’s honesty, but more on the enclave hardware, firmware, attestation system, cryptographic implementation, and contract code. A TEE is not the same as a zero-knowledge proof that lets anyone verify a computation without trusting special hardware. Hardware isolation can reduce exposure to a host, but it does not remove the need to assess hardware and software risks.

Privacy is also not automatic just because a contract runs in an enclave. Public inputs, event structure, transaction timing, application design, and user behavior can leak information. Secret’s current operator guide, updated for software version 1.27.2 on October 3, 2026, still specifies Intel SGX hardware for mainnet node operation. That is evidence about the current operational setup; it does not make every paper-era implementation detail a current guarantee.

What Changed After the Paper

Secret Contracts reached mainnet in September 2020. The network’s more recent history is separate from the paper’s design: in August 2026, Secret’s official announcements reported that Proposal 365 for community continuation passed, with 94.8% voting-power participation, and that the v1.26 community-led upgrade completed. Current operator documentation now describes v1.27.2. These updates indicate that the Cosmos-based network continued under community stewardship after the original development company’s announced support transition; they do not establish that the network’s long-term technical or economic risks are resolved.

The 2026 governance discussion also included a substantial supply restructuring and a remediation allocation. Forum participants raised questions about dilution, how allocations would be governed, security work, and how affected users would be compensated; other participants supported keeping the existing chain running. The vote and upgrade are completed events, while implementation, remediation, and future governance remain matters to evaluate from current records.

Takeaway

The paper’s lasting contribution is its model for running programmable smart contracts over encrypted inputs and state on a shared blockchain. Its main tradeoff is clear: it aims to make application data private while relying on specialized trusted hardware and careful application design. Read it as a foundational design document, then use current documentation and governance records for today’s implementation and network status.

Social Media Sentiment

A small, self-selected sample of discussion on Secret Network’s governance forum around Proposal 365 showed mixed reactions. Supporters argued that community stewardship and a funded continuation plan gave the Cosmos L1 a path forward after the development-support transition. Critics questioned the scale of dilution, concentration and oversight of token allocations, security priorities, and the practical value and timing of the remediation plan. This forum discussion is not a representative measure of all users, token holders, or market sentiment. See the Proposal 365 discussion for the competing views.

Last updated: 2026-10

Related Terms

See Also

Sources