Meanwhile I've updated my P2Pool nodes and added the 4th one. So, there are 3 nodes in different U.S. locations and 1 node in Europe. There are no fees, just a small 1% development donation.

Phoenixcoin P2Pool

I suggest you all to withdraw coins from Cryptopia to your local wallets and stake them. You support the network this way and earn a decent reward as well. I'll keep you informed on the coin swap procedure in advance. I want this project to succeed just like all of you. It's a pity we haven't got much resources to accelerate development unlike many of those ICO token start-ups, but nevertheless.

If I want PXC to grow, I need more development first. Exchanges come and leave. They don't add a lot of actual value to a coin. They are just instruments of trade.

I don't quite understand your question.

Is there any substantial demand for such a wallet? It costs $70 each.

There's always a way. What would you like to do? Maybe PM me if you are not comfortable to talk about it in public.

BTW please subscribe to our official Twitter and Facebook pages. All important news, updates, etc. will be posted there as well.

Twitter

Facebook

Orbitcoin v1.6.1.0 is available now! Upgrade isn't required, though advised. There are new features and performance improvements.

The wallet is able to synchronise time with over a hundred NTP servers worldwide. By default, it picks a random server from the built-in list and syncs time every few hours. Although you can specify a particular server or even do the synchronisation manually using the new RPC ntptime.

The wallet is able to encrypt/decrypt text messages or hex data using private/public keys in your wallet. For example, if you encode a message with someone's public key, only this person can decode it with his private key. You can use encoded data in transaction comments, emails, notes, etc. See RPC encryptmessage, decryptmessage, encryptdata, decryptdata. The next objective is to encrypt/decrypt whole files with your wallet.

The wallet supports dual threaded stake mining. It isn't an issue for most users to run a single threaded stake miner, but wallets with hundreds or even thousands of inputs may benefit from multiple threads since modern CPUs are multicore anyway. Of course, those two threads shouldn't be working on the same data, so there is a new option -stakefence defining which inputs are going to either thread. It's set to 360 hours (15 days) by default. Those inputs younger than 360 hours are processed by the 1st thread and the remaining ones by the 2nd. If you set -stakefence to zero, it disables the 2nd thread.

The wallet supports watch only addresses. It means you can put any address into your wallet, see how many inputs are there, watch them accumulate or move. You cannot spend these coins because there is no respective private key in the wallet. Although no one can steal these coins for the same reason. See RPC importaddress, importpubkey

Our P2SH aka multisig addresses have got a better prefix. It used to be legacy '4', now 's' for "script". Redeem scripts are not affected by this prefix change. If you don't use P2SH, you have nothing to worry about anyway.

I have enquired Cryptopia on the delisting matter. One customer support agent has given me a tinned response and suggested to ask the coin listing team. Those have given me the same tinned response and no more communication. They refer to their delisting policy, but cannot tell what part of it has to do with Halcyon being delisted!

It was unexpected to say the least. Yet it doesn't change my plans.

I've just tagged the v1.1.0.3 maintenance release and uploaded the 32-bit and 64-bit Windows binaries. This update comes with a much better block explorer I've written earlier for Orbitcoin. There is also support for the Network Time Protocol (NTP) which allows for the best possible time synchronisation.

Pools may be down from time to time. They don't run on mission critical servers with redundant uplinks. However TBF is a reliable one in general.

v0.7 is in progress, though expect v0.6.6.2 sooner because some steps should be taken for the ease of migration. In particular, I'm going to drop support for the legacy Litecoin magic number. We have our own since v0.6.6.0.

I've just pushed a patch adding the NTP (Network Time Protocol) support for precise time synchronisation. The next patch will do a dual threaded stake miner. We shall have a new release after that.

I'm not aware of a good way to combine two projects as such. Much of my work can be shared among my projects. I never trade security for features, performance, etc. None of the coins under my management have ever been successfully 51% attacked.

Maybe you do your research first? The particular vulnerability was intoduced to Bitcoin v0.14 in 2016: https://github.com/bitcoin/bitcoin/pull/9049
This code appeared first in Bitcoin v0.4 in 2011: https://github.com/bitcoin/bitcoin/pull/443

We have it in place still.

I work on the project as my free time allows. I don't make time lines.

Your exchange looks good. A UK location is a plus. Submitted the dev form.

UPDATE: There is a 0.02 BTC fee to get listed. Anyone willing to contribute anything?

The domain name has been renewed for another year. It's that kind of things I routinely forget to do in time.

The miner can be customised to support ASICs as well. NeoScrypt may also evolve in the future.

There are a few ways to send a block to the daemon. How do you do it?

The old bootstrap was left on the old VPS which is offline currently. I haven't uploaded a new one yet. Although the client can sync on its own in a single day online give or take.