Topic: [ANN][DCR] Decred - Community Governance | Bitcoin Devs | Lightning Network - page 491. (Read 1201332 times)

Really, you're not being as picked on as it seems - CUDA is great when it comes to more complex algos, or algos that can benefit from Nvidia-specific optimizations that the compiler is unable to find by itself, but this is not the case for Decred. Really, you're talking about a minor bump I would guess, at most. The algo is dead simple - I've made the miner a few percent faster on AMD - but we're talking single digit percentages... and low digits. The Nvidia OpenCL compiler would really have a hard time fucking it up.

Sorry if I missed that earlier, didn't want to dig through the thread. Thanks!

Will remain the same.

@ocminer

Do you know what address and port number the pool will use when decred officially launches on Monday? Wasn't sure if you were going to change it. I will be away from my gear with no internet access during launch and I'm trying to get this sucker started through a scheduled task.

Well.. You should be able to rent out getwork rigs too.. It's just a matter of the rental service to integrate getwork instead/beside stratum but getwork is not really meant for such things, it's a old, http based protocol vs. stratum which ls lightweight, tcp based with calls/broadcasts like "mining.notify" when new blocks are seen on the network. Long time ago getwork was not able to tell when new blocks on the network showed up, so the miner literally continued to mine on the old block until the pool then lastly noticed there IS a new block and with the next http request the miner threw away the old work (stales) and started mining on the new block. This was later tried to fix with LP (LongPoll). LP uses a separate connection to the Pool (still http) which should notify about new blocks. This works, simplified, so that the miner pings the pool every 50 or 100ms "Is there a new block?" and the pool answers with "No" - or "Yes" if there's a new block which then leads to a refresh of the miners work.

Still you have a gap of 49 or 99ms between every LP check - which is quite a lot but setting this interval higher, like every 10ms, causes a big load on the pool, especially when you have lots of miners there. Just imagine 100 miners, polling every 10 ms "Is there a new Block?" from the pool.. It like sitting in a Subway and all the passengers shout "I want to get out here" every tenth of a second... The more people you have in there, the louder it gets, and at some point the pool is just overloaded and not working anymore.

Getwork is old and deprecated - definitely.

Stratum was introduced by slush as a websocket protocol. It's TCP based, miners don't poll the pool every 10ms or 100ms - they don't even need to make a second connection for long poll, they simply establish ONE connection over which they get data submitted from which they then generate their own work - so they don't need to ask the pool anymore for new work and if a new block at the network shows up - the pool does a broadcast "mining.notify" via this single TCP connection (every miner has) to notify them to poll new base work to work on - it's simply the way it should be.

I don't want to be boring here with such technical stuff, it's just a matter of time until stratum will be and shall be used IMHO - getwork will just not scale enough.

Read more here if you're interested in history and technical stuff

https://mining.bitcoin.cz/help/#!/manual/stratum-protocol#lp

even after stratum will we have to get the same Blake256 8 round 16 whatever or will any Blake256 work ?

Question for the nerds!!!
will rented hash work ? or will it not cos this isn't the same Blake257 algo.

@wolf0
@ocminer

you know yourselves.

Did you get an answer on this?

Try http://dcr.suprnova.cc:9110 instead of stratum+tcp

just what I read at https://forum.decred.org/threads/suprnovas-dcr-pool.422/#post-6120

After spreading food against some altcoins GMaxwell admits the Bitcoin Lightning Network is vaporware

https://twitter.com/traderminer/status/695084561382928384

there you go - wolf just answered it again ...

so cuda would have very little - if any - effect on the hashrate of the algo ...

ok - tanx wolf ...

now to get this darn thing to compile ...

ill work on it a little later this afternoon ...

#crysx

o we have enough nvidia miners - and some farms too ...

even though cgminer that ocminer released apparently does work with nvidia ( i havent tried yet - as mine STILL wont compile ) - the opencl mining on nvidia is weak ...

so maybe the nvidia dev that comes out with this algo before mining commences will take a nice chunk of the pie in general - and im more than willing to give them a nice chunk of the mining with thefarm if the code will compile on my machines under fedora 23 x64 cuda 7 ...

djm34 - sp - tpruvot - anyone? ...

#crysx

Pretty sure it's gonna be on Bittrex also. bittrex-richie has been lurking in #decred on freenode for a couple weeks at least I think.

Very interesting project, unfortunate that Nvidia miners are not getting the same love as AMD

Do we need to crowd fund to get something valid released?


Maybe we just do not have enough Nvidia miners to Justify our existence.

The launch si scheduled for 12:00 PM CST February 8th, 2016, probably the exchange where to buy is Bleautrade.


For every information or ask for support you i suggest to join and refer to the Official Decred forum here >> https://forum.decred.org
Very friendly and helpfull community here

i guess yobit will list decred first, so get your btc ready to buy some cheap dcr.

Now you can not buy anywhere @boro1345, Monday begins to mine. You have all the information in https://forum.decred.org and the OP.

Maybe i skipped this part, but where to buy these coins? My pc is too weak for mining ;_;