Quote from: Come-from-Beyond on January 29, 2014, 12:16:11 PM

Quote from: pandaisftw on January 29, 2014, 11:54:25 AM

Quote from: NxtChg.com on January 29, 2014, 11:20:56 AM

Not to mention that now we have a whole bunch of clients and need to somehow switch to the new format.

Well, at least for this part, jean-luc said he would support whatever format the community came up with, right? So whenever you and ricot finish your RS implementation (how is that going btw?) I'm sure we can seamlessly integrate it into NRS and all other clients.

It still doesn't make sense coz we move from signing transactions on NRS to signing on client side.

Ah, right, I forgot NRS is being removed. Yes, implementing this client-side.

Quote from: NxtChg.com on January 29, 2014, 12:35:46 PM

Quote from: pandaisftw on January 29, 2014, 11:54:25 AM

So whenever you and ricot finish your RS implementation (how is that going btw?) I'm sure we can seamlessly integrate it into NRS and all other clients.

The code is done, I am waiting for people to review it.

Then we must have another, legitimate vote on the alphabet to use and we don't have any legitimate voting system yet. Even BTT removed the newbie restrictions...

And I am not sure about "seamlessly". This will be a big change, which needs to be synchronized across all clients and sites.

Clients can simply accept both old and new addresses. But the client will tell new users to use the new address scheme because it is safer. Eventually, most people will move to the new standard, if it proves superior, but we will still have legacy support for those few stubborn ones who like their old addresses (perhaps vanity). Of course, if you run an exchange, you can demand your customers to use RS format addresses only, so you don't have to deal with legacy addresses.

EDIT: How will this affect API calls?