IPO miner has it working fine, so I gather the node issue was easily resolved.
That did cause the soloers or dev to get the first 500 blocks, but these blocks
are flying very fast, we are already over double that, so I am not concerned.
The node in the windows wallet was allegedly correct, however the node included in the thread was not working.. Too bad of a launch just to be a coincidence. |
|
|
|
Dev, I already asked you twice to remove www.suchpool.pw/geek from the selection of pools. Since minerpools too is leaving your coin you can empty your pool list. Next time, why not doing a proper launch with working nodes?  |
|
|
|
|
The problem is that this is a scam.
Your nodes are also utter shit, I can'.t even connect to 203.88.161.143 anymore.
|
|
|
|
|
Dev, why do you put one of my ips there?
addnode=67.215.12.41
This node is not valid at all, the wallet is not even on a 67.215 ip....
This dev has no idea of what he's doing obviously.. I'd even go to say we're facing a full blown 'tard.
|
|
|
|
eEcho eEcho
LOL!!!!!!!!!!!!!!!!!!!!!!!!!!!
This is same dev of eEchoCoin!
LOL!!!!!!!!!!!!!!!!!!!!!!!!!!!
HAHAHAHAHA
Whoever it is he made it obvious this was prepared in advance to instamine the shit out of it. |
|
|
|
Ok fuck this shit, wouldn't sync, now 600 blocks instamined. We're out.
please addnode addnode=104.28.28.100 addnode=67.215.12.41 Sorry too late, we're gonna let the pooper scoopers have it. Ugly ass launch, and it was rigged on purpose so you could instamine 600 blocks, we kinda got to know the game by now. Good luck with your coin  |
|
|
|
|
We're out:
-Nodes were blocking sync at first
-No nethash
-600 blocks+ instamine
- Retarget is shit
Pure shitcoin.
|
|
|
|
|
Same here, the wallet is buggy as hell and has weird behavior, like it places all it's files directly in the /home instead of creating a subfolder.
EDIT: Can't get any nodes connected.
|
|
|
|
|
Watch out, high possibility that this coin be a scam.
Lots of instamine (~600+ blocks), published nodes wouldn't work, dev seems not to know what he's doing. Also the diff retarget is sketchy as hell.
(edited after launch)
|
|
|
|
Happy to be back! We missed this community, which is the main reason why we're back! Anything you guys need just let us know and we'll try to help in any way we can! |
|
|
|
https://SuchPool.pw/cann
We are back! Fresh new servers, we restored accounts/workers and logins! You can login with your old credentials.
Same old receipe as before:
1 account and 1 set of workers for all pools
SSL on all pools
Multiple Load-Balanced Node.JS Stratums + VARDIFF
24/7 Monitoring on Stratum, MPOS, Central Wallet, Mysql and much more
Helpdesk Support System, Active team
DDoS Protected and Flood filtered
Private VMWare-based Cloud infrastructure
Multiple databases and frequent full database dumps
Hosted in a state of the art Datacenter using n+1
Best bandwidth carriers, excellent connectivity and latency worldwide
We also have our own on-site tech support, since we are the hosters.
All the pools have fresh databases; that means there are no transaction history. This allows us to keep a lower hardware overhead for the moment until they grow up again.
https://suchpool.pw/cann
To reach us:
URL: http://www.suchpool.pw
Email: support@suchpool.pw
IRC: irc.freenode.net - #suchpool
Twitter: @SuchPool
|
|
|
|
https://SuchPool.pw/start
We are back! Fresh new servers, we restored accounts/workers and logins! You can login with your old credentials.
Same old receipe as before:
1 account and 1 set of workers for all pools
SSL on all pools
Multiple Load-Balanced Node.JS Stratums + VARDIFF
24/7 Monitoring on Stratum, MPOS, Central Wallet, Mysql and much more
Helpdesk Support System, Active team
DDoS Protected and Flood filtered
Private VMWare-based Cloud infrastructure
Multiple databases and frequent full database dumps
Hosted in a state of the art Datacenter using n+1
Best bandwidth carriers, excellent connectivity and latency worldwide
We also have our own on-site tech support, since we are the hosters.
All the pools have fresh databases; that means there are no transaction history. This allows us to keep a lower hardware overhead for the moment until they grow up again.
https://suchpool.pw/start
To reach us:
URL: http://www.suchpool.pw
Email: support@suchpool.pw
IRC: irc.freenode.net - #suchpool
Twitter: @SuchPool
|
|
|
|
https://SuchPool.pw/dash
We are back! Fresh new servers, we restored accounts/workers and logins! You can login with your old credentials.
Same old receipe as before:
1 account and 1 set of workers for all pools
SSL on all pools
Multiple Load-Balanced Node.JS Stratums + VARDIFF
24/7 Monitoring on Stratum, MPOS, Central Wallet, Mysql and much more
Helpdesk Support System, Active team
DDoS Protected and Flood filtered
Private VMWare-based Cloud infrastructure
Multiple databases and frequent full database dumps
Hosted in a state of the art Datacenter using n+1
Best bandwidth carriers, excellent connectivity and latency worldwide
We also have our own on-site tech support, since we are the hosters.
All the pools have fresh databases; that means there are no transaction history. This allows us to keep a lower hardware overhead for the moment until they grow up again.
https://suchpool.pw/dash
To reach us:
URL: http://www.suchpool.pw
Email: support@suchpool.pw
IRC: irc.freenode.net - #suchpool
Twitter: @SuchPool
|
|
|
|
I'm more convinced than ever that BTC is basically dead...
...
4) Centralization problems haven't been solved. In the last two years, two major 51% scares have happened, both involving ghash.io. Each time the alarm bells ring, new ideas are offered, and absolutely nothing changes.
You are right on all counts, but on any given day DRK's hash is usually even more centralised than BTC's. Evan and team need to a) Admit the fucking problem and b) Fix it by shifting blockchain security to Masternodes. Most of the code and all of the infrastructure already exists. Blockchain security can and should be practically unbreakable, the same as Darksend and InstantX, not left in the hands of two or three pool ops. Go talk to anyone with serious money about trusting big chunks of it to a mightily 'decentralised' 3 shitty pool servers, all run as cheaply as possible by some noddy from the interwebs, see what reaction you get. Then have the same conversation again but with 3000 servers, n-of-m subsetting, 1/(10^20) attack success probability... your charts might suddenly start to look a bit more exiting than less than a fiftieth of the price of crappy old Bitcoin. And what about a single individual could own half of the masternodes? Financially it's not making much sense but this COULD happen. You're one who always talks in ifs and buts, here's a good IF for you. Masternodes are NOT the solution to decentralize everything effectively. |
|
|
|
It's sad to see the coin being renamed to a brand that already has patents filed on it... moreover that is also an existing coin that's been here a while.
Those are some of the reasons why I decided to empty my DRK stash and move on. It's kind of a slap in the face for the early DRK people.
Anybody would happen to know the filing number of the challenge application? Would be interesting to see.
Just to be specific, any dispute here would not be regarding "patents" but rather "trademarks"... which I'm quite sure Evan said is being dealt with... FYI: http://www.lawmart.com/forms/difference.htmWell he spoke about trademark here and patents somewhere on DCT so it was confusing. Without having any actual number or precise informations it's hard to tell what's going on. |
|
|
|
|
It's sad to see the coin being renamed to a brand that already has patents filed on it... moreover that is also an existing coin that's been here a while.
Those are some of the reasons why I decided to empty my DRK stash and move on. It's kind of a slap in the face for the early DRK people.
Anybody would happen to know the filing number of the challenge application? Would be interesting to see.
|
|
|
|
|
Show Posts
