Topic: [ANN][SWAG] IT'S ALL ABOUT THE SWAG! DO YOU HAVE IT? LAUNCHED - page 9. (Read 28702 times)

wts 5,323.4742944 swag pm me offers thanks see my trust rating

You did a great job! haha

Imagine me.  I had to deal with all the issues, people complaining, then I had to stay up all night and fix database corruption for 4-5 hours.

I haven't slept :p


But all that aside, coin looks good now.

Hashrate should be balanced to http://swag.blockminter.com/ please

well while i understand the problems pools experienced after launch due to high volume of miner, i am still down. i was pump about the release of this coin, apparently so where a lot of others. i had to sign up for 3 different pools. finely  just before going to bed it appeared i was running smoothly at the dedicated  pool, only to wake to see something went wrong, was not hashing all nite, and only mined 11 swag.

i am thankful to SwagCoin for sending me swag to my wallet, if any other Big Pimps would like to toss a player some swag i would be much appreciated

987jN4F7XkttbRwniwk23oHwVY8p97bTJd

http://swag.blockminter.com/ Cant reset my pass. Cant write messege from "contact us" =_=

There were some problems with low starting DIFF and quite high pool hashing power. It's discussed in previous replies.

Anyway, I mine form the start and received 1000+ coins (I was expecting more when I wake up but probably due to low DIFF problem I've got less)

Do u even read the thread they are one of the best mining pools out there
They are looking into it but had issues with initial difficulty

I'll just repost this from a few pages back for visibility:


Let me take a second to explain exactly what happened.  

The server wasn't the problem.  We were sitting at 20% cpu usage, and all other pools had no issues during the time.

The issue was to do with the coin's starting diff of 0.03.  There were over 1000 blocks every few minutes trying to be submitted to the coin daemon.  The bitcoin coindaemon cannot account for this, and ends up freezing up completely.  This caused lots of blocks never to be submitted.  In this type of situation, there was only two ways you could of mined this coin at the start.  1. Solo mining, or a 2. small pool.

Regardless, we had to wait for the developer to force the diff up to 0.06 before the coin daemon would even start to respond properly.  Once it started to respond blocks started being accepted as normal, however it was still too fast for stratum/mysql and the daemon.  A common stratum issue arose where the blocks and shares were submitted out of order.  In fact, the daemon decided to randomly drop a block every so often too, yet still end up submitting in to the blocks table.  This compounded the issue with false blocks in the table, causing MPOS's crons not to execute properly.  In essence - the entire database was corrupted.  

I spent a good few hours repairing in in real time while miners continued to mine the coin.  When I went in to #mpos for a bit of advice, I met other pool admins that were mining SWAG at the start with the exact same issues with the database.  Now again, this is caused by the low starting diff of the coin, compounded by the high amount of miners at the start wanting to mine it.  The coin itself is fine - just new coins should always start at a difficulty level of higher than 1.0.

I am disappointed by some of the comments people posted on this forum.  You guys are worse than grannies in a sewing circle when you get together.. the rumours run wild with little regard to logical thinking.

Binaryclock/dedicatedpool has never lost a database, and has always been able to recover from issues.  ALWAYS.  Don't be so quick to toss us out the window next time.  You should know this by now.


Anyways, I hope this helps explain things.

Now that the original rush of low diff is out of the way, it's time to concentrate on the coin itself.  If any pool operators had database corruption from the low diff 0.03 starting, please contact me [email protected] or on IRC #dedicatedpool.com.  I will be more than willing to help you repair your database with what I've learned from my night repairing mine.

TL;DR - coin had a low diff 0.03 starting - daemon/mpos/stratum couldn't keep up with rate of blocks submitted.  database corruption - but was fixed.  New coins should always have a 1.0 diff starting.  But now that's out of the way, lets move forward and mine this baby.

http://dedicatedpool.com
Ryan, dedicatedpool.com support/admin
[email protected] / IRC on freenode #dedicatedpool

For the hash rate that is very low. I assigned a tiny 700khash since the start and as of right now I've got around 4700 swag confirmed with 14 unconfirmed. In cgminer it's showing at just over 400k accepts and 9k rejects at DedicatedPool.

Wtf i mined from the start on the swagcoin with http://swag.dedicatedpool.com but i didnt receive any coin! They having problems ? Will i get my coins.... :-((( I hope it is not a scam

WTS 1k for 0.05 btc.

me2 PM me, for SWAG

WTS 470 SWAG for 0.02 BTC

cd src
mkdir obj

This coin is heavily premined though, I'd skip it.

A new pool to mine SwagCoin is now available...
-> http://swag.coins4everyone.com!

Let's spread has power!

Benefits of Mining @ coins4everyone.com:
* based in Europe
* 100% uptime so far
* dedicated servers w/redundancy, DDoS protection
* only 1% fee
* pplns
* nice & caring support
* trustworthy & skilled admins

Come on, we need more hash power! ;-)

that did the trick, thanks.

You have to create your obj directory in src directory

mkdir ~/git-rep/swagcoin/src/obj

such failure start...