Are you certain these coins were stolen from Cryptopia?  I notice Cryptopia has delisted the coin without warning.  It's on the delisted page today with an announcement and delist date as the same, Dec 21, 2018.

I've never been able to get 1.7 to sync so I've been using Bokrug, 1.6.2.

I would volunteer to be a part of keeping this coin alive but this supposed 51% attack gives me pause.  I'm not sure I'd want to touch it until I know what happened there.  Nice work vampirus keeping track of that.

Use the bootstrap.  I tried and failed syncing from scratch numerous times but the bootstrap linked in the pinned messages in the wallet-support section of the Discord, worked.

Anyone know a working sync node?

Zeewolf did you ever get it to compile?  I am not sure what source is up on git but I found the last source I had that compiled, 1.6.2-Bokrug.  I am thinking there needs to be more than 1 sync node, I'd hate to see this coin die.  Thank the dark lord for Cryptopia.

I've run into another issue I've run into nowhere else.

When running blakebitcoind I get the following:

Error: Unable to bind to 0.0.0.0:356 on this computer (bind returned error 13, Permission denied)
Error: Failed to listen on any port. Use -listen=0 if you want this.

For giggles I try -listen=0 and get the following:

An error occurred while setting up the RPC port 243 for listening on IPv4: bind: Permission denied

Then get the unable to bind on 0.0.0.0:356 bind error above once again.

Thank you, this worked fine.

Trying to compile from source from git repo and get the following error:

~/BlakeBitcoin/src $ make -f makefile.unix
Building LevelDB ...
make[1]: Entering directory `/BlakeBitcoin/src/leveldb'
make[1]: *** No rule to make target `libleveldb.a'.  Stop.
make[1]: Leaving directory `/BlakeBitcoin/src/leveldb'
make: *** [leveldb/libleveldb.a] Error 2

I've dealt with this once before with another coin by simply copying these files from another coin's source but would be interested in finding out why this happens.

Thanks shimlbit, that worked.  I also had a make the leveldb/build_detect_platform script executable.

Trying to compile from source from the github repo on Ubuntu, I get the following error:

auxpow.cpp:127:1: fatal error: opening dependency file obj/auxpow.d: No such file or directory
compilation terminated.
make: *** [obj/auxpow.o] Error 1

There is no obj directory in fact, that might have something to do with it.  Did I miss something or repo missing something?

blackpools.pw is running the 1.3 Offeringd now.  I've set fee to 0, it's not worth all the tiny mined transactions.  Nice work on the wallet Blazr, it's awesome. 

I didn't know the japool Offerings pool was offline.  I have no intention of shutting down the blackpools Offerings pool btw but if I need to for one reason or another I will try to give warning.  The machine that hosts the Offerings p2pool also hosts Quark and now Frozen.  The Quark pool has offset a bit of the server cost.  Even if I spent a bit keeping it up I would, it's a leaning experience for me.  For those that use the pool, sorry for the high number of DOAs a day or so ago, crazies mining Frozen crushed the modest hardware, which is now since upgraded.

In addition to changes to the config, I just reset the data directory as an experiment.  Current accounting for shares are lost resetting the data of course.  I've sent each worker address 20 OFF, which hopefully offsets lost shares for my playing around.  Thank you for using my pool.

Adjusted and restarted.  I am not a p2pool expert, this is all a learning experience for me.  Theoretically the short term data will be more accurate now but I am not sure what the net effect of reducing lookback will have.

Hmm.  I think this is because I have the look back period set too far back.  It's accounting for shares back 144 hours.  This is the default for the p2pool-quarkcoin and my current setting for offerings.  Here is the relevant portion of the networks.py:

PARENT=networks.nets['offerings'],
        SHARE_PERIOD=15, # seconds
        NEW_SHARE_PERIOD=15, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=50, # shares  //with that the pools share diff is adjusting faster, important if huge hashing power comes to the pool
        SPREAD=30, # blocks
        NEW_SPREAD=30, # blocks

I am going to test a shorter look back time and restart and avoid touching the data directory.  There doesn't appear to be anything nefarious going on.  I am not sure I can look at a history of hash rates but I think QdXXBSJNcVYnjWm57KVL797typum4JZ5fe had a significantly higher hash rate in the recent past.  This address/worker is still getting more work even though his or her hashrate has dropped, because of the lookback period.  The pool has 6-8 MH/s in the not too distant past but I am not quite sure how to see the history of worker hash rates.  This address isn't my own unfortunately.

So are block rewards infinite, just get very very small?

My little quark p2pool is quite lonely, if you want to spread the hash around.

http://blackpools.pw:3336

Hello.

I've been running a Quarkcoin p2pool since about September for my own solo-pool mining purposes.  The more the merrier?  It's there, please feel free to use it.  Fee is set at 2%.

http://blackpools.pw:3336

---
For those just getting started...

Here is the link to the pre-compiled quark cpuminers for Windows.

https://docs.google.com/file/d/0BxKqW4aMUczmaTVfWjZEdnpqLVk/edit?usp=sharing

Be careful, there was malware floating around not long ago as a quark cpuminer, scan whatever you download.

For unix I found the "uncle bob" cpuminer performs quite well:

https://github.com/uncle-bob/quarkcoin-cpuminer

Installing the latest GMP library could also make a difference in performance.

Command to start mining with this pool:

minerd.exe -a quark -o http://blackpools.pw:3336 --userpass=YourWalletAddress:AnyPassword

Make sure "YourWalletAddress" is part of the command otherwise you're donating everything to the pool.

Hi Blazr.

Would you mind adding my pool to the original post?  This is the same pool I announced on Sept 21st.  I'll cut and paste my original post again below.  I have also added a Cthulhu inspired domain name to make it easier.  Thank you!

This coin really needs to get on an exchange.  What can I do to help?

-- original post --

Here is an alternate ritual site (p2pool) for worshiping the Great Old One:

NEW!
http://blackpools.pw:3333

http://192.241.200.142:3333/static/

I've set the fee at 1%, I don't imagine ever increasing that.  This is all for a fun coin and a great learning experience.

Here is the link to the pre-compiled quark cpuminers for Windows.  Should be same link that thcst8 posted previously:

https://docs.google.com/file/d/0BxKqW4aMUczmaTVfWjZEdnpqLVk/edit?usp=sharing

Be careful, there was malware floating around not long ago as a quark cpuminer, scan whatever you download.

For unix I found the "uncle bob" cpuminer performs quite well:

https://github.com/uncle-bob/quarkcoin-cpuminer

Installing the latest GMP library could also make a difference in performance.

Command to start mining with this pool:

minerd.exe -a quark -o http://192.241.200.142:3333 --userpass=YourWalletAddress:AnyPassword

Make sure "YourWalletAddress" is part of the command otherwise you're donating everything to the pool.

If by too slow you mean the rate then yes there are only a handful of miners using it at the moment.