Any account can appear and should be activated in domain

[s8sato]

I think the point is the domain membership screening.
How should a new account apply for and be allowed to join a domain?
In terms of authority, there will be a gap between transferring one's own asset to a new account and registering a new account, especially in "private domain".
So as you pointed out, the admission process should be managed by a different authority than the sender of the first transaction that mentioned the account.

One idea is that each domain has its own admission policy as a trigger that "activates" a new account in response to the account creation event.
Admission policies may vary from domain to domain e.g.

• No screening
• Wait for approval of the domain owner
• Wait for approvals of m of n domain members

In any case, as I implied, I'm going to create a new issue on this and remove the 2nd commit from this PR

Originally posted by @s8sato in #4411 (comment)

[s8sato]

Related discussions so far:

• feat!: authenticate personal accounts by ID #4411 (comment)
• feat!: authenticate personal accounts by ID #4411 (comment)
• feat!: authenticate personal accounts by ID #4411 (comment)