Regarding JetainM and sudo both wanting mi.
Toast may override my decision or I may change it if I decide my facts are incorrect.
JetainM is a keyhotee founder. I am not sure if sudo is, but sudo's claim for 'mi' is because he registered 'mi' as delegate on btsx. This was after JetainM's post and realizing that registering as delegate meant it would be on DNS blockchain.
JetainM is both keyhotee donator and requested 'mi' on new blockchain first, so I am giving JetainM 'mi'.
I'm sorry sudo, I know it doesn't seem fair but I am at a loss as what else to do. I think I3 wants to honor the keyhotee founders, and JetainM did ask first to have it on new chain.
i got the infomation(delegate would be transfer to dns) form qq&www.bts.hk, prepared to register two or three character id to be delegate for saving time
I am busy on Moving the office those days,when i have time to register the short id,conflict happened.
so it will be funny
xiaomi in btsx&dns will belong to the same person.
mi in btsx belongs to me&in dns, it's not。
xiaomi is similar XiaoMi
not mi
>> blockchain_get_account xiaomi
Name: xiaomi
Registered: 2014-07-19T22:41:00
Last Updated: 73 hours ago
Owner Key: BTSX4wo1Hagazg17ffgonZRuCmDwWfk7uTC4A8gjhenw69wAtU2La1
Active Key History:
- BTSX4wo1Hagazg17ffgonZRuCmDwWfk7uTC4A8gjhenw69wAtU2La1, last used 22 days ago
ID NAME (* next in line) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
============================================================================================================================
1744 xiaomi 0.0000000000 % 0 0 N/A 50 % 0.00000 BTSX NONE
Public Data:
{
"gravatarID": "8e5bca264f2f60a4a8a408c93065a869"
}