Blocklock is the most concrete application-facing conditional-encryption surface in the dcipher stack. The docs are not just about threshold signatures in the abstract; they show how developers actually register encrypted payloads, fund requests, and receive decryption callbacks onchain.
The core reusable mechanism is committee-produced decryption after condition verification. The docs explicitly describe threshold BLS signatures plus identity-based encryption, with the signature generated only after the target condition is observed.
Blocklock exposes a real delivery stack rather than just a cryptographic promise: offchain ciphertext generation, condition encoding, BlocklockSender contract routing, request-price calculation, funding mode choice, and callback-based decryption handling.
Supported-network policy is a meaningful control surface. The docs list predeployed sender contracts on a finite set of mainnets and testnets, which means practical chain coverage and contract deployment policy matter as much as the cryptography.
The agent repo is especially useful because it reveals how the condition-monitoring and fulfillment layer operates in practice: event listeners, BLS signing, IBE decryption handling, replay logic, rate limiting, and health endpoints. That makes the operational surface much more legible than a high-level lightpaper alone.
There is a productive tension between the docs’ permissionless-threshold-network framing and the practical deployment path described in the repos, where dcipher-operated agents and predeployed contracts appear to play a large role today.
Specific source signals worth retaining
features/conditional-encryption: best mechanism page for the threshold-BLS-plus-IBE model and the availability / honest-majority assumptions.
quickstart/blocklock: best source on the application path — request construction, receiver inheritance, callback handling, and funding routes.
networks/blocklock: best evidence that chain deployment and sender-contract addresses are first-class parts of the system design.
blocklock-js: strongest source for the offchain encryption and application-level developer flow.
blocklock-solidity: strongest source for the contract interface, pricing, subscription sharing, and callback model.
blocklock-agent: strongest source for the operator / fulfillment mechanics that are easy to miss in higher-level docs.
Why this entry belongs in the corpus
It gives the corpus a concrete lower-middle comparison point between public randomness/timed-release systems and richer encrypted-orderflow or policy-enforced threshold networks.
It is especially useful for comparing how conditional decryption gets packaged for real developers: not just cryptography, but request pricing, callback gas assumptions, supported-chain contracts, and fulfillment infrastructure.
The durable insight is that Blocklock should be analyzed as a delivery rail for threshold conditional access, not just as a library and not just as a marketing example of threshold encryption.