Advertisement
xhiggy

Selfish Mining

May 26th, 2017
329
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 58.44 KB | None | 0 0
  1. csw [1:36 AM]
  2. @cypherblock
  3. If you have done this correctly.
  4.  
  5. Explain the data pre and post 2016 blocks.
  6.  
  7. csw [1:38 AM]
  8. @satoshi
  9. That is the correct value.
  10.  
  11. Where is the working :wink:
  12. 3 replies Last reply 4 days ago View thread
  13.  
  14. csw [1:39 AM]
  15. @cypherblock
  16. The maximum Gamma based on the actual Bitcoin network is 0.002
  17.  
  18. That will come later.
  19.  
  20. Without Gamma, what are the results?
  21.  
  22. elliotolds [6:04 AM]
  23. @cypherblock sounds correct to me. props for going through the effort and proving it to yourself
  24.  
  25. csw [6:08 AM]
  26. Now, the issue is that the State diagram is wrong :slightly_smiling_face:
  27.  
  28. [6:08]
  29. But we will get to that.
  30.  
  31. [6:09]
  32. First, @cypherblock
  33.  
  34. What is the distribution without gamma of the discovery over the first week of blocks?
  35.  
  36. How many are discovered by your 1/3 SM in a day?
  37.  
  38. csw [6:16 AM]
  39. Fig 1 - State diagram.
  40.  
  41. State 3 goes to state 2
  42.  
  43. Explain how this is the case from the State diagram.... (G) when the pool wins from 1 -2 goes to state 0....
  44. Not state 3- state 2...
  45.  
  46. Did you not see the contradiction?
  47.  
  48. [6:19]
  49. Let us take Gamma at zero and ask what is the state table that results?
  50.  
  51. [6:20]
  52. 0.1 BTC for the first person (not you sorry @joeldalais ) to the person who posts it... Ending today
  53.  
  54. joeldalais [6:20 AM]
  55. :stuck_out_tongue:
  56.  
  57. csw [6:20 AM]
  58. If 12 hours pass, you can do one @joeldalais
  59.  
  60. joeldalais [6:21 AM]
  61. i can try :slightly_smiling_face:
  62.  
  63. thatwildcard [8:01 AM]
  64. it is, and now I know what a MOOC is - great idea :slightly_smiling_face:
  65. iang
  66. https://docs.google.com/document/d/1UiMS4Br7LkTIRdEOPjCukOxG6gIdCJTOgXbeOPBHrcE/edit#
  67. Posted in #selfish-miningMay 14th at 5:07 PM
  68.  
  69. cypherblock [8:29 AM]
  70. I’m doing some trials now with low gamma.
  71.  
  72.  
  73. csw [8:38 AM]
  74. Please track the solutions a day :slightly_smiling_face:
  75.  
  76. cypherblock [8:55 AM]
  77. Low gamma drastically reduces (or eliminates??) the selfish mining advantage in terms of rewarded-blocks per unit time. Right now my simulations are doing more retargeting than real bitcoin network. But I can see if I can normalize it.
  78.  
  79. csw [8:56 AM]
  80. As stated... Gamma is an assumption.
  81.  
  82. [8:57]
  83. The max you can in theory get for Gamma is 0.002 and closer to 0.00098
  84. And this is expensive
  85.  
  86. [8:58]
  87. To gain a 0.00098 Gamma right now will cost more than adding 10% Hash power to the network...
  88.  
  89. [8:58]
  90. Hence why I was saying that a test of the network is essential and that experiment is needed :wink:
  91.  
  92. [9:01]
  93. The network distance is so small and the density of vertices so high, that you will need 2.1x10^4 Sybil nodes for each Gamma gain of 0.00001
  94.  
  95. [9:02]
  96. To obtain a Gamma that radically alters the network will require 2x10^6 nodes.
  97.  
  98. [9:05]
  99. Amazon gave me a discounted monthly cost for this. $29,280,000.00 USD
  100.  
  101. [9:07]
  102. Does anyone argue that I *could not* obtain 10% of the network hash rate for less than the Amazon fees?
  103.  
  104. cypherblock [9:08 AM]
  105. Sybil nodes would not be the most effective way to do this. Probably do something like this describes: https://arxiv.org/abs/1605.07524
  106.  
  107. csw [9:08 AM]
  108. True, but the SM paper uses a Sybil node.
  109.  
  110. [9:09]
  111. That method is also wrong - for a completely different reason, but one thing at a time :slightly_smiling_face: (edited)
  112.  
  113. [9:11]
  114. The mapping of Bitcoin to the AS system is interesting. I will present this towards the end of the year.... too much to do
  115.  
  116. [9:12]
  117. The attack would slow transactions, but not blocks. So it is not the same as a SM attack and still does not help
  118.  
  119. [9:14]
  120. Quotes from SM:
  121. _"These virtual miners act as advance sensors by participating in data dissemination, but do not mine new blocks."_
  122.  
  123. _"By adding enough virtual nodes, the pool operator can thus increase γ"_
  124.  
  125. _"The virtual miners are managed by the pool, and once they hear of block X, they ignore it and start propagating block P"_
  126.  
  127. [9:15]
  128. So, we have:
  129.  
  130. "But a savvy pool operator can perform a sybil attack on honest miners by adding a significant number of zero-power miners to the Bitcoin miner network"_
  131.  
  132. [9:17]
  133. This is a logical Fallacy.
  134. http://rationalwiki.org/wiki/Appeal_to_probability
  135.  
  136. This is an extended for of the logical fallacy, *Appeal to probability*
  137.  
  138. This is the alternate form of the fallacy known as *"the appeal to possibility*. This flawed logic states in effect _"it is possible, therefore it is certain"_.
  139.  
  140. [9:20]
  141. *Next*
  142.  
  143. We come to the CORE of the argument.... What the authors NEED to address and fail miserably on.
  144.  
  145. _*"Because the protocol was believed to reward miners strictly in proportion to the ratio of the overall mining power they control, a miner in a large pool was believed to earn the same revenue as it would in a small pool."_*
  146.  
  147. Most critically,
  148. _"We show that, above a certain threshold size, the revenue of a selfish pool rises superlinearly with pool size above its revenue with the honest strategy."_
  149.  
  150. This is *the* thesis. The hypothesis.
  151.  
  152. [9:21]
  153. So, if you make more orphan blocks and even if you are close to 50%... you still gain under the revenue you would have gained.
  154.  
  155. [9:21]
  156. 50% of 144 blocks a day = 72 blocks
  157.  
  158. [9:22]
  159. At best, SM can make many orphans and increase the loss to the other party, but at what cost :slightly_smiling_face:
  160.  
  161. [9:22]
  162. Remember this is a hypothesis on:
  163.  
  164. *"We show that, above a certain threshold size, the revenue of a selfish pool rises superlinearly with pool size above its revenue with the honest strategy."*
  165.  
  166. [9:25]
  167. A rational business thinks differently to an academic.
  168. You think in terms of absolute returns.
  169.  
  170. Above *ITS* (the selfish miners' revenue with the honest strategy." (edited)
  171.  
  172. [9:27]
  173. *Next*
  174.  
  175. The authors say this is difficult to detect and stop....
  176.  
  177. Clearly they have no idea of statistical detection methods.
  178.  
  179. [9:28]
  180. In 2008, I wrote a paper and a tool to detect the use of Hydan, a stegonographic tool designed to hide information in code by flipping (ADD A) to (Sub -A) in the binary compiled code
  181.  
  182. [9:28]
  183. https://uk.sans.org/reading-room/whitepapers/stenganography/detecting-hydan-statistical-methods-classifying-hydan-based-stegonagraphy-execut-32839
  184.  
  185. [9:28]
  186. That was easy and it was 10,000,000,000,000 times harder than checking the release of blocks in the SM strategy (edited)
  187.  
  188. [9:32]
  189. Think on it...
  190. For a place where the SM has a lead:
  191.  
  192. HM releases, SM orphans it in seconds
  193. HM releases, SM orphans it in seconds
  194. HM releases, SM orphans it in seconds
  195. HM releases, SM orphans it in seconds
  196.  
  197. HM has lead...
  198.  
  199. HM finds a block after a long period...
  200. SM releases two and HM is orphaned
  201.  
  202. This is the simplest - *PUBLICLY* most simple to check real time attack to stop....
  203.  
  204. [9:33]
  205. Oh... and the state table is wrong....
  206.  
  207. If you actually check the processes, the state table never releases 2 or more blocks, but the strategy does...
  208.  
  209. cypherblock [9:34 AM]
  210. yes, detection seems like it would not be that difficult.
  211.  
  212. csw [9:34 AM]
  213. And this is not even a third of the way into the problems :wink:
  214.  
  215. [9:35]
  216. @cypherblock
  217. You detect this - it has been 2 days....
  218.  
  219. Will Honest miners allow it?
  220.  
  221. Or will they simply block the Selfish pool (and reject all its blocks (and this does not need code changes...
  222.  
  223. [9:35]
  224. They could fork the defecting pool...
  225.  
  226. [9:36]
  227. The pool could (at expense) reorg and try again, but at what gain and what costs?
  228.  
  229. [9:38]
  230. I will dig up and link the paper later, but it was myself who created and wrote the tool to detect *Hidden* TruCrypt volumes....
  231.  
  232. The process was used by law enforcement - hence TC is not used now.
  233.  
  234. cypherblock [9:38 AM]
  235. ok, have to eat now. First thing was to validate that IF gamma of say 50% is used, AND ignoring all other problems, does selfish strategy work? Seems like answer is yes. Next, sure we can show that achieving high gamma is difficult/expensive and detection not so hard.
  236.  
  237. csw [9:38 AM]
  238. THAT. That was difficult
  239.  
  240. TC hidden volumes, small entropy changes. Hard
  241.  
  242. [9:39]
  243. I have a paper and data that will kill Gamma
  244.  
  245. [9:39]
  246. :slightly_smiling_face:
  247.  
  248. [9:39]
  249. I have a complete node map of the bitcoin network from 2009 to well this year.
  250.  
  251. [9:40]
  252. We need to anonymise it prior to releasing the data
  253.  
  254. csw [9:40 AM]
  255. uploaded this image: image.png
  256. Add Comment
  257.  
  258. csw [9:41 AM]
  259. Oh, we could detect Hydan at an encoding level of 1/15,000
  260.  
  261. [9:43]
  262. The SM can be detected at the rate of a SM with 0.000,067% of the overall network and up doing it....
  263. And for a small SM, there is a loss :wink:
  264.  
  265. [9:43]
  266. I am off for now as well... Enough procrastination. I have a Risk paper for my MSc to get submitted :slightly_smiling_face:
  267.  
  268.  
  269. tomothy [11:23 AM]
  270. Gonna invite linzheming if that's ok? Im assuming it is?
  271.  
  272. csw [11:24 AM]
  273. It is ok
  274.  
  275. tomothy [11:24 AM]
  276. Oh, he's already here.
  277.  
  278. linzheming [11:25 AM]
  279. I’m not quite follow the concept sorry.
  280.  
  281. [11:26]
  282. Is there any definition or theory I can read first?
  283.  
  284. tomothy [11:26 AM]
  285. It's well above me. From my understanding, emir started from a flawed assumptions and therefore study is flawed.
  286.  
  287. csw [11:49 AM]
  288. Has anyone thought what happens to the "extra hidden blocks" when the difficulty changes?
  289.  
  290.  
  291. [11:49]
  292. The ones at a difficulty that is LOWER than the main honest chain...
  293.  
  294. [11:50]
  295. They do not need to be far ahead...
  296.  
  297. [11:50]
  298. Try adding it next :slightly_smiling_face:
  299.  
  300. david [12:01 PM]
  301. joined selfish-mining by invitation from @onchainscaling
  302.  
  303. cypherblock [12:46 PM]
  304. @csw yes this is an issue, but I don’t think it is a major flaw in SM algo. I can see if I can account for that in my model (reset private branch to 0 on difficulty change or something).
  305.  
  306. csw [12:48 PM]
  307. @cypherblock If the SM has a lead, they will have a small difficulty adjustment...
  308.  
  309. [12:48]
  310. Small is still rejected :slightly_smiling_face:
  311.  
  312. cypherblock [12:49 PM]
  313. the most number of blocks published at once in SM algo is 2.
  314.  
  315. csw [12:49 PM]
  316. Yes Published
  317.  
  318. [12:50]
  319. But Difficulty is calculated by them on their hidden blocks (edited)
  320.  
  321. [12:50]
  322. And this can differ from the main chain
  323.  
  324. cypherblock [12:51 PM]
  325. presumably SM miner uses main chain difficulty.
  326.  
  327. csw [12:51 PM]
  328. They do not know it
  329.  
  330. [12:51]
  331. Remember, they have hidden blocks
  332.  
  333. cypherblock [12:51 PM]
  334. They can run ‘border’ node or something to get this. Or multiple listener nodes around the world.
  335.  
  336. csw [12:52 PM]
  337. Again, they have blocks that are ahead of the change
  338.  
  339. [12:52]
  340. And they are not able to see the future are they?
  341.  
  342. [12:53]
  343. Block 2016 for the Honest miner is not the same as Block 2016 for the SM
  344.  
  345. [12:53]
  346. So, 2017 is not the same when it is republished
  347.  
  348. cypherblock [12:53 PM]
  349. It is a reasonable issue. I have been thinking about it as well. I’m not sure if the impact will be huge though. Yes they could predict the future, but that is probably unwise.
  350.  
  351. csw [12:53 PM]
  352. Each small issue erodes it.
  353.  
  354. [12:54]
  355. It was always a small gain. And each incorrect assumption makes it smaller and smaller
  356.  
  357. [12:54]
  358. :slightly_smiling_face:
  359.  
  360. [12:54]
  361. AND
  362.  
  363. [12:54]
  364. People are slowly learning how a few things may actually work
  365.  
  366. jpjp [12:56 PM]
  367. joined selfish-mining by invitation from @tomothy
  368.  
  369. iang [2:05 PM]
  370. :slightly_smiling_face:
  371.  
  372. csw [2:25 PM]
  373. Also remember this is off revenue. Each point on revenue makes a massive change in profit.
  374.  
  375. [2:25]
  376. :slightly_smiling_face:
  377.  
  378. [2:26]
  379. I guess we forgot that
  380.  
  381. [2:26]
  382. And non profitable = losses
  383.  
  384. elliotolds [3:16 PM]
  385. @ cypherblock , note that nothing bad happens to the selfish miners private blocks during a difficulty adjustment, because when he releases his own private blocks, the public chain will adopt the difficulty adjustment in the private chain
  386.  
  387. [3:17]
  388. @cypherblock
  389.  
  390. csw [3:30 PM]
  391. Will they now...
  392.  
  393. [3:30]
  394. Maybe you should test it and not assume.
  395.  
  396. [3:31]
  397. As the majority calls for a higher difficulty, you will find your statement is not the case
  398.  
  399. [3:31]
  400. The SM releases and is rejected
  401.  
  402. [3:31]
  403. And needs to align back to the chain.
  404.  
  405. [3:32]
  406. Even 2 blocks of 2016 can make a small difference.
  407.  
  408. [3:33]
  409. The SM can mine on a higher difficultly to ensure that this does not occur, but -
  410. 1. This is not a part of the strategy
  411. 2. It lowers returns at the end.
  412.  
  413. elliotolds [3:42 PM]
  414. csw you should try to give a concrete example of the difficulty adjustment causing problems for the SM, and you should see your mistake.
  415.  
  416. the public chain's difficulty adjustment will be roughly equal to the private chain's adjustment, fyi
  417.  
  418. csw [3:43 PM]
  419. If you have (HM +2), (SM +4)
  420.  
  421. SM changes at a lower difficulty than the HM.
  422.  
  423. Roughly is not the same as equal
  424.  
  425.  
  426. [3:44]
  427. Have you tested it :slightly_smiling_face:
  428.  
  429. elliotolds [3:46 PM]
  430. you mean the chain split is at block X, and HM is 2 blocks ahead and SM is 4 blocks ahead? the SM's chain's difficulty will end up slightly higher in this case. you seem to have the order backwards.
  431.  
  432. but the main point is that this doesn't matter, because the HM will publish their blocks, the public chain will start using the HM's difficulty, but then the SM will reveal hidden blocks and the public chain will switch over to the SM's difficulty adjustment
  433.  
  434. [3:46]
  435. give a concrete example, and you'll see your mistake :slightly_smiling_face:. gotta go for a bit
  436.  
  437. csw [3:47 PM]
  438. @elliotolds
  439. You seem extremely vested in a flawed model...
  440.  
  441.  
  442. I wonder why?
  443.  
  444. [3:47]
  445. And very much not interested in actually testing it,
  446.  
  447. [3:47]
  448. Real systems, real data :wink:
  449.  
  450. [3:48]
  451. And you may want to look up and real on the Negative Binomial distribution.
  452.  
  453. bitcoinsteffen [4:58 PM]
  454. joined selfish-mining by invitation from @bitsko
  455.  
  456. cypherblock [9:31 PM]
  457. I will see if I can improve my difficulty calcs a bit more. I am using one simplification which could affect outcome. I think @elliotolds is probably right though, but a couple of things I’m going to check.
  458.  
  459.  
  460. ----- May 22nd -----
  461. travin
  462. [12:55 AM]
  463. `https://pastebin.com/9s1VF16Z`
  464.  
  465.  
  466. csw [1:18 AM]
  467. Here is a big clue. Revenue is a time based and not block based function.
  468.  
  469. cypherblock [6:38 AM]
  470. my simulations calculate reward-blocks/hour, which should be a good indicator if a strategy has a revenue benefit or not.
  471.  
  472. csw [6:52 AM]
  473. What do you get in the first week for a 40% SM @cypherblock ?
  474.  
  475. [6:53]
  476. They will normally get 403.2 blocks
  477. And how many orphans?
  478.  
  479. [6:54]
  480. Here is a little secret. In this time frame, the SM can still not mine faster than alpha.
  481.  
  482. cypherblock [6:55 AM]
  483. Yes there may be a ‘transition cost’ when switching initially from honest to selfish, is that what you mean?
  484.  
  485. csw [6:56 AM]
  486. In part.
  487.  
  488. [6:56]
  489. But, remember that even if the HM gives up in the first week leaving ONLY the SM, the SM still only gets alpha of the total
  490.  
  491. [6:57]
  492. So, at best, they can get as much as they would have received.
  493.  
  494. [6:57]
  495. AT BEST
  496.  
  497. [6:57]
  498. Forget this notion of relative pools and other lies used in graphs to mislead.
  499.  
  500. [6:58]
  501. Some SM blocks are orphaned. Some HM blocks. It may be more HM than SM, BUT and here is the kicker...
  502.  
  503. [6:59]
  504. If the SM can at alpha = 0.4 earn at most 1 block every 25 mins (and that is the rate)
  505.  
  506. [6:59]
  507. Then, even if the Honest miners leave, the SM does not gain more.
  508.  
  509. csw [7:00 AM]
  510. uploaded this image: image.png
  511. Add Comment
  512.  
  513. csw [7:01 AM]
  514. The funny thing is that at 50% the SM earns less than a standard attack
  515.  
  516. At 50%, the SM earns 71.94 Blocks
  517.  
  518. A standard 50% plus attack gets them 72 (edited)
  519.  
  520. csw [7:54 AM]
  521. https://en.wikipedia.org/wiki/Base_rate_fallacy
  522. Wikipedia
  523. Base rate fallacy
  524. The base rate fallacy, also called base rate neglect or base rate bias, is a formal fallacy. If presented with related base rate information (i.e. generic, general information) and specific information (information only pertaining to a certain case), the mind tends to ignore the former and focus on the latter.
  525. Base rate neglect is a specific form of the more general extension neglect. (62kB)
  526.  
  527. [7:57]
  528. https://www.logicallyfallacious.com/tools/lp/Bo/LogicalFallacies/55/Base_Rate_Fallacy
  529. https://www.logicallyfallacious.com
  530. Base Rate Fallacy
  531. Ignoring statistical information in favor of using irrelevant information, that one incorrectly believes to be relevant, to make a judgment. This usually stems from the irrational belief that statistics don’t apply in a situation, for one reason or another when, in fact, they do. (226kB)
  532.  
  533. [7:57]
  534. Bar-Hillel, M. (1977). The Base-Rate Fallacy in Probability Judgments. Defense Technical Information Center.
  535.  
  536. csw [8:19 AM]
  537. Oh.... Did we consider what happens to transactions?
  538.  
  539. csw [8:19 AM]
  540. uploaded this image: image.png
  541. Add Comment
  542.  
  543. csw [8:21 AM]
  544. The result over time is that you add a queue load factor rho which becomes much larger than 0.5 then the average queue length (Transaction wait time) and response time for messages in the queue get large very quickly. When rho becomes 1.0, the queue will no longer reach a steady state, but will, in fact, grow in length as long as messages continue to arrive.
  545.  
  546. There are reasons Bitcoin holds a copy of the forked chain and what occurs when you try and hide this...
  547.  
  548. [8:24]
  549. AT 33.33% the SM will stop earning profit as the chain degrades exponentially
  550.  
  551. Do we believe that the other miners will just stop and give up?
  552.  
  553. They can stop this in seconds.
  554.  
  555. [8:24]
  556. 1. An introduction to Probability Theory and its Applications, Volume 1, William Feller, Wiley, 1957
  557.  
  558. phoenix
  559. [8:24 AM]
  560. @antanst
  561.  
  562. antanst [8:25 AM]
  563. joined selfish-mining by invitation from @phoenix
  564.  
  565. csw [8:25 AM]
  566. Oh and did you know that there is a very simple code fix for a SM attack (not for revenue, but to try and break the system)?
  567.  
  568. pesa [8:25 AM]
  569. lol! i can't make out what CSW says, but seems he knows what he talking about ! :grinning:
  570.  
  571. can't wait for the super secret release
  572.  
  573. csw [8:26 AM]
  574. It is so very simple.
  575.  
  576. You are going to kick yourself when it all comes out :slightly_smiling_face:
  577.  
  578. [8:27]
  579. And I will incorporate a code patch as an IF this ever occurs (as well as how to just use firewalls and a tool to detect it)
  580.  
  581. [8:29]
  582. The patch is simple.
  583.  
  584. Include the recorded blocks in the chain tree as a marker of orphans
  585.  
  586.  
  587. Use these with the difficulty increase and the orphans that are a part of the SM "attack" are then included meaning the SM attack even if allowed to go on for years can NEVER make a small increase in revenue let alone a profit
  588.  
  589. [8:30]
  590. @pesa
  591. I am smart enough to have others working with me who can change Craig Speak into Standard English :slightly_smiling_face:
  592.  
  593. csw [8:34 AM]
  594. uploaded this image: image.png
  595. Add Comment
  596.  
  597. csw [8:37 AM]
  598. Poisson is simpler to calculate and a fair approximation in certain circumstances...
  599.  
  600. That is why it is used.
  601.  
  602. However, when you are making time dependent calculations and testing hypothesis'... you need to be more exact.
  603.  
  604. Simple approximations do not suffice.
  605.  
  606. csw [8:37 AM]
  607. uploaded this image: image.png
  608. Add Comment
  609.  
  610. csw [8:38 AM]
  611. These differences seem minor.
  612. The use of the standard Lambda equation certainly saves time... But, small errors magnify.
  613.  
  614. csw [8:38 AM]
  615. uploaded this image: image.png
  616. Add Comment
  617.  
  618. csw [8:39 AM]
  619. These small differences from the Poisson approximation to the Binomial (and later the negative binomial all add up.
  620.  
  621. [8:39]
  622. Each roll is compounded. It is not one roll and move on the queue, but one after another after another...
  623.  
  624. [8:40]
  625. Error, multiplied by error, , multiplied by error, , multiplied by error, , multiplied by error, , multiplied by error,
  626.  
  627. [8:40]
  628. Small at first....
  629.  
  630. [8:42]
  631. See “An Introduction to Probability Theory and its Applications”, 2nd Edition, William Feller, Wiley, 1957
  632.  
  633. [8:43]
  634. *Question*
  635.  
  636. What does a 2-3% difference do to the model?
  637.  
  638. tomothy [8:48 AM]
  639. Make the error much much more worse?
  640.  
  641. csw [8:51 AM]
  642. Yes
  643.  
  644. [8:51]
  645. Small differences add up when run 1000s of times
  646.  
  647.  
  648. tomothy [8:54 AM]
  649. Like a manufacturing imperfection which wears over time due to the defect, exacerbates, and ultimately breaks
  650.  
  651. csw [8:55 AM]
  652. I am releasing a few papers.
  653.  
  654. 1. A very easy one with a fix and lots of diagrams.
  655. This shows the revenue flaws. Very easy to understand and a simple fix that kills SM even without the error.
  656. Also helps with some Time Warp attacks etc
  657.  
  658. 2. A more complex paper and model
  659. Based on real systems and hosts - incorporating the
  660.  
  661. 3. An SEIR system that defines how the Blocks propagate in detail.
  662.  
  663. 4. The maths. As done from the integrated values (on time censored data)
  664. Sorry, but this one is not easy and will be ignored for the simple stuff by most people
  665.  
  666. 5. The network models. All the data on how the Bitcoin network looks and reacts.
  667.  
  668.  
  669. tomothy [8:58 AM]
  670. Anything soon, like a press release, regarding dangers of segwit? Would be timely in light of consensus news. Need a counter narrative starting
  671.  
  672.  
  673. cryptorebel [9:18 AM]
  674. segbleed
  675.  
  676.  
  677. csw [9:34 AM]
  678. LOL
  679.  
  680. [9:34]
  681. Soon yes.
  682.  
  683.  
  684. pesa [9:37 AM]
  685. segboost
  686.  
  687. checksum0
  688. [9:38 AM]
  689. asicbleed...
  690.  
  691. [9:38]
  692. Oh wait...
  693.  
  694. erik.beijnoff [11:31 AM]
  695. joined selfish-mining by invitation from @bitsko, along with @mengerian
  696.  
  697. satoshi [12:34 PM]
  698. Looking forward to the release of those papers csw
  699.  
  700. macsga
  701. [12:36 PM]
  702. just caught up with -most of- the news
  703.  
  704. [12:36]
  705. they don't know the significance of btc protocol
  706.  
  707.  
  708. phoenix
  709. [3:05 PM]
  710. @dimitrist
  711.  
  712. dimitrist [3:05 PM]
  713. joined selfish-mining by invitation from @phoenix
  714.  
  715.  
  716. ----- May 23rd -----
  717. satoshi [6:15 AM]
  718. @adamselene
  719.  
  720. adamselene [6:16 AM]
  721. joined selfish-mining by invitation from @satoshi
  722.  
  723. adamselene [6:19 AM]
  724. @csw the odds of a selfish miner with 30% hashrate finding 3 blocks before honest miners found 1 block works out to 2.7%?
  725.  
  726. csw [6:44 AM]
  727. Yes
  728.  
  729. foorbarbaz [7:00 AM]
  730. left selfish-mining
  731.  
  732. csw [8:33 AM]
  733. uploaded this image: image.png
  734. Add Comment
  735.  
  736. csw [8:34 AM]
  737. On pseudo profound bullshit. | Selfish Mining :slightly_smiling_face:
  738.  
  739. bitalien
  740. [3:40 PM]
  741. joined selfish-mining by invitation from @cryptorebel
  742.  
  743.  
  744. ----- Yesterday May 25th, 2017 -----
  745. csw [12:41 PM]
  746. Here you go... a Little reading...
  747. https://bitcoil.co.il/Doublespend.pdf
  748.  
  749. csw [12:41 PM]
  750. uploaded this image: image.png
  751. Add Comment
  752.  
  753. csw [12:42 PM]
  754. I have been telling you that the maths is an approximation....
  755.  
  756. csw [1:08 PM]
  757. http://organofcorti.blogspot.co.uk/2015/07/faq-bitcoin-mining-and-luck-statistic.html
  758. organofcorti.blogspot.co.uk
  759. FAQ: Bitcoin mining and the luck statistic
  760. "Bitcoin mining pool, network and exchange analysis" (73kB)
  761.  
  762. [1:08]
  763. Also got it...
  764.  
  765. [1:09]
  766. And here is a detailed model
  767.  
  768. [1:09]
  769. https://arxiv.org/pdf/1702.02867.pdf
  770.  
  771. zbingledack [2:15 PM]
  772. Oh wow
  773.  
  774. [2:15]
  775. This seems clearer
  776.  
  777. csw [2:15 PM]
  778. :slightly_smiling_face:
  779.  
  780. [2:16]
  781. I like suspense
  782.  
  783. macsga
  784. [2:16 PM]
  785. @csw did you write that faq (organofcorti)? (edited)
  786.  
  787. csw [2:16 PM]
  788. No, not I
  789.  
  790. macsga
  791. [2:16 PM]
  792. he's a very bright man
  793.  
  794. csw [2:16 PM]
  795. But it is by a maths geek :slightly_smiling_face:
  796.  
  797. macsga
  798. [2:16 PM]
  799. :slightly_smiling_face:
  800.  
  801. csw [2:16 PM]
  802. I do recomend the page
  803.  
  804. macsga
  805. [2:17 PM]
  806. I do too :slightly_smiling_face:
  807.  
  808. csw [2:17 PM]
  809. So, as I said... wrong math
  810.  
  811. [2:18]
  812. https://bitcoinwisdom.com/bitcoin/difficulty
  813. bitcoinwisdom.com
  814. Bitcoin Difficulty and Hashrate Chart - BitcoinWisdom
  815. Bitcoin Difficulty hashrate chart and accurate estimated next difficulty.
  816.  
  817. [2:18]
  818. This is next
  819.  
  820. [2:19]
  821. https://bitcoinwisdom.com/assets/difficulty/bitcoin-difficulty.png?1495736104 (41kB)
  822.  
  823. [2:19]
  824. As difficulty is not static, it radically alters the distrbution
  825.  
  826. macsga
  827. [2:20 PM]
  828. this is correct
  829.  
  830. [2:20]
  831. more complex calc is needed
  832.  
  833. [2:20]
  834. may I suggest a FFT?
  835.  
  836. zbingledack [2:21 PM]
  837. So I gather that the probability of a selfish miner with 40% of the hashpower finding the next block starting from a given time _t_ is indeed 40%
  838.  
  839. But the probability of the SM finding a certain number of blocks before the HM finds a certain other number of blocks involves binomials
  840.  
  841. This was not in the SM paper? They used the simplified math?
  842.  
  843. csw [2:21 PM]
  844. Yes
  845.  
  846. [2:21]
  847. The simple 10 min exact (Only) approximation
  848.  
  849. [2:21]
  850. And yes, they did not use the Neg Binomial
  851.  
  852. zbingledack [2:22 PM]
  853. Oops :)
  854.  
  855. csw [2:22 PM]
  856. Starting to see what I was trying to get others to see?
  857.  
  858. zbingledack [2:22 PM]
  859. It at least seems quite plausible that there is something there
  860.  
  861. csw [2:22 PM]
  862. Sorry I have dragged this on, but I was hoping people would see it without my slapping them in the face with it
  863.  
  864. zbingledack [2:23 PM]
  865. Funny how you always seem to be keenly aware of what was written in the whitepaper.....
  866.  
  867.  
  868. csw [2:23 PM]
  869. Moore's law and increasing competition harm the selfish miner as well
  870.  
  871. [2:23]
  872. Yes, funny :stuck_out_tongue:
  873.  
  874. [2:24]
  875. I tried to tell Gun, but he told me how much smarter he was than me... so his loss
  876.  
  877. [2:26]
  878. If you just model using their model, you fail to test the system
  879.  
  880. [2:26]
  881. You do not do science, you validate what you are given.
  882.  
  883. csw [2:29 PM]
  884. uploaded this image: image.png
  885. Add Comment
  886.  
  887. csw [2:29 PM]
  888. uploaded this image: image.png
  889. Add Comment
  890.  
  891. csw [2:29 PM]
  892. uploaded this image: image.png
  893. Add Comment
  894.  
  895. csw [2:30 PM]
  896. Sorry... messy - the edited version is in the office
  897.  
  898. csw [2:30 PM]
  899. uploaded this image: image.png
  900. Add Comment
  901.  
  902. csw [2:31 PM]
  903. AND....
  904.  
  905. This is where I lose people:
  906.  
  907. csw [2:31 PM]
  908. uploaded this image: image.png
  909. Add Comment
  910.  
  911. macsga
  912. [2:32 PM]
  913. lol
  914.  
  915. [2:32]
  916. you actually found one to peer review it ?
  917.  
  918.  
  919. csw [2:33 PM]
  920. Yes, it is going into a maths journal (edited)
  921.  
  922. [2:33]
  923. I could find nobody in the Bitcoin world
  924.  
  925.  
  926. csw [2:34 PM]
  927. uploaded this image: image.png
  928. Add Comment
  929.  
  930. zbingledack [2:36 PM]
  931. Is the "differentiation on a net" stuff necessary to destroy the SM argument, or just icing?
  932.  
  933. elliotolds [2:36 PM]
  934. What makes this seem plausible to you? You saw how cypherblock's simulations made him think me and peter_r were right, no? Isn't it still the case that no technical person who has looked into this agrees with csw?
  935. zbingledack
  936. It at least seems quite plausible that there is something there
  937. Posted in #selfish-miningYesterday at 2:22 PM
  938.  
  939. csw [2:36 PM]
  940. uploaded this image: image.png
  941. Add Comment
  942.  
  943. csw [2:36 PM]
  944. Oh @elliotolds
  945. You still try and protect Gun's model
  946.  
  947. macsga
  948. [2:37 PM]
  949. My mind is fried; been on a continuous 6h lecture on Bioinformatics & Bioethics
  950.  
  951. [2:37]
  952. I think I'll pass out
  953.  
  954. csw [2:37 PM]
  955. CYRIL GRUNSPAN AND RICARDO PEREZ-MARCO ´
  956.  
  957.  
  958. [2:37]
  959. They proved it IS a Negative Binomial :wink:
  960.  
  961. [2:37]
  962. Independantly
  963.  
  964. [2:38]
  965. They did not then go on to apply it to all the cases I used
  966.  
  967. zbingledack [2:39 PM]
  968. @elliotolds Seems an easy error to make, especially since the approximation is so close.
  969.  
  970. csw [2:39 PM]
  971. Oh @elliotolds
  972.  
  973. You believe that as I cannot simplify this sufficiently for you it makes it wrong..
  974.  
  975. [2:40]
  976. https://arxiv.org/pdf/1702.02867.pdf
  977.  
  978. [2:40]
  979. Have a read
  980.  
  981. elliotolds [2:41 PM]
  982. What specific error do you think is being made, @zbingledack? The only assumption in the paper about mining probabilities is that the probability of finding the next block equals your proportion of the hash power
  983.  
  984. [2:41]
  985. which you seem to accept
  986.  
  987. csw [2:41 PM]
  988. And it is wrong
  989.  
  990. [2:42]
  991. It is an approximate for 10 mins exactly AND only for a following block (edited)
  992.  
  993. [2:43]
  994. A percent or two here and there, multiplied (edited)
  995.  
  996. [2:43]
  997. All goes to making it more and more error bound
  998.  
  999. elliotolds [2:43 PM]
  1000. It has nothing to do with the time to find a block. It applies no matter how long it takes. If you buy 10% of lottery tickets randomly and there's one winner, you have a 10% chance of winning. Same concept
  1001.  
  1002. csw [2:44 PM]
  1003. Then just assume a 1.0 Gamma for the network
  1004.  
  1005. [2:44]
  1006. You DO understand that it is NOT possible to EVER get a gamma of 1.0 or even be close with pool mining going on?
  1007.  
  1008. [2:44]
  1009. @elliotolds
  1010. You believe that
  1011.  
  1012. [2:45]
  1013. Try and selfish mine
  1014.  
  1015. elliotolds [2:45 PM]
  1016. No matter how long finding the next block takes, if you have x% of hash power you're buying x% of the lottery tickets...
  1017.  
  1018. csw [2:45 PM]
  1019. And - it is the EASIEST thing to detect and stop
  1020.  
  1021. [2:45]
  1022. Yes @elliotolds
  1023.  
  1024. You know best. Ignore all that nasty maths
  1025.  
  1026. [2:46]
  1027. http://organofcorti.blogspot.co.uk/2015/07/faq-bitcoin-mining-and-luck-statistic.html
  1028. organofcorti.blogspot.co.uk
  1029. FAQ: Bitcoin mining and the luck statistic
  1030. "Bitcoin mining pool, network and exchange analysis" (73kB)
  1031.  
  1032. [2:46]
  1033. Ignore these nasty difficult to use Erlang distributions.
  1034.  
  1035. [2:46]
  1036. Why use the actual thing when you can approximate
  1037.  
  1038. cypherblock [2:47 PM]
  1039. @csw do you agree that with SM approach, the SM releases blocks more slowly than they would otherwise?
  1040.  
  1041. csw [2:47 PM]
  1042. They create far more orphans
  1043.  
  1044. [2:47]
  1045. They cause all miners to lose
  1046.  
  1047. [2:48]
  1048. And they can NEVER gain more than the amount they could have gained if they did not selfish mine
  1049.  
  1050. [2:48]
  1051. Here is a web page to try see if you can play with compounding error
  1052. http://statpages.info/erpropgt.html
  1053.  
  1054. [2:49]
  1055. And
  1056.  
  1057. [2:49]
  1058. http://ipl.physics.harvard.edu/wp-uploads/2013/03/PS3_Error_Propagation_sp13.pdf
  1059.  
  1060. [2:50]
  1061. And
  1062.  
  1063. [2:50]
  1064. https://www.lhup.edu/~dsimanek/scenario/errorman/propagat.htm
  1065.  
  1066. [2:50]
  1067. The best a SM can do id screw all miners (including themselves) up
  1068.  
  1069. cypherblock [2:51 PM]
  1070. The main flaw with SM is the assumption that high gamma can be achieved, and that other miners can’t do things in defense of it. But I’m not sure @csw you have a case against it if you accept those premises.
  1071.  
  1072. csw [2:52 PM]
  1073. They can never earn more than the daily revinue, they can earn less but screw up all miners
  1074.  
  1075. [2:52]
  1076. @cypherblock
  1077. Gamma for bitcoin can never be more than 0.0002
  1078.  
  1079. [2:52]
  1080. And it is costly to make it more than 0.0001
  1081.  
  1082. cypherblock [2:52 PM]
  1083. my simulations show otherwise. I admit my sims could be wrong. Assume gamma of .5 !!! .5 I tell you :slightly_smiling_face:
  1084.  
  1085. csw [2:53 PM]
  1086. You are not modeling the network
  1087.  
  1088. cypherblock [2:53 PM]
  1089. SM miner releases blocks only when honest miners do and at most 1 or 2.
  1090.  
  1091. [2:53]
  1092. what does this do to difficulty?
  1093.  
  1094. [2:53]
  1095. assume gamma of .5
  1096.  
  1097. csw [2:53 PM]
  1098. https://bitcoinwisdom.com/bitcoin/difficulty
  1099.  
  1100. [2:54]
  1101. https: // bitcoinwisdom.com/bitcoin/difficulty
  1102.  
  1103. cypherblock [2:54 PM]
  1104. 50% of honest miners will receive and mine on top of a selfish block when it is published immediately after an honest block. This is the assumption.
  1105.  
  1106. csw [2:54 PM]
  1107. The network distance is under 1.32
  1108.  
  1109. [2:54]
  1110. You CANNOT send to 50% of miners
  1111.  
  1112. [2:54]
  1113. in a single hop
  1114.  
  1115. cypherblock [2:55 PM]
  1116. fine but IF you COULD.
  1117.  
  1118. csw [2:55 PM]
  1119. Then it is NOT Bitcoin
  1120.  
  1121. [2:55]
  1122. That will be what they make with Seg Wit
  1123.  
  1124. [2:55]
  1125. In ordere to do that, you need to add hops
  1126.  
  1127. [2:56]
  1128. The network is far too densely connected.
  1129.  
  1130.  
  1131. cypherblock [2:56 PM]
  1132. Whatever, but IF gamma is .5 or other suitably high number, then SM strategy might work, don’t you think? Can we not speak in hypotheticals?
  1133.  
  1134. [2:56]
  1135. if gamma is 0 SM strategy does not work.
  1136.  
  1137. csw [2:56 PM]
  1138. That will require that you go back to 21 machines and slow networks and even that will only get you a distrance of 3-4
  1139.  
  1140. [2:56]
  1141. Ok. Are we talking SegWit
  1142.  
  1143. [2:57]
  1144. That CAN have a high Gamma
  1145.  
  1146. cypherblock [2:57 PM]
  1147. it is a hypothetical. Assume gamma is .5, what is the result of SM strategy? (edited)
  1148.  
  1149. csw [2:57 PM]
  1150. SegWit can have a gamma as high as 0.8 (edited)
  1151.  
  1152. [2:58]
  1153. People are confusing centrality with being centralised
  1154.  
  1155. [2:58]
  1156. IFF Gamma was to be altered in this way
  1157.  
  1158. [2:58]
  1159. The SM does not benifit still (edited)
  1160.  
  1161. [2:59]
  1162. The network collapses
  1163.  
  1164. [2:59]
  1165. All lose
  1166.  
  1167. [3:00]
  1168. Over 50% of all mined Transactions are orphaned
  1169.  
  1170. [3:01]
  1171. Wallets in SegWit can pretend to be nodes, so in SegWit coin. Gamma can be 0.8 and nobody wins
  1172.  
  1173. cypherblock [3:01 PM]
  1174. Assume single mining pool is using SM strategy and they are at like 33% hash power. Assume high gamma like .5. Assume other pools don’t detect the SM. This is what I ran my simulations with. It is fine to say those assumptions are completely unrealistic. But given these completely unrealistic assumptions, does SM strategy work? What other unrealistic assumptions must be added?
  1175.  
  1176. csw [3:02 PM]
  1177. Block Tree
  1178.  
  1179. [3:02]
  1180. Remember nodes are not JUST a store of the main chain, they also hold memory of orphans and create a tree map
  1181.  
  1182. [3:03]
  1183. At 33%. What is the most blocks that a miner can create in a day?
  1184.  
  1185. [3:03]
  1186. Selfish or even Gamma =1
  1187.  
  1188. [3:03]
  1189. The absolute most blocks?
  1190.  
  1191. [3:04]
  1192. Averaged :slightly_smiling_face:
  1193.  
  1194. [3:04]
  1195. And assume 10 mins for now
  1196.  
  1197. [3:04]
  1198. Average
  1199.  
  1200. cypherblock [3:04 PM]
  1201. 144*.33
  1202.  
  1203. [3:04]
  1204. if you assume their hashpower is accounted for in difficulty
  1205.  
  1206. csw [3:05 PM]
  1207. So, if 20% of those blocks are orphaned... Can they solve more?
  1208.  
  1209. cypherblock [3:05 PM]
  1210. What if their hash power is not adequately accounted for?
  1211.  
  1212. csw [3:05 PM]
  1213. Explain?
  1214.  
  1215. cypherblock [3:05 PM]
  1216. Simplistic example.
  1217.  
  1218. csw [3:06 PM]
  1219. Explain sorry?
  1220.  
  1221. cypherblock [3:06 PM]
  1222. Imagine miner comes on right now, with 100% of existing hashpower.
  1223.  
  1224. [3:06]
  1225. Sorry no like 110%
  1226.  
  1227. csw [3:06 PM]
  1228. A SM or Honest
  1229.  
  1230. [3:06]
  1231. ?
  1232.  
  1233. cypherblock [3:07 PM]
  1234. Selfish I guess. How many blocks can they mine in a day?
  1235.  
  1236. csw [3:08 PM]
  1237. So, they add 10% or they are now 110%
  1238.  
  1239. cypherblock [3:09 PM]
  1240. They have 110% of existing hashpower. Imagine hash power is X, they come online today with X(plus a bit). So total hashpower is now 2X plus a bit.
  1241.  
  1242. csw [3:10 PM]
  1243. Then they have over 50% of the network
  1244.  
  1245. [3:10]
  1246. They can do attacks that do not require SM
  1247.  
  1248. cypherblock [3:10 PM]
  1249. yes, but difficulty is not set for them.
  1250.  
  1251. csw [3:10 PM]
  1252. And SM earns less than if they just drop all other miners :slightly_smiling_face:
  1253.  
  1254. [3:10]
  1255. It does not matter
  1256.  
  1257. [3:11]
  1258. They now have 52.38% of the network
  1259.  
  1260. cypherblock [3:11 PM]
  1261. My point is that they can mine more blocks than they could if difficulty accounted for them. They could mine 145 blocks in a day, and publish all of those. If difficulty accounted for them, then they could not do this.
  1262.  
  1263. csw [3:11 PM]
  1264. They can simply mine a block in less time then all others combined
  1265.  
  1266. [3:11]
  1267. If they added 110%
  1268.  
  1269. cypherblock [3:12 PM]
  1270. Have to run out for a bit. Think on this. I’m trying to prove the point that if your hash is not accounted for in difficulty then you can mine extra blocks.
  1271.  
  1272. csw [3:12 PM]
  1273. They have 68.25% of the network
  1274.  
  1275. [3:12]
  1276. It is still better from a revenue point to just mine and not drop over half the network
  1277.  
  1278. cypherblock [3:13 PM]
  1279. SM paper works if difficulty adjusts to be lower than what it would be if everyone using honest approach. It is difficulty hiding attack.
  1280.  
  1281. csw [3:13 PM]
  1282. Assuming a static difficulty
  1283.  
  1284. [3:13]
  1285. Difficulty grows in a log linear manner
  1286.  
  1287. [3:13]
  1288. See bitcoinwisdom.com/bitcoin/difficulty
  1289.  
  1290. [3:14]
  1291. So, in a static world without Moore's l;aw, competition or markets... maybe
  1292.  
  1293. [3:14]
  1294. But I model this world
  1295.  
  1296. zbingledack [3:15 PM]
  1297. To be clear, my understanding is that the CSW claim is that SM doesn't even work under those unrealistically-favorable-to-SM conditions.
  1298. cypherblock
  1299. Assume single mining pool is using SM strategy and they are at like 33% hash power. Assume high gamma like .5. Assume other pools don’t detect the SM. This is what I ran my simulations with. It is fine to say those assumptions are completely unrealistic. But given these completely unrealistic assumptions, does SM strategy work? What other unrealistic assumptions must be added?
  1300. Posted in #selfish-miningYesterday at 3:01 PM
  1301. (edited)
  1302.  
  1303. csw [3:16 PM]
  1304. What is the claim to the paper?
  1305.  
  1306. zbingledack [3:16 PM]
  1307. By "the claim" I meant your claim
  1308.  
  1309. [3:17]
  1310. (Though see edit)
  1311.  
  1312. csw [3:17 PM]
  1313. My claim their claim is false.
  1314.  
  1315. zbingledack [3:17 PM]
  1316. Yeah
  1317.  
  1318. csw [3:17 PM]
  1319. _"enables the selfish pool to collect higher revenues"_
  1320.  
  1321. zbingledack [3:18 PM]
  1322. I just think @cypherblock is thinking his question wasn't answered there
  1323.  
  1324. csw [3:18 PM]
  1325. What is revenue?
  1326.  
  1327. [3:20]
  1328. _"We show that, above a certain threshold size, the revenue of a selfish pool rises superlinearly with pool size above its revenue with the honest strategy."_
  1329.  
  1330. Fair revenue is .33 * 144 = 48 blocks a day
  1331.  
  1332. [3:20]
  1333. Show me how they earn more than this?
  1334.  
  1335. [3:21]
  1336. _"We assume that miners are rational; that is, they try to maximize their revenue"_
  1337.  
  1338. [3:21]
  1339. The loss is in Orphans.
  1340.  
  1341. [3:21]
  1342. 20 or so lost blocks a day.
  1343.  
  1344. joeldalais [3:21 PM]
  1345. i think he's aiming at - the paper claims that if you withhold a block just before a difficulty adjustment, then difficulty adjustment happens, then you can finish/propagate the block (from before the adjustment changed) faster than the HM
  1346. 6 replies Last reply a day ago View thread
  1347.  
  1348. csw [3:22 PM]
  1349. The assumption here is that difficulty is static
  1350.  
  1351. joeldalais [3:22 PM]
  1352. yes
  1353.  
  1354. csw [3:22 PM]
  1355. Try and see what happens when it is log linear....
  1356.  
  1357. [3:22]
  1358. As Bitcoin is and always has been :slightly_smiling_face:
  1359.  
  1360.  
  1361. [3:23]
  1362. Now, you also seem to think that the withholding of 4-5 blocks at the difficulty change makes a large difference? Over 2016 blocks and a log linear system
  1363.  
  1364. joeldalais [3:24 PM]
  1365. they work with the assumption difficulty for their withheld block won't change, that nodes are not 'inoculated' by honest miners (they don't see that the honest miner 'block' is already fast propagating over the network and that the sm block can never ever catch up)
  1366.  
  1367. csw [3:24 PM]
  1368. Or result in storms of orphans
  1369.  
  1370. joeldalais [3:24 PM]
  1371. they think that the 'released sm' block (which is late), competes against the 'same level of blocks'
  1372.  
  1373. csw [3:25 PM]
  1374. And orphans are not revenue inducing. (edited)
  1375.  
  1376. csw [3:25 PM]
  1377. uploaded this image: bitcoin-difficulty.png
  1378. Add Comment
  1379.  
  1380. csw [3:26 PM]
  1381. Look at the saw tooth effect....
  1382.  
  1383. [3:26]
  1384. Linear even as an approximation is so far in error
  1385.  
  1386. elliotolds [3:27 PM]
  1387. @cypherblock you said "if gamma is 0 SM strategy does not work." .. don't your simulations show that even if gamma is 0, SM is profitable if their hash rate is above 33%?
  1388.  
  1389. csw [3:28 PM]
  1390. Do you understand what profit is @elliotolds ?
  1391.  
  1392. [3:28]
  1393. If you can NEVER earn more than 48 a day at 33% and you intro orphans
  1394.  
  1395. [3:28]
  1396. You lose profit
  1397.  
  1398. joeldalais [3:29 PM]
  1399. they wouldn't be 'profitable' until they have a super majority of hash (which then destroys the system), then it becomes - whats the point of selfish mining? if its for profit, then its more profitable to honest mine
  1400.  
  1401. [3:30]
  1402. honest mining is always more profitable than selfish mining, short term and long term
  1403.  
  1404. [3:30]
  1405. occam's razor - if selfish mining actually was legit, then it would have occurred already
  1406.  
  1407. csw [3:30 PM]
  1408. :slightly_smiling_face:
  1409.  
  1410. [3:30]
  1411. Max rate - alpha
  1412.  
  1413. [3:30]
  1414. Never more
  1415.  
  1416. [3:31]
  1417. Gamma = 1 -> alpha = alpha (edited)
  1418.  
  1419. [3:31]
  1420. Gamma <1 -> Alpha is < Honest Alpha
  1421.  
  1422. [3:32]
  1423. The *BEST* you can do is honest
  1424.  
  1425.  
  1426. [3:32]
  1427. The only *attack* is trying to damage the network and this ALSO has a solution
  1428.  
  1429. [3:33]
  1430. Scale. Larger blocks, more TXs and scale means lower attack rates
  1431.  
  1432. [3:33]
  1433. SegWit is higher Gamma.
  1434.  
  1435. [3:33]
  1436. SegWit INCENTIVIZES attacks
  1437.  
  1438.  
  1439. zbingledack [3:44 PM]
  1440. Just to check I have understood the claims:
  1441.  
  1442. Even under Segwit we are safe from SM (even if it went undetected), right? It's just that it moves us in the wrong direction by increasing gamma?
  1443.  
  1444. [3:44]
  1445. Or rather safe from SM being profitable
  1446.  
  1447. csw [3:45 PM]
  1448. Safe from stollen money
  1449.  
  1450. zbingledack [3:45 PM]
  1451. So basically SM will never profit, but Segwit does make it easier to use SM to disrupt the network?
  1452.  
  1453. csw [3:45 PM]
  1454. Not safe from Sybil attacks
  1455.  
  1456. [3:45]
  1457. Yes
  1458.  
  1459. [3:46]
  1460. SegWit makes all these Sybil nodes
  1461.  
  1462. zbingledack [3:46 PM]
  1463. I see
  1464.  
  1465. csw [3:46 PM]
  1466. The very thing Bitcoin solved, they want to add back
  1467.  
  1468. csw [4:27 PM]
  1469. Marshall-Olkin exponential distribution
  1470.  
  1471. [4:27]
  1472. Marshall, A. W. and Olkin, I. (1997). A new method for adding a parameter to a family of distributions with application to the exponential and Weibull families. Biometrika,
  1473. 84, 641-652. (edited)
  1474.  
  1475. [4:28]
  1476. A little closer to the real model
  1477.  
  1478. cypherblock [4:30 PM]
  1479. I am back now. Catching up on above.
  1480.  
  1481. cypherblock [5:25 PM]
  1482. running a couple more sims to test gamma zero for SM higher than 33%.
  1483.  
  1484. [5:29]
  1485. to see if @elliotolds is correct about SM approach winning in these scenarios
  1486.  
  1487. nicholat [6:22 PM]
  1488. joined selfish-mining by invitation from @tomothy. Also, @bergun joined, @hantheme joined.
  1489.  
  1490.  
  1491. ----- Today May 26th, 2017 -----
  1492. csw [3:48 AM]
  1493. _“Selfish miners achieve this goal by selectively revealing their mined blocks to invalidate the honest miners’ work. Approximately speaking, the selfish mining pool keeps its mined blocks private, secretly bifurcating the blockchain and creating a private branch.”_
  1494.  
  1495. Any miner can do this at any time it is called forking.
  1496.  
  1497. The majority group of miners do not do this as their forked chain would have far less value and have a longer transaction rate and not be able to maintain the same level of service as the primary chain. A selfish miner doing the strategy will find very quickly that they are isolated in their own chain. The issue with this is that they will create a separate bitcoin fork and not rejoin with the main chain.
  1498.  
  1499. At any time, any miner can choose to fork.
  1500.  
  1501. This does not occur as it is not in their rational self-interest. If a pool miner was to do this, they would quickly find that their pool members leave for the main chain reducing their hash rate in the selfish pool further. (edited)
  1502.  
  1503. [3:49]
  1504. _“ and enables the selfish pool to collect higher revenues by incorporating a higher fraction of its blocks into the blockchain.”_
  1505.  
  1506. Again, the authors failed to see the difference between absolute and fractional revenue. They do not understand that a smaller overall revenue comes with the existing costs making a far less profitable strategy.
  1507.  
  1508. For instance, if a miner manages to make a little over 10% gross profit, and they have 33% of the hash power, they will expect to earn 48 blocks a day of which just under five blocks a day is attributable to gross profit.
  1509.  
  1510. If this 33 percent selfish mines, they will expect to earn a revenue of 42 blocks a day. We have already seen that they are profitable over 43 blocks. Consequently, the selfish mining strategy does not only reduce revenue but it creates a profit loss. The selfish miner moves from a scenario where they are making money to one where they are creating loss. The value of bitcoin is determined at market. As more and more bitcoin are released and the block reward is diminishing, the impact of mining you blocks also diminishes.
  1511.  
  1512. [3:50]
  1513. _“Its decisions depend only on the relative lengths of the selfish pool’s private branch versus the public branch.”_
  1514.  
  1515. The decisions do not depend solely on the selfish mining pools perceived ratio, or mining activity involves profitability calculations. This is a combination of costs and earnt revenue. There are ways to reduce costs. Capital and sunk costs can be attributed over a longer period but operational costs depend on the actions being undertaken. A miner can choose to turn equipment off, lowering the hash rate and their revenue at a particular point in time but at the same time reducing operational costs as they are not paying for the use of the equipment.
  1516. This strategy can make sense when there are differentials in operational costs such as off peak versus peak electricity fees.
  1517.  
  1518. In the case of the selfish mining strategy, the announced “rational” strategy suggested by the paper’s authors is to maintain costs including operational costs whilst simultaneously lowering revenue. Any first-year business or finance student let alone anyone who has run a company will quickly tell you that this is a recipe for disaster.
  1519.  
  1520. Many academics on the other hand who have never worked in the real world see money as a source of endless supply. What they see, is grant funding that comes from a bottomless pool called the government. Because of this lack of real world understanding they fail to understand scarcity. The majority of academics fail to understand the economic effect of revenue versus profitability. To them, sinking more money into something is always good.
  1521.  
  1522. csw [4:55 AM]
  1523. _“In this section, we argue that the current Bitcoin protocol has no measures to guarantee a low γ. This implies that the threshold may be as low as zero, and a pool of any size can benefit by running Selfish-Mine. We suggest a simple change to the protocol that, if adopted by all non-selfish miners, sets γ to 1/2, and therefore the threshold to 1/4.”_
  1524.  
  1525. The authors of the selfish mining paper have completely ignored testing anything to do with the network or its topography. They have made assumptions and have failed to understand anything to do with how the machines interconnect.
  1526.  
  1527. The gamma of the real network is set to be maximised at a rate of 0.002 (in reality as as Bitcoin is constructed) and no rational decision would be likely to ever create a scenario where more than a gamma of 0.0001 can exist. The so-called proposed change would actually increase the likelihood of the network being attacked. There assumption that their change decreases gamma is false. The solution proposed by the authors of the selfish mining paper creates the scenario that they are seeking to model.
  1528.  
  1529. The ONLY way a Gamma can be at 0.5 is to implement the absolutely asinine _solution_ proposed in that paper.
  1530.  
  1531. [4:58]
  1532. *Detecting selfish mining*
  1533.  
  1534. In contradiction to the comments that it is difficult to detect the selfish mining, I will counter this with the notion that the authors of paper are dangerously deluded by their own model.
  1535.  
  1536. Any selfish mining attack is *trivial* to detect (visually by a 3 year old with no training) and block (resulting ion a complete revenue loss to the SM. The current model does not drop orphan blocks but rather holds a block tree in memory. In failing to analyse the protocol or the software the authors have ignored the actual system for their mythical idealised system that they hold in their head that is never existed.
  1537.  
  1538. The authors of the selfish mining paper choose a version of reality dictated by Aristotle. They seek to model a perfect scenario in their head without ever checking reality. They see a perfect version of their ideal of bitcoin and not the code or the protocol as it actually exists. In this, they model a circle and talk about the perfection of the circle and how it could be better. Unfortunately the closest analogy would be that the item there modelling is a cube that they are talking about as a two-dimensional circle. The authors are simply wrong and they are completely ignorant.
  1539.  
  1540. The authors of the selfish mining paper are *dangerously deluded*, *horrendously unscientific* and their processes and failed to comprehend the basics of developing a scientific experiment.
  1541.  
  1542. [4:58]
  1543. As for detecting hidden patterns:
  1544. https://uk.sans.org/reading-room/whitepapers/stenganography/detecting-hydan-statistical-methods-classifying-hydan-based-stegonagraphy-execut-32839
  1545.  
  1546. [4:59]
  1547. I used to write code to detect Steganographic information.
  1548. https://en.wikipedia.org/wiki/Steganography
  1549. Wikipedia
  1550. Steganography
  1551. Steganography (/ˌstɛɡ.əˈnɒɡ.rə.fi/, STEG-ə-NOG-rəfee) is the practice of concealing a file, message, image, or video within another file, message, image, or video. The word steganography combines the Greek words steganos (στεγανός), meaning "covered, concealed, or protected", and graphein (γράφειν) meaning "writing".
  1552. The first recorded use of the term was in 1499 by Johannes Trithemius in his Steganographia, a treatise on cryptography and steganography, disguised as a book on magic. Generally, the Show more… (2MB)
  1553.  
  1554.  
  1555. [5:00]
  1556. I was the one who ruined Trucrypt.
  1557.  
  1558.  
  1559. [5:00]
  1560. http://www.ibtimes.co.uk/truecrypt-goes-way-lavabit-developers-shut-it-down-without-warning-1450467
  1561. International Business Times UK
  1562. TrueCrypt Goes the Way of Lavabit as Developers Shut it Down Without Warning
  1563. The encryption service used by Edward Snowden and other privacy-concerned citizens has shut down without warning (88kB)
  1564. May 29th, 2014 at 10:37 AM
  1565.  
  1566. [5:02]
  1567. Some of the fragments of my papers and reports (though this was a draft - no idea where this was leaked...) on this topic are floating about
  1568. https://www.homeworkmarket.com/sites/default/files/q4/03/09/samplereport1.pdf
  1569.  
  1570. [5:02]
  1571. I developed the statistical tools that broke the so called hidden partitions in TrueCrypt.
  1572.  
  1573. [5:03]
  1574. So, I will say with certainty (as TrueCrypt and Hydan are hard, Selfish mining is trivial.
  1575.  
  1576. [5:03]
  1577. Trivial for a person who has never used a computer level trivial.
  1578.  
  1579. cypherblock [6:51 AM]
  1580. @csw if you are writing a paper to refute SM strategy, please take into account difficulty adjustments caused by SM strategy.
  1581.  
  1582. csw [6:52 AM]
  1583. I am
  1584.  
  1585. [6:52]
  1586. I did note the saw tooth structure of mining difficulty remember
  1587.  
  1588. [6:52]
  1589. It is Log Linear with periodic adjustments...
  1590.  
  1591. [6:53]
  1592. I believe that I noted that, and this makes the assumptions incorrect in the model used
  1593.  
  1594. cypherblock [6:58 AM]
  1595. well I guess my point is, if everyone’s hash power is fixed, and a 33% pool starts mining selfishly, will the difficulty go up, go down or stay the same? To me it looks like difficulty adjust downward because rate of blocks published is lower.
  1596.  
  1597. csw [6:59 AM]
  1598. Poisson is not an approximation in this instance
  1599.  
  1600. [6:59]
  1601. Not even close
  1602.  
  1603. [7:00]
  1604. 2016 blocks - the time is longer
  1605.  
  1606. [7:00]
  1607. The number of blocks is the same :slightly_smiling_face:
  1608.  
  1609. cypherblock [7:01 AM]
  1610. yes, takes longer to get to 2016 blocks, so won’t difficulty adjust downward to make this happen sooner?
  1611.  
  1612. csw [7:01 AM]
  1613. At 33% the Selfish miner loses more to orphans then the honest miner
  1614.  
  1615. [7:02]
  1616. It is a Black Swan form of error.
  1617.  
  1618. The distribution is asymmetric. It is not distributed evenly around the means
  1619.  
  1620. [7:05]
  1621. @cypherblock
  1622. ] Marshall, A. W. and Olkin, I. (1997). A new method for adding a parameter to a family of distributions with application to the exponential and Weibull families. Biometrika, 84, 641-652.
  1623.  
  1624. [7:06]
  1625. This is still an approximation, but it is far closer
  1626.  
  1627. [7:06]
  1628. http://home.iitk.ac.in/~kundu/moged-rev-3.pdf
  1629.  
  1630. cypherblock [7:07 AM]
  1631. While I appreciate all the references, the question remains, won’t difficulty adjust downwards in the scenario I just described?
  1632.  
  1633. csw [7:07 AM]
  1634. It is probabilistic
  1635.  
  1636. [7:07]
  1637. So, are we talking once, on average, over several changes?
  1638.  
  1639. cypherblock [7:07 AM]
  1640. over several changes let’s say
  1641.  
  1642. [7:08]
  1643. although I’m pretty sure even the first change has high probability of being affected
  1644.  
  1645. csw [7:08 AM]
  1646. The time will get shorter, so the difficulty is lowered across several "standard" changes - if these can be said to exist
  1647.  
  1648. [7:08]
  1649. Here is the thing with the Negative Binomial model
  1650.  
  1651. [7:09]
  1652. When the time to discovery is shorter, that is lambda is lower, the distribution favors the honest miner
  1653.  
  1654. [7:09]
  1655. When it is greater, it favors the attacker
  1656.  
  1657. macsga
  1658. [7:09 AM]
  1659. good morning
  1660.  
  1661. [7:09]
  1662. https://i.imgflip.com/1pr66c.jpg (14kB)
  1663.  
  1664. csw [7:11 AM]
  1665. LOL
  1666.  
  1667. [7:11]
  1668. @macsga Good one
  1669.  
  1670. macsga
  1671. [7:11 AM]
  1672. :wink:
  1673.  
  1674. csw [7:13 AM]
  1675. uploaded this image: image.png
  1676. Add Comment
  1677.  
  1678. csw [7:13 AM]
  1679. https://arxiv.org/pdf/1702.02867.pdf
  1680.  
  1681. [7:13]
  1682. That is not my paper, that is what using the Negative Binomial does
  1683.  
  1684. [7:15]
  1685. Here is something that you may have not gotten with the Negative Binomial, as the difficulty decreases, the time to find a block is lower. For all parties.
  1686.  
  1687. When this occurs, it is the Honest miner who has the greater advantage. It is not symmetric.
  1688.  
  1689. cypherblock [7:16 AM]
  1690. Anyway, so difficulty adjusts downward. This effects # of reward blocks the SM miner can produce in a day (yes effects everyone else too).
  1691.  
  1692.  
  1693. csw [7:16 AM]
  1694. uploaded this image: image.png
  1695. Add Comment
  1696.  
  1697. csw [7:16 AM]
  1698. Yes. And to point you to a paper and a quote:
  1699.  
  1700. "Therefore the correct results for bitcoin security are worse than those given in
  1701. [7]. The explanation is that Nakamoto’s result is correct only if the mining time by
  1702. the honest miners is exactly the expected time. *Longer than average times help the attackers*"
  1703.  
  1704. [7:17]
  1705. As the time decreases, the selfish attacker loses...
  1706.  
  1707. [7:20]
  1708. What happens - 33%
  1709.  
  1710. 1. Selfish Miner loses orphans - at 33% just slightly more than the HM
  1711. 2. Difficulty adjusts - this makes the discovery faster
  1712. 3. The HM mines far more than the SM who loses MANY blocks at an increased Orphaning
  1713. 4. Difficulty adjusts
  1714. 5. Selfish Miner loses orphans - at 33% just slightly more than the HM
  1715.  
  1716. ...
  1717.  
  1718. looping
  1719.  
  1720. [7:22]
  1721. At 40%
  1722.  
  1723. 1. Selfish Miner loses orphans - at 40% just slightly *less* than the HM
  1724. - lowewr revenue, but a slight ration gain
  1725. 2. Difficulty adjusts - this makes the discovery faster
  1726. 3. The HM mines far more than the SM who loses MANY blocks at an increased Orphaning
  1727. - The SM loses more than the HM
  1728. 4. Difficulty adjusts
  1729. 5. Selfish Miner loses orphans - at 40% just slightly more than the HM...looping
  1730.  
  1731.  
  1732. ...
  1733.  
  1734. Loops
  1735.  
  1736. cypherblock [7:22 AM]
  1737. difficulty adjust will stabalize. Compare SM blocks per day after difficulty adjsuts and stabalizes, vs SM pool mining honestly
  1738.  
  1739. csw [7:22 AM]
  1740. At 44% - the system becomes chaotic
  1741.  
  1742. [7:23]
  1743. No, it actually becomes cyclic at 33% and chaotic above 44
  1744.  
  1745. [7:26]
  1746. And @cypherblock You are modeling with Poisson assumptions
  1747.  
  1748. [7:26]
  1749. These are not valid assumptions. (edited)
  1750.  
  1751. csw [7:44 AM]
  1752. uploaded this image: image.png
  1753. Add Comment
  1754.  
  1755. csw [7:44 AM]
  1756. uploaded this image: image.png
  1757. Add Comment
  1758.  
  1759. csw [7:45 AM]
  1760. These are the long term effects of difficulty and selfish mining.
  1761.  
  1762. [7:45]
  1763. The results are chaotic - as in they express fractal dimensionality
  1764.  
  1765. [7:45]
  1766. Over 44%, the chain cannot be predicted.
  1767.  
  1768. csw [7:47 AM]
  1769. uploaded this image: image.png
  1770. Add Comment
  1771.  
  1772.  
  1773. csw [7:47 AM]
  1774. This is what I mean by periodic.
  1775.  
  1776. [7:48]
  1777. Or the basic (hand drawn) version
  1778.  
  1779. csw [7:48 AM]
  1780. uploaded this image: image.png
  1781. Add Comment
  1782.  
  1783. nicholat [7:49 AM]
  1784. please explain to me the subject of this debate and channel like I'm 5 years old? :stuck_out_tongue:
  1785.  
  1786. csw [7:49 AM]
  1787. Selfish mining is not profitable
  1788.  
  1789. csw [7:49 AM]
  1790. uploaded this image: image.png
  1791. Add Comment
  1792.  
  1793. cypherblock [7:50 AM]
  1794. @nicholat discussing whether selfish mining approach (described in paper by Guy Sirer and Eyal) works or not
  1795.  
  1796. csw [7:51 AM]
  1797. At 44% you simply cannot say what will occur. Small differences in the inital condition or changes in hash rate or discovery lead to Bifurcation
  1798.  
  1799. [7:51]
  1800. A maximum Lyapunov exponent is created.
  1801.  
  1802. I cannot explain this to anyone without using maths
  1803.  
  1804. nicholat [7:52 AM]
  1805. well, the gist of it?
  1806.  
  1807. [7:52]
  1808. I mean, try to explain it as you would to your mother
  1809.  
  1810. csw [7:52 AM]
  1811. uploaded this image: image.png
  1812. Add Comment
  1813.  
  1814. csw [7:53 AM]
  1815. That is at 45%
  1816.  
  1817. [7:53]
  1818. Completely unable to be predicted.
  1819.  
  1820. cypherblock [7:54 AM]
  1821. @nicholat : selfish mining strategy means instead of publishing blocks as soon as you find them, you build a private chain of blocks and only publish your blocks to the bitcoin network when the remaining honest miners find a block. Sometimes you publish 2 blocks as needed to confirm your rewards and beat the others.
  1822.  
  1823. nicholat [7:54 AM]
  1824. so basically, "selfishly mining" can cause problems with less than 51% of the network hash rate?
  1825.  
  1826. [7:54]
  1827. right, I've heard about that
  1828.  
  1829. tomothy [7:55 AM]
  1830. The paper alleges miners can cheat and if they cheat they have more revenue. It assumes revenue is what drives miners not profit. Revenue doesn't help much if you aren't profitable. Their study is based on assumptions. (edited)
  1831.  
  1832. tomothy [7:55 AM]
  1833. If the assumptions are wrong, their study is wrong. (edited)
  1834. 1 reply Today at 6:11 PM View thread
  1835.  
  1836. nicholat [7:56 AM]
  1837. right, and that's what csw is trying to find out about
  1838.  
  1839. tomothy [7:57 AM]
  1840. More or less yes. He shows that they used simple math.
  1841.  
  1842. csw [7:57 AM]
  1843. I have papers in review already
  1844.  
  1845. tomothy [7:57 AM]
  1846. For a complex problem.
  1847.  
  1848. csw [7:57 AM]
  1849. I am trying to teach others :slightly_smiling_face:
  1850. 1 reply Today at 6:13 PM View thread
  1851.  
  1852. csw [7:58 AM]
  1853. uploaded this image: image.png
  1854. Add Comment
  1855.  
  1856. tomothy [7:58 AM]
  1857. And ultimately, you can't cheat maths.
  1858.  
  1859.  
  1860. csw [7:58 AM]
  1861. That is what happens at 45%
  1862.  
  1863. [7:58]
  1864. as a Selfish miner
  1865.  
  1866. nicholat [7:58 AM]
  1867. right; I mean, I have a few years of university calculus and linear algebra behind me, I understand some of the terminology you're using in the paper
  1868.  
  1869. [7:58]
  1870. but definitely not all of it
  1871.  
  1872. mai8304 [7:58 AM]
  1873. joined selfish-mining by invitation from @tomothy, along with @demoforyelin
  1874.  
  1875. csw [7:58 AM]
  1876. I needed to have a pure maths journal for publication.
  1877.  
  1878. cypherblock [7:59 AM]
  1879. @csw what is that chart? What is it showing. Looks impressive, but useless without explanation
  1880.  
  1881. csw [7:59 AM]
  1882. I was unable to find peers to understand the maths in the Bitcoin community. We all have different skills
  1883. 1 reply Today at 6:00 PM View thread
  1884.  
  1885. csw [7:59 AM]
  1886. That chart is the blocks over time won by the selfish miner when the difficulty is accounted for
  1887.  
  1888. [8:00]
  1889. It leads to Bifurcations and Chaos and is a Periodic Model
  1890.  
  1891. [8:01]
  1892. That image is what happens to the chain at 45% if the honest miners all allow (and they can stop this at will) the chain to have selfish mining and they have only 55% as honest miners
  1893.  
  1894. [8:02]
  1895. They *may* get a lot of control. They *may* get nothing
  1896.  
  1897. More than not, they lose
  1898.  
  1899. [8:02]
  1900. I do not believe that a rational miner will engage in a strategy that will cost them money. The paper stated they would
  1901.  
  1902. new messages
  1903. weekend_engineer [5:04 PM]
  1904. joined selfish-mining by invitation from @tomothy, along with @daganb
  1905.  
  1906. newliberty
  1907. [5:51 PM]
  1908. uploaded this image: Pasted image at 2017-05-26, 2:50 PM
  1909. Add Comment
  1910.  
  1911. newliberty
  1912. [5:57 PM]
  1913. It applies to a lot more than selfish mining, as do the other elements used in the proofs, (or more accurately, the disproof of the conjecture). The SM things here are basics. An application of principles of maths. If you get all of it, and can show the work, it may qualify you for going where the angles fear to walk. (edited)
  1914.  
  1915. newliberty
  1916. [6:02 PM]
  1917. uploaded this image: Pasted image at 2017-05-26, 3:02 PM
  1918. Add Comment
  1919.  
  1920. nicholat [6:17 PM]
  1921. looking at your interviews from 2014 btw @csw, what's your current take on PSOs?
  1922.  
  1923. [6:17]
  1924. I recall an optimization problem I never found a good method for, which I now realize I could possibly have used it for (edited)
  1925.  
  1926. btcalbin [6:20 PM]
  1927. Kind of non-technical intuition, but I have the feeling that the general class of block-withholding attacks and Maxwell's conception that without a block reward, the chain will not move forward (because of miners constantly reorging at the same height to take each others fees) have something very significant in common. They both seem to be predicated on the idea that a malicious miner can just keep attacking forever without actually taking the money, as though there is no time value of money.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement