DNS and frontend trust assumptions for OISY and security-critical ICP dapps

I’m currently building a crypto wallet map, and OISY increasingly looks to me like the golden path between traditional custody and conventional self-custody: strong security without giving up mainstream usability.

This thread is an important area where I want to keep that assessment honest. The DNS/frontend trust assumption is still a meaningful weakness, even if the custody layer itself is extremely strong.

It also feels like another argument for CNS and a native .icp domain. Could an oisy.icp identity, cryptographically bound through CNS to the actual OISY canister, substantially reduce this remaining trust surface?

Not necessarily a complete solution by itself, but it seems like a clear direction toward making the frontend and naming layer match the security of the custody layer underneath.

Curious how others see this.

Related: