Why ciphernodes exist

Encryption can hide data while leaving control centralized. Interfold’s ciphernode layer is designed to distribute the authority required to generate encryption keys and reveal permitted outputs.

The trust problem

Imagine several organizations want a shared answer from sensitive data but cannot reveal their raw inputs to one another. Encrypting the data is necessary, but it does not answer a second question: who controls the key?

If one server creates or holds the complete decryption key, confidentiality still depends on that server. The operator can be compromised, coerced, or simply become unavailable. The computation is encrypted, but the control plane remains a single point of trust.

Where ciphernodes sit in an E3

An E3 is an Encrypted Execution Environment: a request-scoped confidential computation. Ciphernodes are selected into an E3 committee. The committee participates in publicly verifiable distributed key generation, contributes to the public encryption key, stays available while the E3 runs, and later produces decryption shares for the accepted encrypted output.

Ciphernodes are not compute providers

The distinction matters. The compute provider executes the secure process over encrypted inputs. The ciphernode committee supplies distributed cryptographic authority around that process. One role evaluates ciphertexts; the other prevents encryption and decryption control from collapsing into one party.

How committee selection works

Eligible registered operators hold ticket balances. For each E3, sortition derives deterministic ticket scores from the operator, ticket number, E3 identifier, and request-bound seed. Lower scores rank better. Operators submit their best ticket, and the registry finalizes the committee from those results.

availableTickets = floor(ticketTokenBalance / ticketPrice)

score = keccak256(node, ticketNumber, e3Id, seed)

More available tickets increase selection probability, but a ticket balance is not a guarantee of committee membership. The balance is economic weight in a verifiable selection process.

Why public verifiability matters

Threshold cryptography alone can distribute secret material, but observers still need evidence that the participants followed the protocol correctly. Interfold couples its threshold BFV workflow with zero-knowledge proof systems and publicly verifiable DKG so key-generation, share, and decryption behavior can be checked rather than merely trusted.

Economics completes the operator model

Cryptography tells the network what correct behavior looks like. Bonding and slashing attach consequences to operator behavior. A registered operator can face ticket penalties, FOLD bond penalties, committee removal, or bans under configured slash policies when assigned duties are violated.

Primary sources

• Network Alpha: The Interfold on Mainnet
• Ciphernode Operators
• Tickets & Sortition
• Cryptography implementation guide