Kevin shares his journey in fintech and Bitcoin infrastructure, revealing why a governance-first design is key to true security and operational control.
Kevin, could you share your journey in fintech and digital asset infrastructure, and what led you to your current role as CEO at Liana?
My background has always sat at the intersection of security and financial infrastructure. I’ve worked around Bitcoin and digital asset systems long enough to see the same pattern repeat: people underestimate how different bearer assets are from traditional financial instruments.
In traditional fintech, we’re used to accounts, intermediaries and reversibility. Bitcoin removes those layers. It forces you to confront what control actually means.
What led me to build Liana Business was the gap between how organisations think about governance and how Bitcoin actually enforces it. There was a clear need for infrastructure that translates institutional control requirements into protocol-level enforcement, rather than relying on policy documents and hope. That’s what we focus on: aligning operational governance with how Bitcoin really works.
Many fintech platforms focus on convenience and user experience. Why do yout think these models struggle when it comes to handling bearer assets like Bitcoin?
Convenience is not inherently a problem. The issue is when convenience masks control. Most fintech platforms abstract complexity away from the user. That works well for account-based systems where reversibility and dispute resolution exist. With bearer assets like bitcoin, abstraction can remove visibility into who actually controls funds.
If a user does not control the keys, they do not control the asset. When platforms optimise purely for frictionless experience, they often centralise custody in the background. That centralisation reintroduces counterparty risk, which is precisely what Bitcoin was designed to remove.
In fintech, platform security often feels robust to users. How does this perception diverge from the realities of operational control, especially when dealing with self-sovereign assets like Bitcoin?
Security optics and operational control are not the same thing. A platform may have strong authentication, polished interfaces, and compliance certifications. But if asset control ultimately depends on a single entity’s backend infrastructure, then operational risk is still concentrated.
With Bitcoin, strong security posture must extend beyond perimeter defence to governance architecture. That includes how approvals are enforced, how recovery works, and what happens if internal roles change. The perception of security often focuses on preventing hacks but proper operational control focuses on preventing structural failure.
What are some of the most common pitfalls fintech builders encounter when attempting to provide “secure” Bitcoin custody for users?
The most common mistake is assuming traditional custody patterns apply unchanged.
Builders often replicate account-based logic like internal ledgers, pooled custody, backend-controlled key management, and then layer user interfaces on top. That approach can appear secure but does not fundamentally align with Bitcoin’s architecture.
Another pitfall is relying solely on threshold multisignature without carefully designing recovery and governance logic. Not all multi-signature structures are equally robust. Without structured fallback conditions and clear separation of duties, complexity can increase risk rather than reduce it. Security in Bitcoin is about policy design as much as cryptography.
How can studying Bitcoin’s infrastructure inform better security practices in conventional fintech platforms?
Bitcoin forces discipline at its core. It operates on transparent, deterministic rules. And because of this there is no discretion, no override function, no quiet administrative interventions. That design encourages clarity around authority and responsibility.
Fintech platforms can learn from that. Clear segregation of duties, minimising implicit trust assumptions, and designing systems that behave predictably under stress are principles that extend beyond digital assets. Bitcoin is uncompromising about finality and that mindset encourages stronger internal control frameworks.
Bitcoin enforces accountability through transparent, auditable rules. How does this contrast with typical centralized fintech models, and what lessons should builders take away?
In most centralised fintech systems, governance lives in internal databases and policy documents. Enforcement of this governance depends on internal processes and human oversight.
Bitcoin enforces rules at the protocol layer, so if a transaction does not meet predefined conditions, it simply does not execute. There is no escalation path and for this reason the lesson for builders is that structural enforcement reduces ambiguity. When governance is encoded into system logic rather than layered on top, operational risk decreases. Transparency and verifiability become inherent features, not afterthoughts.
What are the operational or systemic risks fintech platforms often overlook when abstracting away control from users?
Vendor concentration risk is frequently underestimated. When custody is centralised, access becomes dependent on infrastructure, regulatory positioning, and operational continuity of a single provider. Availability risk is also overlooked. In digital asset markets, being unable to move funds during volatility can be as damaging as loss.
Finally, governance fragility is often missed. If key management or approval structures are unclear, internal disputes or personnel changes can create real operational disruption. Abstraction simplifies user experience, but in many ways it can critically obscure accountability.
If fintech platforms took cues from Bitcoin’s uncompromising approach to security and ownership, what would change in their design philosophy or user experience?
There would likely be more transparency around who controls assets and how approvals are enforced. User experience might shift slightly from invisible control to clear control. That does not mean adding friction unnecessarily, but it does mean making governance visible and understandable. Design philosophy would move toward minimising hidden dependencies and ensuring that no single failure, human or technical, can compromise the system.
Are there common misconceptions about integrating Bitcoin into mainstream fintech that you think need to be challenged?
One misconception is that integrating Bitcoin automatically requires sacrificing usability. Another is that self-custody equals single-key risk. Properly designed custody distributes control across roles and enforces policy at the protocol level. It is possible to achieve both resilience and governance clarity. The real misconception is that Bitcoin custody is primarily a technical problem. It is a governance problem first.
Finally, what advice would you give fintech entrepreneurs who want to responsibly integrate with bearer assets like Bitcoin while maintaining true security and accountability?
Governance. Governance. Governance. Start with governance, not user interface. Put time into mapping internal approval structures, role segregation, and recovery procedures before writing code. Design custody architecture that aligns with those structures at the protocol level. Avoid over-reliance on marketing terms like insured or institutional grade. Instead, ask: who controls the keys, how are approvals enforced, and what happens under stress?
Bearer assets demand deliberate design. Security cannot be outsourced entirely. It must be engineered.
Quote: “Bearer assets like bitcoin force fintech builders to confront a hard truth: risk can’t be outsourced, only engineered.”
