I am working on transferring the via funds to Romano. I think we're going to opt to timelock some/most of the coins as well.

XCH is up to Romano, I think it needs a rethink. The super fast blocktimes make it quite fragile. You can still operate it at command line, but whether it is worth spending development time right now is his decision.

So I've been talking quite a lot with Romano about his intentions and ideas for Viacoin which include recruiting more developers. He thinks it would be better for the long term prospects if I step aside from the project. Regarding ClearingHouse, I think the idea needs some extensive revision. There are technical issues with the way it is implemented that clash with short block intervals that make it problematic to operate in a stable and reliable fashion. It is still possible to operate it using the command line but the web wallet is extremely unstable. I think it would be best to leave it for the time being and give most attention to Viacoin. After careful consideration I think to agree with Romano that stepping aside would be for the best allowing for Romano to take over the project development with a clean slate. I already spend most of my  available time on Bitcoin Core so making this more formal transition will be a net gain for Viacoin. I can certainly be available for technical advice and opinion.

The twitter handle @viacoin is not fake!

Yes, this makes sense. I have added you.

I don't know about a "takeover", maybe you are reading too much into his comments. In any case, the 1 million via is still there unspent for bounty.

It would be great if you can help out. I agree that supporting payment channels and privacy enhancement is really important for digital currency.

In terms of what you can do, there are certainly quite a few updates that can be made to Viacoin, I mentioned some earlier in the thread. You're welcome to contribute as much or as little as you can.

Can you try again. If SSL doesnt work see if TCP protocol makes a difference.

Exactly this. If Viacoin rebases on top of 0.13 it will get a who bunch of new features like BIPs 9,68,112,113,141,143,144, libsecp etc. I'm not saying it will be easy, or that I will do it for sure. I would certainly like help in reviewing such a rebase because it's quite extensive and risky. There is no immediate need to make such an update though it would be a nice addition making Viacoin compatible with payment channel stuff like LN. In any case, Bitcoin Core 0.13 is unlikely to be released until I would have thought Aug/September so there's nothing to do until then anyway. In the end, I cannot force people to use via. But what is important is that things works. There's no chance anything can be successful if there is no security or stability.

On the other side of things, in hindsight, I'm not convinced 24 second block targets are such a good idea any more, certainly not at large scale. I do think the future is more in payment channels because payments are instant and in terms of usability, that seems like the more expected behaviour. But anyway, not really much we can do about that now.

Yes, that's certainly been my thinking. It certainly doesn't make sense to rebase until 0.13. There's a huge difference between 0.10 and 0.13 base. The rebase is not non-trivial due to the number of changes however and would need to proceed with caution.

No reason was given that I am aware of. I emailed Tristan the day they announced it to ask what the delisting criterion were. Another user here also did the same. Neither of us received a reply so far unfortunately. While they dont have to change their minds, you'd think they would at least reply...

Of this I am aware. However are you able to log in using your seed once the watch settings have been cleared (I am able to). Yuo said you cannot use the wallet with a watch only address in it, I have cleared it (the server stores preferences like labels etc for the wallet, but not the wallet details itself).

Please try now.
If not send me a PM with your email address.

Is this intermittent? I can log straight in.

The wallet has been working for ages, fixed since issues were reported. Note that Counterparty has not added the EVM yet, it's still in the works and fwiw, I am being consulted about some of the implementation details. I also provide the Bitcoin fork which powers the backend of Counterparty (which was ported from Via).

Your assumption is wrong. I only learned about it this morning when someone pasted Polo's tweet on Telegram.

What is the process for this? Maybe someone would like to take the initiative?

Nothing is stored on clearwallet.co. Your private keys are always with you browser side (derived from your seed passphrase) and never transmitted anywhere.#
However, you still use the system at your own risk as per the terms on the website which you have to agree to use use the "wallet" (wallet is a bad word since wallets store funds. In cryptocurrencies, wallets are actually keychains).

Not that I am aware of.

Viaectrum is a lite-wallet convenience and people are welcome to run their own vialectrum-server... it is a federated model afterall (same as Electrum). Otherwise run the full node for full security.

You are missing dependencies. You have to install slowaes (sudo pip install slowaes).

Vialectrum servers should be up.