Should solve #1. Users register mappings like normal, but the Numerifides protocol allows a user-specified address to be used as an input to an update transaction. Note that the original funds are still locked up, this is because a lot of the deterrence for namesquatting comes from the fact that committed funds cannot be spent before the CSV time expires.
For honest users, this means one can register a mapping in one block, update it in the next, and then update it a third time in the subsequent block.
Should solve #1. Users register mappings like normal, but the Numerifides protocol allows a user-specified address to be used as an input to an update transaction. Note that the original funds are still locked up, this is because a lot of the deterrence for namesquatting comes from the fact that committed funds cannot be spent before the CSV time expires.
For honest users, this means one can register a mapping in one block, update it in the next, and then update it a third time in the subsequent block.