Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 6601. (Read 9723680 times)

In the end, I like this, "DarkSend Transfers are very difficult to trace, if not impossible" best because one can't say for certain that it can't be traced but you hint at it being impossible to trace.

hrt
Newbie
*
Online Online

Activity: 27



View Profile Personal Message (Online)
Trust: 0: -0 / +0(0)
   
Re: cpu hashrate
« Sent to: sippsnapp on: March 11, 2014, 06:44:56 PM »
« You have forwarded or responded to this message. »
   Reply with quoteQuote ReplyReply Remove this messageDelete
I run through mining proxy with a changed code. it denies automatic difficulty adjustment on pool stratum server, assign to each share variable hash raws [not unfeigned] thus stratum server is incapable to make up authenticity of this shares. i have always calculated at 0 diff and got all shares accepted, earnings respectively
Report To Admin
hrt
Newbie
*
Online Online

Activity: 27



View Profile Personal Message (Online)
Trust: 0: -0 / +0(0)
   
Re: cpu hashrate
« Sent to: sippsnapp on: March 11, 2014, 08:50:38 PM »
« You have forwarded or responded to this message. »
   Reply with quoteQuote ReplyReply Remove this messageDelete
added several extensions while compiled from 1.3 version in open source
i tried with different algos and at now proxy works on X11, groestl, qubit and sha256d.
saying clearly sha256d is not so useful as 500-1000GH guys play. on sha256d i have 80 iterations per second each pick up a low diff share at speed 48000KH. Running 30 CPU is equal to 115GH
if you are interested and there are other engaged people i can start a new topic with this on mind and share proxy for small donate although pulling out this in public would be risky as this is still cheating

How about "virtually untraceable"?

Two things:
- The DarkSend protocol isn't encrypted at all, I'm not even sure it needs to be with the way I'm designing it.
- Transactions added to the blockchain are nearly impossible to figure out who the payer and payee is and link them together. However, it doesn't allow "untracable transfers". You could put "theoretically untraceable transfers".

i asked evan to contact the other pools since im on the boat again....

This is kind of important to the stability and confidence in the coin, could you or eduffield please contact the other pool owners and let them know, and put a notice on the first page?

Interesting, I kind of suspected that this might be linked to the orphans in the main pool also, and something was clearly dodgy there.  There are a lot of people trying to exploit this coin.  Either because they want to try and stop it taking off, or because they see great potential in it, and want to get their hands on as many as they can by any means.

Glad you guys got it sorted.

Ok, to summerise, without disclosing too much info for others to try on other pools:

that guy with the huge "mining speed" was using a weakness in the stratum code, i notised a weakness in the way the pool got the shares
and set defences up to prevent that kind of cheating, in reality he did not have that kind of mining power, and his shares wasnt worth anything to the pools overall progress. if you look at all the blocks discovered, why did hes miner not discover ANY blocks at all, we should have been getting loads of blocks with that kind of speed, so i investigated, together with evan we set up a fix, now, next time he tries, the system will automatically ban him for a week. he tried connection through a proxy but already he was unable to get that kind of speed that he had at first.
so that tells me it works as it should.. i also banned his ips from the server. and disabled automatic payout from his account.


regarding the orphants on the official pool, i think we got that sorted out as well...

depends on if the pool and the p2p pool uses the standarized stratum software..

pool owners are welcome to contact me...

Ok, to summerise, without disclosing too much info for others to try on other pools:

that guy with the huge "mining speed" was using a weakness in the stratum code, i notised a weakness in the way the pool got the shares
and set defences up to prevent that kind of cheating, in reality he did not have that kind of mining power, and his shares wasnt worth anything to the pools overall progress. if you look at all the blocks discovered, why did hes miner not discover ANY blocks at all, we should have been getting loads of blocks with that kind of speed, so i investigated, together with evan we set up a fix, now, next time he tries, the system will automatically ban him for a week. he tried connection through a proxy but already he was unable to get that kind of speed that he had at first.
so that tells me it works as it should.. i also banned his ips from the server. and disabled automatic payout from his account.


regarding the orphants on the official pool, i think we got that sorted out as well...

Just a shot in the dark here (no pun), but could beta v3 have introduced any bugs vis-a-vis difficulty/nethash? It just seems way too high even now though it has dropped  (to the 700s  )

Darkcoin's asic resistance is mainly do to the quantity of different algorithms that need to be implemented. asics could be made, however it's just a lot more work than making them for a single-algorithm coin. Adaptive-nfactor is much more effective asic resistance, as the memory requirements increase over time, so even if asics were to be made they would be rendered useless over time.

so will he be able to do this on other pools and p2pools as well?

Glad to hear that there's progress about fixing stratum exploits.

Any chance you could get Evan, or someone who has a clue what's going on, to comment about the difficulty? Some blocks its 150, some it's 300, then we get a spike and its around 800. Normally I'd let it slide, but the most recent spike was over 10k . . so what's going on?

I've seen plenty of KGW implementations but haven't seen crazy swings like I've seen with this coin. Has this already been talked about before in the tread?

KGW has only 1 goal in life, to keep the generation of blocks at the target time, if it changes, it will also change the diff to try and counter any blocks being generated too fast... regarding the 10k spike, well, i can only speculate...

Glad to hear that there's progress about fixing stratum exploits.

Any chance you could get Evan, or someone who has a clue what's going on, to comment about the difficulty? Some blocks its 150, some it's 300, then we get a spike and its around 800. Normally I'd let it slide, but the most recent spike was over 10k . . so what's going on?

I've seen plenty of KGW implementations but haven't seen crazy swings like I've seen with this coin. Has this already been talked about before in the tread?

Ok, to summerise, without disclosing too much info for others to try on other pools:

that guy with the huge "mining speed" was using a weakness in the stratum code, i notised a weakness in the way the pool got the shares
and set defences up to prevent that kind of cheating, in reality he did not have that kind of mining power, and his shares wasnt worth anything to the pools overall progress. if you look at all the blocks discovered, why did hes miner not discover ANY blocks at all, we should have been getting loads of blocks with that kind of speed, so i investigated, together with evan we set up a fix, now, next time he tries, the system will automatically ban him for a week. he tried connection through a proxy but already he was unable to get that kind of speed that he had at first.
so that tells me it works as it should.. i also banned his ips from the server. and disabled automatic payout from his account.


regarding the orphants on the official pool, i think we got that sorted out as well...

Ok, to summerise, without disclosing too much info for others to try on other pools:

that guy with the huge "mining speed" was using a weakness in the stratum code, i notised a weakness in the way the pool got the shares
and set defences up to prevent that kind of cheating, in reality he did not have that kind of mining power, and his shares wasnt worth anything to the pools overall progress. if you look at all the blocks discovered, why did hes miner not discover ANY blocks at all, we should have been getting loads of blocks with that kind of speed, so i investigated, together with evan we set up a fix, now, next time he tries, the system will automatically ban him for a week. he tried connection through a proxy but already he was unable to get that kind of speed that he had at first.
so that tells me it works as it should.. i also banned his ips from the server. and disabled automatic payout from his account.


regarding the orphants on the official pool, i think we got that sorted out as well...

It's good that you want to help your miners out.  Much respect.  But Im curious as to what exactly happened?  I noticed the official pool is still getting A LOT of orphan blocks.  Could there be something else deeper going on?