Yea when we pointed out this code was shit upon opening our pool he kept deleting our messages and sending nagging ones in PM's, like the one posted in OP.
That guy has to be stopped. Releasing shitcoins (that dont even work properly) on purpose....
|
|
|
Just noticed this: ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fpuu.sh%2FjP5Sl%2Fc3a899fb9c.png&t=663&c=FDxAmtgS1XJhUg) Thanks spots for being the man you are, as usual ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Lots of laughs! This post will probably be deleted pretty quickly as per your usual censorship policy but still is fun to post.
|
|
|
Thanks if ocminer is in nothing shady about this coin I wouldn't be ready to make such a statement LOL. There is no way pool ops can know if the project is 100% legitimate and scam-free unless they are a part of the team. He is just taking a gamble, so are we.
|
|
|
is it mineable now?
Seems so, we are getting blocks at SuchPool
|
|
|
Had to read the OP at least 5 times.. and I still dont understand. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
Thanks iGotSpot for your usual shadyness and deleting my posts.
Here is what I posted for those who tried mining at our pool. The developper will probably erase it, but for those who wonder why we stopped the pool here is the explanation:
This coin has bizzare RPC calls which prevent us from launching our stratums properly.
Since we would need to use deprecated old stratums to make it work and it would prevent us from using our anti-flood system, we will pass on this one. Sorry for the inconvenience.
|
|
|
I love the ideas of this project, bought some of the ICO myself and looking forward to the launch to mine some more!!
|
|
|
C'mon spread some hash on SuchPool. Afterall, we were first to the party ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
This is why i always run a sandbox for new coins ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) That's just a false detect given by the old source used by the dev, still doesn't changes the fact that coin has major bugs You think I should redo the whole thing from 0.11.0 or nah? I mean, I have time to waste :L To be honest i wouldn't waste my time with it, but it is your decision. Maybe it is better to make a new coin where everything is working, or if you want to stick to this relaunch so it gets a fair start I'll be sticking to it because I would like to continue the Ponycoin/Pwnycoin legacy, ever since they discontinued their coins. Make a working source and pm us to test it. If it works, we'll be glad to run a pool for it ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Must be a coingen.
Moreover, it's based off BTC 0.8, pretty ol code.
|
|
|
No pools scheduled at launch? lol
|
|
|
Could be good if there was some anti instamine protection.
With a coin distribution like this, this is guaranteed dev instamine. 100 blocks can go fast, even with a CPU at launch with the proper timining.
Not guaranteed dev instamine. But some chance for small miners, not only nicehash and miningrigs rentals Ahh c'mon... been there since a while now, got to know a bunch of devs.. This is common practice. Indeed it is a chance for small miners if crypto was fair.. but I think at this point we can safely say it's not ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
Could be good if there was some anti instamine protection.
With a coin distribution like this it is guaranteed dev instamine. 100 blocks can go fast, even with a CPU at launch with the proper timining.
|
|
|
trying connection 45.55.249.167:43208 lastseen=74.0hrs connect() failed after select(): Connection refused trying connection 45.55.249.167:43208 lastseen=74.0hrs connect() failed after select(): Connection refused trying connection 45.55.249.167:43208 lastseen=74.0hrs connect() failed after select(): Connection refused trying connection 45.55.249.167:43208 lastseen=74.0hrs Nodes are rejecting connections. Moreover, they are hosted at digital ocean.. It seems that many times in the past some coins have had sync/fork issues with nodes hosted there. I thought devs understood by now it was shite.. Surprisingly ocminer had no trouble syncing, everyone else did ![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif) No problems here either, just use the nodes from the OP, we were up before 'nova I had problems too syncing, but in fact I just used your pool as seednode ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) My daemon was never synced, so technically you didn't sync for me. I didn't get the chance to get a single working connection. Dunno why exactly since I can trace/ping both seednodes, but they end up in socket error and won't connect.
|
|
|
Nodes are rejecting connections. Moreover, they are hosted at digital ocean.. It seems that many times in the past some coins have had sync/fork issues with nodes hosted there. I thought devs understood by now it was shite.. Surprisingly ocminer had no trouble syncing, everyone else did ![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif)
|
|
|
"connections" : 0, DOA! Have it all Suprnova ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Busy at work, no time to loose on this.
|
|
|
up but not synced yet.. waiting on nodes to connect but they aren't...
|
|
|
my pool is already prepared, waiting on the source to launch. www.suchpool.pw/pulse(i might be slow because I am beyond busy at work, sorry!) edit; nodes won't sync. no go.
|
|
|
|