This is a good thing, as it will help sell more domains and make the team profitable.
Our biggest problem now is that the team is too poor, so no more developers are willing to develop for the project. 
The proposal is that it goes towards the community fund that is managed by the Community Fund Committee and not the development core team fund.
Some progress happening here!
Core team has decided that it’s best that only the owner of a spark address can register an alias to it. This is to prevent troll registrations on addresses that you don’t control. As such when registering an address, you will need to post a proof of ownership together with the registration.
We have figured out a relatively easy way for people to transfer ownership of aliases with its remaining subscription over.
It would require the recipient to share certain data to prove ownership etc before the transfer can happen.
We are also proposing a nominal ‘transfer fee’ that would go towards the Community Fund for every transfer something like 1 FIRO for normal transfers and 10 FIRO for the one letter transfers.
The idea is that the more ‘apps’ like this we build, the more sources of income the Community Fund can have beyond just block rewards.
4 Likes
Are some keywords banned? For example, Binance, Reuben
I don’t think we’ll ban those. It’s a bit of dangerous for us to put up banlists since then there would be an obligation for us to police what sort of names are acceptable or not. The core team believes this would be a point of centralization and one that can be used to show that we exert control over the protocol. We will put up the usual disclaimers so that people know that just cause someone has a brand name, doesn’t mean they represent it.
2 Likes
Can we have both options?
When it comes to payments. I actually think there is value in having a permanent option. I’d feel better knowing that once I buy it, it’s mine and I can forget about it.
To avoid squatting, make it non-transferable, but and charge more.
For example, say you have a youtube channel or something that accepts Firo donations, and you accidentally let your name expire and someone else re-registers it. Does that mean they would end up receiving all my funds that viewers send to @cooldude not knowing cooldude doesn’t own the name any more?
Perhaps at least have a 100 year option incase someone dies with the name, and the name isn’t lost forever.
Other than that, I actually really like the idea. It would be useful when sending money between friends and family etc.
1 Like
Aeternity（AE）早就实现了这个功能，当时这个功能也被当作AE的一个重大亮点来推出，但现在的AE基本上已经是一个即将死亡的项目。所以，我不认为这个功能会给Firo带来什么变化。
It’s not about what is good for ‘hype’ but what adds utility to the project. The work required isn’t very long so I think it’s a worthwhile feature to have.
A quick update here. We are almost ready to deploy this on devnet. After devnet it would be to testnet then to mainnet.
It would require a hard fork but I don’t think it would be a contentious one given the added utility of this feature.
Following @Fiendish’s concerns we would have no max limit for registration so people can choose to pay upfront if they want a lot of years.
Registration fee for 1 year would still remain like this:
One letter: 1000 FIRO
Two letter: 100 FIRO
3-5 letters: 10 FIRO
6 letters and above: 1 FIRO
4 Likes