Fairblock primary sources

Reviewed: 2026-05-12 UTC

Core project framing

  • https://docs.fairblock.network/
    • Top-level docs entrypoint. Minimal on its own, but useful for confirming current positioning around confidential amounts/data and for navigating into the more specific architecture pages.
  • https://docs.fairblock.network/docs/welcome/Vision
    • Best concise official summary of the current product framing. Most useful source for FairyRing as a native confidentiality execution layer, cross-ecosystem access without bridging, dynamic confidentiality, and the selective-disclosure posture.

v1 mechanism docs

  • https://docs.fairblock.network/docs/learn/v1/
    • Best short mechanism overview for the original Fairyring / v1 design. Makes explicit that apps listen for master public keys, encrypt against condition IDs, and later receive decryption key shares once a condition is satisfied.
  • https://docs.fairblock.network/docs/learn/v1/cryptography
    • Most useful cryptography page in this pass. Explains threshold IBE, the split between master public key and validator-held secret-key shares, and the distinction between private shared state and private access control.

Cross-chain confidential-transfer architecture

Private-decryption / app-design layer

  • https://docs.fairblock.network/docs/build/fairyring/fairyring_private_decryption
    • Best source for the user-specific decryption variant. It makes explicit that validator key shares can be encrypted to a specific wallet public key instead of being revealed publicly, which turns decryption policy into a separate control surface.
  • https://github.com/Fairblock/fairyring
    • Useful implementation-level summary page. Confirms FairyRing’s framing as a decentralized network hosting homomorphic encryption, identity-based encryption, ZKP verification, and DKG for apps on FairyRing and external ecosystems.

Cryptographic ancestor / research framing

  • https://eprint.iacr.org/2022/1066
    • The underlying FairBlock: Preventing Blockchain Front-running with Minimal Bandwidth Overheads paper. Not a full current product spec, but still useful for the cryptographic and fair-ordering lineage behind the threshold-IBE framing.

Main takeaways from this pass

  • Fairblock is most useful in the corpus as conditional-decryption and confidential-execution infrastructure, not just as a generic privacy or confidential stablecoin brand.
  • The important analytical split is between FairyRing as the confidential execution layer, external-chain custody/settlement contracts, threshold-key-share generation, condition-definition policy, and selective-disclosure rules.
  • The cross-chain technical overview is especially valuable because it avoids flattening the system into one chain: users can stay on an external ecosystem while Fairblock hosts the confidential ledger and proof logic elsewhere.
  • The private-decryption flow adds a second control surface beyond when is a transaction decryptable?: for whom is the decryption material visible once the condition is met?
  • Fairblock is a strong comparison class for Shutter, drand, shielded-intent systems, and privacy-preserving payment rails because each of those systems makes fairness/confidentiality claims that ultimately depend on who controls release conditions, key material, and integration chokepoints.