What are ciphernodes?

The Interfold is a distributed network for confidential coordination: the ability for multiple independent parties to produce shared outcomes from private inputs without pooling data or delegating execution authority to a single operator.

Ciphernodes are the operators that make this possible.

Their network role is to participate in distributed key generation (DKG) and threshold decryption. For each computation, ciphernodes help produce the public key used to encrypt inputs, then contribute decryption shares once the approved output is ready.

To learn what ciphernodes do and how to register interest in future operator participation, keep reading.

Why ciphernodes matter

Encrypted inputs are not enough.

A system can keep data encrypted and still concentrate authority around whoever controls setup, execution, completion, or decryption. In that model, privacy depends on a trusted operator.

Confidential coordination requires something stronger: threshold guarantees that ensure no single party can expose inputs, control decryption, or unilaterally control the process.

That is why the Interfold needs ciphernodes.

A ciphernode’s role is not to access private data. Its role is to participate in the threshold processes that prevent any single operator from exposing inputs or decrypting approved outputs alone.

What ciphernodes do

Ciphernodes participate in the network processes that make confidential coordination possible.

In practice, they participate in the processes that allow an E3 (Encrypted Execution Environment) to be created, executed, verified, and completed. These include:

• participating in distributed key generation (DKG)
• coordinating committee duties for each E3
• supporting protocol-defined execution conditions
• participating in threshold decryption of E3 program outputs
• supporting E3 verification and closure once execution is complete

They do not act as custodians. They do not hold raw data. They do not independently determine results.

Their role is to participate in a distributed keygen and decryption process where authority is constrained by cryptography, protocol rules, and threshold participation.

From network to committee

Ciphernodes do not act as one undifferentiated network for every computation.

For each E3, the protocol uses sortition — randomized committee selection — to form a bounded committee from the broader ciphernode network.

An E3 is an ephemeral execution surface created for a specific computation. It receives encrypted inputs, runs defined program logic under threshold-governed conditions, supports verification, and closes once the E3 program output is decrypted.

That committee handles the threshold duties for the computation: setup, execution coordination, threshold decryption of E3 program outputs, and closure.

This distinction matters: the full ciphernode network is the operator layer of the Interfold, but each computation depends on threshold duties carried out by a specific committee selected under protocol rules.

In order to keep confidential coordination from depending on a single runtime, execution authority is distributed across a selected committee rather than assigned to one operator.

Why execution needs its own operator layer

Most blockchain systems already have operators. Validators maintain state. Sequencers determine ordering.

Ciphernodes participate in a different part of the system: the operator layer that provides threshold guarantees for confidential coordination.

Most networks distribute validation, but few distribute execution authority.

For confidential coordination, that difference is the point. Private inputs and verifiable outcomes are not enough if execution is still governed by one operator.

Without this operator layer, encrypted execution risks becoming another hosted service. Private inputs may remain encrypted, but authority over setup, completion, and decryption still concentrates around whoever controls the environment.

What ciphernodes make possible

Ciphernodes support systems where multiple parties contribute private inputs to produce a shared, verifiable result.

These systems tend to fall into three coordination types:

• Competitive coordination: sealed-bid auctions, confidential pricing, allocation systems
• Collective coordination: secret ballots, impartial selection, governance voting
• Data coordination: model evaluation, shared metrics, cross-institutional analysis

At the end of an auction, the winning bid can be revealed without turning every losing bid into market intelligence. At the close of a vote, a result can be verified without creating a public record of individual pressure points. At the completion of a shared analysis, institutions can rely on a result without turning collaboration into data custody.

The point is not that ciphernodes create these applications by themselves. The point is that they provide the distributed threshold guarantees those applications need.

The genesis operator set

The Interfold is currently operating in testnet, with ciphernodes active in a controlled configuration. The next phase is controlled external onboarding, beginning with selected infrastructure participants rather than open operator access.

This phase is intended for infrastructure operators, protocol teams, staking providers, and technically capable organizations comfortable running network infrastructure and coordinating with protocol teams during a controlled rollout. Early operators will help establish how committee-based duties are performed, how reliability expectations are set, how threshold decryption is coordinated, and how verifiable results are produced in practice.

Ciphernode operation will be a token-based, economically accountable role, with rewards for correct participation and penalties for provable misbehavior or failure to meet protocol requirements. Details on system requirements, operator eligibility, rewards, staking, and slashing will be introduced separately. External onboarding remains controlled during this phase, with broader operator expansion planned for later stages.