(DRAFT!)
As long as an email domain e.g. @example.com didn't register public key of Doichain node inside a DNS TXT value like so:
doichain-opt-in-key= or
doichain-opt-in-provider=
all opt-ins will be validated through the public key of the so far centralized fall back server.
As soon as a email domain name registers it's Doichain node. We need a RPC call which allows
transfering / rewriting DOI permissions onto for the new Doichain address.
Implement new RPC call "opt-ins/transfer" (parameter email domain, signature)
Request public key of email domain from DNS and generate the Doichain address for it
Get all DOI permission nameId's of a target-domain (this might be difficult, as we do not store recipients emails nor domains on the fallback server - need research / more implementation needed)
Get all transactions which holds the SOI permissions of this email domain and send it back to the new validator.
Make sure the validator is the right validator by checking the signature of the transferred email domain with the public key in the DNS of the email domain.
(DRAFT!) As long as an email domain e.g. @example.com didn't register public key of Doichain node inside a DNS TXT value like so:
As soon as a email domain name registers it's Doichain node. We need a RPC call which allows transfering / rewriting DOI permissions onto for the new Doichain address.