Ninth Circuit Reverses Order Denying Motion to Compel Arbitration Concluding Delegation Provision Is

Noting the court was deciding, as a matter of first impression, “what a party must do to specifically challenge a delegation provision and what a court may consider when evaluating this challenge,” the Ninth Circuit Court of Appeals, in Bielski v. Coinbase Inc., reversed a district court order that denied defendant Coinbase’s motion to compel arbitration.

Coinbase is an online cryptocurrency exchange. Plaintiff Abraham Bielski maintained an account, or “digital wallet,” with Coinbase that allowed him to store and transfer cryptocurrency in and out of his account. Before opening his account, Bielski was required to accept Coinbase’s user agreement, which included a three-step process to resolve any disputes: (i) an “informal complaint process,” which involved contacting Coinbase and attempting to resolve the dispute amicably; (ii) a “formal complaint process” involving a written complaint; and (iii) arbitration of the dispute pursuant to an arbitration agreement. The arbitration agreement included a “delegation provision” providing that disputes arising out of the agreement including the “enforceability, revocability, scope, or validity” of the agreement were delegated to the arbitrator.

Shortly after opening his account, a dispute arose involving an unauthorized transfer from Bielski’s digital wallet. Bielski “live chatted” with company representatives, called the company hotline, and wrote two letters requesting help to recover his funds. He then filed a lawsuit under the Electronic Fund Transfer Act and Regulation E alleging Coinbase failed to investigate the unauthorized transfer of funds from his account. Coinbase moved to compel arbitration of the claims under the user agreement. The district court denied the motion to compel concluding the arbitration agreement and the delegation provision were “inseverable” and unconscionable.

On appeal, Bielski argued that the delegation provision and the arbitration agreement were unconscionable and unenforceable. The court first addressed what a party must do to challenge a delegation provision, and what a court may consider in evaluating the challenge. Coinbase argued on appeal that Bielski did not do enough to challenge the delegation provision. The court rejected this argument, concluding that by specifically objecting to the delegation provision in his opposition to the motion to compel, Bielski sufficiently challenged the provision. The court noted its approach was consistent with decisions in the Second, Third, and Fourth Circuits, but contrary to the approach in the Sixth and Eleventh Circuits, which require a party to provide “more substance in their delegation provision challenge.” The court then addressed what a court may consider in evaluating the challenge, concluding that “a court must be able to interpret that provision in the context of the agreement as a whole, which may require examining the underlying arbitration agreement as well.” Finally, the court rejected Bielski’s argument that the delegation provision was unconscionable, held that the district court erred in refusing to enforce the delegation provision, and reversed the order denying Coinbase’s motion to compel arbitration.

Bielski v. Coinbase, Inc., No. 22-15566 (9th Cir. Dec. 5, 2023).

©2026 Carlton Fields, P.A. Carlton Fields practices law in California through Carlton Fields, LLP. Carlton Fields publications should not be construed as legal advice on any specific facts or circumstances. The contents are intended for general information and educational purposes only, and should not be relied on as if it were advice about a particular fact situation. The distribution of this publication is not intended to create, and receipt of it does not constitute, an attorney-client relationship with Carlton Fields. This publication may not be quoted or referred to in any other publication or proceeding without the prior written consent of the firm, to be given or withheld at our discretion. To request reprint permission for any of our publications, please use our Contact Us form via the link below. The views set forth herein are the personal views of the author and do not necessarily reflect those of the firm. This site may contain hypertext links to information created and maintained by other entities. Carlton Fields does not control or guarantee the accuracy or completeness of this outside information, nor is the inclusion of a link to be intended as an endorsement of those outside sites.

Perspectives on reinsurance and arbitration law and practice.

Recent Posts

Editorial Contacts

Archives

Jump to Page

Carlton Fields, P.A. Cookie Preference Center

Your Privacy

When you visit our website, we use cookies on your browser to collect information. The information collected might relate to you, your preferences, or your device, and is mostly used to make the site work as you expect it to and to provide a more personalized web experience. For more information about how we use Cookies, please see our Privacy Policy.

Strictly Necessary Cookies

Always Active

Necessary cookies enable core functionality such as security, network management, and accessibility. These cookies may only be disabled by changing your browser settings, but this may affect how the website functions.

Functional Cookies

Always Active

Some functions of the site require remembering user choices, for example your cookie preference, or keyword search highlighting. These do not store any personal information.

Form Submissions

Always Active

When submitting your data, for example on a contact form or event registration, a cookie might be used to monitor the state of your submission across pages.

Performance Cookies

Performance cookies help us improve our website by collecting and reporting information on its usage. We access and process information from these cookies at an aggregate level.

Powered by Firmseek