Advertisement
Guest User

Untitled

a guest
Jul 30th, 2014
382
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 11.77 KB | None | 0 0
  1. [09:12] <Duvulpr> Your net seems a bit unstable ;p
  2. [09:12] <ProjectMayhemWRK> b) is a little more complicated because I've never done it, and finding out that information is difficult because it's somewhat illegal. As you would be the only miner on the chain, I guess I could create a duplicate block of the next block and remove all but your transactions so it becomes the next block in the chain and stratum to be commanded to accept and confirm that block
  3. [09:13] <ProjectMayhemWRK> it's strange it's only just started happening
  4. [09:13] <Duvulpr> Well 51% attacks aren't illegal. They're a perfectly valid state. There isn't any laws or regulations on which rules miners must follow in crafting their own blocks.
  5. [09:14] <ProjectMayhemWRK> that's debateable, it's theft and computer manipulation, crypto's are just untraceable, but if you could be traced I imagine you could be charged
  6. [09:14] <Duvulpr> Possibly, however jurisidiction will be a significant legal question.
  7. [09:14] <ProjectMayhemWRK> I'd have to research the b) part anyway
  8. [09:14] <Duvulpr> Anyways, I would imagine that you would need to modify the coin daemon to change how the conflict resolves.
  9. [09:15] <Duvulpr> Actually
  10. [09:15] <Duvulpr> You'd just need the coin daemon to maintain a blacklist of TX hahes it will not include.
  11. [09:15] <ProjectMayhemWRK> may just be able to avoid the conflict
  12. [09:15] <Duvulpr> Perform a) first
  13. [09:15] <Duvulpr> Then, blacklist the TX you want to double spend.
  14. [09:16] <Duvulpr> Now, create a new TX with the same inputs. That'll be the only TX that'll get in the block, and your pool will keep building blocks until it overtakes the main chain, to which point other miners will switch to it.
  15. [09:17] <Duvulpr> I think these two changes should only incur a few hours of exploration and implementation. I can pay 700k doge, or another cryptocurrency of your choice - interested?
  16. [09:17] <ProjectMayhemWRK> I'll chedck with my sources and get back to you, I need to know how much work is involved
  17. [09:18] <Duvulpr> Cool. How long might that take?
  18. [09:18] <ProjectMayhemWRK> in my head the block height thing can be put in from the start because you can have an incorrect chain with any hashrate. The block thing may be something that has to be done quick
  19. [09:18] <ProjectMayhemWRK> for a)... minutes?
  20. [09:19] <ProjectMayhemWRK> for b) don't know :P
  21. [09:19] <ProjectMayhemWRK> have to check with some of my shady friends
  22. [09:19] <ProjectMayhemWRK> who I know have carried out these attacks
  23. [09:19] <ProjectMayhemWRK> will let you knnow after work
  24. [09:20] <Duvulpr> ah okay, I just mean how long it might take for you to check with your shady friends ;p OK
  25. [09:20] <Duvulpr> I might not be here, hold on I'll give you an email.
  26. [09:20] <Duvulpr> And, I'd like this as pool software, so it should read a configuration file for a) and b).
  27. [09:23] <Duvulpr> If I'm no longer here, please email me at opwolf@mail.com
  28. [09:24] <ProjectMayhemWRK> there isn't already existing pool software?
  29. [09:24] <ProjectMayhemWRK> I thought this was just a mod?
  30. [09:26] <Duvulpr> this is a modification to an existing pool software
  31. [09:26] <Duvulpr> But I mean it as, I don't want you to hardcode it to a certain block, or to certain transactions.
  32. [09:26] <ProjectMayhemWRK> ah good, if it was from scratch there's no way I'd be doing it :P
  33. [09:27] <ProjectMayhemWRK> it will coded to certain blocks as string from a file
  34. [09:27] <ProjectMayhemWRK> you'd change them as you like
  35. [09:27] <Duvulpr> That'd work :)
  36. [09:27] <ProjectMayhemWRK> there should already be a config file for that
  37. [09:27] <Duvulpr> To be fair, it might be quite easy to make a simple stratum pool, that would just read TXNs to mine from a textfile
  38. [09:27] <Duvulpr> Yeah.
  39. [09:27] <Duvulpr> Or an option.
  40. [09:28] <ProjectMayhemWRK> I did tinker with a 51% theory
  41. [09:28] <ProjectMayhemWRK> a few months ago, where you would mine and get every block
  42. [09:29] <ProjectMayhemWRK> by rejecting blocks found by other pools
  43. [09:29] <Duvulpr> uhuh, so orphan everyone else's block
  44. [09:29] <Duvulpr> Yeah, that is nice, but I want to double spend for lots more profit :)
  45. [09:29] <ProjectMayhemWRK> Duvulpr hmm
  46. [09:29] <ProjectMayhemWRK> you know once you do this the value is going to plummet :P
  47. [09:30] <Duvulpr> Indeed, but I don't think it'll hit zero.
  48. [09:30] <Duvulpr> Maybe it'll crash by 50-80%, but so? That's extra profit!
  49. [09:30] <ProjectMayhemWRK> well
  50. [09:30] <Duvulpr> (I will be exchanging it for BTC you know)
  51. [09:30] <ProjectMayhemWRK> you need the maintain 51% until you've sold
  52. [09:31] <Duvulpr> That's not an issue!
  53. [09:31] <ProjectMayhemWRK> Good, because if other miners don't switch to your chain
  54. [09:31] <Duvulpr> People will only detect the double spending when it is spent (they will see a new pool with lots of hashpower, but that might just be a multipool they'd think.
  55. [09:31] <ProjectMayhemWRK> the old chain can be brought back
  56. [09:31] <Duvulpr> Yeah.
  57. [09:32] <Duvulpr> I have enough hashpower to guarantee 51% by a wiiiiiide margin.
  58. [09:32] <ProjectMayhemWRK> this will cancel all transactions and the exchange may attempt to claim that back from you
  59. [09:32] <Duvulpr> right
  60. [09:32] <ProjectMayhemWRK> I can hit about 2g/hash on scrypt for an hour or so
  61. [09:33] <Duvulpr> That's really nice, how much will you charge?
  62. [09:33] <ProjectMayhemWRK> does beg the question why you don't just mine all the coins but I won't judge :P
  63. [09:33] <Duvulpr> haha
  64. [09:33] <ProjectMayhemWRK> Involves controlling all computers at my work and using the ~3000 PC's to CPU mine
  65. [09:33] <Duvulpr> it's simple, if I mine 51% and reject everyone else's mine, devs will probably end up forking and rollbacking
  66. [09:33] <ProjectMayhemWRK> they could do that anyway
  67. [09:34] <ProjectMayhemWRK> :P
  68. [09:34] <Duvulpr> Yeah, but not when I already cashed out my BTC from exchanges.
  69. [09:34] <Duvulpr> Good luck :P
  70. [09:34] <Duvulpr> The altcoin I have? Already got people who are willing to mix ready.
  71. [09:35] <ProjectMayhemWRK> what you do with it after I make it isn't my issue :P
  72. [09:35] <ProjectMayhemWRK> but tbh if you wanted to save 700k doge you could mod it yourself :-S
  73. [09:35] <Duvulpr> Absolutely. This is just for demonstration purposes only and will only be done on testnet.
  74. [09:35] <Duvulpr> :P
  75. [09:36] <Duvulpr> Well, I don't know C++ and can't be bothered trying to figure it out. I'd much prefer paying someone to do it, and reviewing their patch and learning C++ based on that.
  76. [09:37] <ProjectMayhemWRK> I'll give it a go, but I'll need to know which coin too
  77. [09:37] <ProjectMayhemWRK> and have access to the pool source
  78. [09:37] <Duvulpr> Why? I'd prefer if there is no market manipulation in advance.
  79. [09:37] <ProjectMayhemWRK> also this stratum will only be able to be used by you
  80. [09:37] <Duvulpr> That's correct
  81. [09:37] <ProjectMayhemWRK> you won't be able to role it out to your miners
  82. [09:38] <Duvulpr> What do you mean?
  83. [09:38] <ProjectMayhemWRK> if it attempts to mine another coin it will just fuck shit up :P
  84. [09:38] <Duvulpr> I'm pretty confused because most scrypt coins are API compatible
  85. [09:38] <Duvulpr> i.e.: changing to another coin consists of modifying the coind path.
  86. [09:38] <ProjectMayhemWRK> well the stratum will have a blockheight start on it
  87. [09:38] <Duvulpr> That's how it works for Scrypt mining pools.
  88. [09:39] <Duvulpr> Mhm, I thought that's supposed to be read from a text file?
  89. [09:39] <ProjectMayhemWRK> if you used it to mine another coin, it would attempt to carry out that command
  90. [09:39] <ProjectMayhemWRK> yeh it will read the height from whatever .ini file it's in
  91. [09:39] <ProjectMayhemWRK> but it will always attempt to read the height
  92. [09:39] <Duvulpr> Oh, you mean the block will be hardcoded?
  93. [09:39] <ProjectMayhemWRK> no...
  94. [09:39] <Duvulpr> as in the block header it starts off
  95. [09:40] <ProjectMayhemWRK> the command to mine >rs"blockheight"
  96. [09:40] <ProjectMayhemWRK> will be hard coded
  97. [09:40] <ProjectMayhemWRK> but blockheight, the actual number will be in a .ini file
  98. [09:40] <Duvulpr> OK
  99. [09:41] <Duvulpr> So it'd work for every scrypt coin, I just need to change the block height ?
  100. [09:41] <ProjectMayhemWRK> only if you have get 51% yes
  101. [09:41] <Duvulpr> Yeah, of course.
  102. [09:41] <ProjectMayhemWRK> but for ordinary mining you won't be able to use it
  103. [09:41] <Duvulpr> Yeah, so this can just do 51% attacks
  104. [09:41] <ProjectMayhemWRK> exactly
  105. [09:42] <ProjectMayhemWRK> so you can't roll it out to your miners
  106. [09:42] <Duvulpr> What do you mean?
  107. [09:42] <ProjectMayhemWRK> because it cannot mine normally
  108. [09:42] <Duvulpr> But I'm not interested in mining normally.
  109. [09:43] <Duvulpr> I'm just interested in rolling it out to my miners to 51%.
  110. [09:43] <ProjectMayhemWRK> your pool would be :P
  111. [09:43] <Duvulpr> what? so this doesn't mine 51%s?
  112. [09:43] <ProjectMayhemWRK> it wouldn't work like that, you can't physically manipulate the config file for the stratum once downloaded
  113. [09:44] <ProjectMayhemWRK> you also seriously risk being exposed letting anyone see this
  114. [09:44] <Duvulpr> 'once downloaded' ?
  115. [09:44] <ProjectMayhemWRK> your pools miners download a stratum program to mine on your pool?
  116. [09:44] <ProjectMayhemWRK> I haven't mined non-solo in a whilew
  117. [09:44] <Duvulpr> The pool's miners connect via stratum-tcp
  118. [09:45] <Duvulpr> It gets JSON-RPC payload of what hash to work on.
  119. [09:45] <Duvulpr> This is a job:
  120. [09:45] <Duvulpr> {"params": ["bf", "4d16b6f85af6e2198f44ae2a6de67f78487ae5611b77c6c0440b921e00000000",
  121. [09:45] <Duvulpr> "01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff20020862062f503253482f04b8864e5008",
  122. [09:45] <Duvulpr> "072f736c7573682f000000000100f2052a010000001976a914d23fcdf86f7e756a64a7a9688ef9903327048ed988ac00000000", [],
  123. [09:45] <Duvulpr> "00000002", "1c2ac4af", "504e86b9", false], "id": null, "method": "mining.notify"}
  124. [09:45] <Duvulpr> As you can see, Stratum simply tells miners what height to work on, and what difficulty to report back for a share.
  125. [09:46] <Duvulpr> The miners don't even know the block height. It just knows what to hash.
  126. [09:47] <ProjectMayhemWRK> things have changed
  127. [09:47] <Duvulpr> A lot. People who mine at pools no longer have any voting power ;)
  128. [09:48] <ProjectMayhemWRK> I would, but I can out hash most pools, as I just discovered a few minutes ago, my hour of solo mining last night found a block :P
  129. [09:48] <Duvulpr> Haha, nice, what coin?
  130. [09:48] <ProjectMayhemWRK> dogecoin
  131. [09:48] <Duvulpr> That's nice :)
  132. [09:48] <Duvulpr> Oh, and the pool software should be switchable to normal mode if the blockheight override isn't set.
  133. [09:48] <ProjectMayhemWRK> 73k :-p
  134. [09:49] <Duvulpr> Neat :P
  135. [09:49] <ProjectMayhemWRK> Duvulpr you would need to switch out the stratum
  136. [09:49] <ProjectMayhemWRK> like 2 seconds downtime as you do it
  137. [09:49] <Duvulpr> Yeah, restart it.
  138. [09:50] <Duvulpr> There's actually a Linux utility that allows you to hotswap any program with no downtime.
  139. [09:50] <Duvulpr> It starts the new executable, but keeps the old executable running till it finishes all pending tasks.
  140. [09:50] <Duvulpr> But anyway.
  141. [09:51] <Duvulpr> The reason why it should be minable normally, is in order for us to get 51%, we need to get the multipools to stop mining.
  142. [09:51] <Duvulpr> Hence: we mine normally with our GH/s, to make the difficulty higher, and for multipools to mine another coin.
  143. [09:51] <Duvulpr> Then, we'll have 51%++.
  144. [09:51] <ProjectMayhemWRK> I won't be able to do that
  145. [09:51] <ProjectMayhemWRK> :-/
  146. [09:51] <ProjectMayhemWRK> switch out would be the only option
  147. [09:52] <Duvulpr> Indeed, switch out is perfectly fine?
  148. [09:52] <Duvulpr> a few seconds of downtime is nothing
  149. [09:52] <ProjectMayhemWRK> I can't see why not
  150. [11:31] <Duvulpr> Hey, I'm going to go now but email me on opwolf@mail.com if you're intereste please
  151. [11:32] <ProjectMayhemWRK> will do
  152. [11:32] == No such nick/channel: Duvulpr
  153.  
  154.  
  155. ~Duvulpr@74-50-124-83.static.hvvc.us
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement