KYB for Non-Custodial Wallets in DeFi Onboarding: Anyone Cracked This?

asked by u/kavya_k · 3d · 1 answers

Hey everyone,

I've been wrestling with a particular challenge related to KYB for DeFi onboarding, specifically when dealing with entities that operate primarily with non-custodial wallets. We're looking at a scenario where a corporate entity, say a DAO or a fund, wants to access institutional DeFi protocols through a smart contract wallet like a Gnosis Safe. The issue isn't just the individual behind the wallet – we have processes for that – but how to effectively perform the 'Business' part of KYB.

Traditional KYB checks rely heavily on registered addresses, corporate documents, directorships, etc. But for many native crypto entities, this isn't always neat. You might have multisig signers globally distributed, no central legal entity in a conventional sense, or the 'business' itself is essentially a smart contract.

Are there any emerging best practices or solutions out there that folks are exploring or have successfully implemented for robust KYB when the counterparty is fundamentally a set of blockchain addresses and not a traditional corporation with clear legal registration? We want to stay compliant, but it feels like the existing frameworks weren't designed for this. Any thoughts or experiences would be hugely appreciated.

Join the full discussion

Top answers

  • u/hferrari· 5 pts· 3d

    This is a really tough nut to crack. We've explored using attested credentials for the entity itself, but the 'know your business' part really struggles when beneficial ownership is so fluid and often anonymous within certain DAO structures. Have you looked into any solutions that might integrate with soulbound tokens or similar identity primitives?

Related questions