What features could Galaxy Digital add to its over-the-counter trading desk to increase liquidity for digital assets?

Introduction

To increase liquidity for digital assets on Galaxy Digital's over-the-counter (OTC) trading desk, we need to identify and implement features that will attract more traders, improve transaction efficiency, and enhance overall market depth. I'll approach this challenge by first clarifying our current position, then analyzing user segments and pain points before proposing and evaluating solutions.

Step 1

Clarifying Questions

• Looking at the OTC trading landscape, I'm thinking Galaxy Digital might be facing competition from both traditional finance players and crypto-native platforms. Could you help me understand our current market position and who our main competitors are?

Why it matters: Determines if we need to focus on differentiation or catch-up features Expected answer: Mid-tier player with competition from both traditional finance and crypto-native firms Impact on approach: Would focus on unique value propositions that leverage Galaxy's strengths

• Considering the volatility in digital asset markets, I'm curious about the types of assets we currently support. Can you provide insights into our current asset offerings and any plans for expansion?

Why it matters: Influences the scope and direction of liquidity-enhancing features Expected answer: Support for major cryptocurrencies with plans to add more altcoins and potentially tokenized traditional assets Impact on approach: Would prioritize features that facilitate easier onboarding of new assets

• Given the regulatory landscape around digital assets, I'm wondering about our current compliance processes. How robust are our KYC/AML procedures, and are there any regulatory constraints we need to consider when adding new features?

Why it matters: Ensures any new features comply with regulatory requirements Expected answer: Stringent KYC/AML processes in place, with ongoing monitoring of regulatory changes Impact on approach: Would incorporate compliance considerations into feature design from the outset

• Thinking about user behavior, I'm interested in understanding the typical profile of our current traders. What's the split between institutional and high-net-worth individual clients, and what are their average transaction sizes?

Why it matters: Helps tailor features to the needs of our primary user base Expected answer: 70% institutional, 30% high-net-worth individuals, with varying transaction sizes Impact on approach: Would prioritize features that cater to institutional needs while also improving accessibility for individual traders