Have to think of the UX regarding the Home page, the Search feature, ... and the technical implications to manage the different cases (verida.one domain vs verida.one sub-domain vs self-hosting with custom domain).
Very roughly: we could have a check on the domain. If it's a sub-domain of verida.one, we could adapt the router so that only the Profile page and sub-pages (collectible list, ...) to be available and fixed on a single identity (resolved by the sub-domain). It would also disable some features (search, ... depending on our UX reflection).
If self-hosted, we could have an environment variable to define the DID instead of resolving it from the sub-domain.
Have to think of the UX regarding the Home page, the Search feature, ... and the technical implications to manage the different cases (verida.one domain vs verida.one sub-domain vs self-hosting with custom domain).
Very roughly: we could have a check on the domain. If it's a sub-domain of verida.one, we could adapt the router so that only the Profile page and sub-pages (collectible list, ...) to be available and fixed on a single identity (resolved by the sub-domain). It would also disable some features (search, ... depending on our UX reflection). If self-hosted, we could have an environment variable to define the DID instead of resolving it from the sub-domain.