With the ever increasing list of cryptocurrencies (especially Proof-of-Stake coins) I was wondering if anyone had any tips or advice for people on how to safely, securely and reliably run all the wallets for themselves.

Hopefully this thread will grow into a good source of information for users in the future on how to handle their growing lists of desired wallets.

Novaexchange wallet is offline with no peers. My node wont sync either..

Anyone got a node list?

My miner is a solo CPU miner - I did send a private message for the O.P to be updated - but this hasn't been done yet. To give a rough idea of performance my old Xeon L5340 server is mining roughly 2 blocks a day at the moment while also acting as a file / media server.

What version of windows and what CPU do you have and I'll put a fresh binary build up

Basically I just need to know if its 64bit (if not why not ) and if your CPU is SSE4/AVX/AVX2.

I've got a few planned updates to the CPU miner - which should make it quite a bit faster.. My proof of concept in .Net currently sieves at almost the same speed as the previous C++ code I had on Github - so watch this space  

Thanks

And I have fixed it Here's my first block using the updated version of my jhPrimeMiner

http://www.bytestamp.net/blocks/qblo/en/2066210

My "mined" blocks are not even showing up as orphaned in the wallet - the debug log file shows the call to SubmitBlock, then sometimes some network related block activity but my mined blocks are never included in the blockchain. Clearly something is awry with the generated blocks - but the wallet is not rejecting them outright - so I'm not sure what lol

*EDIT* Nevermind! - I think I've found the issue in my coinbase generation

Devs - Are there any known issues with RPC GetBlockTemplate + SubmitBlock?

I've updated my jhPrimeMiner source to work with DTC - and have been trying to solo mine for the past few weeks - my miner is submitting blocks and getting success return values from the RPC - but the blocks don't seem to be accepted by the network

Ideas?

My actions are those of someone who has been burnt before in crypto and want my coins to be swapped and paid out to me - not left languishing in a queue somewhere.

*EDIT* Apologies but all the delays and "issues" with this launch have not exactly filled me with confidence and have certainly not left me with a warm cuddly feeling. Who is at fault here? Exchange says contact dev, everyone here says contact exchange.. yet another example of poor transparency and communication. I feel my comments are all justified based on communications / lack thereof.

Actually my intent is to hold - and while you are strictly correct that profits/losses only happen when you click sell - my immediate estimated portfolio value in BTC/$ will be down..

Market prices may not be in anyone's control - but if the swap had been properly organised and gone ahead as planned, then there would be no queued coins stuck in the swap process.

Additionally, if queued coins had been returned when the swap was postponed, this risk would have been mitigated and given users the freedom to handle the market swing as they see fit. Instead we're stuck hoping that we get our coins swapped at some stage while watching the markets trade and new swaps being paid instantly.

And guess what - the swap is active - but has issues!!

The swap is progressing for *NEW* swap requests - all while the earlier queued requests get overlooked and just sit there!

Oh and guess what - COLX has been dumped to pre-swap CV2 levels - so thanks to a botched swap me and a LOAD of other people are down at least 50% and still without our coins!!

Thanks dev - way to go!

How soon can we start crying scam / theft?

And the small swaps continue? What is going on? Please can you just come clean and explain why its so hard to deposit the premine and let the swap commence?

This swap should never have been allowed to start without everything being in place for it. There are now millions of CV2 locked in a queue and live markets continuing to trade.

Are you going to reimburse any losses if either CV2 / COLX are dumped to oblivion in the next few hours until the swap hopefully resumes?

What about the possibility for further delays?

Surely the moral thing to do here is to return all queued coins and get everything fully prepared for a proper swap?!

I understand that delays happen - but earlier communication would be greatly appreciated by all I'm sure. It was pretty obvious that there were going to be issues when 30mins before the swap there was still only "13.0" coins available for swap.. Why even let it open in the first place - all that's happened is mud on everyone's faces.

Now there are MILLIONS of CV2 added to a coin swap queue on NovaExchange that have "disappeared" and NovaExchange are going to take a pasting all day for yet another delay in this swap. It's not really fair on NovaExchange mods as they will be fielding claims of lost/stolen coins all day now.

So - as stated by NovaExchange - we need to check with you as to whats going to happen to the coins in the queue?
Will they still be swapped?
Are they lost?

Umm stupid question time!

On the "Information from devs" on the coinswap notice at NovaExchange it says:


According to the mods etc at NovaExchange, thats how many coins have been deposited for the swap.. Given the huge number of CV2 in circulation - thats gonna be 1 helluva short swap then!

Please tell me its wrong!!

A new prime chain is found with each block (~1minute). Within a prime chain, each number is prime and is larger than the one before. Currently we're looking for chains with at least 10 consecutive primes. The first prime in the chain is guaranteed to be at least 256bits long - but could actually be much much bigger depending on the primorial and multiplier chosen. Miners don't tend to look for larger primes as the maths involved takes longer - hence mining is slower. 

This is a very intellectually challenging coin to write a good miner for - there are several conflicting aspects that directly influence mining speed and pretty much every design decision becomes a trade off
For example:
1. Mining with a large primorial increases the base prime probability at the cost of fundamentally larger numbers that are slower to verify and work with.
2. Mining with lots of primes increases the sieve accuracy and reduces the number of false positives that then get passed through to chain length determination, but using too many primes above a certain threshold removes so few candidates that its actually faster to deal with false positives!

Without doing more exhaustive tests I couldn't say for certain, but I suspect the issue will be on-die cache differences within the CPUs..

A quick look at CPU-World (I didn't go any further so data could be wrong) indicates that despite the higher core count, the L1 data cache is smaller (half the size!) on the FX-4300 compared to the Athlon II..

FX-4300:
2 x 64 KB 2-way set associative shared instruction caches
4 x 16 KB 4-way set associative data caches

Athlon II 280:
2 x 64 KB 2-way set associative instruction caches
2 x 64 KB 2-way set associative data caches

If this is true, it will result in a higher L1 miss ratio - which could account for the performance difference. Having said all that, I'd be a bit surprised if that was the sole reason for a such a drastic difference in performance..

I've been running GMP6 in my Linux port for a few days now and I can confirm that on a Core2 it's about 5% faster. . Apparently AVX systems will see even more increase,  but I haven't been able to find some one capable of confirming this increase. .

Have you got details of any of those private miners. . Always keen to compare my miner to the competition. .

At a minimum you'd have:
JhPrimeMiner.exe -o http://ypool.net:10034  -u yourworker -p yourpassword

If you're using the computer for other things you may want to reduce the thread count. To do this add -t x where x is less than total cores in computer.

If Wps is very high > 100 consider a bigger sieve size.  Default size is approximately 2 Mill.  If Wps < 30 consider smaller sieve size.  Try keep sieve Size a multiple of 16384. Change sieve size with -s xxxxx

Finally use as high a  primorial as gives a decent mnps. I recommend 61 its been very lucky for me.  Change primorial with -m xx

That's it really. .

New BETA v4.0J (Win & Linux)
======================

I've posted a new build of my miner this morning to the mega.co.nz folder. This is mainly an update for linux compatibility issues, but does include a cache optimisation that yields a neat little boost in raw sieve speed (~5-10%).

I will be posting a trial build of v4J with GMP6 statically linked later today, but this is very much a trial build.. I have not run extensive tests with the GMP6 - although on my test PC it does appear to work as expected.

Happy Mining!