Cowrie Research

blocklock

3 min read

Blocklock

  • Name: Blocklock
  • URL: https://docs.dcipher.network/features/conditional-encryption/
  • Category: conditional-decryption middleware / sender-contract release rail
  • Summary: Blocklock is dcipher’s condition-triggered release rail. Keep it for the explicit application path: sender contract, fee funding, committee watch, threshold release, and callback delivery. Useful for auctions and delayed reveals, but still just a narrower rail under the broader threshold-policy layer.
  • What it does:
    • Lets users encrypt data against a future block height or other supported condition so the plaintext cannot be recovered until the condition is satisfied
    • Uses dcipher committees to watch the relevant condition and collectively produce a threshold signature that doubles as the decryption key
    • Exposes Solidity and TypeScript libraries so applications can register ciphertexts, pay request fees, and receive decryption callbacks directly in smart-contract flows
    • Supports both direct funding and shared subscription funding models for repeated conditional-encryption requests
    • Deploys chain-specific BlocklockSender proxy contracts across multiple production and test networks, giving applications a standard onchain ingress point
    • Positions the primitive for sealed-bid auctions, delayed reveals, conditional access control, and MEV-resistant transaction or payload release
  • Key claims:
    • Blocklock clears the bar because it turns conditional access into a comparison-ready middleware stack: condition expression, ciphertext creation, committee attestation, onchain request/funding, and callback delivery are all explicit layers.
    • The most important mechanism is the signature-as-decryption-key path. The docs describe a committee that does not store a preexisting release key; instead, it produces the threshold signature only after verifying the condition, and that artifact unlocks the ciphertext.
    • Blocklock is analytically useful because it exposes operational choke points that generic threshold encryption language often hides: supported-chain contract deployments, callback gas pricing, availability assumptions, and the trust boundary around the committee that monitors conditions.
    • The reviewed materials also show a valuable tension between protocol framing and deployment reality. dcipher presents itself as a permissionless threshold-signing network, but the Blocklock docs and repos make clear that today’s application path relies on predeployed sender contracts and dcipher-operated fulfillment infrastructure on supported chains.
    • Unlike Shutter’s ordering-focused framing or drand’s public-beacon framing, Blocklock is a narrower delivery rail for condition-triggered decryption. That lower-middle position makes it a strong comparison baseline for auctions, delayed reveals, and encrypted-mempool experiments.
    • Blocklock belongs in the active corpus because it preserves a distinct conditional-encryption layer that would be flattened if kept only under dcipher broadly or only as a developer library.

Internal linkages

Graph View

Backlinks