Account names - length and characters

[kroggen]

Proposals

1. Allow account names with less than 12 characters (the engine can pad up to 12 characters when making a lookup, if needed)
2. Allow . or - or _ as word separator
3. Also, if possible, allow names with more chars, like 20 or 30
4. Allow to remove/unset a name. This also allows other user to use the name later
5. Allow to set a name to a smart contract in a single call (second argument to v1createName)
   On this case it should:
   A. be owned by the contract itself, the creator has no longer control over it
   B. be owned by the creator
   C. the creator becomes an operator
   D. the contract becomes an operator (can remove, update or transfer it)

[kroggen]

6. Limit the names to lower case letters, to avoid confusing I and l, O and 0
   In this case it should throw an error if upper case letters are used
   Problem: what if used to map token symbol to address? like USDT
7. Allow unicode characters (UTF-8) (may affect the above)

[kroggen]

8. Allow smart contracts to transfer names
9. Approvals: approve another account as an operator, to transfer the name
10. Add method to check the ownership of a name (at least to smart contracts, like name_service.owner() or alike

[kroggen]

11. Remove charging for transferring a name (v1updateName). Currently it is charging twice when setting a name to a smart contract
12. Expiration and Renewals? What if the owner dies? Or the access to the private key is lost?

[kroggen]

SECURITY

Regarding a name pointing to a smart contract, we can trust it (that the name will not change and point to another address) when:

1. the owner of the name is the contract itself, not an EOA or another contract
2. the name has no operator
3. the contract has no code to change or transfer it
4. the current time is not near or after the expiration time (if this is enabled)

Note that a name could point to a smart contract in 3 ways:

1. owned by an EOA
2. owned by the contract itself
3. owned by another contract

Another option is when the name is owned by a central authority in which we can trust.
It could be a smart contract managed by a DAO.
On this case the DAO could update the name to another address if needed.

[kroggen]

SCENARIO 1: New method

The owner can point a name to any address and continue having the ownership over the name

---

SCENARIO 2: Old method

When a name is updated to point to a new address, it is also transferred to that address

---

SCENARIO 3: Delay on transfer and update

Do not allow update and transfer of names on the same block. It must be an asynchronous operation to avoid sandwich-type exploits

---

SCENARIO 4: Controlled by DAO

Some names (or all) are controlled by a DAO, requiring confirmation from participants

Also use AI with web access to check if the name is used by some cryptocurrency on the top 1000 list

May also include auctions / bidding on names

EOA accounts using lower case characters, contracts can use upper-case chars for token symbols