In reference to the earlier mining conversation, I easily get 2.5Mhs out of my 290x mining Darkcoin but only the provided GPU miner seems to work and I can only get 1Mhs out of it regardless of settings.

How would non-IPv6 clients be able to connect to a masternode? I believe most end users like myself currently do not have access to IPv6 through their ISP.

Guys, I'm no not so confident with my English, but look what I've done within 10 minutes after two cups of red wine..
There are templates.. you can change the text, the pics, the videos..

http://www.makewebvideo.com/en/previewvideo/181474

Couldn't we make and buy some clips there..  


P.S. By the way I like the POS Girl..  

I have optimized synchronization code, next version will sync much faster.

DarkCoin code is pretty complicated, sometimes for no reason (if you are interested I can point you to examples). I want to make simpler and cleaner implementation which is easier to understand and easier to done right. I will prioritize instant transactions over anonymity since they are simpler to implement and I think they are useful for more people than DarkSend.
After new year I will have hell of a lot of free time, so I hope in the second half of January we will have some code for public testing, maybe sooner.

AFAIK,2 or 3 of the whales in the QQ group can launch 51% attack now if they want.
so, it has nothing to do with pools.

Wouldn't any pool be able to do this? Like ones for Bitcoin?

On a separate note I tried to mine some Spreadcoins over the last two days but the provided X11 miner only gets 1MH out of a 290x and network hashrate is over 2GH.  I'd be interested to see whether by removing pools this coin has simply created a solo mine arms race.  2GHps of X11 is a lot of GPUs  

Oh god I think I have hit rock bottom  

I'm actually solo CPU mining Bitcoin in the hope that I'll "win the lottery" and make up for my losses this week.

{
"blocks" : 334949,
"currentblocksize" : 91553,
"currentblocktx" : 187,
"difficulty" : 39457671307.13873300,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 239184231147850880,
"pooledtx" : 221,
"testnet" : false,
"generate" : true,
"hashespersec" : 6926968
}

Interesting concept -- I've browsed through most of the thread but haven't seen a clear answer on a key point:

How specifically are mining pools avoided with this coin?

50 out of 100 up, the rest tomorrow

if that 2 to 3k asks under 0.006 are still there then I'll see about adding them too maybe

I thought my screen needed cleaning when I saw your sig 

How many of these bad boys can I mine in 24hrs with an AMD R9 290?

Cheers.

And it's roughly 1 SPR per day. It has little sense with pools or without them. SPR blocks are generated pretty fast, every minute. So somebody with 1/1000 of net hashrate still can get the block about every 2/3 of the day. And even with 1/10000 it's every 7 days. When (if) price will go up, mining will be even harder, sure. But I like the idea that only dedicated miners will mine SPR, without switching on it for quick profit.

Idea of 'poolless' mining is good for coin security, even if it is not easy for miners. And honestly, I think sooner or later there will be workaround, there are some ideas ITT how to do it. But Mr. Spread is a good programmer and very good person. I think SPR will have a bright future.

Is there any Spreadcoin Wallet that works on a gnu/linux terminal ?

Thanks!

I think there are only two possibilities why he went awol

May I post a suggestion here?

Since some DRK features are implemented, and some could be improved upon, the original concept for the Darkcoin masternodes (RC2/RC3 releases) involved a protocol-level enforcement of the masternode payments. The problem with these releases was that there was some kind of bug that triggered sporadic network forking by misbehaving nodes or mining clients. The consensus wasn't working as it should.

In a sense, Darkcoin tried to use a dual consensus for every block: One for the transactions / mining, and one for the masternode payout. This didn't work as planned (there were sporadic forks of the network) and DarkSend development was lagging - so a workaround system was created instead that was "safer" and relieved some of the price speculation (it was the period of the great pump - and all eyes were on DRK news and how something would succeed or fail).

In that payment system (an evolution of which, is the current system of MN payments) the pools decided whether to pay or not in a semi-voluntary scheme. If a pool wanted to cheat payment, they could. The strategy was to shame the pools that "cheated" and it worked to compliance levels of 80-90%. The added threat of "enforcement" where Evan would "flip the switch" to fork off the non-compliant pools was also added as an extra measure. However, in my view, this is not the ideal solution to the problem. Rather, it should be done like it initially was conceived so that misbehaving clients are simply forked by themselves out of the network. No centralization / enforcement switch, no need for asking pools to play nice etc etc.

Perhaps the dev wants to give it a look* and see if he can come up with a system that works and which is free of forking bugs. It could also be implemented by DRK if successful, and it would also give added credibility to SPR itself for improving something in a significant way. The good thing with SPR is that, unlike DRK which is more mature, it can risk multiple hard forks to try things out.

* Perhaps the RC2/RC3 bugged solutions of DRK where there was a voting system in place to decide the MN payments are not the ideal concept for this implementation and another idea can be used altogether.

Are there any indications on how many Spreadcoins you will need to operate a masternode?  Is there a rough timeline for the introduction of masternodes to Spreadcoin?

Hi spreadnodes, i don't know what's your people do when someone find out some bugs. There is no need to sarcasm here. In fact, it's encouraged to do so in the Darkcoin Community and It's what OpenSource meaning: A better Darkcoin Project.

The bugs, no matter how critical as Aswan had posted in the DCT that occurred in the protocol level or just some variables setting, they are not mean Darkcoin Project is worse than any other crypto currency. It is just the opposite that the Darkcoin Project is more and more close to perfect, and ready for actual use.

So, i'm appreciate the people that provide the bugs to our great Dev-team to fix. The community appreciate the people who contribute their private  time to the Darkcoin Project.

More and more DRK fans may join SPR.