Pith. sign in

REVIEW 1 cited by

Blockchain and Trusted Computing: Problems, Pitfalls, and a Solution for Hyperledger Fabric

Not yet reviewed by Pith; the record is open.

This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.

SPECIMEN: schema-true, not a live event

T0 review · schema-true

One-sentence machine reading of the paper's core claim.

pith:XXXXXXXX · record.json · timestamp

arxiv 1805.08541 v1 pith:MSEEDF5G submitted 2018-05-22 cs.DC cs.CR

classification cs.DCcs.CR
keywords blockchainexecutionblockchainsteesapplicationcannotfabricapplications
verification ladder T0 review T1 audit T2 compute T3 formal
0 comments
read the original abstract

A smart contract on a blockchain cannot keep a secret because its data is replicated on all nodes in a network. To remedy this problem, it has been suggested to combine blockchains with trusted execution environments (TEEs), such as Intel SGX, for executing applications that demand privacy. Untrusted blockchain nodes cannot get access to the data and computations inside the TEE. This paper first explores some pitfalls that arise from the combination of TEEs with blockchains. Since TEEs are, in principle, stateless they are susceptible to rollback attacks, which should be prevented to maintain privacy for the application. However, in blockchains with non-final consensus protocols, such as the proof-of-work in Ethereum and others, the contract execution must handle rollbacks by design. This implies that TEEs for securing blockchain execution cannot be directly used for such blockchains; this approach works only when the consensus decisions are final. Second, this work introduces an architecture and a prototype for smart-contract execution within Intel SGX technology for Hyperledger Fabric, a prominent platform for enterprise blockchain applications. Our system resolves difficulties posed by the execute-order-validate architecture of Fabric and prevents rollback attacks on TEE-based execution as far as possible. For increasing security, our design encapsulates each application on the blockchain within its own enclave that shields it from the host system. An evaluation shows that the overhead moving execution into SGX is within 10%-20% for a sealed-bid auction application.

Discussion (0). Continue with ORCID to comment.

Forward citations

Cited by 1 Pith paper

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score. Full citation record

  1. ODYSSEY: Reestablishing Confidentiality in Confidential Blockchain via Delegated Execution

    cs.CR 2026-06 unverdicted novelty 5.0 of 10

    ODYSSEY mitigates execution-inference and execution-replay attacks in confidential blockchains via delegated execution to trustees, with a FISCO BCOS prototype achieving ~4k TPS and 0.4-0.5s latency in a 3-node WAN setup.

Pith tools