Abstract
Purpose The US Commodity Futures Trading Commission (CFTC), to date, has not directly addressed how liability for Commodity Exchange Act (CEA) violations involving blockchain or distributed ledger technology should be allocated among the various parties involved in the distributed ledger network, such as the network itself, persons running consensus nodes, developers building applications on the platform, and businesses and end users using such applications. This article discusses recent statements by CFTC Commissioner Brian Quintenz regarding this issue and the approach that the CFTC may take going forward. Design/methodology/approach This article examines the allocation of liability in the context of smart contracts that may violate the CEA. The article discusses how the CFTC, despite its significant focus in recent years on virtual currency and blockchain, has not addressed the issue of liability allocation directly. Recent remarks by Commissioner Quintenz may shed light on the CFTC’s future approach. Findings This article finds that liability allocation questions may become increasingly pressing as smart contracts that potentially violate the CEA proliferate, possibly exposing a broad range of parties involved in a distributed ledger network to liability. To the extent that Commissioner Quintenz’s recent remarks are indicative, the CFTC ultimately may adopt a foreseeability standard in determining liability. Practical implications Applications of distributed ledger technology (DLT) are ever-expanding, continually posing novel CFTC regulatory issues. This is especially the case with respect to smart contracts that may be subject to CFTC jurisdiction. Parties involved in such applications should be mindful of potential liability. Originality/value Practical guidance from experienced finance and derivatives lawyers with strong CFTC expertise.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.