Go back to first post of this thread. You have all the links there.

wgd
What is wrong with current algorithm?

startsts
This is reply I got from dev about difficulty change:

That sort of thing is unavoidable. Bad algorithms can exaggerate the effects of it, but your algorithm seems fine - maximum adjustment of 10% upward. Changing algorithms wouldn't stop this from happening. You just need more hashpower to limit the effect of what this miner is doing.

Leave 30 seconds between blocks?

There will be a new version of wallet (fork) probably next week.

Nobody is asking you to do anything with that attitude.

I will try my way and you can try yours. People will decide who to follow.
I am not angry, I just don't like your arrogant attitude.

You call yourself a helping hand?!

I PM'd you because you were not posting any news. I was not expecting this answer so I had to share it with others.

We don't need this kind of help. You are just trying to help your self.

OK so here is the reply I got from our "very concerned" member TheKingInYellow (look at few posts above) on my question about finding developer:

"I wasn't aware the network was in such dire straights. I've got some messages out to PoS developers I know. But, I will remind you, it's in my best interest to let Q2C die for a time and drop to 1 sat so i can buy it all up for nothing. So I'm not in a very big hurry, I will let you know about a timeframe if anyone is interested."

 

I think for now the best solution is to continue as it is now with the correction of difficulty re-targeting more often.
After that we can try to find someone who is willing to do the conversion and properly plan it.

I have absolutely no problem with this
Thanks for getting involved. Just don't fuck up the coin with this conversion to hybrid.

I don't know why you are making drama over all this. Coin is working fine like it is. I must say I didn't see an hour between block but even it is like that it is occasional.

If you have solution on how to handle difficulty please tell us and if people agree, we can change it.

I tried with few developing teams and none of them want to accept the job of converting to PoS/PoW hybrid.
Correct me if I'm wrong, but looking at the pro's and con's for both PoW and PoS, this conversion would just make the coin "greener".
Considering that this PoW/PoS area is undefined on how exactly it supposed to work, I think we should stick to PoW until things clear up a little bit.

The plan is to go to POW/POS combination as transition to POS.

I am looking for developer as we speak. The plan is to go for PoW/PoS combination for transition period and after that to PoS.

What about PoW/PoS combination?

I think it's fair at least as a transition to PoS.

There should be around 180 000 left if total supply is still 248 million.
Considering that a big part of that is forever lost (people just deleted wallets) we could say there is a lot less in total available.

I would suggest to prolong period of 1 Q2C reward and from now on start halving every 2 000 000 blocks (aprox 2 years). After it reaches 0.01 Q2C we leave reward like that for indefinite time.

Please post your suggestions so we can find the best solution for the future of Qubitcoin.

Once we find the best solution, I will find developer to implement the changes.

Also if you have some idea on how to start a service which would use Q2C as a means of payment feel free to suggest.
I was looking at idea of exchanging Q2C for coupons or vouchers for ebay.

Thanks

 

It works for me...

http://qubitcoin.cc/

In here you will find the list of nodes which were active in last 24h.
http://qubitcoinxplorer.cc/network

My bad   

Thanks for the effort but I think that there is no point in having more than one exchange for now.

Which site are you talking about?

Trend on Cryptopia (last two weeks) looks promising

https://www.cryptopia.co.nz/Exchange/?market=Q2C_BTC#
 

This node 188.2.118.59 is mine and it is online all the time. I am currently connected to 4 nodes from your list so something is wrong on your side. Check your firewall settings for ports (router).
Enter node IP only from console without port number.