Advertisement
satoshi_n

hardfork

Jun 14th, 2017
138
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 172.23 KB | None | 0 0
  1. tomothy [9:12 AM]
  2. joined hardfork
  3.  
  4. tomothy [9:12 AM]
  5. Enclosed is some ongoing discussion concerning using EC to HF to 2mb
  6.  
  7. zarry [9:17 AM]
  8. joined hardfork by invitation from @tomothy, along with @mwilcox, @coinspeak, @klee, @kyuupichan, @chritchens, @rajsallin, @lunar, @davids and some others
  9.  
  10. tomothy [9:17 AM]
  11. I think everyone was added. If I missed someone, feel free to add them as well.
  12.  
  13. [9:18]
  14. I figured having some additional eyes look at and review the aforementioned EC 8mb discussion from Peter would be good. I know there are concerns about preventing a re-org regarding majority/minority chain and ensuring continued protection for spv miners.
  15.  
  16. foorbarbaz [9:20 AM]
  17. set the channel topic: https://blocksizeproposals.github.io
  18.  
  19.  
  20. tomothy [9:32 AM]
  21. I thought Bcoin is taking an interesting stance regarding BIP148
  22.  
  23. [9:32]
  24. https://github.com/bcoin-org/bcoin/pull/205
  25. GitHub
  26. chain/mempool: implement uasf support. by chjj · Pull Request #205 · bcoin-org/bcoin
  27. This is my initial implementation of UASF (BIP148, proposed by Shaolin Fry). It's pretty simple and sits behind a --uasf flag (other options for the mempool also exist, see comments/code in the dif...
  28.  
  29.  
  30. [9:33]
  31. I think it's even more concerning however, that Wladimir is not running core...
  32.  
  33. [9:33]
  34. https://np.reddit.com/r/Bitcoin/comments/6bxpsj/bip148_and_the_risks_it_entails_for_you_whether/dhqmb4v/
  35. reddit
  36. BIP148 and the risks it entails for you (whether you run a BIP148 node or not) • r/Bitcoin
  37. I think it's very likely that if there is a prolonged split, Core will abandon the legacy chain. But each developer would need to decide for...
  38.  
  39.  
  40. foorbarbaz [9:34 AM]
  41. did you mean to post those in #segwit ?
  42.  
  43. tomothy [9:34 AM]
  44. no, i think it all relates to a hardfork
  45.  
  46. [9:34]
  47. but you're right, maybe crosspost
  48.  
  49. [9:34]
  50. at this point in time the issues are so intertwined :confused:
  51.  
  52. macsga
  53. [9:34 AM]
  54. joined hardfork by invitation from @klee, along with @karasako
  55.  
  56. tomothy [9:37 AM]
  57. in hindsight, maybe this should have simply been named 'scaling' lol
  58.  
  59. tomothy [9:37 AM]
  60. and then there is the merge mine discussion from oliver, i think that's a bit of a weird one. maybe bitsko can reach out to some of the other significant notables
  61. 1 reply 26 days ago View thread
  62.  
  63. tomothy [9:37 AM]
  64. https://www.reddit.com/r/btc/comments/6c29np/interesting_idea_lets_discuss_olivier_janssens/
  65. reddit
  66. Interesting Idea? Let's Discuss Olivier Janssens Proposal To Fork A MergeMined Chain - Even With Less Than 51% Hash Power • r/btc
  67. 26 points and 12 comments so far on reddit
  68.  
  69.  
  70. foorbarbaz [9:40 AM]
  71. set the channel topic: in hindsight, maybe this should have simply been named 'scaling'
  72.  
  73. tomothy [9:40 AM]
  74. LOL
  75.  
  76. foorbarbaz [9:42 AM]
  77. Content I wrote elsewhere;
  78.  
  79. UASF is an idea where people running a wallet decide to stop following the miners chain if the miner doesn't vote for SegWit.There are several important details here.
  80. - Miners can last much much much longer without sending their coins to an exchange than an exchange can last without the miners chain.
  81. - Miners would be embraced again by just voting for segwit. There is no way for miners to be forced to accept, mine or validate segwit transactions. There is not even a reason for miners to start running Core.
  82.  
  83. The only effect uasf could possibly have is for miners to vote segwit in, without validating it. Which means that if one miner includes segwit transactions he will quickly get himself hard forked off the net because other miners will happily include a transaction spending that segwit tx because it is an everyone-can-spend.UASF is a stupid idea. There is no way that exchanges will cut their own veins open by using it.
  84. If it were to actually work, it would actually kill SegWit.
  85.  
  86.  
  87. [9:43]
  88. ----
  89. and; https://www.reddit.com/r/btc/comments/6byunq/if_segwit_were_to_activate_today_it_would_have/
  90. *«If SegWit were to activate today, it would have absolutely no positive effect on the backlog. If big blocks activate today, it would be solved in no time.»*
  91. reddit
  92. If SegWit were to activate today, it would have absolutely no positive effect on the backlog. If big blocks activate today, it would be solved in no time. • r/btc
  93. Should SegWit activate today, it will generate the same size blocks we have today. 1MB max. It would have no positive effect whatsoever on the...
  94.  
  95.  
  96.  
  97. csw [9:59 AM]
  98. If SegShit activates, they will never increase Block Size to the level of demand
  99.  
  100. [9:59]
  101. They will use this as a means to subsidise off block solutions and kill on chain scaling.
  102.  
  103.  
  104. tomothy [10:00 AM]
  105. Absent a strong united alternative by 8/1/17, I think it could be messy. Although we champion the death of Segwit, this could result in a shock to bitcoin's price 'stability'. I.e., We could see a similar price correction mirroring the mtgox event/SR event. I think the recovery would be fast and quick but it would still be disconcerting. (edited)
  106.  
  107. pesa [10:08 AM]
  108. perhaps there is a united alternative underway
  109.  
  110. [10:08]
  111. just not public
  112.  
  113. tomothy [10:09 AM]
  114. if so, it's certainly not being moved forward by core, evident by the fact that lead maintainer is running 148...
  115.  
  116. checksum0
  117. [10:19 AM]
  118. Anybody can TL;DR? Kind of busy today :sweat_smile:
  119.  
  120. tomothy [10:20 AM]
  121. oh shit, it didnt copy any of the important discussion stuff
  122.  
  123. [10:20]
  124. ugh.
  125.  
  126. [10:23]
  127. ok, trying the snippet again
  128.  
  129. tomothy [10:23 AM]
  130. added this Plain Text snippet: BUIP056 discussion re: anti-reorg
  131. Anyone following the BUIP056 discussion re: anti-reorg ?
  132. [6:38]
  133. I'd like to discuss a proposal for dynamically adding checkpoints, which I've posted about in this comment:
  134. https://bitco.in/forum/threads/buip056-increase-the-block-size-limit-triggered-by-a-support-threshold.2111/page-2#post-39031 (edited)
  135. Add Comment Click to expand inline 724 lines
  136.  
  137. tomothy [10:23 AM]
  138. tldr, 2 chains.
  139.  
  140. checksum0
  141. [10:25 AM]
  142. The merge mining stuff?
  143.  
  144. [10:26]
  145. Or literally a minority hardfork?
  146.  
  147. tomothy [10:26 AM]
  148. no, like jihan's looking for re-org protection with the EC stuff
  149.  
  150. [10:26]
  151. sounds like they will push for 2mbs afterwards
  152.  
  153. [10:26]
  154. was wanting to protect spv miners/wallets etc, realizes it's not necessarily possible
  155.  
  156. [10:27]
  157. so trying to figure out how to setup checkpoints to prevent the re-org
  158.  
  159. tomothy [10:27 AM]
  160. ultimately everyone recognizes we will have an etc/eth like situation, at least for a bit
  161. 2 replies Last reply 26 days ago View thread
  162.  
  163. tomothy [10:27 AM]
  164. since they want re-org protection, and from my understanding, this will cause a split
  165.  
  166. checksum0
  167. [10:32 AM]
  168. I really hope shits don't hits the fan this summer
  169.  
  170. tomothy [10:32 AM]
  171. i think it's going to; they're pushing bip148 8/1
  172.  
  173. [10:32]
  174. how can it not?
  175.  
  176. [10:32]
  177. some stupid people will send anyonecanspend segwit stuff
  178.  
  179. [10:32]
  180. it will get stolen
  181.  
  182. checksum0
  183. [10:33 AM]
  184. I received a 4ph shipment this morning + 1000 gpu + 75 th of scrypt miner this morning
  185.  
  186.  
  187. tomothy [10:33 AM]
  188. people will go rabid
  189.  
  190. [10:33]
  191. gpu = eth?
  192.  
  193. checksum0
  194. [10:33 AM]
  195. + zcash
  196.  
  197. tomothy [10:33 AM]
  198. ahh
  199.  
  200. [10:33]
  201. well, i mean if btc goes crazy in war; you might see a bump in zec/ltc
  202.  
  203. checksum0
  204. [10:33 AM]
  205. Really hope shits don't hit the fan now, I never did an investment that big in one go...
  206.  
  207. tomothy [10:33 AM]
  208. not the worst hedge
  209.  
  210. christophbergmann [11:30 AM]
  211. hi
  212.  
  213. tomothy [11:31 AM]
  214. just reposted the bu stuff here, tomz had some additional comments. trying to get more info on bip148/149
  215.  
  216. checksum0
  217. [11:35 AM]
  218. Tomothy
  219.  
  220. [11:36]
  221. I get fucking pissed off at that guy because he thinks it's all a fucking game
  222.  
  223. [11:36]
  224. With his lonely bitcoin he thinks it's play money, if he loses 1 bitcoin, well too bad, it was fun
  225.  
  226. [11:37]
  227. Real people really invested in Bitcoin don't think it's a fucking game. People like him are destroying what I have been building for the past 8 years
  228.  
  229. [11:37]
  230. If he'd say things like that in front of me, I'd literally punch him out cold (edited)
  231.  
  232. [11:40]
  233. I wonder how much I'd have to pay him to go away
  234.  
  235. [11:40]
  236. I guess another bitcoin should be enough :joy:
  237.  
  238. tomothy [11:45 AM]
  239. i know, it's what they do
  240.  
  241. [11:45]
  242. can't take it too seriously
  243.  
  244. [11:45]
  245. :slightly_smiling_face:
  246.  
  247. [11:45]
  248. he gets excited when you do
  249.  
  250. [11:45]
  251. its like star wars and like the dark side
  252.  
  253. [11:46]
  254. don't give in to the dark side, it makes them stronger lol
  255.  
  256. pesa [3:05 PM]
  257. just read this https://btcchat.slack.com/files/tomothy/F5GD7HP70/buip056_discussion_re__anti-reorg.txt
  258.  
  259. pesa [3:05 PM]
  260. mentioned tomothy’s Plain Text snippet: BUIP056 discussion re: anti-reorg
  261. Anyone following the BUIP056 discussion re: anti-reorg ?
  262. [6:38]
  263. I'd like to discuss a proposal for dynamically adding checkpoints, which I've posted about in this comment:
  264. https://bitco.in/forum/threads/buip056-increase-the-block-size-limit-triggered-by-a-support-threshold.2111/page-2#post-39031 (edited)
  265. Add Comment Click to expand inline 724 lines
  266.  
  267. pesa [3:05 PM]
  268. very interesting
  269.  
  270. [3:06]
  271. thought crossed my mind, why cant CSW help them out? Looks like they could use a pair of extra hands
  272.  
  273. [3:06]
  274. somewhere they mentioned "we are a small team" and this limited what they could do. Kinda felt sorry for them
  275.  
  276.  
  277. freetrader [7:27 PM]
  278. don't feel sorry for us :slightly_smiling_face:
  279.  
  280. [7:28]
  281. help review code, write some, test some, run a node etc.
  282.  
  283. [7:29]
  284. on the HF subject, best we can all do is strap in tight, because shit is going to hit the fan one way or another.
  285.  
  286.  
  287. [7:29]
  288. I think right now miners are preparing for every possible means.
  289.  
  290. [7:30]
  291. The opposite side is willing to burn a lot of money to stifle Bitcoin.
  292.  
  293.  
  294. freetrader [7:32 PM]
  295. If anyone's got technical input on checkpoints etc., I am interested.
  296. 4 replies Last reply 22 days ago View thread
  297.  
  298. freetrader [7:33 PM]
  299. Even if BUIPyyy (dynamic checkpoints suitable for anti-reorg) doesn't get into BU - and there's a good chance members might not want it, perhaps because it seems too unnecessary -- I will still want to develop this feature. (edited)
  300.  
  301. [7:34]
  302. I saw on the Wiki a note about some altcoins doing periodic automated checkpointing.
  303. Anyone know of a coin which does this?
  304.  
  305. tomothy [7:36 PM]
  306. Sorry, nothing I can think of off the top of my head.
  307.  
  308. adamselene [8:04 PM]
  309. csw what are your thoughts on BUIP055 (increase to 8MB at height 488,888)?
  310.  
  311.  
  312. ----- May 20th -----
  313. klee [5:15 AM]
  314. https://twitter.com/BryceWeiner/status/865847867704958981
  315. Bryce Weiner @BryceWeiner
  316. Anyone with even a passive interest in #Bitcoin has made a decision.
  317.  
  318. The only thing to talk about is August 2nd.
  319. TwitterMay 20th at 4:33 AM
  320.  
  321. [5:16]
  322. so it is 2nd of August?
  323.  
  324. cryptorebel [5:22 AM]
  325. August 2nd is probably the date the UASF supporters will commit blockchain suicide
  326.  
  327. [5:22]
  328. I think Bryce is probably drinking the koolaid with them
  329.  
  330. klee [5:22 AM]
  331. I think he opposes it
  332.  
  333. [5:22]
  334. he is anti Core
  335.  
  336. cryptorebel [5:23 AM]
  337. luke-jr is saying that by AUG 1st they will have completed UASF
  338.  
  339. klee [5:23 AM]
  340. So HF needs to be done before then, right?
  341.  
  342. cryptorebel [5:24 AM]
  343. I dont know, UASF may result in a chain split, and then on the real Bitcoin chain we would have enough hash for a BU block increase fork, as the segwit hash would leave the network for their alt coin chain
  344.  
  345. [5:25]
  346. i wish HF happened yesterday, lol
  347.  
  348. cryptorebel [5:30 AM]
  349. last i heard they are proposing new BUIP056: https://bitco.in/forum/threads/buip056-increase-the-block-size-limit-triggered-by-a-support-threshold.2111/
  350. Bitcoin Forum
  351. BUIP056: Increase the Block Size Limit triggered by a support threshold
  352. I propose a BUIP056 similar BUIP055, but which I believe better may align with the requirements of miners: BUIP056 - Increase the Block Size Limit...
  353.  
  354.  
  355. [5:30]
  356. trying to appease some of Jihan's and other miners concerns I guess
  357.  
  358. [5:30]
  359. hopefully we will see a push for something soon
  360.  
  361. cryptorebel [5:37 AM]
  362. I guess Bryce does appear to be against the UASF, I was not sure because he did introduce that troll BUIP a while back
  363.  
  364. csw [7:51 AM]
  365. 8MB is a small start. 20 right now would be better
  366.  
  367.  
  368. [7:51]
  369. But it is a temp measure
  370.  
  371. macsga
  372. [10:01 AM]
  373. @csw is there a way to enforce this (other than collision ?)
  374.  
  375. klee [10:04 AM]
  376. if someone steals the repo pwd and assassinate all Core (edited)
  377.  
  378.  
  379. [10:04]
  380. How man?
  381.  
  382. [10:04]
  383. How can you enforce this?
  384.  
  385. csw [10:07 AM]
  386. And if there was a group of developers. Ones with skill and experience.
  387.  
  388. Ones that worked for the majority of the miners and validated code and created tests and reports etc etc?
  389.  
  390. [10:07]
  391. Ones that are funded
  392.  
  393. macsga
  394. [10:07 AM]
  395. we're getting somewhere it seems
  396.  
  397. [10:07]
  398. :slightly_smiling_face:
  399.  
  400. csw [10:07 AM]
  401. And who manage a repo that any can use but that is a new foundation code base?
  402.  
  403.  
  404. klee [10:07 AM]
  405. Ah ok
  406.  
  407. [10:07]
  408. Totally agree
  409.  
  410. csw [10:07 AM]
  411. And this is audited
  412.  
  413. [10:08]
  414. And reviewed
  415.  
  416. klee [10:08 AM]
  417. I thought macsga wanted a 'hack'
  418.  
  419. csw [10:08 AM]
  420. And goes into test cycles before release
  421.  
  422.  
  423. macsga
  424. [10:08 AM]
  425. no; not hack
  426.  
  427. csw [10:08 AM]
  428. On real senarios and systems
  429.  
  430. macsga
  431. [10:08 AM]
  432. agree on this
  433.  
  434. klee [10:08 AM]
  435. We are here for this CSW
  436.  
  437. [10:09]
  438. patiently waiting for it
  439.  
  440. macsga
  441. [10:09 AM]
  442. so, the 1M question: ETA?
  443.  
  444. csw [10:10 AM]
  445. Something like that would hit before any UASF would I think :wink:
  446.  
  447. [10:10]
  448. But, who am I to say?
  449.  
  450. macsga
  451. [10:10 AM]
  452. hehe
  453.  
  454. tomothy [10:10 AM]
  455. So if Uasf is 8/1/17...
  456.  
  457. macsga
  458. [10:10 AM]
  459. I thought so
  460.  
  461. tomothy [10:10 AM]
  462. Have you bought plane tickets yet?
  463.  
  464. ger [10:10 AM]
  465. An educated guess lol
  466.  
  467. macsga
  468. [10:11 AM]
  469. @tomothy to me?
  470.  
  471. [10:11]
  472. lol, no... I'm still poor :stuck_out_tongue:
  473.  
  474. klee [10:12 AM]
  475. I will be drinking frappe/beer under the sun, next to the sea, while Core sinks?
  476.  
  477. [10:12]
  478. What else can I ask in this life?
  479.  
  480.  
  481. macsga
  482. [10:12 AM]
  483. lol
  484.  
  485. klee [10:14 AM]
  486. I have an idea
  487.  
  488. [10:14]
  489. beach party
  490.  
  491. [10:14]
  492. when HF starts
  493.  
  494. [10:14]
  495. everyone in here should join
  496.  
  497. [10:14]
  498. We gather at macsga
  499.  
  500. [10:15]
  501. he has good sea there (this mfer)
  502.  
  503. macsga
  504. [10:15 AM]
  505. yeah, beach party
  506.  
  507. klee [10:15 AM]
  508. fire
  509.  
  510. [10:15]
  511. alcohol
  512.  
  513. [10:15]
  514. music
  515.  
  516. [10:15]
  517. Mac can you sing?
  518.  
  519. [10:15]
  520. :joy:
  521.  
  522. macsga
  523. [10:15 AM]
  524. like a donkey
  525.  
  526.  
  527. [10:16]
  528. https://ainafetst.files.wordpress.com/2012/11/anes-autres-animaux-autres-insolite-galway-irlande-1728631855-925871.jpg (26kB)
  529.  
  530. klee [10:16 AM]
  531. hehe
  532.  
  533. [10:16]
  534. fluffy donkey
  535.  
  536. macsga
  537. [10:17 AM]
  538. :stuck_out_tongue:
  539.  
  540. digitsu [11:35 AM]
  541. joined hardfork by invitation from @klee
  542.  
  543.  
  544. phoenix
  545. [12:37 PM]
  546. welcome @digitsu , great to have you here
  547.  
  548.  
  549. ----- May 21st -----
  550. simonliu [7:15 AM]
  551. joined hardfork by invitation from @gregnie. Also, @jpjp joined, @tula joined.
  552.  
  553.  
  554. ----- May 22nd -----
  555. digitsu [7:20 PM]
  556. hello all
  557.  
  558. norway [7:22 PM]
  559. hello digitsu! :wave:
  560.  
  561. bitsko
  562. [8:25 PM]
  563. welcome digitsu!
  564.  
  565.  
  566. ----- May 23rd -----
  567. christophbergmann [3:54 AM]
  568. hello all
  569.  
  570. phoenix
  571. [3:54 AM]
  572. welcome Christoph
  573.  
  574. adamselene [4:14 AM]
  575. Have you used windump (windows port of tvpdump) for testing csw?
  576.  
  577. csw [4:16 AM]
  578. It sucks
  579.  
  580. [4:16]
  581. TCPDump
  582.  
  583. [4:16]
  584. If on windows, use WireShark
  585.  
  586. [4:16]
  587. Command line - use Linux
  588.  
  589. [4:17]
  590. I used to teach it... I taught at SANS, but also for a few Masters programs in Oz as well as for the Police academy in their cyber area
  591.  
  592. adamselene [4:36 AM]
  593. Yeah I decided to just set up my machine to dual boot again. Going to dig some is machines out of the garage tomorrow to set up some tests.
  594.  
  595. foorbarbaz [7:00 AM]
  596. left hardfork. Also, @bitalien joined.
  597.  
  598. tomothy [11:15 PM]
  599. https://www.reddit.com/r/Bitcoin/comments/6cyvpe/proposed_community_scaling_compromise/
  600. reddit
  601. Proposed COMMUNITY scaling compromise • r/Bitcoin
  602. * Activate (2 MB) Segwit BIP141 with UASF BIP148 beginning 2017 August. * Activate [a *really*-only-2-MB hard...
  603.  
  604.  
  605. bitalien
  606. [11:42 PM]
  607. "Activate a really-only-2-MB hard fork in 2018 November, if and only if the entire community reaches a consensus"
  608.  
  609. [11:42]
  610. What a fucking idiot
  611.  
  612. [11:43]
  613. Because the hardware that supports Bitcoin simply isn't capable of supporting 2-fucking-megabyte blocks until another 1.5 years?
  614.  
  615. [11:43]
  616. And they are trying to pretend that the "COMMUNITY" is backing this?
  617.  
  618. [11:45]
  619. And since they don't ACTUALLY want to scale Bitcoin EVER, when November 2018 roles around they will simply say "Sorry... the ENTIRE community did not reach consensus so we can't hardfork"
  620.  
  621. bitalien
  622. [11:46 PM]
  623. set the channel topic: 1 MB blocks are too large and should be reduced to 300 KB
  624.  
  625. bitalien
  626. [11:47 PM]
  627. We have the technology capable of supporting 64 MB blocks and BEYOND, yet these autistic Core devs are trying to convince us that even 2 MB is dangerous? LOL
  628.  
  629. [11:49]
  630. Sure, we have a 170,000 transaction backlog NOW, and the price is rising NOW, but we can _totally_ afford to wait one and a half years to _MAYBE_ implement 2 MB blocks! :smiley::gun:
  631.  
  632. [11:51]
  633. Bitcoin is on the verge of becoming the ultimate shitcoin... All the altcoins will simply fill in the void that Bitcoin has left because it has willingly refused to make _any_ advancements for years
  634.  
  635.  
  636. ----- May 24th -----
  637. bitsko
  638. [12:49 AM]
  639. luke needs forked
  640.  
  641. checksum0
  642. [12:50 AM]
  643. Luke gonna fork himself with three of his trolls and 10% of fake node
  644.  
  645. [12:50]
  646. Have fun alone with yourself
  647.  
  648. xhiggy [10:08 AM]
  649. A bunch of them need some fork
  650.  
  651. klee [10:24 AM]
  652. EOS solved the problems, no gas no EVM needed.
  653. The only scalable blockchain with 1000 commercial dapps
  654.  
  655. [10:24]
  656. (zillionaire)
  657.  
  658.  
  659. ----- May 25th -----
  660. btcalbin [8:42 AM]
  661. it's gravely immoral to engage in all that sexual UASF kissing and not fork
  662.  
  663.  
  664. checksum0
  665. [9:46 AM]
  666. @klee Does EOS released any details on anti-spam measure then?
  667.  
  668. tomothy [9:49 AM]
  669. ping zilli
  670.  
  671. checksum0
  672. [9:50 AM]
  673. Fucking bot put another fucking dump stop order
  674.  
  675. [9:50]
  676. What is going on :rage: (edited)
  677.  
  678. tomothy [9:50 AM]
  679. time to turn off bot
  680.  
  681. checksum0
  682. [9:51 AM]
  683. I guess yeah
  684.  
  685. tomothy [9:51 AM]
  686. maybe someone hitting stops magically w/ huge instant volume up / down
  687.  
  688. checksum0
  689. [9:51 AM]
  690. Will have to check the logs to see what is going on
  691.  
  692. [9:51]
  693. Volume, price, and spike are all high
  694.  
  695. [9:51]
  696. I don't think that bot ever saw conditions like those...
  697.  
  698. [9:52]
  699. Looks like it will need more training data...
  700.  
  701. tomothy [9:52 AM]
  702. whipsaw ups and downs
  703.  
  704. checksum0
  705. [9:52 AM]
  706. It placed the stop order 25$ below the ATH
  707.  
  708. [9:52]
  709. COMMON!
  710.  
  711.  
  712. hostfat [5:02 PM]
  713. is it true that Liquid boxes are protected by thermite, and that this will need to be defused for any update/repair?
  714.  
  715. this seems explain a lot about their adversity against hard forks.
  716.  
  717. are there more information about this?
  718. 1 reply 19 days ago View thread
  719.  
  720. tomothy [5:03 PM]
  721. That seems like a stupid rumor
  722.  
  723. [5:03]
  724. Incredibly so
  725.  
  726. checksum0
  727. [5:07 PM]
  728. So they want you do use a closed-source sidechain
  729.  
  730. hostfat [5:07 PM]
  731. whatever way to make it, can it be a problem because of possible hard forks?
  732.  
  733. checksum0
  734. [5:07 PM]
  735. That requires tamper-proof hardware to work?
  736.  
  737. [5:07]
  738. ON TOP OF BITCOIN?
  739.  
  740. [5:07]
  741. Fuck them.
  742.  
  743. tomothy [5:08 PM]
  744. Wait is there proof?
  745.  
  746. hostfat [5:08 PM]
  747. I want to find more information about this
  748.  
  749. checksum0
  750. [5:09 PM]
  751. No proof
  752.  
  753. [5:09]
  754. gotta drive, afk
  755.  
  756. zbingledack [5:12 PM]
  757. Protected by thermite? Sounds like the lawsuit of the century.
  758.  
  759. 1 reply 19 days ago View thread
  760.  
  761. bitsko
  762. [6:15 PM]
  763. I had read that 1, maybe 2 years ago???
  764.  
  765. [6:17]
  766. a few months ago I was bugging people on the core slack about it.. couldn't get a straight answer... probably realized how retarded it sounds, if that is the actual plan
  767.  
  768. [6:18]
  769. huh. https://bitcoincore.slackarchive.io/-/search-thermite/page-1
  770.  
  771. [6:19]
  772. lol the search results are heavy on my trolling :awesome:
  773.  
  774. tomothy [6:21 PM]
  775. Can't be real. If so. It's really stupid. I told Nichols to come over. Gonna take a nap but someone invite him to some stuff. Sleep now. (edited)
  776.  
  777. nicholat [6:21 PM]
  778. joined hardfork by invitation from @tomothy
  779.  
  780. cypherblock [7:01 PM]
  781. you gotta love a chemistry class thermite demo though.
  782.  
  783. hostfat [7:03 PM]
  784. I really think that there should be a deeper study on Liquid and its hardware part
  785.  
  786. [7:03]
  787. I think that it is here that there is the key to understand why they are so against hard forks
  788.  
  789. bitsko
  790. [7:05 PM]
  791. If someone can schmooze gregory sanders a bit in the core slack its possible he will actually say... possible...
  792.  
  793. [7:07]
  794. lol are all of us known? hmm. tomothy... covert op?
  795.  
  796. [7:07]
  797. :slightly_smiling_face:
  798.  
  799. checksum0
  800. [7:10 PM]
  801. I dont think I'm known under that username in core slack besides shinobibullshit
  802.  
  803. cypherblock [7:11 PM]
  804. https://youtu.be/AckDlVGbB5s?t=1m29s
  805. YouTube HACKADAY
  806. Thermite Vs Laptop: Slow motion destruction
  807.  
  808.  
  809.  
  810. ----- May 26th -----
  811. jonald_fyookball [4:59 PM]
  812. this thermite thing sounds batshit crazy
  813.  
  814. [5:00]
  815. i dont even see how that would work
  816.  
  817. csw [5:01 PM]
  818. The temp that Thermite burns at is incredibly high
  819.  
  820. [5:01]
  821. It is used to start smelting processes
  822.  
  823. [5:01]
  824. It is a shame it is low grade
  825.  
  826. jonald_fyookball [5:02 PM]
  827. yeah but it also requires a high kindling temperature to start...how are they going to ignite it?
  828.  
  829. csw [5:02 PM]
  830. http://www.wikihow.com/Make-Thermite
  831. wikiHow
  832. How to Make Thermite
  833. Thermite is a material used in welding to melt metals together. It burns at around and can melt through most metals. This wikiHow will show you how to make it. Select your site carefully. Make sure there is nothing that can burn within... (333kB)
  834.  
  835. weekend_engineer [5:02 PM]
  836. joined hardfork by invitation from @tomothy, along with @daganb
  837.  
  838. csw [5:02 PM]
  839. Magnesium works wonders
  840.  
  841. [5:02]
  842. Small strips can be purchased and used a s a fuse
  843.  
  844. nicholat [5:02 PM]
  845. thermite can't melt steel beams
  846.  
  847. [5:03]
  848. oh wait
  849.  
  850. jonald_fyookball [5:03 PM]
  851. but whatever sets the fuse off in the first place could be doused
  852.  
  853. csw [5:03 PM]
  854. I made it when I was on my mad craze to prove one man could make a pencil
  855.  
  856. bitsko
  857. [5:04 PM]
  858. LOL
  859.  
  860. nicholat [5:04 PM]
  861. read I, Pencil one too many times?
  862.  
  863. csw [5:04 PM]
  864. I was in touch with Timothy
  865.  
  866. [5:04]
  867. I actually did it
  868.  
  869. [5:05]
  870. 7 years work
  871.  
  872.  
  873. tomothy [5:05 PM]
  874. Did you make a video of this project!?
  875.  
  876. csw [5:05 PM]
  877. 1600 USD a pencil later...
  878.  
  879.  
  880. [5:05]
  881. Somewhere
  882.  
  883. [5:05]
  884. ld blog is partially on the way back
  885.  
  886. [5:05]
  887. One of these days I will dig it up :slightly_smiling_face:
  888.  
  889.  
  890. nicholat [5:06 PM]
  891. heh, the guy who made a ham sandwich from scratch spent $1500 and only 6 months; get on his level
  892.  
  893.  
  894. csw [5:06 PM]
  895. I like the Toaster project better
  896.  
  897. [5:06]
  898. It melted
  899.  
  900. cryptorebel [5:06 PM]
  901. https://www.youtube.com/watch?v=R5Gppi-O3a8
  902. YouTube LibertyPen
  903. Power of the Market - The Pencil
  904.  
  905.  
  906. csw [5:07 PM]
  907. Finding and grinding graphite with bronze tools is a bitch
  908.  
  909.  
  910. [5:08]
  911. I used a Japanese Raku kiln... But the think I could not do was information
  912.  
  913. [5:09]
  914. If I did not have the internet, it would have failed
  915.  
  916.  
  917. [5:09]
  918. I was planning to write it all up - I may still do one day
  919.  
  920. [5:10]
  921. Before I was Doxed and in the panic deleted all my stuff
  922.  
  923. [5:10]
  924. The plan was to write an "I Pencil" 21st C version
  925.  
  926.  
  927. [5:10]
  928. That now, the internet changes all this
  929.  
  930. [5:11]
  931. How it is all there
  932.  
  933. bitsko
  934. [5:11 PM]
  935. People accuse me of being smart, they must not know how to google...
  936.  
  937. csw [5:11 PM]
  938. Step by step
  939.  
  940. bitalien
  941. [5:11 PM]
  942. Were you doxed the same year you met with Gavin and gave him that proof
  943.  
  944. csw [5:11 PM]
  945. No, Dec 2015
  946.  
  947. [5:11]
  948. Gavin was May 2016
  949.  
  950. [5:11]
  951. Other shit
  952.  
  953. [5:12]
  954. Gavin was March... May was other shit
  955.  
  956. bitalien
  957. [5:12 PM]
  958. Was the meeting just some sort of distraction to make sure that people would never believe you are actually Satoshi, and just a scammer looking for attention
  959.  
  960. csw [5:12 PM]
  961. Satoshi will remain a myth, that is the best I can do
  962.  
  963.  
  964. [5:14]
  965. I have 17 degrees. 2 doctorates, 7 masters and I am on my 8th
  966. I start my 3 doctorate this year.
  967.  
  968. I AM a smart ass and ppl do not like that.
  969.  
  970. I am also a geek and isolated. money = training to handle people. I did not have this in the past
  971.  
  972. [5:14]
  973. This is not a brag
  974.  
  975. [5:14]
  976. It just is
  977.  
  978. [5:15]
  979. I like study
  980.  
  981. [5:15]
  982. I have never been out of a university (form 17 0n)
  983.  
  984. klee [5:15 PM]
  985. do you use any smart drugs?
  986.  
  987. csw [5:15 PM]
  988. I was in the military, and in UNI
  989.  
  990. [5:15]
  991. No - just lots of caffine
  992.  
  993. klee [5:15 PM]
  994. haha me too
  995.  
  996. csw [5:15 PM]
  997. I was working, and in UNi
  998.  
  999. bitsko
  1000. [5:15 PM]
  1001. Starting again from square -1... ever thought about a second alias to have greater reach with your ideas? The bias is insurmountable... at least until some papers make it out there...
  1002.  
  1003. csw [5:16 PM]
  1004. You are assuming that I do not have sockpuppets :slightly_smiling_face:
  1005.  
  1006.  
  1007. bitsko
  1008. [5:16 PM]
  1009. :ohyeah:
  1010.  
  1011. bitalien
  1012. [5:16 PM]
  1013. csw is actually neohippy
  1014.  
  1015. bitsko
  1016. [5:16 PM]
  1017. Noooo
  1018.  
  1019.  
  1020. csw [5:16 PM]
  1021. This is the I am me sock puppet
  1022.  
  1023.  
  1024. [5:16]
  1025. LOL
  1026.  
  1027. bitalien
  1028. [5:17 PM]
  1029. csw, how do you have enough time to get so many degrees. Doesn't a doctorate take 8 years?
  1030.  
  1031. csw [5:17 PM]
  1032. 3-4
  1033.  
  1034. [5:17]
  1035. And I am naughty
  1036.  
  1037. [5:17]
  1038. I do 2 or 3 at once
  1039.  
  1040. bitsko
  1041. [5:18 PM]
  1042. I cant wait to get my life back in a place i have time for study...
  1043.  
  1044.  
  1045. csw [5:18 PM]
  1046. I cannot imagine life without it
  1047.  
  1048.  
  1049. csw [5:18 PM]
  1050. uploaded this image: image.png
  1051. Add Comment
  1052.  
  1053. csw [5:19 PM]
  1054. My first real University rejection
  1055.  
  1056. bitsko
  1057. [5:20 PM]
  1058. Heh. What a problem to have.
  1059.  
  1060. csw [5:21 PM]
  1061. I was thinking of amateur boxing... get hit until they accept me :slightly_smiling_face:
  1062.  
  1063.  
  1064. tomothy [5:21 PM]
  1065. Omg. LMFAO
  1066.  
  1067. [5:21]
  1068. They rejected you for being over qualified. I'm not sure what to think about that. How did you react?
  1069.  
  1070. [5:22]
  1071. That's... Wow...
  1072.  
  1073. csw [5:22 PM]
  1074. uploaded this image: image.png
  1075. Add Comment
  1076.  
  1077. csw [5:22 PM]
  1078. Waiting
  1079.  
  1080. [5:22]
  1081. PhD, Pure Maths at Cambridge
  1082.  
  1083. tomothy [5:22 PM]
  1084. Ah, you mentioned that before my bad. Makes sense in light of prior response
  1085.  
  1086. csw [5:23 PM]
  1087. I figure Cambridge has people I can deal with...Ones who do not fit in the real world
  1088.  
  1089.  
  1090.  
  1091. ----- May 27th -----
  1092. travin
  1093. [1:40 AM]
  1094. Well, that's the first legitimate rejection letter I saw for someone being overqualified.
  1095.  
  1096.  
  1097. neohippy [2:25 PM]
  1098. funny since those credentials are a different craig from australia
  1099.  
  1100. tomothy [2:29 PM]
  1101. No neo, it's the same. If you scroll up enough in private you can see him with degrees and him in front of computer. It's the same craig
  1102.  
  1103. neohippy [2:31 PM]
  1104. fool there are two craig wrights from Australia, one has a middle name with different spelling, one has credentials, the other does not
  1105.  
  1106. tomothy [2:31 PM]
  1107. Oh the other here is a day trader if that's what you mean
  1108.  
  1109. neohippy [2:32 PM]
  1110. no, from Australia in general the country not here in the slack
  1111.  
  1112. [2:32]
  1113. this csw is the one claiming to have invented bitcoin, but bitcoin was a plagairism
  1114.  
  1115. [2:32]
  1116. and this csw does noty have dredentials
  1117.  
  1118. tomothy [2:33 PM]
  1119. This csw has credentials and is not claiming to have invented BTC. See private. Do csw search for better info so you can fully evaluate facts and arguments
  1120.  
  1121. checksum0
  1122. [2:34 PM]
  1123. Behaving?
  1124.  
  1125. tomothy [2:34 PM]
  1126. AFK neo, yard work. Do the search.
  1127.  
  1128. [2:34]
  1129. Yes.
  1130.  
  1131. [2:34]
  1132. Debating well
  1133.  
  1134. neohippy [2:34 PM]
  1135. bullshit tom, this csw is the one claiming to have invented bitcoin and he was using someone elses credentiuals to bolster that claim
  1136.  
  1137. checksum0
  1138. [2:35 PM]
  1139. lol :slightly_smiling_face:
  1140.  
  1141. joeldalais [3:51 PM]
  1142. the channel is about #hardfork, not who or who is not satoshi (i'm not sure why that matters anyway), keep on topic, ty :slightly_smiling_face:
  1143.  
  1144.  
  1145.  
  1146. ----- May 30th -----
  1147. psztorc [11:42 AM]
  1148. joined hardfork by invitation from @bitsko, along with @hmr. Also, @neohippy left.
  1149.  
  1150.  
  1151. ----- June 1st -----
  1152. bitalien
  1153. [12:44 AM]
  1154. It seems like we are reaching a tipping point in the scaling debate
  1155.  
  1156. cryptorebel [12:45 AM]
  1157. BUIP 056 or whatever comes out of it might have promise
  1158.  
  1159. bitalien
  1160. [12:45 AM]
  1161. The last couple days, it seems as if /r/btc has had a LOT more activity, and a lot of LEGITIMATELY pissed off people at /r/Bitcoin and BlockstreamCore
  1162.  
  1163.  
  1164. bitalien
  1165. [12:53 AM]
  1166. Also, I just want to say how ridiculous it is that SegWit still needs at least 80% of hash rate to activate. That's a very large amount, and I can't foresee it EVER activating
  1167.  
  1168. [12:55]
  1169. BU should honestly fork at 60% or less. 60% is perfectly safe. I think by the time BU gets a SOLID 50% for a couple weeks straight, businesses will wake up and people will start preparing for the inevitable fork
  1170.  
  1171. [12:55]
  1172. It will be game over if BU can get just 10% or so more hash rate
  1173.  
  1174. phoenix
  1175. [5:18 AM]
  1176. for anyone that still says that b/w is a problem to larger blocks https://www.akamai.com/us/en/multimedia/documents/state-of-the-internet/q1-2017-state-of-the-internet-connectivity-report.pdf
  1177.  
  1178. phoenix
  1179. [5:19 AM]
  1180. uploaded this image: unnamed (2).jpg
  1181. Add Comment
  1182.  
  1183. phoenix
  1184. [5:19 AM]
  1185. uploaded this image: unnamed (1).jpg
  1186. Add Comment
  1187.  
  1188. phoenix
  1189. [5:19 AM]
  1190. uploaded this image: unnamed.jpg
  1191. Add Comment
  1192.  
  1193. csw [5:26 AM]
  1194. But I cannot run a $20 USD version 0.1 raspberry pie in rural Africa as a full node
  1195.  
  1196. [5:26]
  1197. :wink:
  1198.  
  1199. pesa [5:41 AM]
  1200. Kenya
  1201.  
  1202. im using a Telcos data bundle right now. tethering my phone $10 for 3GB for 30 days
  1203. Orange telcos modem bundle $35 per month for 30GB
  1204. where i used to live Zuku fibre $190 for 250Mbps Unlimited High Speed Internet
  1205.  
  1206. [5:42]
  1207. my friend Tim runs a full node in Nigeria
  1208.  
  1209.  
  1210. [5:42]
  1211. https://motherboard.vice.com/en_us/article/meet-the-man-running-the-only-bitcoin-node-in-west-africa
  1212. Motherboard
  1213. Meet the Man Running the Only Bitcoin Node In West Africa
  1214. A Nigerian developer wants to start building the bitcoin network in the region. (113kB)
  1215.  
  1216. pesa [5:42 AM]
  1217. Tim though is pro-Segwit :slightly_smiling_face:
  1218. 1 reply 13 days ago View thread
  1219.  
  1220. checksum0
  1221. [9:27 AM]
  1222. @pesa You are in Kenya?
  1223.  
  1224. [9:27]
  1225. Are you native from there or working there?
  1226.  
  1227. pesa [9:59 AM]
  1228. born and raised here
  1229. 3 replies Last reply 13 days ago View thread
  1230.  
  1231. checksum0
  1232. [10:07 AM]
  1233. You are like the unicorn Core says can't exists!
  1234.  
  1235.  
  1236. btcalbin [3:57 PM]
  1237. What is the limiting factor in nodes happening in W. Africa? the bandwidth / resource costs of running a node, or people wanting to use Bitcoin in the first place?
  1238.  
  1239. checksum0
  1240. [3:58 PM]
  1241. Sure thing, we NEED nodes in Africa
  1242.  
  1243. [3:58]
  1244. I once looked at renting hardware their to run nodes in Africa but it was a pretty large hassle and I couldn't find any offer that made any sense at all to run a node...
  1245.  
  1246. pesa [6:12 PM]
  1247. incentives for running a node? i bet if running a node (not a mining node) paid BTC, we could see more
  1248.  
  1249. csw [6:12 PM]
  1250. Nodes mine
  1251.  
  1252.  
  1253. pesa [6:12 PM]
  1254. yes
  1255.  
  1256. csw [6:13 PM]
  1257. You mean a wallet
  1258.  
  1259. pesa [6:13 PM]
  1260. yes :slightly_smiling_face:
  1261.  
  1262. [6:13]
  1263. ive seen your discussions on what a 'node' really is
  1264.  
  1265. tomothy [6:13 PM]
  1266. Would be nice to have updated hardware
  1267.  
  1268. csw [6:13 PM]
  1269. Wallets help the owner of the wallet
  1270.  
  1271. [6:14]
  1272. What is there to pay them.
  1273.  
  1274. pesa [6:14 PM]
  1275. theres wallets like mycelium
  1276.  
  1277. [6:15]
  1278. then theres 'nodes' like the ones that are about 5k across the world that store copy of blockchain
  1279.  
  1280. tomothy [6:15 PM]
  1281. Those 21inc machines as well. They mine and are a wallet I believe
  1282.  
  1283. [6:15]
  1284. Not sure if they're still sold
  1285.  
  1286. hmr [6:17 PM]
  1287. I want to build a little weather station. Maybe, one day, I could offer the data for sale as well.
  1288.  
  1289.  
  1290. pesa [6:20 PM]
  1291. I think every moderate user of bitcoin would benefit by running a full node and using it as their wallet. There are several ways to do this.
  1292.  
  1293. Run a bitcoin-qt full node.
  1294. Use wallet software that is backed by a full node (e.g. Armory, JoinMarket)
  1295. Use a lightweight wallet that connects only to your full node (e.g. Multibit connecting only to your node running at home, Electrum connecting only to your own Electrum server)
  1296. So what are you waiting for? The benefits are many, the downsides are not that bad. The more people do this, the more robust and healthy the bitcoin ecosystem is.
  1297.  
  1298. [6:21]
  1299. what benefit? i imagine regular users are comfortbale with mobile/desktop/hardware wallets
  1300.  
  1301. hmr [6:26 PM]
  1302. Is there a point, say a certain amount of full blockchain wallets, at which the network becomes too 'robust' in your opinion?
  1303.  
  1304. hmr [6:26 PM]
  1305. Or would it be ideal to have a full ledger for each person on earth or more...?
  1306. 2 replies Last reply 13 days ago View thread
  1307.  
  1308. pesa [6:27 PM]
  1309. hmm
  1310.  
  1311. [6:28]
  1312. i imagine there is an ideal solution where every person can verify the authenticity of the ledger by just checking a small part of it thats ideally small enough for a light weight device
  1313.  
  1314. [6:28]
  1315. it would have to be almost unnoticeable to the end user
  1316.  
  1317. [6:29]
  1318. i think ive seen CSW suggest something like this for merchant POS equipment
  1319.  
  1320. hmr [6:29 PM]
  1321. :slightly_smiling_face:
  1322.  
  1323. [6:30]
  1324. https://pastebin.com/xEr36iiK (edited)
  1325.  
  1326. [6:30]
  1327. it may be in there... haven't looked yet...
  1328.  
  1329. pesa [6:31 PM]
  1330. yeah. im waiting for what nChain will bring to the industry with that kind of solution
  1331.  
  1332. hmr [6:31 PM]
  1333. ah, thats not the one I was looking for anyhow...
  1334.  
  1335. pesa [6:34 PM]
  1336. link?
  1337.  
  1338. [6:34]
  1339. not it
  1340.  
  1341. [6:34]
  1342. by i recall what the implications were
  1343.  
  1344. [6:35]
  1345. i have an elec eng academic background, but thats faded over the years as i transitioned into human centred/user research/biz dev/trading roles
  1346.  
  1347. [6:36]
  1348. i only understand enough for a take away
  1349.  
  1350.  
  1351. ----- June 2nd -----
  1352. freetrader [6:51 AM]
  1353. UASF? UAHF!
  1354.  
  1355. [6:51]
  1356. :smile:
  1357.  
  1358. [6:52]
  1359. Softies gotta learn. Life is hard.
  1360.  
  1361.  
  1362. movrcx [2:11 PM]
  1363. joined hardfork by invitation from @tomothy
  1364.  
  1365. movrcx [2:31 PM]
  1366. So I'm going to spend my day writing a new BIP to forceably de-activate SegWit. Would be cool if you all could review it before I publicly release.
  1367.  
  1368. checksum0
  1369. [2:31 PM]
  1370. Sure thing
  1371.  
  1372. [2:31]
  1373. Just post it here
  1374.  
  1375. movrcx [2:31 PM]
  1376. ok
  1377.  
  1378. checksum0
  1379. [2:32 PM]
  1380. I wouldn't worry about funding, there are a lot of whale behind big block :wink: (edited)
  1381.  
  1382. tomothy [2:32 PM]
  1383. Also if you get bored I think @jvwvu wants bip109+parval, :face_with_rolling_eyes: and no segshit....
  1384.  
  1385. jvwvu [2:32 PM]
  1386. joined hardfork by invitation from @tomothy
  1387.  
  1388. tomothy [2:34 PM]
  1389. I know BU is maybe working on an 8mb HF
  1390.  
  1391.  
  1392. [2:34]
  1393. Peter is here too. Sometimes. I'm not sure about tom z anymore.
  1394.  
  1395. [2:35]
  1396. There are a number of devs and people working on things elsewhere who stop by here. Mainly in the private channel
  1397.  
  1398. checksum0
  1399. [2:42 PM]
  1400. https://twitter.com/movrcx/status/870527842789892096
  1401. movrcx @movrcx
  1402. #Bitcoin Core 0.11.x-0.14.x 0day DoS for sale: 500 BTC. 100% effective at stopping #UASF and hostile forks. cc: @JihanWu @rogerkver
  1403. TwitterJune 2nd at 2:29 AM
  1404.  
  1405. [2:42]
  1406. If your tweet is real, it likely affect BU, XT and Classic too (edited)
  1407.  
  1408. joeldalais [2:46 PM]
  1409. seems odd to request payment in the currency that you're planning on helping to ddos ..
  1410.  
  1411. movrcx [2:46 PM]
  1412. I don't really care about the money...
  1413.  
  1414. joeldalais [2:47 PM]
  1415. ahh hi
  1416.  
  1417. movrcx [2:47 PM]
  1418. I also have a credit from ZcashCo for DoS security research as well. One sec I'll find it
  1419.  
  1420. joeldalais [2:47 PM]
  1421. if it only effects wallet 'nodes' then its just going to make noise and paint the pro-bigger blocks side in not a pretty light (edited)
  1422.  
  1423. movrcx [2:47 PM]
  1424. https://z.cash/blog/security-announcement-2017-04-13.html *I'm listed on the bottom*
  1425.  
  1426. checksum0
  1427. [2:48 PM]
  1428. Well crashing core on August 1st could be fucking great, somebody that might or might not be in this slack might or might not be willing to fund this initiative. (edited)
  1429.  
  1430. joeldalais [2:48 PM]
  1431. cool, but still, wondering about the effectiveness of ddos'ing core
  1432.  
  1433. checksum0
  1434. [2:48 PM]
  1435. If it is safe for big block client...
  1436.  
  1437. joeldalais [2:48 PM]
  1438. better to let them fork off
  1439.  
  1440. [2:49]
  1441. won't have a need to attack them
  1442.  
  1443. [2:49]
  1444. but hey, its a free market, so
  1445.  
  1446. movrcx [2:49 PM]
  1447. I'm going to work this for free most likely @checksum0
  1448.  
  1449.  
  1450. joeldalais [2:49 PM]
  1451. personally, i'm happy for blockstreamcore to burn :slightly_smiling_face: (edited)
  1452.  
  1453.  
  1454. [2:49]
  1455. so..
  1456.  
  1457. cryptorebel [2:50 PM]
  1458. joeldalais has good point, but also seems reasonable to protect the network also
  1459.  
  1460. joeldalais [2:50 PM]
  1461. well.. we're going to be publicly letting people know that uasf is a huge clusterfuck and how to protect yourself (e.g. how to do your due diligence)
  1462.  
  1463. tomothy [2:50 PM]
  1464. So, you aren't located​ in us correct? Or any western nation?
  1465.  
  1466. movrcx [2:51 PM]
  1467. Sounds good @joeldalais I'm working on a BIP too
  1468.  
  1469. [2:51]
  1470. It should cause some controversy
  1471.  
  1472. tomothy [2:51 PM]
  1473. Just, if the concern is valid, it could be not fun
  1474.  
  1475. joeldalais [2:51 PM]
  1476. but its a free market, so, i expect that segshitcoin will be attacked, and i'll be eating popcorn and watching with a smile :wink:
  1477.  
  1478. checksum0
  1479. [2:51 PM]
  1480. :popcorn:
  1481.  
  1482. tomothy [2:51 PM]
  1483. Maybe a j/k tweet?
  1484.  
  1485. cryptorebel [2:52 PM]
  1486. they seem to attack and DDOS BU all the time
  1487.  
  1488. tomothy [2:52 PM]
  1489. Yes, but it's not an identifiable actor
  1490.  
  1491. [2:52]
  1492. So
  1493.  
  1494. movrcx [2:52 PM]
  1495. I see a bunch of the Core devs almost monthly and they all know SegWit is a scam I think
  1496.  
  1497.  
  1498. [2:52]
  1499. I really don't understand why they support it
  1500.  
  1501.  
  1502. tomothy [2:53 PM]
  1503. Responsibly disclose, as a cya, Maybe a week prior to 8/1
  1504.  
  1505.  
  1506. joeldalais [2:53 PM]
  1507. its the almighty usd
  1508.  
  1509. tomothy [2:53 PM]
  1510. Or a month before even
  1511.  
  1512. [2:53]
  1513. And then allow market to act
  1514.  
  1515. joeldalais [2:53 PM]
  1516. it'll be a week or so before
  1517.  
  1518. [2:53]
  1519. week by week releases of "segshit is bad because ..."
  1520.  
  1521. cryptorebel [2:54 PM]
  1522. or disclose 2 days before and force them to push back the UASF date
  1523.  
  1524. joeldalais [2:54 PM]
  1525. then the week or so before a big arse summary, a "final warning" kind of thing
  1526.  
  1527. [2:54]
  1528. nah, we don't want them to change the uasf date
  1529.  
  1530. tomothy [2:54 PM]
  1531. I'm just saying State side, far lead timr on responsible disclosure could help avoid uncomfortable questions later
  1532.  
  1533. joeldalais [2:55 PM]
  1534. they'll have a couple months warning, not counting all the warnings everyone here has been saying for years (which is far than enough imho), then the 'week before' final warning
  1535.  
  1536. [2:55]
  1537. after that let the lemmings jump
  1538.  
  1539. cryptorebel [2:55 PM]
  1540. yeah im kind of looking forward to their UASF blockchain suicide day (edited)
  1541.  
  1542. joeldalais [2:55 PM]
  1543. sometimes the hardest lessons are the best :slightly_smiling_face:
  1544.  
  1545. deadalnix [2:56 PM]
  1546. They don't support it. If they wanted it, they'd support HK or NY agreements. They value being in charge, not SW. SW not activating is the best thing that ever happened to them.
  1547. movrcx
  1548. I really don't understand why they support it
  1549. Posted in #hardforkJune 2nd at 2:52 PM
  1550.  
  1551. tomothy [2:56 PM]
  1552. I mean think about it this way. In America they arrested Aaron Schwartz for downloading free publications. No money was lost. Compare that to an exploit that causes monetary losses. I'm just saying cover your self
  1553.  
  1554. joeldalais [2:57 PM]
  1555. karpeles and bad functions/coding with gox.. i see a similar scenario
  1556.  
  1557. [3:00]
  1558. hm.. thing is.. not sure if they/blockstream could be associated with 'responsible 'guardian' of said funds' ... they always act a bit like weasels around this..
  1559.  
  1560. checksum0
  1561. [3:00 PM]
  1562. responsible guardian of the funds are miner
  1563.  
  1564. [3:00]
  1565. per whitepaper
  1566.  
  1567. movrcx [3:01 PM]
  1568. @tomothy I wouldn't do any actual exploiting... Coordinated release is good enough to get the job done :slightly_smiling_face:
  1569.  
  1570. [3:01]
  1571. Just having a 0day is enough to force discussion and that's really valuable in itself
  1572.  
  1573. joeldalais [3:01 PM]
  1574. @checksum0 wonder if that would count legally... whether it would be bitfury/anonymous miners (who actually mine segwit) or blockstream held accountable..
  1575.  
  1576. checksum0
  1577. [3:02 PM]
  1578. No clue, legality and me are not good friend. (edited)
  1579.  
  1580. joeldalais [3:02 PM]
  1581. @csw your thoughts?
  1582.  
  1583. [3:02]
  1584. @roger_murdock and yours
  1585.  
  1586. [3:03]
  1587. or whether it would be the exchanges who allowed the trading... especially if such exchanges label the minority/uasf as 'bitcoin', then its definitely them in the shitter.. but wonder if the miners/blockstream would still be held liable
  1588.  
  1589. [3:05]
  1590. blockstream .. miners .. exchanges ... where does the ball drop when it goes to shit .. i wonder what each of those entities think, where the ball drops.. it might explain some of their actions if they think they can do all this and have zero liability
  1591.  
  1592. tomothy [3:10 PM]
  1593. Yeah in this environment with both sides so angry and heated. Just thinking cya is important
  1594.  
  1595. jvwvu [3:26 PM]
  1596. why?
  1597. jvwvu
  1598. @jvwvu has joined the group
  1599. Posted in #hardforkJune 2nd at 2:32 PM
  1600.  
  1601. tomothy [3:27 PM]
  1602. Thought you were in this channel. Tried to ping you. Saw you weren't. Added you.
  1603.  
  1604. jvwvu [3:29 PM]
  1605. http://www.sideprojectprofit.com/wp-content/uploads/2013/12/ifyoubuildittheywillcome.png (262kB)
  1606.  
  1607. Until then fuck a hardfork, I can live with 1 MB and Coinbase Shift card
  1608.  
  1609. dgenr8 [3:31 PM]
  1610. @deadalnix They do value being in charge, and deluded themselves they could maintain power _and_ resist reasonable blocksize increase (edited)
  1611.  
  1612. freetrader [3:31 PM]
  1613. @movrcx :
  1614. is your public announcement today the first step towards making this exploit known?
  1615. have you tried some form of responsible disclosure with Core, and if so, are you willing to say what happened?
  1616.  
  1617. [3:32]
  1618. FYI:
  1619. I'm hoping that we will have some big-block capable Core nodes running by Aug 1.
  1620.  
  1621. [3:32]
  1622. Unfortunately these would be vulnerable as well, as I take from your messages
  1623.  
  1624. movrcx [3:33 PM]
  1625. @freetrader Yes it's the first step. Core knows how I feel about UASF and they don't care...
  1626.  
  1627. [3:33]
  1628. Honestly I sort of view them as a competitor as well (full disclosure)
  1629.  
  1630. onchainscaling [3:36 PM]
  1631. joined hardfork by invitation from @checksum0, along with @david
  1632.  
  1633. freetrader [3:42 PM]
  1634. @movrcx : thanks, and I look forward to reading your BIP soon.
  1635.  
  1636.  
  1637. pesa [3:53 PM]
  1638. https://twitter.com/eric_lombrozo/status/870668141080260608
  1639. Eric Lombrozo @eric_lombrozo
  1640. @Truthcoin @francispouliot_ @movrcx @JihanWu @rogerkver I already reviewed several such "exploits" sent to me in private. They are all false flags.
  1641. TwitterJune 2nd at 11:47 AM
  1642.  
  1643. [3:53]
  1644. lombrozo bluffing?
  1645.  
  1646.  
  1647. [3:53]
  1648. he's become too loud and vocal of late
  1649.  
  1650. [3:53]
  1651. he changed
  1652.  
  1653. cryptorebel [3:55 PM]
  1654. its false confidence, anybody with credibility would be humble enough to consider all threats as serious, reeks of hubris
  1655.  
  1656.  
  1657. pesa [3:57 PM]
  1658. true
  1659.  
  1660. [3:59]
  1661. i suspect the whole lot of them predicated the future of their companies and consulting services on SegWit after investing time and energy
  1662.  
  1663. movrcx [4:01 PM]
  1664. @cryptorebel I'm a Mozilla Hall of Fame Security Researcher too... i don't think they did their due dilligence. (edited)
  1665.  
  1666.  
  1667. [4:02]
  1668. I definitely enjoy watching hubris get smashed to bits though :slightly_smiling_face:
  1669.  
  1670.  
  1671. bitalien
  1672. [4:03 PM]
  1673. What kind of security research do you do?
  1674.  
  1675. [4:04]
  1676. Do you know C++, and understand exploits like heart bleed?
  1677.  
  1678. freetrader [4:04 PM]
  1679. >Honestly I sort of view them as a competitor as well (full disclosure)
  1680. I guess you refer to Bitcoin as a whole, Core being the front line of it...
  1681.  
  1682. movrcx [4:07 PM]
  1683. Yeah I previously did red team government work @bitalien
  1684.  
  1685. bitalien
  1686. [4:07 PM]
  1687. That's cool, how do you even get involved in that
  1688.  
  1689. movrcx [4:07 PM]
  1690. Just apply lol
  1691.  
  1692. [4:08]
  1693. I have my own blockchain nowadays though
  1694.  
  1695. [4:08]
  1696. well i develop it i mean
  1697.  
  1698. bitalien
  1699. [4:08 PM]
  1700. Judy put my resume in an envelope and address it to "The Government"? lol
  1701.  
  1702. [4:08]
  1703. Apply where though
  1704.  
  1705. movrcx [4:09 PM]
  1706. If you're really interested in doing exploit dev for operational activities then it's mostly contracted work.
  1707.  
  1708. [4:09]
  1709. Having a security clearance is a hassle and I wouldn't recommend going into that line of work tbh.
  1710.  
  1711. bitalien
  1712. [4:09 PM]
  1713. I don't think I would ever work for the government, but I would like to learn about exploits independently.
  1714.  
  1715. movrcx [4:10 PM]
  1716. Come to a security conference...everybody is usually very friendly and there's workshops for all skill levels
  1717.  
  1718. [4:11]
  1719. I can point you to some self-directed resources to if you want to mess around
  1720.  
  1721.  
  1722. tula [5:38 PM]
  1723. https://btcchat.slack.com/archives/G5FFUS6E7/p1496434082708245 could you tell more?
  1724. movrcx
  1725. I have my own blockchain nowadays though
  1726. Posted in #hardforkJune 2nd at 4:08 PM
  1727.  
  1728. checksum0
  1729. [5:57 PM]
  1730. Tula, zencash.io
  1731.  
  1732.  
  1733. Pinned by cryptorebel
  1734. June 3rd at 4:43 AM Pinned by cryptorebel
  1735. movrcx [6:07 PM]
  1736. https://github.com/joshuayabut/bips/blob/master/bip-0200.mediawiki
  1737. GitHub
  1738. joshuayabut/bips
  1739. bips - Bitcoin Improvement Proposals
  1740.  
  1741.  
  1742.  
  1743. [6:07]
  1744. rough draft and doesn't include any 0day requirements
  1745.  
  1746. hmr [6:23 PM]
  1747. Ping everyone!!!a! All the coders!a!
  1748.  
  1749. [6:23]
  1750. :+1:
  1751.  
  1752.  
  1753. movrcx [6:55 PM]
  1754. They closed my BIP lol
  1755.  
  1756. [6:58]
  1757. fuckers i guess ill just need to send it to the bitcoin-dev mailinglist (edited)
  1758.  
  1759. hmr [6:59 PM]
  1760. what!? :awesome:
  1761.  
  1762. movrcx [6:59 PM]
  1763. https://github.com/bitcoin/bips/pull/545
  1764. GitHub
  1765. Mandatory de-activation of forced segwit deployment by joshuayabut · Pull Request #545 · bitcoin/bips
  1766. This BIP supercedes BIP148 and outlines the methods and actions necessary to prevent unwanted network segmentation and forced isolation caused by non-consensual BIP148 and Segregated Witness deploy...
  1767.  
  1768.  
  1769. hmr [7:02 PM]
  1770. I would give you thumbs up on that pull, but it looks like they blocked me :joy:
  1771.  
  1772.  
  1773. csw [10:12 PM]
  1774. Companies will pass the costs and it will be owned
  1775.  
  1776.  
  1777.  
  1778. ----- June 3rd -----
  1779. btcalbin [12:45 AM]
  1780. That's absolutely hilarious what kind of sticklers to process they are when they want to be, when segwit was decided on privately ahead of time, the 2nd Scaling conference was a disingenuous complete waste of everybody's time that was just a press conference announcing segwit, a bunch of Core folks signed onto a pledge that was simply a quick and dirty email by Maxwell as post-conference wrapup that committed them to all kinds of action items none of which have any proposals to review and study, and then well after all this was decided and pledge, then finally the community got to see some BIPs when it was already too late!
  1781.  
  1782.  
  1783. movrcx [1:59 AM]
  1784. Well looks like I'm going to turn bip200.com into a thing. Getting some good support within the cypherpunk community. Stay tuned :slightly_smiling_face:
  1785.  
  1786.  
  1787. zbingledack [3:23 AM]
  1788. >The author of this proposal suggests that significant consensus altering changes should not be applied without unanimous support by the greater Bitcoin community (especially those outside commercial organizations).
  1789.  
  1790. ಠ_ಠ
  1791.  
  1792. "they vote with their CPU power" -Satoshi
  1793.  
  1794. Unanimity has nothing to do with Bitcoin. (edited)
  1795.  
  1796.  
  1797. [3:26]
  1798. >[BIP148] makes miners subject to financial bribery
  1799.  
  1800. Miners are always subject to bribery, though instead of bribing them you may as well just buy hashpower with the money. (edited)
  1801.  
  1802. [3:27]
  1803. Good to kill the UASF nonsense but I'd feel more comfortable if you understood these things.
  1804.  
  1805.  
  1806. klee [3:28 AM]
  1807. So where do we stand from here?
  1808.  
  1809. [3:29]
  1810. What is 'our' roadmap?
  1811.  
  1812. [3:29]
  1813. What will CSW & miners do?
  1814.  
  1815. zbingledack [3:29 AM]
  1816. Remove the cap
  1817.  
  1818. [3:29]
  1819. Let Bitcoin fly
  1820.  
  1821. klee [3:29 AM]
  1822. Will it be announced/coordinated effort ?
  1823.  
  1824. [3:29]
  1825. Yes, agree
  1826.  
  1827. [3:30]
  1828. I mean that Core has decided for it's move
  1829.  
  1830. [3:30]
  1831. What is the counter move from everyone opposed to Core?
  1832.  
  1833. [3:31]
  1834. People, very good friends, ask me what to do with their coins at Aug 1st
  1835.  
  1836. [3:31]
  1837. Hold is always cool but I want an optimal strategy
  1838.  
  1839. [3:31]
  1840. Dump UASFcoin assap?
  1841.  
  1842. zbingledack [3:31 AM]
  1843. Miners should wise up and lift the cap. They must if Bitcoin incentive design isn't a failure. We can help them reach that decision, though, both through arguments and through market mechanisms like futures trading.
  1844.  
  1845. klee [3:31 AM]
  1846. Wait until BU gets very low?
  1847.  
  1848. [3:32]
  1849. So it is futures
  1850.  
  1851. cryptorebel [3:32 AM]
  1852. segwit miners will fork off their minority chain, then that will allow BU to gain higher % hash rate on the real Bitcoin chain and hopefully implement BUIP 056 or similar for 8MB blocks
  1853.  
  1854. klee [3:32 AM]
  1855. Futures are not safe
  1856.  
  1857. [3:32]
  1858. because if I hold BTC (whatever chain) I can't get margin called (edited)
  1859.  
  1860. [3:32]
  1861. Futures = margin calls
  1862.  
  1863. cryptorebel [3:32 AM]
  1864. people like Trace Mayer and others keep saying that BIP 148 chain will win and cause the legacy chain to reorg, but I don't see how that is possible
  1865.  
  1866. klee [3:32 AM]
  1867. Avoid them, especially in wild market like the HF one
  1868.  
  1869. zbingledack [3:33 AM]
  1870. Plenty of people will enjoy the futures market. Most won't play, and that is fine.
  1871.  
  1872. klee [3:34 AM]
  1873. I see REKT people
  1874.  
  1875. [3:34]
  1876. :smile:
  1877.  
  1878. zbingledack [3:34 AM]
  1879. Always ;)
  1880.  
  1881. klee [3:34 AM]
  1882. My plan is either of the two:
  1883.  
  1884. [3:34]
  1885. 1) Stay in btc, have 2 coins in the exchange
  1886.  
  1887. [3:35]
  1888. dump CoreCoin if BU oversold and/or Core overbought
  1889.  
  1890. [3:35]
  1891. 2) Stay in cash
  1892.  
  1893. [3:35]
  1894. buy the BU coin if oversold
  1895.  
  1896. zbingledack [3:35 AM]
  1897. Mainly the people who were wrong get rekt (edited)
  1898.  
  1899. klee [3:36 AM]
  1900. 1 has the risk that both chains will fall very low in price and the winner will make months to get above pre-HF price levels
  1901.  
  1902. zbingledack [3:36 AM]
  1903. That rektage is what has been missing all this time. The idiots need to lose money and thus lose influence, while the smart ones gain.
  1904.  
  1905. klee [3:36 AM]
  1906. 2 has the risk that BU will never get rekt and I will have to buy higher
  1907.  
  1908. [3:36]
  1909. Opinions?
  1910.  
  1911. cryptorebel [3:36 AM]
  1912. I was thinking to dump a % of my BIP 148 coins very quickly, but then again maybe its best to wait, who knows we may end up with like 3 different chains after it all blows over
  1913.  
  1914. klee [3:36 AM]
  1915. haha
  1916.  
  1917. [3:36]
  1918. scary...
  1919.  
  1920. zbingledack [3:38 AM]
  1921. It really depends on hashpower. UASF is pointless, but that doesn't mean miners won't jump on the Aug1 Schelling point as a time to activate Segwit (or bigger blocks, or both)
  1922.  
  1923. movrcx [3:39 AM]
  1924. How easy is it for you all to coordinate miners?
  1925.  
  1926. [3:39]
  1927. I can write some software if need but was looking to build some support for BIP200. I'm guessing it'll hit the news cycles next week.
  1928.  
  1929. zbingledack [3:41 AM]
  1930. We can talk to Jihan (Antpool) and Haipo Yang (ViaBTC) in the BU Slack
  1931.  
  1932. movrcx [3:41 AM]
  1933. I've been looking at block allocation between BU and Core and I think BIP200 is executable with only 33% hashpower.
  1934.  
  1935. [3:41]
  1936. There's going to be alot of panic and people will sell off naturally when they see the BIP200 heart beat signals. (edited)
  1937.  
  1938. [3:42]
  1939. After a period the BIP just reverts to the pre-segwit blockheight.
  1940.  
  1941. zbingledack [3:43 AM]
  1942. And Wang Chun (F2Pool) seems like he might enjoy the fun, since he says he only signalled Segwit because of DDoS attacks
  1943.  
  1944.  
  1945. movrcx [3:43 AM]
  1946. ^That's a simplification of all that's going on but I think it's a good strategy. It hides how much support we have until after the consensus change.
  1947.  
  1948. cryptorebel [3:44 AM]
  1949. what about submitting it as a BUIP??
  1950.  
  1951. movrcx [3:45 AM]
  1952. Sure let me look into that..
  1953.  
  1954. cryptorebel [3:47 AM]
  1955. I think it goes through the bitco.in forum: https://bitco.in/forum/threads/buip055-increase-the-block-size-limit-at-a-fixed-block-height.2103/
  1956. Bitcoin Forum
  1957. BUIP055: Increase the Block Size Limit at a Fixed Block Height
  1958. BUIP055: Increase the Block Size Limit at a Fixed Block Height Proposer: Peter Rizun Submitted: 2017-05-10 Abstract This BUIP proposes to add...
  1959.  
  1960.  
  1961. [3:49]
  1962. makes sense to take steps to stop this UASF attack on the network
  1963.  
  1964. joeldalais [4:06 AM]
  1965. @movrcx, i've been talking to some miners (and others talking to them), but a bit of a hurdle with wang chung/f2pool, i don't have contact with him, working on it though.. but if anyone here does, then please feel free to give him a prod
  1966.  
  1967. [4:06]
  1968. and plan is to use a slightly altered buip055 to signal, and probably for activation, tomtomtom7 and csw were discussing it (edited)
  1969.  
  1970. movrcx [4:10 AM]
  1971. That's just to chainsplit it though right?
  1972.  
  1973. joeldalais [4:11 AM]
  1974. soso.. if they've already split off to uasf, then its more for 'activation', we'd be leaving no one behind at that point
  1975.  
  1976. [4:11]
  1977. still a fork though
  1978.  
  1979. movrcx [4:11 AM]
  1980. Yeah I don't think that's ideal. Either become the dominant chain or it's not worth it.
  1981.  
  1982. joeldalais [4:11 AM]
  1983. if they uasf off then what is left will be the dominant
  1984.  
  1985. [4:12]
  1986. assuming they're all on the same page
  1987.  
  1988. movrcx [4:12 AM]
  1989. Would there by any issues with running modified Bitcoin Core daemons for the miners? I only know the Core codebase but if I had some help could probably do BU
  1990.  
  1991. cryptorebel [4:12 AM]
  1992. BU won't probably activtae larger blocks until it gets majority hash rate, but BIP 148 might fork off a lot of segwit miners, leaving higher % of big block supporting miners on real Bitcoin chain
  1993.  
  1994.  
  1995. [4:13]
  1996. pretty sure many miners run custom implementations
  1997.  
  1998. joeldalais [4:13 AM]
  1999. honestly.. i wouldn't be able to answer you properly, but i can drop you in the other miner (support) channel for miners if you'd like? some BU devs there also
  2000.  
  2001. [4:14]
  2002. but ye, there needs and will be, support
  2003.  
  2004. movrcx [4:14 AM]
  2005. sounds good :slightly_smiling_face:
  2006.  
  2007. joeldalais [4:14 AM]
  2008. a dev/tech team will be provided to all miners, and similar support to all implementations
  2009.  
  2010. movrcx [4:14 AM]
  2011. Bitcoin Core is freaking out about the BIP btw
  2012.  
  2013. joeldalais [4:15 AM]
  2014. 055?
  2015.  
  2016. movrcx [4:15 AM]
  2017. Maybe we are talking different things lol.
  2018.  
  2019. [4:15]
  2020. BIP200
  2021.  
  2022. joeldalais [4:15 AM]
  2023. got a link?
  2024.  
  2025. cryptorebel [4:16 AM]
  2026. https://github.com/joshuayabut/bips/blob/3259b05efe55c2d6146b438909b3909ec1c1739c/bip-0200.mediawiki
  2027. GitHub
  2028. joshuayabut/bips
  2029. bips - Bitcoin Improvement Proposals
  2030.  
  2031.  
  2032. movrcx [4:16 AM]
  2033. bip200.com too
  2034.  
  2035.  
  2036. [4:16]
  2037. i just registered that
  2038.  
  2039. joeldalais [4:16 AM]
  2040. ta
  2041.  
  2042. cryptorebel [4:16 AM]
  2043. seems like a pretty good idea to stop UASF
  2044.  
  2045. joeldalais [4:17 AM]
  2046. nice one :smile:
  2047.  
  2048. cryptorebel [4:17 AM]
  2049. they won't be able to ban non segwit nodes because they won't be able to identify them is what it seems
  2050.  
  2051. movrcx [4:17 AM]
  2052. agreed
  2053.  
  2054. [4:18]
  2055. so BU will roll into segwit and then after a period of blocks signal that they are reverting to the pre-segwit blockheight
  2056.  
  2057. cryptorebel [4:18 AM]
  2058. we definitely need to take evey step possible to mitigate this attack
  2059.  
  2060. movrcx [4:18 AM]
  2061. What do you mean?
  2062.  
  2063. [4:18]
  2064. Like detection of nodes?
  2065.  
  2066. klee [4:19 AM]
  2067. https://twitter.com/CryptXO/status/870917738902020096
  2068. Crypt-XO @CryptXO
  2069. BIP200: https://github.com/joshuayabut/bips/blob/3259b05efe55c2d6146b438909b3909ec1c1739c/bip-0200.mediawiki
  2070.  
  2071. #Bitcoin #FusckSegwit #FuckUASF
  2072. TwitterJune 3rd at 4:19 AM
  2073.  
  2074.  
  2075. movrcx [4:19 AM]
  2076. They could get crafty with it and that's why it might be better to run a modified Core codebase
  2077.  
  2078. [4:19]
  2079. I don't think they are banning nodes explicitly just blocks
  2080.  
  2081. [4:20]
  2082. But that could change
  2083.  
  2084. cryptorebel [4:20 AM]
  2085. yeah true, already roger ver said he is disgusing BU nodes as Core to prevent ddos attacks
  2086.  
  2087. joeldalais [4:21 AM]
  2088. just read it :smile: i can see why they would be shitting themselves, good job :slightly_smiling_face:
  2089.  
  2090.  
  2091. tula [6:12 AM]
  2092. still not understandind your motivation @movrcx. You have your own blockchain project, bitcoin is a competitor to you, right?
  2093.  
  2094. movrcx [10:06 AM]
  2095. I don't really care about the financial aspects of it too much @tula I'm mostly ideologically charged.
  2096.  
  2097.  
  2098. movrcx [10:16 AM]
  2099. Seeing Core and all of the commercial entities back off of a UASF/SegWit implementation would be deeply pleasurable for me to see haha
  2100.  
  2101.  
  2102. newliberty
  2103. [10:23 AM]
  2104. What would give me pleasure would be if all of blockstream and its backers came forward and confessed all, and asked for forgiveness, showed true repentance for their lies, equivocation, poor stewardship and wickedness, their malicious narcissistic selfish greed, and all the rest of their wrongdoings.
  2105. Then took vows of both silence and poverty, where they restrict themselves to only writing code.
  2106. That would make me happy.
  2107.  
  2108.  
  2109. tomothy [10:27 AM]
  2110. So signal segwit. Then rollback to non signalling. Segwit chain is now isolated. Do I get it?
  2111.  
  2112. movrcx [10:34 AM]
  2113. Yes and there's going to be a panic once nodes start signalling they are about to ditch SegWit
  2114.  
  2115. newliberty
  2116. [10:34 AM]
  2117. What would be the effect of setting the BIP148 version bit, but running other code, lets call it cuckoo mining to keep them straight.
  2118. The Segheads would see your blocks as valid because signaling.
  2119. If a true BIP148 block is mined, the cuckoos (and all the non segheads), will not build on it but will orphan it.
  2120. When the clients see a longer chain from a cuckoo than the BIP148 chain, the client will use the longer chain.
  2121.  
  2122. BIP148 clients could use a checkpoint, but it would have to be set dynamicly and deployed fast. I helped the monero guys do something like this a few years back, and ended up with something called MoneroPulse using DNSsec for distribution
  2123.  
  2124. movrcx [10:34 AM]
  2125. SegWit will be a death trap
  2126.  
  2127.  
  2128. klee [10:34 AM]
  2129. So why do they insist?
  2130.  
  2131. [10:34]
  2132. Ignorance?
  2133.  
  2134. movrcx [10:35 AM]
  2135. They think they can pull it off I giess
  2136.  
  2137. newliberty
  2138. [10:35 AM]
  2139. Desire for control
  2140.  
  2141.  
  2142. klee [10:35 AM]
  2143. yes NL but don't they see the death trap?
  2144.  
  2145. [10:35]
  2146. Either we are wrong or they are ignorant or?
  2147.  
  2148. newliberty
  2149. [10:36 AM]
  2150. They can enslave Bitcoin. They do not care if it survives, they just want it to serve ThEM.
  2151.  
  2152. klee [10:36 AM]
  2153. I mean that their manoeuvre will not succeed
  2154.  
  2155. [10:36]
  2156. ok they don't care
  2157.  
  2158. [10:36]
  2159. Still does not make sense to me, why someone wants to get defeated?
  2160.  
  2161. newliberty
  2162. [10:37 AM]
  2163. There is a small group deep in the echochamber that are true believers that it will work.
  2164.  
  2165. [10:38]
  2166. Maybe it would have if it were not for us, who knows?
  2167.  
  2168.  
  2169. [10:38]
  2170. I know that I was pretty much at the point of thinking that it was going to happen no matter what I did.
  2171.  
  2172. movrcx [10:39 AM]
  2173. It's not going to happen I think
  2174.  
  2175. [10:39]
  2176. They are all freaking out right now
  2177.  
  2178. [10:39]
  2179. I see most of the Core devs next week in NY too
  2180.  
  2181. newliberty
  2182. [10:39 AM]
  2183. Give them my regards :slightly_smiling_face:
  2184.  
  2185.  
  2186. movrcx [10:39 AM]
  2187. Will do :slightly_smiling_face:
  2188.  
  2189. klee [10:40 AM]
  2190. Don't forget to have with you the exorcist toolkit
  2191.  
  2192.  
  2193. [10:40]
  2194. and maybe a veteran priest
  2195.  
  2196. movrcx [10:43 AM]
  2197. It's going to be a crazy meetup I think (BitDevs in NYC) but I've got some non-Core allies in the space and they'd probably be willing to voice support the effort.
  2198.  
  2199. [10:43]
  2200. Peter Todd and I go way back; he was involved with the false rape allegations for Jacob Appelbaum (edited)
  2201.  
  2202. newliberty
  2203. [10:44 AM]
  2204. The media is a horrible place for a trial.
  2205.  
  2206. [10:47]
  2207. I've had some good interactions with PT, and also some horrible ones.
  2208. I think he means well and might be one of the savable ones. A good adversarial thinker who knows the inside guts of what we're up against would be the perfect convert. I wish you good luck.
  2209.  
  2210. [10:47]
  2211. He is also severed from Blockstream, or at least that is what I heard from his own mouth at Consensus.
  2212.  
  2213. klee [10:48 AM]
  2214. https://salt-pro.com/wp-content/uploads/2017/01/may_the_force_be_with_you___yoda_flag_by_osflag-d9xe904.jpg (62kB)
  2215.  
  2216. newliberty
  2217. [10:48 AM]
  2218. Sometimes is it good to employ a warrior just so they are not fighting against you.
  2219.  
  2220. movrcx [10:49 AM]
  2221. Good point :slightly_smiling_face:
  2222.  
  2223. newliberty
  2224. [10:52 AM]
  2225. Just the fact that he is no longer taking blockstream money means he has some integrity.
  2226.  
  2227. [10:52]
  2228. When next week is the meet?
  2229.  
  2230. movrcx [10:53 AM]
  2231. It's Tuesday or Wednesday iirc
  2232.  
  2233. cypherblock [11:53 AM]
  2234. can someone give me the tl;dr on this bip 200 thing. Seems like there are details missing.
  2235.  
  2236. tomothy [11:55 AM]
  2237. It's a. Outline from my understanding
  2238.  
  2239. movrcx [11:57 AM]
  2240. @cypherblock I can answer any questions you have (I wrote it up). Basically the strategy is to avoid doing a chainsplit until it's time to depart from the crashing and burning UASF/SegWit chain.
  2241.  
  2242. [11:58]
  2243. Miners will just revert at a time developed in consensus to a pre-SegWit block height
  2244.  
  2245. [11:59]
  2246. It'll be as if SegWit never happened at all and prevents any type of replay attacks from happening
  2247.  
  2248. [12:02]
  2249. Softfork reversion signalling can cause a great bit of unease. Think about what will happen when the first block signals they are going to revert to a non-segwit block height. then think what happens when 10 more do. and then when it's 30% of blocks and so on.
  2250.  
  2251. cypherblock [12:02 PM]
  2252. hmm. but miners will be giving up revenue to do this, yes? And it allows double spending doesn’t it?
  2253.  
  2254. movrcx [12:03 PM]
  2255. The UASF chain will be wrecked and businesses that operate on it will be too
  2256.  
  2257. [12:03]
  2258. Miners will probably make a killing in this by all the double spends
  2259.  
  2260. cypherblock [12:03 PM]
  2261. I think UASF chain will likely fail on its own. Unless miners cave in.
  2262.  
  2263. movrcx [12:04 PM]
  2264. Idk...they have significant financial backing
  2265.  
  2266.  
  2267. [12:04]
  2268. After SegWit activates the banks will come much more visibly out of the woodwork
  2269.  
  2270. cypherblock [12:06 PM]
  2271. well I thought UASF seemed reckless. Bip 200 seems like insane. But maybe you are trying to do the brinksmanship thing?
  2272.  
  2273. movrcx [12:06 PM]
  2274. Yeah I'm trying to do the doomsday scenario lol
  2275.  
  2276. cypherblock [12:07 PM]
  2277. well if bip200 leaves bitcoin users and businesses and bitcoin in general in financial ruin, then it is unlikely to gain wide adoption. UASF needs large miner % to work in any feasible way.
  2278.  
  2279. movrcx [12:08 PM]
  2280. What does the business landscape look like for BU/Core? Are there direct ways to organize a temporary shutdown?
  2281.  
  2282. [12:09]
  2283. Like stopping trading activity
  2284.  
  2285. [12:09]
  2286. I mean if the miners support it then the businesses and users will have to recognize it as well
  2287.  
  2288. [12:09]
  2289. It's not up to the businesses to decide how the blocks are mined and if BIP200 is implemented...this is the heart of the debate lol
  2290.  
  2291. cryptorebel [12:10 PM]
  2292. this part of bip200 seems to make sense: "Miners who oppose BIP148 and Segregated Witness should falsely signal concurrence for Segregated Witness activation. As described within the the BIP148 (UASF) specification, miners who do not signal BIP148 are automatically segregated from the global network. False signaling prevents non-consensual forceable isolation and subsequent removal from the global Bitcoin network. Therefore those who conscientously reject BIP148 should falsely signal and refuse to be forceably subject to network isolation. "
  2293.  
  2294. [12:11]
  2295. the part that worries me is miners going back to a pre seg-wit block height, how does that work?
  2296.  
  2297. cypherblock [12:12 PM]
  2298. none of it makes sense to me. better bip would be just to reject all segwit signalling blocks on aug 1. Clean split.
  2299.  
  2300. movrcx [12:12 PM]
  2301. I was thinking of a system where BIP200 miners start signaling with their coinbase after SegWit activates. "STATUS - WAITING" or something similar would be broadcasted after SegWit activation.
  2302.  
  2303. [12:13]
  2304. The miners can broadcast unix times to switch to the pre-segwit height after enough "STATUS - WAITING" blocks are signaled.
  2305.  
  2306. [12:13]
  2307. The signaling alone will cause a great amount of chaos.
  2308.  
  2309. [12:14]
  2310. I think this strategy could be possible with maybe 20% mining support and 3-8% of coins.
  2311.  
  2312. cryptorebel [12:14 PM]
  2313. but will miners want to give up mining rewards to revert back to the old block height??
  2314.  
  2315. cypherblock [12:14 PM]
  2316. everyone has gone insane.
  2317.  
  2318. tomothy [12:15 PM]
  2319. It's war
  2320.  
  2321. [12:15]
  2322. Half measures have been shown to fail
  2323.  
  2324. [12:15]
  2325. There is no room for compromise
  2326.  
  2327. [12:15]
  2328. Death or glory
  2329.  
  2330. cypherblock [12:15 PM]
  2331. no, war theme is pyscological manipulation. Buy into and you play their game.
  2332.  
  2333. tomothy [12:15 PM]
  2334. Bitcoin or segshit coin
  2335.  
  2336. cryptorebel [12:15 PM]
  2337. I think we should take precautions somehow against this BIP 148, not sure what those precuations would be, we need to start war gaming it
  2338.  
  2339. tomothy [12:16 PM]
  2340. Hard fork pre 8/1
  2341.  
  2342.  
  2343. [12:16]
  2344. Or attempt to destroy Uasf chain
  2345.  
  2346. cryptorebel [12:16 PM]
  2347. yeah that is one avenue, plan a possible reaction to the split, by hardforking to bigger size blocks
  2348.  
  2349. tomothy [12:16 PM]
  2350. Not sure what alternatives exist
  2351.  
  2352. movrcx [12:17 PM]
  2353. the third option is to negotiate too @tomothy :slightly_smiling_face:
  2354.  
  2355. tomothy [12:17 PM]
  2356. No
  2357.  
  2358. [12:17]
  2359. We've all seen negotiation is fruitless
  2360.  
  2361. cypherblock [12:17 PM]
  2362. Reject all segwit signaling blocks on or just before Aug 1. If segwit has no chance of activating normally (95%) then any miner who was previously signaling needs to be told it is over now instead of at normal experation date.
  2363.  
  2364. tomothy [12:17 PM]
  2365. We've been negotiating since 2013
  2366.  
  2367. movrcx [12:17 PM]
  2368. Then let's crush them....
  2369.  
  2370. [12:17]
  2371. SegWit can be their death trap.
  2372.  
  2373.  
  2374. tomothy [12:18 PM]
  2375. Core has one goal only, blocks never larger than 1mb. They need and want cripple coin.
  2376.  
  2377. [12:18]
  2378. And when I say core I also mean blockstream
  2379.  
  2380. [12:18]
  2381. It's certainly kicked the hornets nest
  2382.  
  2383. [12:18]
  2384. Adam has been in damage control mode the last day
  2385.  
  2386. cryptorebel [12:19 PM]
  2387. its sad seeing all these brainwashed segwit souls, watching all these idiots with UASF tagged on their twitter, and their stupid hats, what is this world coming to
  2388.  
  2389. [12:20]
  2390. pretty sure its never going to work, seems like suicide to me
  2391.  
  2392. movrcx [12:20 PM]
  2393. Idk... i think they have a good chance of success
  2394.  
  2395.  
  2396. [12:21]
  2397. It's normal for community resources to be privatized and lots of times it's usually very succesful (edited)
  2398.  
  2399. tomothy [12:21 PM]
  2400. It has a lot of financial backing
  2401.  
  2402. [12:21]
  2403. And miners are scared imho
  2404.  
  2405. [12:22]
  2406. Well not scared but don't know what to do
  2407.  
  2408. [12:22]
  2409. To a lay person. Bitcoins gone insane
  2410.  
  2411. [12:22]
  2412. They just want safe money and profits
  2413.  
  2414. cryptorebel [12:22 PM]
  2415. i think they will succeed in making a minority chain, which is really stupid how they censor and ban everyone that wanted a blocksize increase hard fork out of fears of a chain split, and now they completely support UASF which will undoubtedly result in chain split, the hypocrisy is off the charts
  2416.  
  2417. [12:23]
  2418. they will have to change the POW
  2419.  
  2420. [12:24]
  2421. so BIP200 will have miners revert back to pre-segwit block height? Wouldn't it be better to keep the segwit blocks, and then all their inputs become "anyonecanspend" on the real chain and segwit users lose money?
  2422.  
  2423. movrcx [12:25 PM]
  2424. @cryptorebel There's going to be markets crashing once BIP200 starts getting signalled imo
  2425.  
  2426. [12:25]
  2427. Better to revert to the pre-segwit state
  2428.  
  2429. cypherblock [12:27 PM]
  2430. To prevent UASF chain from ever replacing main chain, a simple soft fork to reject all segwit signalling blocks starting aug 1 might work. This makes a clean chain split. Any thoughts?
  2431.  
  2432. movrcx [12:28 PM]
  2433. A two-chain solution is not ideal imo.
  2434.  
  2435.  
  2436. cryptorebel [12:28 PM]
  2437. That sounds like a good idea maybe, seems a lot of UASF supporters are claiming legacy chain will reorg, not sure if reverting back to pre seg-wit blockheight is same thing as a reorg
  2438.  
  2439. [12:29]
  2440. we have no choice at this point, 2 chain might be best scenario, we get rid of segwit idiots and mining power, and allow big block hash % to grow on real chain until we get bigger blocks
  2441.  
  2442. movrcx [12:29 PM]
  2443. Agreed but I think their strategy is relying on market price to be successful
  2444.  
  2445.  
  2446. [12:30]
  2447. I honestly wouldn't be surprised if they start pumping up after activation then all of the attention goes to them
  2448.  
  2449. cryptorebel [12:30 PM]
  2450. yeah hash power always follows price, but I trust in the market
  2451.  
  2452. movrcx [12:30 PM]
  2453. BIP200 changes the narrative that it was an unwanted consensus change and that we're just trying to revert back to the normal state.
  2454.  
  2455. cryptorebel [12:30 PM]
  2456. yeah of course they will try it, but the market is a powerful force
  2457.  
  2458. movrcx [12:30 PM]
  2459. We'd be the good guys.
  2460. 2 replies Last reply 11 days ago View thread
  2461.  
  2462. cryptorebel [12:31 PM]
  2463. hopefully the market is smart enough to realize that UASF sybil segwit coin is not as secure as a coin protected by POW mining
  2464.  
  2465. movrcx [12:32 PM]
  2466. Judging by their UASF hordes their marketing is effective lol
  2467.  
  2468. cryptorebel [12:32 PM]
  2469. lol yes but we don't know if they are likely sybil hordes
  2470.  
  2471. klee [12:32 PM]
  2472. Ok suppose Jamie Dimon and Goldman Sucks decide to throw billions in UASF chain
  2473.  
  2474. [12:32]
  2475. will the miners find incentive to jump on it?
  2476.  
  2477. cryptorebel [12:32 PM]
  2478. hash power will always follow price
  2479.  
  2480. klee [12:33 PM]
  2481. even if the carrot is poisoned
  2482.  
  2483. [12:33]
  2484. That's the plan
  2485.  
  2486. cryptorebel [12:34 PM]
  2487. probably they wouldn't want to throw billions at it, too risky, plus they are fighting the market they could lose a lot of money
  2488.  
  2489.  
  2490. movrcx [12:35 PM]
  2491. BIP200 will make Bitcoin too unpalatable for awhile :slightly_smiling_face:
  2492.  
  2493. [12:36]
  2494. Like the whole SegWit chain could come crumbling down at any moment.
  2495.  
  2496. [12:36]
  2497. It's best to panic the investors imo
  2498.  
  2499. [12:36]
  2500. The rest will fall into place
  2501.  
  2502. [12:37]
  2503. Everyone is going to hedge if SegWit activates and BIP200 gets signaled
  2504.  
  2505. [12:37]
  2506. Some people might cash out completely
  2507.  
  2508. klee [12:38 PM]
  2509. My opinion is that if we want to have chances we need coordination of 3 very important poles:
  2510. 1) CSW
  2511. 2) Jihan
  2512. 3) Calvin Ayre et al
  2513.  
  2514.  
  2515. [12:38]
  2516. Where are they?
  2517.  
  2518. [12:38]
  2519. (Not the Fermi Paradox)
  2520.  
  2521.  
  2522. cryptorebel [12:41 PM]
  2523. it will come down to miners in the end I guess, but csw did say some stuff happening before Aug 1st so we will have to wait and see what comes to pass in the community
  2524.  
  2525. csw [12:45 PM]
  2526. I am right here
  2527.  
  2528.  
  2529. [12:47]
  2530. Cal is my best friend.
  2531. He is not an investor
  2532. He is heavily invested in BTC
  2533.  
  2534. [12:47]
  2535. He is aligned
  2536.  
  2537.  
  2538. movrcx [12:48 PM]
  2539. Nice to hear. I'm going to see a bunch of the Core devs next week. Would you all be interested in more negotiations with Core or should I frame it as its a plan thats going to be executed? (edited)
  2540. 1 reply 11 days ago View thread
  2541.  
  2542. bitalien
  2543. [12:51 PM]
  2544. I don't think anyone wants to negotiate with Core. They had their chance
  2545.  
  2546.  
  2547. csw [12:56 PM]
  2548. Cal spent more than BS has in total investment on a party once
  2549.  
  2550.  
  2551. movrcx [12:56 PM]
  2552. It might be opportunistic to move to 2mb blocks or whatever proposals you have once segwit gets reverted (edited)
  2553.  
  2554. [12:57]
  2555. Honestly this feels like we're planning a counter-revolution hehe
  2556.  
  2557.  
  2558. csw [12:59 PM]
  2559. Let us say we are taking out the trash
  2560.  
  2561.  
  2562. movrcx [1:00 PM]
  2563. :slightly_smiling_face:
  2564.  
  2565. btcalbin [1:33 PM]
  2566. Everything that jdillon weirdo wanted in the Peter Todd email leaks has come to pass w/ Core!
  2567.  
  2568. tomothy [1:49 PM]
  2569. ? Email leaks?
  2570.  
  2571. checksum0
  2572. [1:51 PM]
  2573. I'm not following either
  2574.  
  2575. Pinned by cryptorebel
  2576. June 3rd at 1:59 PM Pinned by cryptorebel
  2577. [1:54]
  2578. You mean that? http://pastebin.com/4BcycXUu
  2579. Pastebin
  2580. gpg: encrypted with 2048-bit RSA key, ID 0FBEF185, created 2012-04-25 "Pe - Pastebin.com (19kB)
  2581.  
  2582. movrcx [1:57 PM]
  2583. @checksum0 Is that shareable^?
  2584.  
  2585. checksum0
  2586. [1:58 PM]
  2587. This has been leaked a long long long long time ago (edited)
  2588.  
  2589. [1:58]
  2590. So yeah
  2591.  
  2592. movrcx [1:58 PM]
  2593. Ok I just want to weaponize the leak if possible (edited)
  2594.  
  2595. [1:59]
  2596. The Dark Wallet portion really interests me
  2597.  
  2598. [1:59]
  2599. As my Zen project is essentially an extension of that
  2600.  
  2601. checksum0
  2602. [2:01 PM]
  2603. Honestly I never read that leak
  2604.  
  2605. [2:01]
  2606. I was quite disinterested in the bitcoin community during those years and was mining silently without interacting with the community at all
  2607.  
  2608. cypherblock [2:02 PM]
  2609. You can see some explanation from Peter Todd on that stuff here https://bitcointalk.org/index.php?topic=335658.40
  2610. bitcointalk.org
  2611. "John Dillon" We can leak things too you trolling piece of shit
  2612. "John Dillon" We can leak things too you trolling piece of shit
  2613.  
  2614. zbingledack [2:09 PM]
  2615. But if the market does support them the idea is that the hashrate will follow, in which case it _will_ be supported by PoW mining.
  2616. cryptorebel
  2617. hopefully the market is smart enough to realize that UASF sybil segwit coin is not as secure as a coin protected by POW mining
  2618. Posted in #hardforkJune 3rd at 12:31 PM
  2619.  
  2620. zbingledack [2:14 PM]
  2621. Yes, they are taking advantage of the fact that market communication in Bitcoin is still underdeveloped. That is, miners don't have an easy way to ascertain the will of the market. Thus astroturfing can (potentially) fool them.
  2622.  
  2623. We then have two choices:
  2624.  
  2625. 1) Also play the astroturfing game and try to out-astroturf them (hard when they have Theymos on their side).
  2626.  
  2627. 2) Improve market communication, through things like chain futures token trading (which I think will happen anyway and should lead to a full market referendum in advance of the fork date - a win for everyone who wants a higher BTC price because it will allow the market to speak and the miners to have a clear signal as to what blocks to vote in to obtain the most profit).
  2628. cryptorebel
  2629. lol yes but we don't know if they are likely sybil hordes
  2630. Posted in #hardforkJune 3rd at 12:32 PM
  2631. (edited)
  2632. 2 replies Last reply 11 days ago View thread
  2633.  
  2634. cryptorebel [2:17 PM]
  2635. yeah its a scary proposition if the market and miners would choose UASF, I think maybe there is small chance that could happen in the short term due to market manipulations and ignorance in the market. But in the long term if there are two chains, I think the segwit chain will lose because it will have security vulnerabilities and centralization vulnerabilities that will be exposed over time, resulting in the market supporting and favoring the non-segwit chain instead
  2636.  
  2637. [2:19]
  2638. I like the futures market idea, too bad we don't have a true decentralized exchange though, then we would get a truer depiction of the market, because many will be wary of putting their funds on these exchanges
  2639.  
  2640. zbingledack [2:23 PM]
  2641. Well if we steelman* the UASF campaign, it can be seen as an attempt to put Segwit to a market referendum - a good thing, I think. Miners have the final vote, but they are incentized to please the market. So if you want to make a change in Bitcoin you can either try to get the miners to go along directly, or try to get the investors to make a definitive statement that the miners will want to follow. UASF tries to do this in the chaos _after_ the split, but in just credibly scheduling the UASF they create a futures trading opportunity that may well provide a strong, credible market signal to miners _in advance of the event._
  2642.  
  2643. *that is, try to interpret what they were trying to do and then see how one would achieve that in a non-idiotic way (edited)
  2644.  
  2645. cryptorebel [2:25 PM]
  2646. yeah interesting, I guess this is why even a lot of non-segwit supporters are looking forward to the UASF date, because they have trust in the market
  2647.  
  2648.  
  2649. zbingledack [2:26 PM]
  2650. I do think exchanges like Bitmex are reputable and reliable enough that we could easily see deep and liquid enough trading in these chain IOUs to provide a good market answer. Not everyone has to trade; if there is a big discrepancy it opens a great arbitrage opportunity, so it is kind of self-healing as a prediction market, even if centralized.
  2651.  
  2652. [2:28]
  2653. And to be fair, *if* the market is on their side, and they can convince the miners of that very quickly (preferably in advance), the miners will just vote in Segwit without all the hubbub.
  2654.  
  2655. [2:28]
  2656. I suspect the market is not on their side though
  2657.  
  2658.  
  2659. [2:29]
  2660. They are in a bubble chamber over in /r/Bitcoin
  2661.  
  2662. [2:29]
  2663. I posted this to the BU slack, recapping these ideas:
  2664.  
  2665. I think I understand the UASF logic now, or at least what the smarter ones are trying to do. It's the user counterpart of the "miners schedule a fork, futures markets trade it, miners decide whether to go through with it" plan. Instead, someone (users, devs, whoever) proposes a fork and then we trade futures (or maybe trade chains after the fork), then miners follow. Futures would be better as miners would follow early so no uncertainty.
  2666.  
  2667. In other words, the UASF people may very dimly grasp the issue of market communication here. They may fuzzily recognize that the miners have no way of really reading the market with certainty, and they think maybe this is the only way to get them to see how much the market yearns for Segwit.
  2668.  
  2669. And in a way, just like the miners have to schedule a _credible_ fork (or else traders won't want to risk trading it, thinking the miners may just back out beforehand), the "users" also have to make a credible "threat" to fork away. A threat to commit suicide? Well, not if the market really is on their side. The thing they may not see, or only some may see, is that futures trading is necessary to ensure the best chance of this actually resulting in a sound market referendum on Segwit.
  2670.  
  2671. This market referendum is something we should all want. If Segwit is decisively struck down in futures trading, it will be dead in the water.
  2672.  
  2673. But why stop there? Miners supporting big blocks and not crazy about Segwit should use this great timing to schedule a hard fork to bigger blocks (using BU or otherwise). That way the futures markets can cover all three outcomes and we can trade. Investors will be in control, with the miners for the first time having credible market information on which they can base their decisions.
  2674.  
  2675.  
  2676. zbingledack [2:49 PM]
  2677. >Baker McKenzie, founded as Baker & McKenzie in 1949, is a multinational law firm. As of August 2016, it is ranked as the second-largest international law firm in the world by headcount with 13,000 employees including 6,045 fee earners and 4,600 lawyers on a full-time equivalent basis in 77 offices across 47 countries. It is also ranked as the second largest law firm in the world in terms of revenue with US$2.62 billion in annual revenue in FY2016.
  2678.  
  2679. [2:49]
  2680. Hmmmm...
  2681.  
  2682. csw [4:02 PM]
  2683. UASF - user activated suicidal fuckup
  2684.  
  2685.  
  2686. btcalbin [6:28 PM]
  2687. UASF is bringing us such wonder, for example Tone Vays's twitter photo where he's indistinguishable from a future high school shooter!
  2688.  
  2689. bitalien
  2690. [6:41 PM]
  2691. That was some cringey shit
  2692.  
  2693. btcalbin [6:41 PM]
  2694. They better keep that Obamacare, because I need coverage for these pre-existing douchechills
  2695.  
  2696.  
  2697. btcalbin [6:48 PM]
  2698. does anybody know how to find that crazy meme photo with the dorky looking guy holding like cash with ridiculous karate weapons hanging behind him on the wall?
  2699.  
  2700. [6:49]
  2701. i like to think i'm not hallucinating such a thing existing, but for the life of me can't figure out how to search it
  2702.  
  2703. [6:49]
  2704. b/c that photo is screaming to have Tone shopped in!
  2705.  
  2706. bitalien
  2707. [6:53 PM]
  2708. I have no idea what meme that is
  2709.  
  2710. anarch33 [7:06 PM]
  2711. joined hardfork by invitation from @hmr
  2712.  
  2713. satoshi [9:41 PM]
  2714. This guy @btcalbin ?
  2715.  
  2716. satoshi [9:41 PM]
  2717. uploaded this image: B15-1.jpg
  2718. 1 Comment
  2719.  
  2720. ger [9:50 PM]
  2721. https://youtu.be/mitn_bT7GUk
  2722. YouTube Cyborg Rouslan
  2723. Homer Simpson Screams - HD Video version
  2724.  
  2725.  
  2726.  
  2727. checksum0
  2728. [9:54 PM]
  2729. Guys, I was eating for fuck sake
  2730.  
  2731.  
  2732. [9:54]
  2733. not cool
  2734.  
  2735. movrcx [9:56 PM]
  2736. We should really avoid futures markets I think.
  2737.  
  2738.  
  2739. movrcx [10:03 PM]
  2740. Futures don't happen on the network
  2741.  
  2742. [10:04]
  2743. There shouldn't be a chainsplit for them to trade until after everything is done.
  2744.  
  2745. [10:05]
  2746. They can trade the worthless chain against the miner supported one. (edited)
  2747.  
  2748. [10:05]
  2749. But I don't see a point why they would.
  2750.  
  2751. movrcx [10:48 PM]
  2752. A chainsplit should be 100% avoided unless it's on terms that are agreeable with locally.
  2753.  
  2754. newliberty
  2755. [11:25 PM]
  2756. uploaded and commented on this image: 9-layer-osi-shirt.png
  2757. 1 Comment
  2758. Futures may:
  2759. - hedge risks
  2760. - provide information
  2761. - for the bold, a method for requisitioning discount coin.
  2762.  
  2763. Without them, involvement takes more commitment.
  2764. Perhaps we are fully committed, and others are not, and this changes over time.
  2765. So on the question of 'should', one might ask which path engenders greater commitment, and at the right times.
  2766. Some blocks may be more important than others when the protocol is operating both at the Monetary Layer as well as the Political Layer. :wink:
  2767.  
  2768.  
  2769. ----- June 4th -----
  2770. btcalbin [12:48 AM]
  2771. commented on satoshi’s file B15-1.jpg
  2772. Sadly no, but bravo nonetheless!
  2773.  
  2774. newliberty
  2775. [1:01 AM]
  2776. Committed hashpower operates at the political layer with SegWit. SegWit upsets the balance of powers between Hash, Code, and the Fast Money.
  2777.  
  2778. Hashpower is slow money, requiring long term investment in a geography. This makes is a matter of local politics as well as protocol politics. Ultimately, these are the only soldiers on the battlefield.
  2779.  
  2780. Some soldiers can be swayed by fast money or perceived risk. It is prisoner dilemma, except miners can communicate and coordinate on consensus time and decision, so there is no dilemma.
  2781. That's the virtue of Nakamoto Consensus PoW. (edited)
  2782.  
  2783. zbingledack [5:38 AM]
  2784. Futures can be the best way to avoid a chain split. It can show the real support for something is not what people thought.
  2785.  
  2786. movrcx [6:31 AM]
  2787. time for me to start signaling UASF BIP200 :slightly_smiling_face:
  2788.  
  2789.  
  2790. [6:33]
  2791. With IPv6 I don't think it should be an issue getting a large amount of nodes to signal
  2792.  
  2793. movrcx [7:33 AM]
  2794. https://github.com/joshuayabut/bip200-seeder
  2795. GitHub
  2796. joshuayabut/bip200-seeder
  2797. bip200-seeder - Damnatio memoriae is the Latin phrase literally meaning "condemnation of memory," meaning that a person must not be remembered. It was a form of dishonor that could be pas...
  2798.  
  2799.  
  2800. movrcx [7:39 AM]
  2801. My gameplan is to throw a bunch of these seeders on some Tor boxes to prevent them from getting DDoS'd (edited)
  2802.  
  2803. [7:40]
  2804. I can assign multiple interfaces over the Tor network and run a ton of these seeders on the same box they are pretty light weight (edited)
  2805.  
  2806. movrcx [7:50 AM]
  2807. First clearnet node is up :slightly_smiling_face: hehehehe
  2808.  
  2809. [7:54]
  2810. As long as they include tor nodes in the metrics (which they should) then I could probably get a majority signaling BIP200 as a UASF quickly (edited)
  2811.  
  2812. [7:55]
  2813. So if they want to use that voting majority bullshit as establishing authority across the network then that argument will become invalid.
  2814.  
  2815.  
  2816. hmr [8:03 AM]
  2817. I like it!
  2818.  
  2819. movrcx [8:04 AM]
  2820. Expect 1000 nodes UASF BIP200 signaling within 24 hours :slightly_smiling_face: (edited)
  2821.  
  2822. hmr [8:04 AM]
  2823. Im swamped but hope to find time to help.
  2824.  
  2825. movrcx [8:04 AM]
  2826. I got this fam :smile:
  2827.  
  2828.  
  2829. cypherblock [9:30 AM]
  2830. @movrcx running a ton of fake nodes is not going to do anything. BIP 200 is crazy and no miner will run that code, no regular person will run it either. The code does not exist yet. Sorry I just don’t see any logic in this. Feel free to convince me otherwise.
  2831.  
  2832. movrcx [9:30 AM]
  2833. It doesn't matter what you think I'm rolling with it anyway
  2834.  
  2835.  
  2836. cypherblock [9:30 AM]
  2837. Do you want bitcoin to succeed or fail?
  2838.  
  2839. [9:30]
  2840. real question
  2841.  
  2842. movrcx [9:30 AM]
  2843. I want Bitcoin Core out of the picture.
  2844.  
  2845.  
  2846. cypherblock [9:31 AM]
  2847. that is not an answer
  2848.  
  2849. [9:31]
  2850. you have competiting interests, your own coin or something?
  2851.  
  2852. movrcx [9:31 AM]
  2853. I do as I mentioned earlier but that's not a priority
  2854.  
  2855. cypherblock [9:32 AM]
  2856. lol. You are trying to further split the community and cause mahem it looks like to me.
  2857.  
  2858. movrcx [9:32 AM]
  2859. I think after all the chaos happens BIP200 will be seen as the reasonable alternative.
  2860.  
  2861. [9:32]
  2862. Honestly Core has you guys outgunned in every single way.
  2863.  
  2864.  
  2865. [9:33]
  2866. I can write the miners and I've executed a chain reversion before.
  2867.  
  2868. [9:33]
  2869. It went fine.
  2870.  
  2871. cypherblock [9:34 AM]
  2872. will your 1000 fake nodes signaling UASF-BIP 200 get counted as UASF nodes in their node trackers? If so it will just make them think they have a lot of support. This will have opposite effect that you want.
  2873.  
  2874. movrcx [9:34 AM]
  2875. https://bitnodes.21.co/nodes/?q=uasf (edited)
  2876.  
  2877. [9:34]
  2878. Yes it should be easily detectable.
  2879.  
  2880. [9:35]
  2881. Their trackers break down the statistics further too.
  2882.  
  2883. [9:36]
  2884. What I want out of taking Core out is a reasonable relationship with BU.
  2885.  
  2886. cypherblock [9:36 AM]
  2887. ok, whatever you are in your own world. enjoy your attacks on the bitcoin network.
  2888.  
  2889.  
  2890. movrcx [9:37 AM]
  2891. I'm the only one who can end the stalemate in here.
  2892.  
  2893. cypherblock [9:37 AM]
  2894. no there are better solutions.
  2895.  
  2896. [9:38]
  2897. you will fail to write the code for bip200, and if you succeed to write it you will fail to get more than a handful of people to run it. none of them will be mining pools. Sorry this is just how it is.
  2898.  
  2899. movrcx [9:39 AM]
  2900. Then I'll buy the mining contracts out.
  2901.  
  2902. [9:39]
  2903. Ill signal BIP200 and short the market.
  2904.  
  2905. cypherblock [9:39 AM]
  2906. I think you are just trolling everyone really.
  2907.  
  2908. movrcx [9:39 AM]
  2909. What about the plan won't work?
  2910.  
  2911. [9:39]
  2912. How much BTC will it take to mine a BIP200 Signaling block?
  2913.  
  2914. [9:39]
  2915. It's all within reach
  2916.  
  2917. cypherblock [9:40 AM]
  2918. as I said. no one will be running your code.
  2919.  
  2920. [9:40]
  2921. you also did not even explain your signaling / reversion mechanism in the BIP
  2922.  
  2923. movrcx [9:40 AM]
  2924. It's still in proposal and it's not relevant to the strategy.
  2925.  
  2926. [9:40]
  2927. Have you read the latest revisions?
  2928.  
  2929. [9:41]
  2930. If you all chainsplit prior to UASF why does it even matter?
  2931.  
  2932. [9:41]
  2933. It's not your fight then so don't complain.
  2934.  
  2935. movrcx [9:48 AM]
  2936. What if I artificially reduce the difficulty for a period of blocks after the fork reversion? I bet miners would swarm on it.
  2937.  
  2938. [9:49]
  2939. If you all don't want to support it then that's fine. That doesn't mean it's not going to be successful. (edited)
  2940.  
  2941. tomothy [9:57 AM]
  2942. I think it makes sense to have it as alternative
  2943.  
  2944.  
  2945. [9:58]
  2946. You have no idea if core has anything hiding behind their back
  2947.  
  2948. movrcx [9:58 AM]
  2949. BIP200 is the final line after the earler chainsplits happen
  2950.  
  2951. [9:58]
  2952. It gives a backdoor into Core's UASF chain
  2953.  
  2954. tomothy [9:58 AM]
  2955. The recent update and iteration of the new scaling war is premised on who does the craziest crap they can think of or argue.
  2956.  
  2957. movrcx [9:58 AM]
  2958. You might succeed with other plans but that doesn't mean BIP200 can't be executed
  2959.  
  2960. [9:59]
  2961. Agreed
  2962.  
  2963. tomothy [9:59 AM]
  2964. Maybe their idea will fizzle out but I doubt it. They don't care if they break bitcoin as long as they get sevwit
  2965.  
  2966. [10:00]
  2967. You can't negotiate from a position of weakness. Core hasn't changed their offer in three years.
  2968.  
  2969. [10:00]
  2970. 8 mb, 6mb, 4mb, 2mb? There is no counter. It's only segwit.
  2971.  
  2972. [10:00]
  2973. At some point you have to question intent
  2974.  
  2975. newliberty
  2976. [10:04 AM]
  2977. UASF is this pathetic great white shark trying to eat an empty net?
  2978. https://twitter.com/BuzzFeedOzNews/status/865152505268674560
  2979. BuzzFeedOz News @BuzzFeedOzNews
  2980. This Guy Told A Shark To "Fuck Off" And It's Australian AF
  2981. TwitterMay 18th at 6:30 AM
  2982.  
  2983.  
  2984.  
  2985. satoshi [10:05 AM]
  2986. It doesn't get more Australian than that. Crazy bastards.
  2987.  
  2988. hmr [10:21 AM]
  2989. Keep those fuckers scrambling. All the things! Against them.
  2990.  
  2991.  
  2992. movrcx [10:21 AM]
  2993. I like the phrase collective action :slightly_smiling_face:
  2994.  
  2995.  
  2996. movrcx [10:33 AM]
  2997. I think to make BIP200 more palatable to miners (if zero support is recieved at all) someone could drop a new genesis block in on the tip at diff 0 and rework the pow adjusting algorithm to be per block. Altcoiners would definitely pick up mining the chain imo.
  2998.  
  2999. [10:33]
  3000. Best solution is to not adjust the diff imo though
  3001.  
  3002. movrcx [12:15 PM]
  3003. Do you all have a room to organize with the different Bitcoin factions?
  3004.  
  3005. tomothy [12:16 PM]
  3006. Maybe in private or in bu slack. Maybe Ping Peter r and Tom Zander. Not sure if he's still here though. Joel might know
  3007.  
  3008. hmr [12:34 PM]
  3009. Zander left. He is available in the bitcoin classic slack. Dgenr8 is here(xt). Many BU members here. Word can get to viabtc and bitmain most likely. @davids works for roger ver...
  3010.  
  3011. movrcx [12:35 PM]
  3012. Ok well I think we should eventually open discussions and look at our options
  3013.  
  3014. [12:35]
  3015. Just get organized and stuff if we want to survive
  3016.  
  3017. hmr [12:36 PM]
  3018. Even if we cant get everyone on board for bip200, I think there would be benefit to encouraging falsely signalling for segwit... what do you think?
  3019.  
  3020. [12:38]
  3021. This slack is set up such that anyone can make a private channel, this channel seems like a good place for it though...
  3022.  
  3023. [12:38]
  3024. Bbl
  3025.  
  3026. movrcx [12:40 PM]
  3027. Agreed. I think BIP200 should be the final defensive line of all of your other tactics fail. You can always execute it no matter what... (edited)
  3028.  
  3029. [12:40]
  3030. It doesn't become overt until SegWit activates.
  3031.  
  3032. [12:41]
  3033. And when that happens a prisoner's dilemma starts and someone is going to short the market first.
  3034.  
  3035. tula [12:41 PM]
  3036. false signaling segwit seems like a very bad idea at this moment
  3037.  
  3038.  
  3039. movrcx [12:42 PM]
  3040. Pools could explicitly say they are running BIP200 and if they want to be more overt they can go into a `BIP200 - WAITING` status right away before segwit is activated
  3041.  
  3042. [12:43]
  3043. BIP200 supercedes BIP148 and makes all nodes signal for SegWit anyway so it's not necessarily really false. It prohibits Core from ethically enforcing voting based decisions.
  3044.  
  3045. joeldalais [1:00 PM]
  3046. zander left this slack, but is available in BU slack. It's getting miners together that i've found trickier. We can get word out to most the BU/bigger blocks (pool) operators (can we get word to wang chung/f2pool?).. but there's still work to be done there
  3047.  
  3048. [1:01]
  3049. i haven't bothered trying to reach out to the 'hardcore' segwit pools/miners
  3050.  
  3051. [1:02]
  3052. BTCC & Btc.top would be good to build a bridge to (and f2pool) (edited)
  3053.  
  3054. tomothy [1:04 PM]
  3055. Bw as well I think?
  3056.  
  3057. [1:04]
  3058. The undecided pools
  3059.  
  3060. joeldalais [1:04 PM]
  3061. all of the undecided would be nice
  3062.  
  3063. [1:05]
  3064. but if we can get btcc, f2pool and bixin on the same page (bigger blocks) .. then we know whats needed to get that majority hash
  3065.  
  3066. [1:06]
  3067. or we wait for uasf, i'm confident pools will focus on bigger blocks once blockstream uasf's away and basically tells the pools to f'off
  3068.  
  3069. [1:07]
  3070. getting a majority on the same page/bigger blocks before august 1st would be nice, but i don't see it as a 'huge' priority, as they will more than likely come together after the uasf clusterfuck and realise blockstream 'devs' shouldn't be listened to on this matter
  3071.  
  3072. [1:08]
  3073. getting them thinking about it, and most importantly - prepared - to go bigger blocks (without core support, etc) and feeling comfortable about it, that's important (before 1st august)
  3074.  
  3075.  
  3076. movrcx [1:50 PM]
  3077. https://cointimes.tech/2017/06/bip200-a-counter-attack-against-uasf-148-independence-day/
  3078. cointimes.tech
  3079. bip200 a counter-attack against UASF 148 (independence day)? (232kB)
  3080.  
  3081.  
  3082. [1:50]
  3083. Oh it's just a copy/paste of the mediawiki
  3084.  
  3085. movrcx [2:32 PM]
  3086. maxwell responded to it on reddit though in his usual core shilling tone
  3087.  
  3088. tomothy [2:33 PM]
  3089. I wouldn't expect anything else. I'm looking forward to him getting to eat a shoe.
  3090.  
  3091. [2:33]
  3092. Regardless of the outcome of bip200, larger blocks sans segwit, and the look on his face... :mrburn:
  3093.  
  3094. movrcx [2:34 PM]
  3095. We're gonna jack them up boys! :smile:
  3096.  
  3097.  
  3098. tomothy [2:34 PM]
  3099. The tone vay interview was great.
  3100.  
  3101. movrcx [2:34 PM]
  3102. I didn't see that, what did happened?
  3103.  
  3104. tomothy [2:34 PM]
  3105. Nobody came to the Blockstream room.
  3106.  
  3107. checksum0
  3108. [2:34 PM]
  3109. Maxwell has a way to big ego for his good
  3110.  
  3111. tomothy [2:34 PM]
  3112. Oh, it's really really Good
  3113.  
  3114. movrcx [2:34 PM]
  3115. Like funny?
  3116.  
  3117. tomothy [2:34 PM]
  3118. Let me try to find the link
  3119.  
  3120. movrcx [2:35 PM]
  3121. I don't want to be subject to SegWit propaganda unless it's required.
  3122.  
  3123. tomothy [2:35 PM]
  3124. Black humor pulp fiction humor...
  3125.  
  3126. movrcx [2:35 PM]
  3127. :slightly_smiling_face:
  3128.  
  3129. checksum0
  3130. [2:36 PM]
  3131. https://youtu.be/wwht2ExwNRE?t=1333
  3132. YouTube World Crypto Network
  3133. The Bitcoin Group #143 - Price Volatility - Suits not Nerds - ICO Mania - Silbert Accords
  3134.  
  3135.  
  3136. movrcx [2:36 PM]
  3137. *click*
  3138.  
  3139. checksum0
  3140. [2:36 PM]
  3141. @tomothy Got it
  3142.  
  3143. tomothy [2:37 PM]
  3144. Thanks. Was still searching for it lol
  3145.  
  3146. checksum0
  3147. [2:37 PM]
  3148. @movrcx Also https://youtu.be/wwht2ExwNRE?t=1553
  3149. YouTube World Crypto Network
  3150. The Bitcoin Group #143 - Price Volatility - Suits not Nerds - ICO Mania - Silbert Accords
  3151.  
  3152.  
  3153.  
  3154. [2:38]
  3155. I remembered the name of the reddit thread
  3156.  
  3157. [2:38]
  3158. So found it quickly
  3159.  
  3160. tomothy [2:38 PM]
  3161. Not sure when but just fast forward to tones discussion on consensus. He was so bitter
  3162.  
  3163. [2:38]
  3164. His highlight was meeting whale panda...
  3165.  
  3166. movrcx [2:38 PM]
  3167. Consensus was garbage
  3168.  
  3169. tomothy [2:39 PM]
  3170. It was like they were universally despised by everyone else
  3171.  
  3172. movrcx [2:39 PM]
  3173. Tone is part of the problem
  3174.  
  3175.  
  3176. tomothy [2:39 PM]
  3177. He kindof has his lightbulb moment in it
  3178.  
  3179. [2:40]
  3180. But then he posted that Jason knife shit
  3181.  
  3182. [2:40]
  3183. So... Yeah...
  3184.  
  3185. checksum0
  3186. [2:41 PM]
  3187. When you get paid in fiat to promote Segwit
  3188.  
  3189. [2:41]
  3190. You never have a real come to jesus moment
  3191.  
  3192. tomothy [2:41 PM]
  3193. Yeah...
  3194.  
  3195. [2:41]
  3196. I might head to the Netherlands conference after all. Gonna touch base w work next week
  3197.  
  3198. newliberty
  3199. [2:42 PM]
  3200. "EOS was the biggest draw, Dan Larimer's scam number three" lol
  3201.  
  3202.  
  3203. tomothy [2:42 PM]
  3204. That line. The bitterness. Lol.
  3205.  
  3206. newliberty
  3207. [2:44 PM]
  3208. He's right about it though, I got a free EOS t-shirt that I wanted to wear. EOS and Blockstream each had private rooms near each other on the 4th floor, so I went into the Blockstream room for privacy to change my shirt. It was empty. (edited)
  3209.  
  3210. movrcx [2:45 PM]
  3211. I think that's just because everybody was so busy launching ICOs tbh
  3212.  
  3213. [2:46]
  3214. Nobody cares about Bitcoin especially at Consensus
  3215.  
  3216. [2:46]
  3217. Just a bunch of marketing and sales noobs trying to feast on their next project
  3218.  
  3219. tomothy [2:46 PM]
  3220. It doesn't hurt that bitcoin development is hamstrung because of blockstream...
  3221.  
  3222. newliberty
  3223. [2:47 PM]
  3224. Consensus sort of has the reputation of "scamcon" anyhow.
  3225.  
  3226. [2:49]
  3227. But walking around through the demonstrations, there were a lot of blockchain projects using the Bitcoin block chain.
  3228.  
  3229.  
  3230. tomothy [2:49 PM]
  3231. Interesting. That certainly wasn't presented to the public or in streams.
  3232.  
  3233. newliberty
  3234. [2:52 PM]
  3235. It was a bit weird for me also. They were not proud of using the Bitcoin blockchain as I would have expected, I always had to ask, and the answer seemed to come with some reluctance.
  3236.  
  3237.  
  3238. [2:56]
  3239. I get that in my company also. Bitcoin is still a bad word for a lot of folks, unless you call it blockchain, there is a good chance that the proposal goes to the circular file.
  3240.  
  3241.  
  3242. tomothy [2:58 PM]
  3243. That makes sense. The bitcoin stigma is relatively strong.
  3244.  
  3245. movrcx [3:04 PM]
  3246. uploaded this image: Capture.PNG
  3247. Add Comment
  3248.  
  3249. movrcx [3:04 PM]
  3250. Original article removed on behalf of Maxwell. Apparently it isn't a BIP.
  3251.  
  3252. [3:04]
  3253. God I can't wait to smash their hubris. They aren't fit to run a decentralized network.
  3254.  
  3255.  
  3256. checksum0
  3257. [3:05 PM]
  3258. So
  3259.  
  3260. [3:05]
  3261. Anybody can request a BIP
  3262.  
  3263. [3:05]
  3264. Anybody can present a BIP
  3265.  
  3266. [3:05]
  3267. Unless you aren't a core cabal
  3268.  
  3269.  
  3270. movrcx [3:05 PM]
  3271. I don't believe I have to request a thing from Bitcoin Core.
  3272.  
  3273.  
  3274. checksum0
  3275. [3:05 PM]
  3276. Then fuck you
  3277.  
  3278. newliberty
  3279. [3:05 PM]
  3280. Yes, it is open to flooding.
  3281.  
  3282. checksum0
  3283. [3:06 PM]
  3284. Maybe we should just reupload his BIP over and over again
  3285.  
  3286.  
  3287. movrcx [3:06 PM]
  3288. lol just let it fester a bit :slightly_smiling_face:
  3289.  
  3290. [3:06]
  3291. we haven't had any media waves yet which should come tomorrow hopefully
  3292.  
  3293. [3:07]
  3294. and then if that doesn't work i'll egg some of them on at bitdevs on tuesday in front of a live audience
  3295.  
  3296.  
  3297. vlad2vlad [3:24 PM]
  3298. Why do you think media coverage is coming tomorrow, 2 months is a ways out
  3299.  
  3300. checksum0
  3301. [3:25 PM]
  3302. Holy shit
  3303.  
  3304. [3:25]
  3305. Vlad's back
  3306.  
  3307. vlad2vlad [3:25 PM]
  3308. Hahaha
  3309.  
  3310. [3:25]
  3311. Been here just didn't feel like writing much
  3312.  
  3313. checksum0
  3314. [3:26 PM]
  3315. lol
  3316.  
  3317. movrcx [3:27 PM]
  3318. hi @vlad2vlad
  3319.  
  3320. [3:28]
  3321. I've done things like this before lol.... There are others outside of the Bitcoin space that are becoming aware of the UASF shenanigans.
  3322.  
  3323. [3:28]
  3324. No new news articles generally get written over the weekend. So Monday would be the first opportunity.
  3325.  
  3326. tomothy [3:29 PM]
  3327. Vlad, neos been looking for you...
  3328.  
  3329. vlad2vlad [3:30 PM]
  3330. I'll PM him. Maybe he's got my 300 BTC. lol
  3331.  
  3332.  
  3333. checksum0
  3334. [3:30 PM]
  3335. I don't think neo will come back
  3336.  
  3337. [3:30]
  3338. Wonder who is going to be the next persona
  3339.  
  3340. [3:31]
  3341. Hopefully he's more like natoshi
  3342.  
  3343. [3:31]
  3344. Scratch that... lobby was muted... he came back
  3345.  
  3346. [3:31]
  3347. :face_with_rolling_eyes:
  3348.  
  3349.  
  3350. vlad2vlad [3:32 PM]
  3351. He's definitely Natoshi
  3352.  
  3353. [3:32]
  3354. Why won't neo come back? Did the Feds get him again. lol
  3355.  
  3356. tomothy [3:33 PM]
  3357. Nah he's still here
  3358.  
  3359. checksum0
  3360. [3:37 PM]
  3361. I thought we finally got rid of them
  3362.  
  3363. [3:37]
  3364. Or Bitsko lost it and banned him
  3365.  
  3366. [3:37]
  3367. I was wrong :anguished:
  3368.  
  3369. tomothy [3:38 PM]
  3370. Nope. :sunglasses:
  3371.  
  3372. vlad2vlad [4:05 PM]
  3373. I know who he is, he was always a hardcore r/BTC guy. Big Blocker. Don't know why he's messing with people here
  3374.  
  3375. tomothy [4:06 PM]
  3376. Oh. Was he always insane or is that a newer development?
  3377.  
  3378. vlad2vlad [4:07 PM]
  3379. Yeah. He was really funny ever since I first met him.
  3380.  
  3381.  
  3382. tomothy [4:07 PM]
  3383. I bought him a pizza. Seriously. Lol.
  3384.  
  3385. hmr [4:15 PM]
  3386. https://www.reddit.com/r/Bitcoin/comments/6f8jnj/bip200_a_counterattack_against_uasf_148/
  3387. reddit
  3388. bip200 a counter-attack against UASF 148 (independence day)? • r/Bitcoin
  3389. reddit: the front page of the internet
  3390.  
  3391. [4:16]
  3392. Personally I only support bips if they ignore bip2 and lukejr
  3393.  
  3394.  
  3395. movrcx [4:16 PM]
  3396. This is the BIP to do them in :slightly_smiling_face:
  3397.  
  3398. hmr [4:16 PM]
  3399. The whole BIP scheme is a political control
  3400.  
  3401. movrcx [4:17 PM]
  3402. agreed it's a scam
  3403.  
  3404.  
  3405. hmr [4:17 PM]
  3406. Too bad moneytrigz is a maxwell bootlicker.
  3407.  
  3408. [4:18]
  3409. Maybe @davids can ask if bitcoin.com wants to report on it.
  3410.  
  3411. movrcx [4:19 PM]
  3412. That could help push it into the media... I have some WL-related folks trying to pursue their channels right now.
  3413.  
  3414. [4:19]
  3415. Bitcoin.com would kick the beehive again though
  3416.  
  3417. davids [4:20 PM]
  3418. @hmr what are you asking? Sorry not following the chat here so don't know what's happening :)
  3419.  
  3420. hmr [4:20 PM]
  3421. Therebis a bip200 ... bip200.com ...
  3422.  
  3423. movrcx [4:21 PM]
  3424. @davids We're trying to coordinate some media coverage for a blacklisted BIP to destroy Bitcoin Core.
  3425.  
  3426. davids [4:21 PM]
  3427. Do you have a write up with the back story?
  3428.  
  3429. [4:21]
  3430. Background info
  3431.  
  3432. movrcx [4:22 PM]
  3433. I just have the BIP but I could probably find a writer...it reads like a manifesto (as any Bitcoin proposal should imo) (edited)
  3434.  
  3435. [4:22]
  3436. I'm just a dev
  3437.  
  3438. davids [4:23 PM]
  3439. That plus I need the back story. You said black listed BIP etc. I'm online for 10 more mins. Can you email me all the details at david@bitcoin.com and I can see what I can do.
  3440.  
  3441. movrcx [4:23 PM]
  3442. Will do!
  3443.  
  3444. davids [4:23 PM]
  3445. Thanks.
  3446.  
  3447. hmr [4:26 PM]
  3448. :dancing_pickle:
  3449.  
  3450. [4:30]
  3451. I want so much rektage... the bip process and core community are the greatest cause of a diaspora in cryptocurrency development. Imagine if there was enough rektage of core that guys like vitalik came back to the project... :awesome:
  3452.  
  3453.  
  3454. newliberty
  3455. [4:47 PM]
  3456. They have already offered their counter-story to this, which is that there is a process to follow... So any that look under-the-fold, (as the old newspaper guys would call it), will want to be informed about the discretionary use of process, with examples and history. If you are going the news route, the details will matter. (edited)
  3457.  
  3458.  
  3459. [4:51]
  3460. Think of it as going to court, the biggest file has advantage. The concern is discovery costs. Be ready for many inquiries.
  3461. Devs often are often isolated from such support cost, but you seem exceptional and probably know all of this already.
  3462.  
  3463.  
  3464. hmr [5:33 PM]
  3465. I dont think hearn asked anyone for a number when he made bip101, and 'process' feathers got ruffled. To my enjoyment. Imo bip 101 was the best scaling bip so far, and the bip2 process explicity disallows reasonable bips, and if Im correct that luke is also the 'editor'... this kangaroo court process deservingly needs to be laid bare for the bullshit it is... just for shits i want to help make a number stick...
  3466.  
  3467. zbingledack [5:40 PM]
  3468. Core pretends to have neutral processes. We can pretend to run Core.
  3469.  
  3470.  
  3471. movrcx [5:41 PM]
  3472. Operate the Bitcoin protocol as if they don't exist :slightly_smiling_face:
  3473.  
  3474. [5:41]
  3475. Take the initiative :slightly_smiling_face:
  3476.  
  3477. [5:42]
  3478. I think BU would get alot more support if it was a bit more vocal and had someone to represent it besides roger
  3479.  
  3480. zbingledack [5:42 PM]
  3481. Miners need to do that. Or we all need to get into mining.
  3482.  
  3483. [5:42]
  3484. Vocal how?
  3485.  
  3486. movrcx [5:42 PM]
  3487. Start organizing outside of the normal echo chambers...try new things
  3488. 1 reply 9 days ago View thread
  3489.  
  3490. cryptorebel [5:43 PM]
  3491. they are trying new things like new BUIP coming up for a hard fork to 8MBs set at a certain block height
  3492.  
  3493. zbingledack [5:43 PM]
  3494. What do you have in mind?
  3495.  
  3496. cryptorebel [5:43 PM]
  3497. good chance that could gain a lot of new mining support
  3498.  
  3499.  
  3500. zbingledack [5:44 PM]
  3501. Mining pools should really be running their own code. Not sure why they look to third-party dev teams. I say that as one of the first BU members.
  3502.  
  3503.  
  3504. movrcx [5:45 PM]
  3505. Core is definitely more resourced than BU but I don't think they'll win in a fight. They lack creativity and are stuck in a commercialized world. Personally I think BU should pursue better working groups with the mining community.
  3506.  
  3507. [5:45]
  3508. Their buy in is really important and it's hard to coordinate things when everyone is in their own bubbles.
  3509.  
  3510.  
  3511. zbingledack [5:46 PM]
  3512. Miners have been met with. They just seem rather indecisive.
  3513.  
  3514. movrcx [5:46 PM]
  3515. Like they don't know who to trust?
  3516.  
  3517. zbingledack [5:46 PM]
  3518. They are happy with the price up, status quo
  3519.  
  3520. cryptorebel [5:47 PM]
  3521. miners probably trust the market, problem is right now its hard for miners to read what the market wants, especially because of all the censorship, and lies, and dirty tricks
  3522.  
  3523.  
  3524. movrcx [5:47 PM]
  3525. So then they'll go with Core I think
  3526.  
  3527. zbingledack [5:48 PM]
  3528. They are very conservative. They don't seem to consider how much higher the price could be now if the blocksize were lifted.
  3529.  
  3530. [5:49]
  3531. But I see them as falsely conservative. Altcoin competition needs to be defended against.
  3532.  
  3533. They mistake complacency for conservatism.
  3534.  
  3535. movrcx [5:50 PM]
  3536. hmm
  3537.  
  3538. zbingledack [5:50 PM]
  3539. They all want bigger blocks though. They are afraid of Core.
  3540.  
  3541. cryptorebel [5:51 PM]
  3542. price would skyrocket if blocksize increased, so miners are incentivized to increase it since they receive the block reward, also they are likely holders and investors of Bitcoin. One counter-argument to this I have heard is that since the difficulty will always increase, miners will always be making marginal profit, so maybe they don't care about the price going up?? Any thoughts on that?
  3543.  
  3544. zbingledack [5:51 PM]
  3545. They will make bank for a while, not pernanently.
  3546.  
  3547. [5:51]
  3548. Still should be good enough.
  3549.  
  3550. movrcx [5:52 PM]
  3551. What do they think about all of the chainsplit talk?
  3552.  
  3553. [5:52]
  3554. That's Core's biggest threat imo
  3555.  
  3556. zbingledack [5:52 PM]
  3557. Some of them see it as a concern.
  3558.  
  3559. [5:53]
  3560. Core has us outgunned, yes. They know the ins and outs because they designed a lot of the ins and outs.
  3561.  
  3562. [5:54]
  3563. The thorniest ones.
  3564.  
  3565. cryptorebel [5:54 PM]
  3566. maybe instead of being incentivized by a bigger reward, miners have to be disincentivized instead by the market threatening a smaller price and reward, so as price and reward crashes, miners see their investments going under and decide to raise blocksize to increase the reward again...so maybe we have to wait for a bear market and down turn in the price before miners will start to support bigger blocks
  3567.  
  3568. zbingledack [5:54 PM]
  3569. And Segwit just brings that to a whole new level
  3570.  
  3571. [5:55]
  3572. Well they have to see the market bidding up future-redeemable big-block coins
  3573.  
  3574. [5:55]
  3575. Fork futures must happen
  3576.  
  3577.  
  3578. [5:56]
  3579. Then the market can speak, even before a fork
  3580.  
  3581. movrcx [6:01 PM]
  3582. A BIP200 heartbeat on the UASF-chain will crash markets and there's going to be a ton capital flight chaos. UASF'ers have no loyalty and are proud to buy alts instead.
  3583.  
  3584. [6:02]
  3585. Ultimately that signaling is up to the miners to determine.
  3586.  
  3587. [6:03]
  3588. But I have a feeling some parties are going to short then start signaling on their own.
  3589.  
  3590. [6:07]
  3591. There is a ton of money to be made in shorting UASF-chain :smile:
  3592.  
  3593. newliberty
  3594. [6:41 PM]
  3595. Do miners need a way to mergemine chain forks, with both attack and defensive tools? (edited)
  3596.  
  3597. [6:42]
  3598. Basic proposition is to de-risk the chain-fork for miners.
  3599.  
  3600.  
  3601. [6:43]
  3602. Going to war, need armor and weapons.
  3603.  
  3604. movrcx [6:43 PM]
  3605. that's a good idea!
  3606.  
  3607. newliberty
  3608. [6:44 PM]
  3609. My understanding was that this is sort of nChain's bailiwick. The arms dealer for miners.
  3610.  
  3611.  
  3612. newliberty
  3613. [6:54 PM]
  3614. The ability for miners to change strategies swiftly at least means low downtime. More responsitivity.
  3615.  
  3616. [6:55]
  3617. Matonis is the strategy guy, so maybe this is something he works on.
  3618.  
  3619. cryptorebel [6:56 PM]
  3620. it seemed matonis was worried about miners having too much power before, didn't he speak out against Bitcoin XT? then he said he is worried they would inflate the 21 million coin limit, I wonder if he changed his stance on that
  3621.  
  3622. newliberty
  3623. [7:01 PM]
  3624. I congratulated him on getting the position because it seemed it would be great fun, the chance to gamify mining from a holistic perspective. Where mining information gathering, strategy options, and decision-making tools, are all displayed with a game-like front end designed to put them in the driver seats. All those equipped with such a setup would be the barrons of the battlefield.
  3625.  
  3626. joeldalais [7:01 PM]
  3627. I think its fair to say that he's changed his mind @cryptorebel
  3628.  
  3629. cryptorebel [7:04 PM]
  3630. what if miners decide to and succeed in increasing the coin limit? possible? Is it still Bitcoin?
  3631.  
  3632. joeldalais [7:05 PM]
  3633. 'gamify mining' .. i might have to steal that :slightly_smiling_face:
  3634.  
  3635. [7:05]
  3636. ye its possible, but it would be economic suicide
  3637.  
  3638. newliberty
  3639. [7:05 PM]
  3640. Matonis was confused about that for a while too.
  3641. I kept pointing him to the difference between
  3642. https://en.bitcoin.it/wiki/Hardfork_Wishlist
  3643. and
  3644.  
  3645. [7:05]
  3646. https://en.bitcoin.it/wiki/Prohibited_changes
  3647.  
  3648. [7:06]
  3649. "These changes are considered to be against the spirit of Bitcoin. Even if all Bitcoin users decide to adopt any of these changes, the resulting cryptocurrency can no longer be considered "Bitcoin" because it has diverged too much from the original design."
  3650.  
  3651.  
  3652. cryptorebel [7:07 PM]
  3653. Is there a possibility the market could want an increase in coin supply in future in order to subsidize mining? Maybe the market won't allow a huge increase, but they might allow small constant reward of like 0.1 btc forever or something
  3654.  
  3655. joeldalais [7:07 PM]
  3656. if mining needs to be subsidized = bitcoin has failed
  3657.  
  3658. newliberty
  3659. [7:07 PM]
  3660. It wouldn't work to subsidize mining. And there are better ways.
  3661.  
  3662. cryptorebel [7:08 PM]
  3663. but if the miners can truly compete in a market, then it becomes a possibility, no?
  3664.  
  3665. newliberty
  3666. [7:08 PM]
  3667. It becomes a possible alt coin. There are many that do this already.
  3668.  
  3669. joeldalais [7:08 PM]
  3670. i helped design an altcoin some years ago, an investment company/bank took it over (i walked away/was forced out), one of the things they introduced after i left (and i said NO repeatedly), was 'subsidized mining'
  3671.  
  3672. [7:09]
  3673. the coin is worthless now
  3674.  
  3675.  
  3676. cryptorebel [7:09 PM]
  3677. if they can vote on other changes, seems they will be able to vote on coin supply, whos gonna stop them, not saying the market will allow it to win, but its possible
  3678.  
  3679. newliberty
  3680. [7:10 PM]
  3681. They do vote, every ten minutes or so.
  3682.  
  3683. cryptorebel [7:10 PM]
  3684. there was a group I heard that wanted to keep the 50 btc reward during the first halving
  3685.  
  3686. [7:10]
  3687. but it did not gain traction
  3688.  
  3689. joeldalais [7:10 PM]
  3690. reason for increasing coin supply = greed/profit. IF miners are greed incentivized then *not* increasing the supply (and causing economic meltdown for their coin) = the more viable option if greed/profit is the motive (edited)
  3691.  
  3692. newliberty
  3693. [7:11 PM]
  3694. Increase is an attempt to steal from the future. It is how currencies collapse.
  3695. Every national fiat currency is designed to collapse in this way.
  3696.  
  3697. cryptorebel [7:11 PM]
  3698. but maybe if they only increase it a little bit they can get away with it
  3699.  
  3700. joeldalais [7:12 PM]
  3701. what he said - "Increase is an attempt to steal from the future." - much better said than I :slightly_smiling_face:
  3702.  
  3703. newliberty
  3704. [7:12 PM]
  3705. Bitcoin is designed to not fail.
  3706.  
  3707. cryptorebel [7:13 PM]
  3708. so if miners do try to increase the supply, would a user activated hard fork be justified, even changing POW to maintain the 21 million chain? (edited)
  3709.  
  3710. [7:13]
  3711. that seems the only check and balance
  3712.  
  3713. joeldalais [7:13 PM]
  3714. the miner(s) increasing the supply (or trying to) would fork off, the mainchain miners would need to do nothing
  3715.  
  3716. cryptorebel [7:14 PM]
  3717. what if they get majority hash
  3718.  
  3719. newliberty
  3720. [7:14 PM]
  3721. Can look at history, every alt coin is an increase in supply. Lately they hold quite a lot of wealth.
  3722.  
  3723. [7:14]
  3724. It doesn't mean that Bitcoin will change.
  3725.  
  3726. joeldalais [7:14 PM]
  3727. then its economic suicide and the users would diverge
  3728.  
  3729. cryptorebel [7:15 PM]
  3730. yeah its good to ask questions and think of all the angles
  3731.  
  3732. joeldalais [7:15 PM]
  3733. questions are always good :slightly_smiling_face:
  3734.  
  3735. [7:15]
  3736. only 1 'legit' reason to increase the supply
  3737.  
  3738. [7:16]
  3739. and that's for more coinage as usage is pretty much 100% globally
  3740.  
  3741. [7:16]
  3742. and then, you just increase the decimals
  3743.  
  3744. newliberty
  3745. [7:16 PM]
  3746. Yes, increase precision rather than quantity
  3747.  
  3748. joeldalais [7:16 PM]
  3749. what he said :slightly_smiling_face:
  3750.  
  3751. [7:17]
  3752. there's going to be 1-2 generations that will need to break out of the mentality "decimals to the right = baaad" (edited)
  3753.  
  3754. cryptorebel [7:18 PM]
  3755. fees are getting insane, I am thinking I need to move some bitcoin around to new wallets, and soon before fees are over $20 or several millibits
  3756.  
  3757. [7:19]
  3758. its going to be expensive to organize coins
  3759.  
  3760. btcalbin [7:19 PM]
  3761. Like compared to fiat values, 1 sat = $0.01 at $1 million valuation, so that would be the best problem ever to have, but is it possible that there might be a push for more decimal places for IoT or microtx reasons well before that kind of valuation?
  3762. 1 reply 10 days ago View thread
  3763.  
  3764. cryptorebel [7:20 PM]
  3765. these fees are giving me anxiety, its sad to see this happening to Bitcoin
  3766.  
  3767. joeldalais [7:20 PM]
  3768. my guess is $30-40'ish by 1st august (fee's per tx)
  3769.  
  3770. btcalbin [7:20 PM]
  3771. i'm assuming payment channels can't get more granular than the base layer because they have to pass real unconfirmed tx's back and forth?
  3772.  
  3773. cryptorebel [7:21 PM]
  3774. you can;t even use Bitcoin now, now its basically a bet on whether you might be able to use it as a real cash system someday if they increase blocksize
  3775.  
  3776. joeldalais [7:22 PM]
  3777. blocksize increase will happen
  3778.  
  3779. [7:22]
  3780. i'm not worried that it won't tbh
  3781.  
  3782. cryptorebel [7:22 PM]
  3783. we need it so bad, and then price will be instalntly like 20K
  3784.  
  3785. [7:23]
  3786. 2MB won't work either
  3787.  
  3788. [7:23]
  3789. too late for that
  3790.  
  3791. newliberty
  3792. [7:24 PM]
  3793. The only thing that 2mb gives us now, is that it proves the lie about hardforking being the greatest danger to Bitcoin.
  3794.  
  3795. cryptorebel [7:25 PM]
  3796. yeah thats the only reason I ever saw 2MB as important
  3797.  
  3798. [7:25]
  3799. it would set a precedent
  3800.  
  3801. newliberty
  3802. [7:25 PM]
  3803. It rips up a lot of astroturf
  3804.  
  3805.  
  3806. btcalbin [7:26 PM]
  3807. would something like CT maybe act as an ossifier of the decimal places? Like I imagine the fact that changing decimal places is really changing what range of ints you're talking about @ sat level, so that impacts the range proofs something like CT uses?
  3808.  
  3809. [7:27]
  3810. like obviously trivial parameter changes we're talking about, but we all know what it's like now once the parameters are hardcoded into the live system :slightly_smiling_face:
  3811.  
  3812. joeldalais [7:29 PM]
  3813. increasing the decimal places wouldn't 'break' the system, from what i understand it would be a 'similar' change to block size increase. E.g. nothing fundamental with coding, etc, would need to change
  3814.  
  3815. zbingledack [7:49 PM]
  3816. @cryptorebel Miners could vote to increase the coin supply, but if they increased it a lot the price would tank, and if they only did it a little the price would tank almost as hard.
  3817.  
  3818. The recourse against miners being idiots is having dead simple and highly reliable market information. Such as through futures trading.
  3819.  
  3820. If they _still_ do something crazy then Bitcoin design would be shown to have been a failure. Cryptocurrency would be a dead thing, or at least on life support awaiting a whole new invention to save it.
  3821.  
  3822. [7:50]
  3823. https://www.reddit.com/r/btc/comments/6evgkq/one_mining_pool_bixin_has_the_power_to_end_the/diefpxj/
  3824. reddit
  3825. One mining pool, Bixin, has the power to end the stalemate. • r/btc
  3826. You inserted the word "should" because you are thinking about it incorrectly. It's not a matter of "miners *should* be able to" but a matter of...
  3827.  
  3828.  
  3829. newliberty
  3830. [7:52 PM]
  3831. Yes, ETC exists only because of the hubris of ETH, calling victory before the battle.
  3832.  
  3833.  
  3834. [7:53]
  3835. Possibly also the conviction, (or lack thereof), that the fork decision was proper.
  3836.  
  3837. newliberty
  3838. [8:13 PM]
  3839. Hey, you sass that hoopy /u/ForkiusMaximus? There's a frood who knows where his towel is. (edited)
  3840.  
  3841.  
  3842.  
  3843. ----- June 5th -----
  3844. neohippy [2:56 PM]
  3845. joined hardfork by invitation from @tomothy
  3846.  
  3847. neohippy [4:05 PM]
  3848. the issue is a blocksize increase without segwit being active on any chain
  3849.  
  3850.  
  3851. kingofkens [6:53 PM]
  3852. joined hardfork by invitation from @hmr, along with @rifel
  3853.  
  3854. movrcx [8:20 PM]
  3855. hey guys i was on a radio show with most of the core devs earlier today... they seem willing to have some bilateral talks with us on air and the person who moderates it seems to be pretty cool. they also seem open to adding more things into the consensus change (like bigger block sizes). i was thinking of setting up a time in the next week or so for us to have some community talks? i definitely have changed my mind about bip200 and i think it can be avoided.
  3856.  
  3857. [8:22]
  3858. even force activating bip148 is controversial in their group. the UASF-trolls are all probably coordinated by blockstream and silbert & co imo; not the people that would be on the show.
  3859.  
  3860. tomothy [8:24 PM]
  3861. UASF seems to have a life of its own at this point and has to be accounted for. I'm not sure what sense there is of any compromise or negotiation anymore. The war over increasing from 1mb to 2mbs has now been going on for 3-4 years. Bitcoin either lives or dies over this impasse.
  3862.  
  3863. zbingledack [8:24 PM]
  3864. Most of the core devs = who exactly?
  3865. 3 replies Last reply 9 days ago View thread
  3866.  
  3867. cryptorebel [8:25 PM]
  3868. 8MB is better
  3869.  
  3870. movrcx [8:25 PM]
  3871. it was a radio interview for matt but luke was there and some other names i've recognized
  3872.  
  3873. [8:25]
  3874. Core core devs i mean
  3875.  
  3876. [8:25]
  3877. lol
  3878.  
  3879. tomothy [8:25 PM]
  3880. Ah, beauty Belle show
  3881.  
  3882. [8:25]
  3883. It was like and Matt jr
  3884.  
  3885. [8:25]
  3886. She was promoting it earlier on Twitter.
  3887.  
  3888. movrcx [8:26 PM]
  3889. everyone treats luke like an idiot i think
  3890.  
  3891. tomothy [8:26 PM]
  3892. And I have to show myself out now... I don't want to eat any more shoes...
  3893.  
  3894. cryptorebel [8:26 PM]
  3895. Core has lost their credibility in negotiations, they have proved to be liars ever since the hong kong phony agreement
  3896.  
  3897. movrcx [8:26 PM]
  3898. what happened there?
  3899.  
  3900. tomothy [8:26 PM]
  3901. No, Luke is here in slack, private mainly.
  3902.  
  3903. cryptorebel [8:27 PM]
  3904. Adam back flew to hong kong and signed agreement with miners for segwit + hard fork block increase, then they want back on the deal
  3905. 1 reply 9 days ago View thread
  3906.  
  3907. tomothy [8:27 PM]
  3908. He got attacked again so might have left but he's back every now and again.
  3909.  
  3910. movrcx [8:27 PM]
  3911. lol
  3912.  
  3913. movrcx [8:27 PM]
  3914. what made them back out?
  3915. 1 reply 9 days ago View thread
  3916.  
  3917. movrcx [8:27 PM]
  3918. fuck deals submit a BIP
  3919. 1 reply 9 days ago View thread
  3920.  
  3921. cryptorebel [8:27 PM]
  3922. maybe they never intended to honor it, they seem to be complete liars
  3923.  
  3924. [8:27]
  3925. they seem evil
  3926.  
  3927. movrcx [8:28 PM]
  3928. I think they'd be willing to co-write a BIP
  3929.  
  3930. cryptorebel [8:28 PM]
  3931. they want to hold Bitcoin back they dont want an increase because blockstream and their funders like AXA want control over Bitcoin
  3932.  
  3933. [8:28]
  3934. they want to force people off chain onto 2nd layer solutions engineered by them
  3935.  
  3936. movrcx [8:28 PM]
  3937. @cryptorebel That's a part of it but the other part still works too.
  3938.  
  3939. cryptorebel [8:29 PM]
  3940. AXA is funding blockstream and Core devs, and they want technocratic smart cities where they team up with governments to track and control everyone: https://www.youtube.com/watch?v=RKWuj1OlDPo
  3941. YouTube AXA
  3942. Smart Cities: Step into the city of the future!
  3943.  
  3944.  
  3945. [8:30]
  3946. to do this, they must limit on-chain transactions and force people to 2nd layer transactions like lightning network
  3947.  
  3948. movrcx [8:30 PM]
  3949. That's not compulsory though
  3950.  
  3951. cryptorebel [8:30 PM]
  3952. then they can centralize and control it and turn it into a credit system
  3953.  
  3954. [8:30]
  3955. you cant believe a word these liars say
  3956.  
  3957. [8:30]
  3958. they are lying to you
  3959.  
  3960. tomothy [8:30 PM]
  3961. It's segwit and bitcoin or bigger blocks and no segwit. What happens is anyone's guess. (edited)
  3962.  
  3963. movrcx [8:31 PM]
  3964. I trust and like Matt
  3965.  
  3966. cryptorebel [8:31 PM]
  3967. some may be useful idiots, brainwashed and incentivized to go along with the plan
  3968.  
  3969. tomothy [8:31 PM]
  3970. He has been deeply involved in all of the mud.
  3971.  
  3972. zbingledack [8:31 PM]
  3973. Looks like you met the Core devs who are given no negotiating power
  3974.  
  3975. tomothy [8:31 PM]
  3976. I trust Luke more than I trust matt
  3977.  
  3978. movrcx [8:32 PM]
  3979. Come on guys :slightly_smiling_face: just talk to them lol
  3980.  
  3981. tomothy [8:32 PM]
  3982. Matt has occasionally let slip what he would like in hard forks but he's quickly always gone back to to the company line
  3983.  
  3984. [8:32]
  3985. They're welcome to join here
  3986.  
  3987. zbingledack [8:32 PM]
  3988. Greg is basically the only Core dev whose opinion gets actually reflected in overall Core policy
  3989.  
  3990. cryptorebel [8:32 PM]
  3991. I tried talking to them, I offered Greg Maxwell a compromise and he told me "fuck you" you can see the PM exchange on reddit
  3992.  
  3993. tomothy [8:32 PM]
  3994. Everyone everyone's welcome.
  3995.  
  3996. cryptorebel [8:32 PM]
  3997. these people are scum of the earth
  3998.  
  3999. movrcx [8:32 PM]
  4000. I can potentially hire Matt and any other Blockstream dev
  4001.  
  4002. tomothy [8:32 PM]
  4003. Even neohippy
  4004.  
  4005. movrcx [8:33 PM]
  4006. Well not hire... but fund
  4007.  
  4008. [8:33]
  4009. So this is an opportunity to get them to leave their companies
  4010.  
  4011. [8:33]
  4012. My project is based on Bitcoin Core anyway
  4013.  
  4014. tomothy [8:33 PM]
  4015. I'd like to see them survive blockstreams destruction post segwit failure
  4016.  
  4017. movrcx [8:34 PM]
  4018. Matt thinks everyone is going to short it asap
  4019.  
  4020.  
  4021. zbingledack [8:34 PM]
  4022. This is a classic negotiation tactic. Luke and Matt can agree to everything, but it matters not. They aren't the decisionmakers.
  4023.  
  4024.  
  4025. tomothy [8:34 PM]
  4026. If they want to work on a larger bitcoin I think that would be great
  4027.  
  4028. [8:34]
  4029. Going to short what? Uasf? Big block BTC?
  4030.  
  4031. movrcx [8:34 PM]
  4032. UASF
  4033.  
  4034. cryptorebel [8:34 PM]
  4035. its all about making you feel good like you had a voice
  4036.  
  4037. movrcx [8:35 PM]
  4038. no no no i've interacted with him a few times before... nothings changed
  4039.  
  4040. [8:35]
  4041. The problem is Blockstream I think
  4042.  
  4043. tomothy [8:36 PM]
  4044. Yes. That's accurate.
  4045.  
  4046. movrcx [8:36 PM]
  4047. I first met Matt in person at BitDevs in NY and basically I did a presentation about my Bitcoin but with a treasury project for self-funding things and I think he was interested.
  4048.  
  4049. [8:36]
  4050. I explicitly said that the commercialization of bitcoin was bs.
  4051.  
  4052. tomothy [8:37 PM]
  4053. Well, blockstream and Greg. Luke always has interesting ideas on things. But he's manageable.
  4054.  
  4055. movrcx [8:37 PM]
  4056. ok so lets go fuck blockstream up and take their labor force
  4057.  
  4058. 5 replies Last reply 9 days ago View thread
  4059.  
  4060. tomothy [8:38 PM]
  4061. It's why they were freezed out of the consensus negotiations
  4062.  
  4063. [8:39]
  4064. The difficulty is they've added all this stuff that isn't necessary, or wouldn't be, if you simply raised the block size. Like rbf, WTF. Litecoin added segwit but still refused to add rbf.
  4065.  
  4066. [8:40]
  4067. And so I think reconciliation has to happen post fork
  4068.  
  4069. [8:40]
  4070. Not before
  4071.  
  4072. movrcx [8:41 PM]
  4073. As much as Bitcoin's First Civil War intrigues me that's just going to be so bloody though. (edited)
  4074.  
  4075. tomothy [8:41 PM]
  4076. Yes.
  4077.  
  4078. [8:41]
  4079. Moon and doom with BTC at $10k a coin. High stakes to say the least.
  4080.  
  4081. cryptorebel [8:42 PM]
  4082. need some figurative blood to water the Tree of Liberty
  4083.  
  4084.  
  4085. tula [8:42 PM]
  4086. blue matt corallo? compromised as much as the rest of the gang ..ive seen him say too many lies
  4087.  
  4088.  
  4089. movrcx [8:42 PM]
  4090. about what @tula?
  4091.  
  4092. tula [8:44 PM]
  4093. scaring miners not to increase the blocksize before the HK consensus ..for starters
  4094.  
  4095. movrcx [8:45 PM]
  4096. ah
  4097.  
  4098. [8:46]
  4099. Well I pitched this thing as like an open and public Bitcoin community discussion lol
  4100.  
  4101. tomothy [8:46 PM]
  4102. I think it's good to discuss
  4103.  
  4104. [8:46]
  4105. But any agreement​ with segwit is one that shouldn't be agreed to.
  4106.  
  4107.  
  4108. movrcx [8:47 PM]
  4109. Matt said that SegWit is a nice to have for lightning but not a requirement.
  4110.  
  4111. tomothy [8:47 PM]
  4112. Likewise from the opposing group, anything without segwit, has been something they would oppose. How you get to compromise with that, I'm not sure.
  4113.  
  4114. [8:47]
  4115. So it has to come down to blockstream
  4116.  
  4117. [8:48]
  4118. Which makes sense, because he's said he would like larger blocks. But then back pedals after Greg stops by...
  4119.  
  4120. cryptorebel [8:48 PM]
  4121. there is no communication desired from segwit side, they desire to make us shut up instead, that is why they ban and censor everyone in the most popular bitcoin communication platform /r/bitcoin
  4122.  
  4123.  
  4124. movrcx [8:49 PM]
  4125. I'd like to knock Blockstream out of the picture.
  4126.  
  4127. [8:49]
  4128. So my project has like a $200k operating budget right now in it's DAO and I could propose funding Bitcoin developers with it
  4129.  
  4130. [8:50]
  4131. It's beneficial for me because my codebase is based on Core
  4132.  
  4133. tomothy [8:50 PM]
  4134. A better question is how much funding they have left , and when is their next funding round...
  4135.  
  4136. movrcx [8:50 PM]
  4137. Ok so we're in a good position then
  4138.  
  4139. [8:50]
  4140. If SegWit fails Blockstream evaporates
  4141.  
  4142. tomothy [8:50 PM]
  4143. I think so.
  4144.  
  4145. movrcx [8:51 PM]
  4146. The thing is is that they aren't going to let it fail by any means
  4147.  
  4148. tomothy [8:51 PM]
  4149. That's why they need it whereas others don't.
  4150.  
  4151. [8:51]
  4152. Yes. That's why there will be a segwit fork and war is guaranteed.
  4153.  
  4154. [8:52]
  4155. After three failed scaling increases, derailed by blockstream, it starts getting old...
  4156.  
  4157. movrcx [8:52 PM]
  4158. :mrburn:*plots against blockstream*
  4159.  
  4160. [8:53]
  4161. At the very least I'm going to try to poach Matt if that's successful it might shake up the team a bit.
  4162.  
  4163.  
  4164. tomothy [8:55 PM]
  4165. Him and Peter
  4166.  
  4167. movrcx [8:56 PM]
  4168. Peter is solo now I thought?
  4169.  
  4170. tomothy [8:56 PM]
  4171. I don't know​ what to think about Peter. I like Luke as a person I just dislike most of his ideas. But respect where he's coming from.
  4172.  
  4173. [8:56]
  4174. He is
  4175.  
  4176. [8:56]
  4177. Which is interesting...
  4178.  
  4179. [8:56]
  4180. And makes me wonder if blockstream is having burn rate issues...
  4181.  
  4182. movrcx [8:58 PM]
  4183. Hehehehe
  4184.  
  4185. [8:58]
  4186. Bitcoin needs it's own treasury model to keep the companies out imo (edited)
  4187.  
  4188. checksum0
  4189. [8:59 PM]
  4190. Maybe we should just buy out Blockstream and close them out :slightly_smiling_face:
  4191.  
  4192. newliberty
  4193. [9:07 PM]
  4194. Only if you are paying in XBT short contracts and then pump the price. They aren't getting a dime from me.
  4195.  
  4196. movrcx [9:08 PM]
  4197. Same lol
  4198.  
  4199. checksum0
  4200. [9:09 PM]
  4201. A whale might make more money destroying Blockstream than what it cost to buy Blockstream
  4202.  
  4203. newliberty
  4204. [9:16 PM]
  4205. I am happy with the current method of destruction, buying their shorts when they try to destroy Bitcoin, and stopping them from doing so.
  4206.  
  4207. [9:16]
  4208. Discrediting their lies
  4209.  
  4210. [9:18]
  4211. Buying them for a positive number more than US$1 seems too gentle of a defeat.
  4212.  
  4213. andy [9:23 PM]
  4214. joined hardfork by invitation from @satoshi
  4215.  
  4216. movrcx [10:21 PM]
  4217. Hmm so Matt left Blockstream 2 months ago
  4218.  
  4219. [10:22]
  4220. The story is is that he "left"
  4221.  
  4222. tomothy [10:25 PM]
  4223. Yeah. Damn. I knew that. I should have said something.
  4224.  
  4225. [10:25]
  4226. He left and Peter left
  4227.  
  4228. [10:25]
  4229. I wonder if it's funding issues
  4230.  
  4231. checksum0
  4232. [10:26 PM]
  4233. They have funding issues and get Mow on boad?
  4234.  
  4235. [10:26]
  4236. I know Mow is probably a cheap hire but hey...
  4237.  
  4238.  
  4239. cryptorebel [10:27 PM]
  4240. 75 million or whatever doesnt seem like much, but I bet they can get more if needed, turned out buying off core devs was extremely cheap
  4241.  
  4242.  
  4243. tomothy [10:27 PM]
  4244. Hmm. But I think mow was added prior to either Peter or matt leaving
  4245.  
  4246. checksum0
  4247. [10:28 PM]
  4248. Yeah, I guess you are right
  4249.  
  4250. [10:28]
  4251. Still, 75 millions over 4 years
  4252.  
  4253. [10:28]
  4254. Funds gotta start running low now...
  4255.  
  4256. satoshi [10:28 PM]
  4257. Mow just got hired I thought?
  4258.  
  4259. cryptorebel [10:29 PM]
  4260. yeah he got hired like probably 6 months ago or something
  4261.  
  4262. checksum0
  4263. [10:30 PM]
  4264. April 12th a quick google search reveals
  4265.  
  4266. tomothy [10:30 PM]
  4267. So they fire Matt and hire mow? (edited)
  4268.  
  4269. checksum0
  4270. [10:39 PM]
  4271. I don't think mow is related to Matt leaving
  4272.  
  4273.  
  4274.  
  4275. ----- June 6th -----
  4276. btcalbin [1:21 AM]
  4277. Was this a de facto demotion for Johnny Dilley?
  4278.  
  4279. [1:22]
  4280. Like prior I remember him w/ the "strategy" title, although I don't recall it being C-level
  4281.  
  4282. newliberty
  4283. [3:26 AM]
  4284. Sometimes it is good to hire a general, just so they aren't fighting against you.
  4285.  
  4286. neohippy [10:12 AM]
  4287. pay to contract is a good way to have the lightning network
  4288.  
  4289. tomothy [10:14 AM]
  4290. that's what they're looking for
  4291.  
  4292. [10:14]
  4293. it's the only way their 1mb chain makes any sense
  4294.  
  4295. neohippy [10:15 AM]
  4296. blocksize increase + pay to contract bip
  4297.  
  4298. [10:16]
  4299. that is scaling for bitcoin
  4300.  
  4301. taxed4ever [11:58 AM]
  4302. joined hardfork by invitation from @hmr, along with @phil65. Also, @neohippy left.
  4303.  
  4304. jonald_fyookball [3:44 PM]
  4305. whats the story
  4306.  
  4307. leithm [4:06 PM]
  4308. joined hardfork by invitation from @hmr
  4309.  
  4310. jonald_fyookball [8:47 PM]
  4311. if someone were to sue blockstream,
  4312.  
  4313. [8:47]
  4314. it would generate a LOT of press
  4315.  
  4316. [8:47]
  4317. wouldnt even have to win the case
  4318.  
  4319. [8:47]
  4320. that would destroy them
  4321.  
  4322.  
  4323. [8:48]
  4324. they should be sued for maliciously attempting to sabotage the project, causing damage to investors
  4325.  
  4326. [8:49]
  4327. and there's plenty of evidence
  4328.  
  4329. [8:49]
  4330. all of the publicly spoken lies from gmax , luke
  4331.  
  4332. [8:50]
  4333. adam
  4334.  
  4335. [8:51]
  4336. they've probably caused investors to lose $1b
  4337.  
  4338. cryptorebel [8:51 PM]
  4339. maybe they need grand jury investigations for racketeering or something
  4340.  
  4341. jonald_fyookball [8:52 PM]
  4342. woah
  4343.  
  4344. cryptorebel [8:52 PM]
  4345. yeah I think that would be the way to go if anything
  4346.  
  4347. jonald_fyookball [8:52 PM]
  4348. i was just thinking civil suit but if we want to go criminal too
  4349.  
  4350. cryptorebel [8:53 PM]
  4351. there could be an investigation anyways, then the grand jury can decide if there is enough evidence to indict them
  4352.  
  4353. jonald_fyookball [8:53 PM]
  4354. that would be harder...not really necessary
  4355.  
  4356. [8:54]
  4357. a class action lawsuit would be straight forward and discredit them publicly while getting a lot of press attention
  4358.  
  4359. [8:55]
  4360. its an idea
  4361.  
  4362. cryptorebel [9:05 PM]
  4363. It might not be that hard, look the definition of racketeering: "Racketeering, often associated with organized crime, is the act of offering of a dishonest service (a "racket") to solve a problem that wouldn't otherwise exist without the enterprise offering the service. http://www.investopedia.com/terms/r/racketeering.asp
  4364. Investopedia
  4365. Racketeering
  4366. A fraudulent service built to serve a problem that wouldn't otherwise exist without the influence of the enterprise offering the service. (341kB)
  4367. May 27th, 2010 at 1:00 PM
  4368.  
  4369. [9:05]
  4370. This is almost exactly what BlockStream is doing, creating a problem where there wouldnt otherwise be one by limiting the blocksize, so that they can force us onto their 2nd layer solutions
  4371.  
  4372. [9:06]
  4373. what they are trying to do is literally the definition of a racket
  4374.  
  4375.  
  4376. tomothy [9:42 PM]
  4377. Criminal not civil
  4378.  
  4379. [9:42]
  4380. You'd have to be a huge company who's plans were interrupted
  4381.  
  4382. [9:42]
  4383. Tough
  4384.  
  4385. bitalien
  4386. [10:09 PM]
  4387. This debate sucks because it's just the rehashing of arguments that have been said already, every single day
  4388.  
  4389. [10:10]
  4390. It's actually not a scaling *DEBATE* anymore because it's already clear that big blocks have won the debate.
  4391.  
  4392. At this point we just have to wait for miners to do something
  4393.  
  4394. jonald_fyookball [11:07 PM]
  4395. @bitalien good point
  4396.  
  4397. [11:07]
  4398. that could be an article !
  4399.  
  4400. [11:07]
  4401. you just inspired me
  4402.  
  4403. [11:08]
  4404. "The scaling debate is over, and the big blockers have won."
  4405.  
  4406. [11:10]
  4407. but the article would just be more debating lol
  4408.  
  4409. [11:10]
  4410. the next phase is videos
  4411.  
  4412. [11:10]
  4413. i will be getting into video production and youtube promotion to reach a lot of eyeballs
  4414.  
  4415.  
  4416. [11:10]
  4417. i already have someone who promised to fund it
  4418.  
  4419. [11:11]
  4420. but i would like to know what is the battle plan first regarding aug 1
  4421.  
  4422. [11:12]
  4423. i have heard so many different things but only partial bits
  4424.  
  4425. bitalien
  4426. [11:21 PM]
  4427. Sounds like a great idea @jonald_fyookball !
  4428.  
  4429.  
  4430. ----- June 7th -----
  4431. movrcx [12:55 AM]
  4432. *BLOCKSTREAM CLASS ACTION LAWSUIT*
  4433.  
  4434. [12:55]
  4435. ON BEHALF OF ALL BITCOIN USERS ACROSS THE WORLD
  4436.  
  4437. zbingledack [1:02 AM]
  4438. Bitpay? Coinbase? Or huger, like Overstock.com? Newegg?
  4439. tomothy
  4440. You'd have to be a huge company who's plans were interrupted
  4441. Posted in #hardforkJune 6th at 9:42 PM
  4442.  
  4443. bitalien
  4444. [2:03 AM]
  4445. Sadly I don't think anything they've done is illegal
  4446.  
  4447. newliberty
  4448. [4:40 AM]
  4449. If SEC classed it as a security, there might be an argument for manipulation.
  4450. If discovery showed that they were shorting bitcoin during some important mischief they were doing, it could be bad for them.
  4451. Or it could just be bad.
  4452. https://www.sec.gov/fast-answers/answerstmanipulhtm.html
  4453. It is a pretty big can of worms to open getting those folks involved.
  4454.  
  4455. btcalbin [4:43 AM]
  4456. does their FUD from the opposite side that promoting a hardfork makes Gavin some kind of "virtual currency administrator" resemble anything whatsoever that actually exists in the real world?
  4457.  
  4458. 1 reply 7 days ago View thread
  4459.  
  4460. joeldalais [5:30 AM]
  4461. regarding the *debate*, there never has been a *debate*, its been an attempted corporate takeover since before day 1. Greg never believed in bitcoin and neither did Adam, and after it gained some value they now want to steal fees (since they missed the early train).
  4462.  
  4463. [5:32]
  4464. if you think there's a *debate* you're playing into their hands thinking that there is some 'middle-ground' that can eventually be found and reached. There is none. Dash the illusion from your mind and work around blockstreamcore, because they will never ever *debate* with you. Their understanding and use of debating is just pure stalling to cause more congestion in their blind hope to push people to their retarded 'solutions' (aka, subjugation and takeover). (edited)
  4465.  
  4466.  
  4467. lunar [5:44 AM]
  4468. @jonald_fyookball The best argument to win miners over is their bottom line. They must be (honest) intelligently profit seeking, where profit is measured in BTC. We need some nice clear infographics that show exactly how much more money miners will make if they mine and hold bitcoin with an increased blocksize. Small blockers argue there's not point in increasing the blocksize because whatever size we choose will always be filled with transactions. I'd turn this against them, and try to show the anticipated increase in bitcoin price along with increased revenue from Tx processing at various increases in blocksize assuming full blocks with a minimum included Tx fee of 0.05cents and a long tail of fees up to 50 000 Tx at 4$. Metcalf's law seems to be a good approximation to play with here, so you could base your calculations around this chart. http://woobull.com/bitcoin-market-cap-should-be-40b-according-to-metcalfes-law/ to show Bitcoin with 10MB full blocks would be 3million Tx/day and value BTC market cap at 0.9 trillion. Obviously you need to use caution here, because it would actually take quite some time to grow the network to fill 10MB blocks, but this is the point we are trying to show, by keeping fees high they are roadblocking adoption and hence their bottom line.
  4469. Woobull
  4470. Bitcoin Market Cap should be $40b according to Metcalfe’s law
  4471. Metcalfe’s Law states the value of a network is proportional to the number of members squared. I thought it’d be fun to run the numbers on the Bitcoin Network. Since we don’t have…
  4472. Sept 10th, 2016 at 2:35 PM
  4473.  
  4474.  
  4475.  
  4476. tula [6:05 AM]
  4477. > The best argument to win miners over is their bottom line.
  4478. = we need to stop paying fees to the smallblock miners
  4479.  
  4480.  
  4481. movrcx [9:17 AM]
  4482. It might be good to point out that after the block rewards ends then there will be little incentive left for miners with SegWit. There's no reason a miner should support 148 at all.
  4483.  
  4484. hmr [9:18 AM]
  4485. Was that bump in node count your doing?
  4486.  
  4487. movrcx [9:22 AM]
  4488. No shouldn't be... my nodes are just doing outbound connections right now and shouldn't be counter
  4489.  
  4490.  
  4491. movrcx [9:48 AM]
  4492. I think I found a way to bypass Core's transaction replay protection mechanism. It makes a chainsplit absolutely suicidal.
  4493.  
  4494.  
  4495. tomothy [9:48 AM]
  4496. see newliberty's recent comments in private as well
  4497.  
  4498. movrcx [9:48 AM]
  4499. Will do
  4500.  
  4501. tomothy [11:32 AM]
  4502. So I'm finally in the office today. Here is some more speculation concerning Bluematt
  4503.  
  4504. [11:35]
  4505. From Anonymous-
  4506.  
  4507. My two cents about Matt Corello (could be wrong)
  4508. Shortly after the hong kong agreement Lombrozo told me that Matt was having a hard time with something. It is good to know that the Hong Kong plan (segwit and a 2mb hard-fork after) was modeled after a proposal he made. The 75% discount in SWSF would be brought down to 50% during the hard-fork so that the total size would not be over 4mb. After the hong kong agreement (where Matt was present) some of the other Blockstream team members were very publicly upset about it. Greg called them all dipshits and Mark Friedenbach was outraged. They made very clear that the agreement would not find consensus within Core. The deal died within 48 hours even though that was of course not an official statement as Classic was still seen as a threat. Blockstream employees have a deal where if they do not agree with Blockstream policy they can continue working on Bitcoin while being payed by Blockstream. His departure from Blockstream seems to be approx a year after the Hong Kong mess. So I have a feeling his employment came to an end last year but because of the contractual provision of 1 year it came in effect this year. Like I said, I could be wrong
  4509.  
  4510. Just one more note on Matt Correlo. Last year I did see him spread FUD and untruth together with Peter Todd on Chinese chat forums that were intended to keep Chinese miners from going with Classic. Also witnessed him attacking Jeff Garzik in Core slack when he was saying that businesses were very much in need and in favor of a block size increase. The fact he left Blockstream does not mean he changed his character. He can be a nasty piece of work. Seen him comment on other crypto projects and devs too. Huge ego’s, immature, low self reflection……. It is hard to not start seeing something you work on as your own project. Most in Bitcoin do not have a lot of credentials outside of Crypto or in the real world. Some started to believe in the BS that they are the only true experts. If you drive all that think different out, and you create a uniform group you are bound to start fucking up. Main group of developers has so much dysfunctionality in it, its unbelievable.
  4511.  
  4512.  
  4513. csw [11:43 AM]
  4514. Do Any of them have marketable skills?
  4515.  
  4516. [11:44]
  4517. PS
  4518. None of them are cryptographers
  4519.  
  4520. checksum0
  4521. [11:55 AM]
  4522. @tomothy you got that from someone or found it digging around forums?
  4523.  
  4524. tomothy [11:55 AM]
  4525. from someone
  4526.  
  4527. [11:56]
  4528. in this environment sometimes it's not ok to be associated with honest discourse
  4529.  
  4530. [11:56]
  4531. remember coinbase and classic, prior to the segwit stuff? XT? Small block attacks get brutal.
  4532.  
  4533. checksum0
  4534. [11:57 AM]
  4535. So bs was outraged with the deal Matt was a part of?
  4536.  
  4537. tomothy [11:57 AM]
  4538. Yeah, do you recall the HK fallout at all? I know this saga has been going on for ages... so...
  4539.  
  4540. [11:58]
  4541. HK was a shit show. Miners were going to implement Classic.
  4542.  
  4543. [11:58]
  4544. Adam Back flies out, and says NO NO NO NO NO (more or less)
  4545.  
  4546. [11:58]
  4547. just wait...
  4548.  
  4549. [11:58]
  4550. we'll get you a hardfork! and we might have a solution as well, this amazing thing called segwit...
  4551.  
  4552. [11:59]
  4553. he was supposed to sign ON behalf of Block Stream and then didn't...
  4554.  
  4555. [11:59]
  4556. and then everyone attacked matt and todd for being involved in HK
  4557.  
  4558. checksum0
  4559. [11:59 AM]
  4560. Yes I remember everything. That explains why he became a "contractor"
  4561.  
  4562. tomothy [11:59 AM]
  4563. it could
  4564.  
  4565. [11:59]
  4566. i think that was the suggestion
  4567.  
  4568. [11:59]
  4569. i didn't pick up on the timing as such but it's a plausible theory
  4570.  
  4571. [12:00]
  4572. the whole HK thing got really messy/ugly
  4573.  
  4574. [12:00]
  4575. and then I remember (speculation) hearing about exchanges present that had open margin positions and needed certain responses to ensure their positions went well
  4576.  
  4577. checksum0
  4578. [12:00 PM]
  4579. Everything been messy since BS was funded and hired most core devs
  4580.  
  4581. tomothy [12:00 PM]
  4582. I want to say it was Star but no clue
  4583.  
  4584. checksum0
  4585. [12:00 PM]
  4586. Even bs history is messy
  4587.  
  4588. tomothy [12:01 PM]
  4589. BS also has a messy history? (wasn't aware as such)
  4590.  
  4591. checksum0
  4592. [12:01 PM]
  4593. With previous CEO and everything
  4594.  
  4595. tomothy [12:01 PM]
  4596. ?
  4597.  
  4598. [12:02]
  4599. (I probably know these things, it gets so soap opera esque, it all blends together)
  4600.  
  4601. checksum0
  4602. [12:02 PM]
  4603. Austin hill
  4604.  
  4605. tomothy [12:02 PM]
  4606. Ok, what happened to him? (Again, sorry. LOL :smile: )
  4607.  
  4608. checksum0
  4609. [12:04 PM]
  4610. He got pushed to the side big time when axa came in
  4611.  
  4612. [12:04]
  4613. It was ugly
  4614.  
  4615. [12:04]
  4616. Back was unofficially CEO for a while before he got fed up enough to leave by himself
  4617.  
  4618. tomothy [12:04 PM]
  4619. When was this? And when did AXA come in? Who replaced him? How did it get ugly? Is there anywhere I can go to read up on the transition?
  4620.  
  4621. checksum0
  4622. [12:05 PM]
  4623. October 2016 but back was in control before that
  4624.  
  4625. [12:06]
  4626. Best rumours are probably on bct if you got time to lose. On cellphone now
  4627.  
  4628.  
  4629. tomothy [12:06 PM]
  4630. kk
  4631.  
  4632. [12:07]
  4633. I'll try to do a search later once i get these memos out. I'm wondering if with the change, Blockstreams scaling position changed as well.
  4634.  
  4635. [12:07]
  4636. Adam was saying 2-4-8 was ok in 2015
  4637.  
  4638. [12:07]
  4639. 2016, it was then segwit and fuck bigger blocks
  4640.  
  4641. [12:07]
  4642. (figuratively)
  4643.  
  4644. phoenix
  4645. [12:07 PM]
  4646. the individual devs position definitely changes pre and post BS
  4647.  
  4648. cryptorebel [3:58 PM]
  4649. former Blockstream CEO Austin Hill has admitted he was a "straight up scammer": http://betakit.com/montreal-angel-austin-hill-failed-spectacularly-before-later-success/
  4650. BetaKit
  4651. “A Straight Out Scam”: Montreal Angel Austin Hill Recounts First Business at FailCampMTL
  4652. Saturday's FailCamp in Montreal was a gathering of about 160 startup and small business entrepreneurs curious about failure and success. On stage throughout the (76kB)
  4653.  
  4654. [3:59]
  4655. AXA came in Feb. 2016: https://blockstream.com/2016/02/02/blockstream-new-investors-55-million-series-a.html
  4656. blockstream.com
  4657. Blockstream Welcomes New Investors: Adds $55 Million in Series A
  4658. Blockstream is off to a strong start this year with a number of new customer engagements, our announcement of a strategic partnership with PwC, and today bei...
  4659.  
  4660.  
  4661. cryptorebel [10:31 PM]
  4662. user noosterdam has some very interesting comments in this thread regarding spinoffs, and inflation: https://www.reddit.com/r/btc/comments/4q1l1o/it_is_imperative_that_we_encode_resistance_to/
  4663. reddit
  4664. It is imperative that we encode resistance to economic central planning into Bitcoin’s DNA, • r/btc
  4665. 30 points and 15 comments so far on reddit
  4666.  
  4667.  
  4668.  
  4669.  
  4670. ----- June 8th -----
  4671. linzheming
  4672. [12:40 AM]
  4673. Do we already have a hard fork since BIP-0066? so the pre-bip0066 client will reject the longest chain?
  4674.  
  4675. tomothy [6:37 AM]
  4676. Will ask in more frequent channel
  4677.  
  4678. btcalbin [7:35 AM]
  4679. no BIP 66 isn't a hardfork, it just caused temporary chain splits because of header spy-mining on top of blocks made by a miner that signalled the softfork but wasn't actually running the node version to enforce it
  4680.  
  4681. cypherblock [10:25 AM]
  4682. also the whole bitcoin had a hard fork, no it didn’t, yes it did, thing is a bit old IMO.
  4683.  
  4684.  
  4685. btcalbin [11:43 AM]
  4686. the flag day for upgrading to 0.8, a backport with the correct db settings, or manually tweaking db settings definitely was a hardfork
  4687.  
  4688. bagatell [4:54 PM]
  4689. joined hardfork by invitation from @hmr, along with @mrmadden
  4690.  
  4691. hmr [8:38 PM]
  4692. https://twitter.com/movrcx/status/872893481093656576
  4693. movrcx @movrcx
  4694. $Zen and probable $BTC 0day for replay attacks. https://pbs.twimg.com/media/DB0j_RyUwAAZZ8E.jpg
  4695. TwitterJune 8th at 3:09 PM (145kB)
  4696.  
  4697. checksum0
  4698. [9:27 PM]
  4699. tx-replay-prevention?
  4700.  
  4701. [9:27]
  4702. here?
  4703.  
  4704.  
  4705. checksum0
  4706. [9:33 PM]
  4707. Also @hmr, fucking Bitpico replying to movrcx tweet :joy: :joy:
  4708.  
  4709. klakurka [9:47 PM]
  4710. joined hardfork by invitation from @hmr, along with @guanbaiqiang, @bitchcoin, @ntegan1. Also, @el33th4x0r joined.
  4711.  
  4712.  
  4713. ----- June 9th -----
  4714. movrcx [1:21 AM]
  4715. @checksum0 was on a different Slack :)
  4716.  
  4717.  
  4718. shadders [11:03 AM]
  4719. joined hardfork by invitation from @tomothy. Also, @anarch33 left.
  4720.  
  4721. cryptorebel [1:32 PM]
  4722. vitalik has a funny, but interesting proposal for increasing capacity, seems better than segwit anyways: https://www.reddit.com/r/btc/comments/428tjl/softforking_the_block_time_to_2_min_my_primarily/
  4723. reddit
  4724. Soft-forking the block time to 2 min: my primarily silly and academic (but seemingly effective) entry to the "increase the blockchain's capacity in an arbitrarily roundabout way as long as it's a softfork" competition • r/btc
  4725. So given that large portions of the bitcoin community seem to be strongly attached to this notion that hard forks are an unforgivable evil, to the...
  4726.  
  4727.  
  4728. checksum0
  4729. [1:37 PM]
  4730. Fucking shorter block time all the time
  4731.  
  4732. checksum0
  4733. [1:37 PM]
  4734. We don't _need_ shorter block time. Why are they so blinded by that ffs?
  4735. 2 replies Last reply 4 days ago View thread
  4736.  
  4737. csw [1:38 PM]
  4738. More stupidity
  4739.  
  4740. phoenix
  4741. [1:52 PM]
  4742. how does this one sound ? https://www.usenix.org/conference/usenixsecurity16/technical-sessions/presentation/kogias
  4743.  
  4744. [1:53]
  4745. http://hackingdistributed.com/images/2016-bitcoin/byzcoin-throughput.png (106kB)
  4746.  
  4747. [1:54]
  4748. One of the most interesting presentations in "Scaling Bitcoin" in Milan, and not a single question from the whole audience...
  4749.  
  4750. csw [1:57 PM]
  4751. Visa scales to over 50,000 TX/sec now
  4752.  
  4753. [1:58]
  4754. And nothing of use or fact in that entire presentation.
  4755.  
  4756. phoenix
  4757. [2:01 PM]
  4758. I thought they run actual experiments on this, isn't that useful ?
  4759.  
  4760. [2:03]
  4761. https://www.usenix.org/system/files/conference/usenixsecurity16/sec16_paper_kokoris-kogias.pdf or this https://github.com/DeDiS/Cothority ?
  4762. GitHub
  4763. dedis/cothority
  4764. cothority - Scalable collective authority prototype
  4765.  
  4766.  
  4767. zbingledack [2:42 PM]
  4768. Any thoughts on "weak blocks" / subchains?
  4769.  
  4770. phoenix
  4771. [2:45 PM]
  4772. this appears to be similar in several regards (edited)
  4773.  
  4774. cryptorebel [9:12 PM]
  4775. how big of a threat is barry silberts "compromise" chain? some discussion about it here: https://www.reddit.com/r/btc/comments/6g86td/will_uasf_allow_to_bitcoin_unlimited_go_live_on/
  4776. reddit
  4777. Will UASF allow to Bitcoin Unlimited go live on the old chain? • r/btc
  4778. ^
  4779.  
  4780.  
  4781. vlad2vlad [9:20 PM]
  4782. Big threat - Barry has Goldman behind him. It could get pretty ugly.
  4783.  
  4784. csw [9:23 PM]
  4785. Not really
  4786.  
  4787. [9:23]
  4788. Bary sells exagerated claims
  4789.  
  4790.  
  4791.  
  4792. ----- June 10th -----
  4793. phoenix
  4794. [6:28 AM]
  4795. meanwhile, eth already has applications running their LN (state channels) https://www.lykke.com/city/blog/lykke_offchain_settlement Interesting use case: sure. Scaling solution: no.
  4796. lykke.com
  4797. Lykke Offchain Settlement: FAQ
  4798. Offchain settlement is about registering over the blockchain a mutually agreed initial state for a bidirectional payment channel (as represented by a multi...
  4799.  
  4800.  
  4801. ----- June 11th -----
  4802. jonald_fyookball [8:48 AM]
  4803. is it really feasible to have a 4 way split ?:joy:
  4804.  
  4805. vlad2vlad [8:49 AM]
  4806. I think we'll end up having at least 3 chains by the time Core is done playing god
  4807.  
  4808.  
  4809. jonald_fyookball [8:57 AM]
  4810. a little game theory: if their plan really was to rekt BTC...then creating any kind of minority chain that survives might be better than losing their power , at least that would in their hopes cause confusion and perception of splintering
  4811.  
  4812. [8:58]
  4813. they would also no doubt attempt to steal the name
  4814.  
  4815. [8:58]
  4816. even on a minority
  4817.  
  4818. [8:58]
  4819. probably by bribing exchanges etc
  4820.  
  4821. vlad2vlad [9:03 AM]
  4822. I think that's exactly what they're gonna do. Stay on the minority chain and steal the name when it's really a completely new alt.
  4823.  
  4824. jonald_fyookball [9:04 AM]
  4825. is that really going to fly
  4826.  
  4827. [9:06]
  4828. in such a situation i would be concerned about people like Barry
  4829.  
  4830. [9:06]
  4831. they control a lot media
  4832.  
  4833. [9:07]
  4834. i guess there could be a huge post split war over the name
  4835.  
  4836. csw [9:08 AM]
  4837. They think they do....
  4838.  
  4839. jonald_fyookball [9:08 AM]
  4840. thankfully, Adam and Greg gave us plenty of ammunition to demonstrate how deceitful they are by participating in the trolling personally
  4841.  
  4842. [9:08]
  4843. not very strategic on their part.
  4844.  
  4845. csw [9:09 AM]
  4846. No, but very good from my perspective.
  4847.  
  4848. jonald_fyookball [9:09 AM]
  4849. exactly
  4850.  
  4851. [9:10]
  4852. will be easy to compile hit pieces painting them as the usurpers they are
  4853.  
  4854. [9:12]
  4855. one thing that i am not seeing is there is no powerful news outlet (that i'm aware of) on "our side"
  4856.  
  4857. [9:12]
  4858. DCG owned coindesk....
  4859.  
  4860. [9:12]
  4861. not sure who runs cointelegraph, they seem only marginally better
  4862.  
  4863. [9:12]
  4864. actually they just like opportunists
  4865.  
  4866. tomothy [9:12 AM]
  4867. Coingeek
  4868.  
  4869.  
  4870. jonald_fyookball [9:12 AM]
  4871. they will take anyone's money
  4872.  
  4873. [9:12]
  4874. coingeek is cool but needs more prominence
  4875.  
  4876. csw [9:13 AM]
  4877. That will come
  4878.  
  4879. jonald_fyookball [9:13 AM]
  4880. well it should come soon dont you think if there's to be a war over the name
  4881.  
  4882. csw [9:13 AM]
  4883. No, what war...
  4884.  
  4885. [9:13]
  4886. If you think that is a battle
  4887.  
  4888. jonald_fyookball [9:14 AM]
  4889. vlad2vlad
  4890. I think that's exactly what they're gonna do. Stay on the minority chain and steal the name when it's really a completely new alt.
  4891. Posted in #hardforkJune 11th at 9:03 AM
  4892.  
  4893. csw [9:14 AM]
  4894. You are not seeing how easy it is :slightly_smiling_face:
  4895.  
  4896. jonald_fyookball [9:15 AM]
  4897. @csw if dcg calls their fork "BTC" and so does coindesk, and so does cointelegraph, and so does bitfinex, that would be the concern
  4898.  
  4899. csw [9:15 AM]
  4900. Law is law....
  4901.  
  4902. jonald_fyookball [9:16 AM]
  4903. ummm
  4904.  
  4905. [9:17]
  4906. i see your point but people are easily led, fooled, and manipulated, generally more ignorant and less intelligent than imagined...this war has reminded us of that (edited)
  4907.  
  4908. csw [9:17 AM]
  4909. uploaded this file
  4910. LLM_CSW.doc
  4911. 357kB
  4912. Word Document
  4913. Click to download
  4914. Add Comment
  4915.  
  4916. csw [9:18 AM]
  4917. Did you know that my specialty as a (academic and not dumb enough to practice) lawyer was...
  4918.  
  4919. [9:18]
  4920. Internet Intermediary Liability
  4921.  
  4922. jonald_fyookball [9:19 AM]
  4923. I didn't.
  4924.  
  4925. csw [9:19 AM]
  4926. Now you do.
  4927.  
  4928. [9:19]
  4929. AND
  4930.  
  4931. vlad2vlad [9:19 AM]
  4932. What does that mean, csw, we can sue for the name?
  4933.  
  4934. csw [9:19 AM]
  4935. I am smart enough to leave the work to the big firms :wink: (edited)
  4936.  
  4937. [9:20]
  4938. We... no... but...
  4939.  
  4940. jonald_fyookball [9:20 AM]
  4941. i dont think you can sue anyone if everyone just starts calling something by a certain name or a meme takes off
  4942.  
  4943. csw [9:20 AM]
  4944. Really....
  4945.  
  4946. [9:20]
  4947. See, Shapiro, Andrew L., Digital Middlemen and the Architecture of Electronic Commerce, 24 OHIO N.U. L. REV. 795 (1998).
  4948.  
  4949. jonald_fyookball [9:21 AM]
  4950. well you could but it may not change things...memes are very hard to change
  4951.  
  4952. csw [9:21 AM]
  4953. Roadtech Computer Systems Ltd v Mandata (Management and Data Services) Ltd (25 May 2000) unreported, High Court, Chancery Division HC 1999 04573 per Master Bowman.
  4954.  
  4955. jonald_fyookball [9:21 AM]
  4956. are you thinking of sending legal notices to exchanges pre-emptively
  4957.  
  4958. vlad2vlad [9:21 AM]
  4959. So who has the right to sue for the name or is it best to just let it go and focus on proving unlimited blocks are better.
  4960.  
  4961. csw [9:22 AM]
  4962. Also read the original metatag case
  4963.  
  4964. Playboy Enterprises Inc v Calvin Designer Label (1997) 44 USPQ 2d (BNA) 1156 (ND Cal). Was based on the use of registered trade marks of Playboy Enterprises Inc ("PEI"), PLAYMATE and PLAYBOY, as terms in the meta tags of their web sites as well as in the domain names used for their sites.
  4965.  
  4966. vlad2vlad [9:22 AM]
  4967. Sending letters to the exchanges might work. They can't afford a war with big law firms.
  4968.  
  4969. csw [9:22 AM]
  4970. Let us just say.... I have no fears for UASF
  4971.  
  4972.  
  4973. vlad2vlad [9:22 AM]
  4974. Especially if it's clear they're in the wrong
  4975.  
  4976. jonald_fyookball [9:23 AM]
  4977. i take Sun Tzu wisdom to heart
  4978.  
  4979. csw [9:23 AM]
  4980. Most of the *Big Exchanges* do not have enough runway to even consider a battle
  4981.  
  4982. jonald_fyookball [9:23 AM]
  4983. never underestimate your opponent
  4984.  
  4985. csw [9:24 AM]
  4986. I never do
  4987.  
  4988.  
  4989. [9:25]
  4990. I did not a year ago
  4991.  
  4992. [9:25]
  4993. I do not now
  4994.  
  4995. [9:25]
  4996. They did
  4997.  
  4998. vlad2vlad [9:25 AM]
  4999. It's Blockstream/core that has underestimated and dismissed Craig. That's an understatement. Things should get interesting as we approach August 1.
  5000.  
  5001. csw [9:27 AM]
  5002. Trintec Indus. v. Pedre Promotional Products, 04-1293 (Fed. Cir. Jan. 19, 2005)
  5003.  
  5004. _“Specific jurisdiction ‘arises out of’ or ‘relates to’ the cause of action even if those contacts are ‘isolated and sporadic.’ . . . General jurisdiction arises when a defendant maintains ‘continuous and systematic’ contacts with the forum state even when the cause of action has no relation to those contacts._
  5005.  
  5006. So, the US even has provisions to pull the Core developers into a case specifically and personally.
  5007.  
  5008. [9:28]
  5009. Jurisdiction may be found under D.C.'s long-arm statute
  5010.  
  5011. [9:28]
  5012. _Gibbons v Brown (1998) 1998 716 So. 2d 868; A car accident resulted following bad directions; the plaintiff sought to assert jurisdiction over non-resident on the grounds that the defendant had filed a lawsuit in the forum two years earlier stemming from the same incident (the plaintiff was not a party to that suit). The FL long arm-statute permitted jurisdiction over those “engaged in substantial and not isolated activity” within the state. It was held, bringing an action in the state two years earlier does not qualify as substantial activity, no personal jurisdiction. In the case of Dealing with a website (as was expressly not decided in Trintec Indus. v. Pedre Promotional Products) it is likely that a website would have to be shown to operate extensively or particularly target the location for jurisdiction to be applied. As an example, a site in the UK that operates a US page and sells product stating that they deliver to the US could be covered by the US long-arm statutes._ (edited)
  5013.  
  5014. jonald_fyookball [9:28 AM]
  5015. i was reading on r/btc about OKCoin stealing small amounts (less than 1m) btc.... a lot of players seem easily bribed, and very short term thinkers...
  5016.  
  5017. [9:29]
  5018. they arent thinking about legal ramafications
  5019.  
  5020. csw [9:29 AM]
  5021. Yet
  5022.  
  5023. vlad2vlad [9:29 AM]
  5024. Greed!
  5025.  
  5026. jonald_fyookball [9:29 AM]
  5027. they arent even smart enough to know their business reputation is more valuable than 97 BTC....how can you expect them to know to stay out of legal trouble
  5028.  
  5029. csw [9:30 AM]
  5030. More reading:
  5031.  
  5032. Quimbo, Rodolfo Noel S (2003) “Legal Regulatory Issues in the Information Economy”, e-ASEAN Task Force, UNDP-APDIP (MAY 2003); See also, JT03220432 (2007) “Mobile Commerce” DIRECTORATE FOR SCIENCE, TECHNOLOGY AND INDUSTRY COMMITTEE ON CONSUMER POLICY DSTI/CP(2006)7/FINAL, 16-Jan-2007
  5033.  
  5034. csw [9:36 AM]
  5035. uploaded this image: LLMD.jpg
  5036. Add Comment
  5037.  
  5038. csw [9:36 AM]
  5039. Just so you know...
  5040.  
  5041. When Greggie says my degrees are not real and has a paid hit piece on me....
  5042.  
  5043. [9:36]
  5044. It does not change the fact they all still exists.
  5045.  
  5046. [9:37]
  5047. Law
  5048.  
  5049. [9:37]
  5050. Economics
  5051.  
  5052. [9:37]
  5053. Computer science
  5054.  
  5055. [9:37]
  5056. Maths
  5057.  
  5058. [9:37]
  5059. Statistics
  5060.  
  5061. [9:37]
  5062. Physics
  5063.  
  5064. [9:37]
  5065. Business
  5066.  
  5067. [9:37]
  5068. Finance
  5069.  
  5070. [9:37]
  5071. ...
  5072.  
  5073. [9:37]
  5074. :slightly_smiling_face:
  5075.  
  5076. [9:37]
  5077. They are about to discover that the longer they call me out as a fraud....
  5078.  
  5079. [9:38]
  5080. The worse they are going to look.
  5081.  
  5082. vlad2vlad [9:39 AM]
  5083. Like I've been saying: Dr Wright, the one man wrecking crew. Got my popcorn ready for August 1st.
  5084.  
  5085. csw [9:40 AM]
  5086. Oh... I am not one man - me yes, but I have a really great team
  5087.  
  5088. [9:40]
  5089. That will not be secret too much longer
  5090.  
  5091. [9:41]
  5092. There are lawyers, finance people, mathematicians, computer scientists
  5093. Developers...
  5094.  
  5095.  
  5096. [9:41]
  5097. more actually
  5098.  
  5099. jonald_fyookball [9:43 AM]
  5100. Greg seems to be a tragic character.
  5101.  
  5102. [9:44]
  5103. a lot of potential and he chose to go down a road of some really bad karma
  5104.  
  5105. [9:44]
  5106. its kind of sad
  5107.  
  5108. [9:45]
  5109. but i guess that is where some people are at
  5110.  
  5111. vlad2vlad [9:46 AM]
  5112. I think they got corrupted by money
  5113.  
  5114. [9:46]
  5115. I bet AXA threw more money at them than they've ever seen so they have no loyalty to bitcoin
  5116.  
  5117. jonald_fyookball [9:46 AM]
  5118. yes , well that was the karmic test for Greg
  5119.  
  5120. [9:46]
  5121. and he failed
  5122.  
  5123. vlad2vlad [9:46 AM]
  5124. It seems that way
  5125.  
  5126. jonald_fyookball [9:47 AM]
  5127. i look at his old picture from Github...and compare that to the picture of him on blockstream.com....and its like i can literally see the life force drained from him
  5128.  
  5129. vlad2vlad [9:47 AM]
  5130. Hahaha
  5131.  
  5132. [9:47]
  5133. Good eye
  5134.  
  5135. [9:47]
  5136. All that cash soaked it up.
  5137.  
  5138. btcalbin [9:51 AM]
  5139. He's like a real life Walter White, in person he's this weak soft-spoken weasel, but give him the venue to lord over people online and he's an over-the-top sadistic monster
  5140.  
  5141. [9:52]
  5142. A decade ago people involved in Wikipedia already knew he was trash
  5143.  
  5144. jonald_fyookball [9:52 AM]
  5145. hah yea
  5146.  
  5147. jonald_fyookball [9:58 AM]
  5148. someone should do a spoof video of jesse pinkman telling hank "you dont understand, mr white is the devil. " scene...and dub in greg maxwell or nullc
  5149.  
  5150.  
  5151. btcalbin [10:00 AM]
  5152. i can't personally vouch for this, but over the years I've heard many accounts from people of the downright psychotic direct messages he sends to anonymous posters on like reddit, etc
  5153.  
  5154. jonald_fyookball [10:01 AM]
  5155. i sort of got one
  5156.  
  5157. btcalbin [10:01 AM]
  5158. did he brag to you about how rich he is?
  5159.  
  5160. [10:01]
  5161. just curious b/c that seems to be a common theme
  5162.  
  5163. jonald_fyookball [10:02 AM]
  5164. no
  5165.  
  5166. [10:04]
  5167. but if he is rich that makes his decisions even dumber.
  5168.  
  5169. [10:05]
  5170. i can understand (more) if you sell out because you'll go from poor to rich
  5171.  
  5172. btcalbin [10:10 AM]
  5173. my guess so far is that all of this goes way deeper than just mundane money concerns, the guy is vain and self-important on a level that's almost impossible to wrap your head around
  5174.  
  5175. csw [10:13 AM]
  5176. I guess Greggie also did not believe that a person could be an overqualified git like me who refuses to get out of Uni :wink:
  5177.  
  5178. [10:14]
  5179. Too easy to attack without really checking :wink:
  5180.  
  5181. [10:14]
  5182. Oh well... he is about to learn
  5183.  
  5184. btcalbin [10:21 AM]
  5185. I suppose you're like the worst possible person for him to deal with, because he needs to be the expert on everything
  5186.  
  5187. jonald_fyookball [10:21 AM]
  5188. @csw so, any advice for investors? Besides hodl?
  5189.  
  5190. [10:22]
  5191. i mean "opinion"
  5192.  
  5193. tomothy [10:22 AM]
  5194. Buy more.
  5195.  
  5196. [10:22]
  5197. Hold.
  5198.  
  5199. [10:22]
  5200. Sell top at 14k and rebuy at maybe 8k
  5201.  
  5202. lunar [10:22 AM]
  5203. yeah the ETH situation is getting pretty hot, they are closing the gap very fast. We need action not words.
  5204.  
  5205. jonald_fyookball [10:23 AM]
  5206. haha yeah i would like to buy more but not sure its worth it because it wouldnt increase my crypto holdings by a great % but would deplete my fiat holdings by a good %... my crypto holdings became worth more than my fiat in this boom.
  5207.  
  5208. btcalbin [10:24 AM]
  5209. the long term log trend is definitely holding
  5210.  
  5211.  
  5212. csw [10:24 AM]
  5213. @jonald_fyookball
  5214. Create apps - ones that increase use
  5215.  
  5216.  
  5217. jonald_fyookball [10:24 AM]
  5218. i have a few projects yes
  5219.  
  5220. btcalbin [10:25 AM]
  5221. i can't even tell you how many real life friends i have who are interested in Bitcoin just for online gambling
  5222.  
  5223. [10:25]
  5224. like there is crazy mainstream demand to use it brewing
  5225.  
  5226. jonald_fyookball [10:25 AM]
  5227. i was thinking today about getting that monaco visa card
  5228.  
  5229. [10:26]
  5230. heard about it?
  5231.  
  5232. [10:27]
  5233. its a debit card you can fund with BTC or ETH
  5234.  
  5235. tomothy [10:28 AM]
  5236. Coinbase shift works well. Fund w LTC/eth/btc
  5237.  
  5238. [10:28]
  5239. Should switch to private. We've jumped the shark here :innocent:
  5240.  
  5241. jonald_fyookball [10:28 AM]
  5242. i dont trust coinbase anymore, their CS is terrible
  5243.  
  5244. [10:29]
  5245. in any other industry, they'd have gone out of business
  5246.  
  5247. [10:29]
  5248. you can't take weeks to get back to customers
  5249.  
  5250. btcalbin [10:29 AM]
  5251. i wonder if maybe they're too selective about who they hire, like a while back i looked at their online test to interview customer service people, and it was all this like Bitcoin specific stuff
  5252.  
  5253. [10:30]
  5254. customer service doesn't need to know any of that
  5255.  
  5256. [10:30]
  5257. they just need to know how to look up your account in the computer!
  5258.  
  5259. tomothy [10:30 AM]
  5260. Nature of huge growth. Most exchanges/providers having similar trouble
  5261.  
  5262. jonald_fyookball [10:30 AM]
  5263. the thing is, I signed up with Gemini ....yeah was just gonna say... they too are taking weeks to verify me
  5264.  
  5265. [10:30]
  5266. demand is out of control
  5267.  
  5268. [10:31]
  5269. it could get even crazier
  5270.  
  5271. [10:32]
  5272. when there's office talk around the water cooler of "did you get some bits yet"
  5273.  
  5274. [10:32]
  5275. and Joe mainstream wants a piece
  5276.  
  5277. [10:32]
  5278. we'll probably have 6 figure coins
  5279.  
  5280. btcalbin [10:35 AM]
  5281. a few years ago just kind of to see what it was all about, i took a phone interview with them for a business position, i got the distinct impression that their strategy had something to do with getting as many people as possible on their API
  5282.  
  5283. [10:37]
  5284. this was prior to GDAX and at this time they were still pushing merchant adoption services
  5285.  
  5286. brad1121 [7:25 PM]
  5287. joined hardfork by invitation from @hmr. Also, @hankdasilva joined, @dagurval joined, @elliotolds joined, @ericwulff joined, @torusjkl joined, @bergun joined, @mengerian joined, @painlord2k joined along with some others.
  5288.  
  5289.  
  5290. ----- June 12th -----
  5291. jonald_fyookball [12:23 PM]
  5292. i pasted this in another slack, reposting here:
  5293.  
  5294. question...
  5295. 12:21
  5296. i am putting together a new article with some economic type graphs for the miners... one argument is that if BTC price followed , say, ethereum trajectory, miners' revenue would be so much more...HOWEVER, that doesnt account for difficulty increases... still, there would certainly be SOME increase.. any insight on the right math to use here?
  5297.  
  5298. csw [12:25 PM]
  5299. In a sec
  5300.  
  5301. csw [12:26 PM]
  5302. uploaded this file
  5303. Scale.xlsx
  5304. 31kB
  5305. Excel Spreadsheet
  5306. Click to download
  5307. Add Comment
  5308.  
  5309.  
  5310. csw [12:28 PM]
  5311. uploaded this file
  5312. Scale Calcs.xlsx
  5313. 22kB
  5314. Excel Spreadsheet
  5315. Click to download
  5316. Add Comment
  5317.  
  5318. csw [12:32 PM]
  5319. uploaded this file
  5320. Equilibrium Tx Fee distribution.xlsx
  5321. 35kB
  5322. Excel Spreadsheet
  5323. Click to download
  5324. Add Comment
  5325.  
  5326. csw [12:33 PM]
  5327. uploaded this image: image.png
  5328. Add Comment
  5329.  
  5330. csw [12:35 PM]
  5331. Rolling Bitcoin out to have 5 billion users means that there will be an average of 0.004 BTC per person. Just 4 MilliBitcoin and these will not be evenly distributed (as they shouldn't be).
  5332.  
  5333. This is 400,000 Satoshi per person globally.
  5334.  
  5335. The majority of people globally have less than 4000 USD in wealth.
  5336.  
  5337. As we approach the billions of users we will come to issues with. Right now, we have 51 bits of precision (this is where the 400,000 satoshi per person average comes from).
  5338.  
  5339. With billions of users, we will need more than 51 bits of precision to allow micro-payments. When this occurs, we will HAVE to send numbers as strings. This will mean that we have C++ or JavaScript (choose a language) convert the strings into a bignum library using a series of handlers.
  5340.  
  5341. When we get to this point and require more precision, it will be possible to implement fraction of satoshi payments. Bitcoin is always sent in Satoshi, so changing precision is not a simple task. But there was ways to implement an introduction of fractional Satoshi without breaking the existing blockchain information. This will require the creation of completely new forms of company and intermediaries. These do not exist at the moment so I cannot say with certainty what they would look like yet.
  5342.  
  5343. These would aggregate fractional payments of Satoshi. The protocol would not change, but it would be a form of payment channel. You enter a Satoshi and it is transferred when the full value is spent.
  5344.  
  5345. When we get to the stage that BTC is used by 5 billion people, I would expect that 1 Satoshi would be equal to up to 1 USD in purchasing power parity of today.
  5346.  
  5347. A microservice could hold 1 Satoshi and divide this in payment channels with 10EXP8 precision for a 32 bit value that can be written to the block in script (BTC script works on 32 bit values).
  5348.  
  5349. This way, one Satoshi could be split into 1 millionth of a cent by these aggregators for a small fee.
  5350.  
  5351. All on block and recorded, but with a means to allow the sale of a single match. I remember in Ghana seeing people on the side of the road who would buy a few boxes of matches and sell these one by one as people required them.
  5352.  
  5353. It also means word by work, second by second sales of media.
  5354.  
  5355. jonald_fyookball [12:50 PM]
  5356. having a look
  5357.  
  5358. csw [12:51 PM]
  5359. Just steal what you need with permission :wink:
  5360.  
  5361. [12:51]
  5362. Ignore the typos
  5363.  
  5364. jonald_fyookball [12:51 PM]
  5365. @csw were these in response to my question?
  5366.  
  5367. csw [12:52 PM]
  5368. Personal planning and notes
  5369.  
  5370. [12:52]
  5371. But yes
  5372.  
  5373. jonald_fyookball [12:52 PM]
  5374. it seems to be a lot more than what i was asking, let me try to rephrase my question
  5375.  
  5376. csw [12:53 PM]
  5377. of course
  5378.  
  5379. zbingledack [12:55 PM]
  5380. You want to know how miner profits increase with BTC price
  5381.  
  5382. csw [12:56 PM]
  5383. More use, more value
  5384.  
  5385. jonald_fyookball [12:56 PM]
  5386. lets ignore fees for a moment and deal with subsidies based on price. If lets say Y-T-D, BTC appreciated 300% and ETH appreciated 3000%, how much of that 300% translated into increased miner revenue? That's the basic question.
  5387.  
  5388. zbingledack [12:56 PM]
  5389. It really depends on how fast competition enters, as well
  5390.  
  5391. csw [12:57 PM]
  5392. 100% for revenue... but I think you want profit.
  5393.  
  5394. jonald_fyookball [12:57 PM]
  5395. thats what i meant
  5396.  
  5397. [12:57]
  5398. yes
  5399.  
  5400. zbingledack [12:58 PM]
  5401. While new miners are getting into the game, difficulty stays low despite a massive price increase. Unless you have miners and equipment resting on the sidelines, like after a big bear market. So it is complicated.
  5402.  
  5403. [1:00]
  5404. For example, if bitcoin suddenly went 100x, and it took a year for any new hashpower to come online, current miners would get all that profit for themselves (more than 100x in fact)
  5405.  
  5406. csw [1:00 PM]
  5407. Far more
  5408.  
  5409. [1:00]
  5410. As the revenue would stay low
  5411.  
  5412. zbingledack [1:00 PM]
  5413. Yes, because whatever their margin was
  5414.  
  5415. csw [1:00 PM]
  5416. And the Profit margin increase
  5417.  
  5418. zbingledack [1:01 PM]
  5419. Yep. So like if they had 10% margin, I guess it's about 1000x profit increase
  5420.  
  5421. jonald_fyookball [1:01 PM]
  5422. i guess i could simply calculate during this boom whats the price increase / difficulty increase ratio
  5423.  
  5424. zbingledack [1:01 PM]
  5425. Yeah, in the past. Historical data
  5426.  
  5427. csw [1:01 PM]
  5428. Profit is also better if you can risk holding
  5429.  
  5430.  
  5431. [1:02]
  5432. Rather than make and dump
  5433.  
  5434. jonald_fyookball [1:02 PM]
  5435. no , but you are right @zbingledack because: I think the price increase has been so dramatic that difficulty increases would not be greater even if the price appreciation was 10-fold
  5436.  
  5437. zbingledack [1:03 PM]
  5438. Yeah, only so much hashpower can be manufactured per month
  5439.  
  5440. jonald_fyookball [1:03 PM]
  5441. exactly, and that is likely near max already
  5442.  
  5443. csw [1:03 PM]
  5444. We are looking at double the hash rate in a thime frame for triple the price right now
  5445.  
  5446. jonald_fyookball [1:04 PM]
  5447. so this supports my argument very well
  5448.  
  5449. [1:04]
  5450. miners got robbed of profits
  5451.  
  5452. zbingledack [1:04 PM]
  5453. By Core? Oh yeah
  5454.  
  5455. jonald_fyookball [1:04 PM]
  5456. blockstream
  5457.  
  5458. [1:05]
  5459. and core yea
  5460.  
  5461. [1:06]
  5462. thanks for helping me think this through
  5463.  
  5464. csw [1:07 PM]
  5465. So, at around 7% profit (short term dumping)
  5466. We start at point 0 (7%)
  5467.  
  5468. Then, we have 50% of the returns for the same hardware by block
  5469.  
  5470. But 150% of the value.
  5471.  
  5472. 100 -> 50x3 = 150
  5473. So...
  5474.  
  5475. Profit could be as much as 8.5x as much - attracting many new miners...
  5476.  
  5477.  
  5478. jonald_fyookball [1:09 PM]
  5479. yes but they wont be able to get the asics quickly since production is already near max, right?
  5480.  
  5481. csw [1:09 PM]
  5482. Yes
  5483.  
  5484. [1:10]
  5485. And - a hold strategy makes more
  5486.  
  5487. zbingledack [1:12 PM]
  5488. And when ASIC production is maxed out the existing miners get it all as gravy for even longer
  5489.  
  5490. linzheming
  5491. [1:14 PM]
  5492. You forget the obsolete miners will be brought online.
  5493.  
  5494. jonald_fyookball [1:15 PM]
  5495. good point @linzheming ..what % of extra difficulty will that add?
  5496.  
  5497. zbingledack [1:15 PM]
  5498. If your costs are $10 per second and your revenue is $11/sec, you're making $1/sec.
  5499.  
  5500. If your revenue goes 10x, to $110/sec, while your costs stay the same at $10/sec, you're now making $100/sec.
  5501.  
  5502. 100x profit increase on a 10x price increase. Until new hashpower comes online.
  5503.  
  5504. linzheming
  5505. [1:16 PM]
  5506. Maybe the hash rate 1-2 yeas ago.
  5507.  
  5508. jonald_fyookball [1:16 PM]
  5509. makes sense
  5510.  
  5511. [1:16]
  5512. good stuff, i will use all this
  5513.  
  5514. linzheming
  5515. [1:17 PM]
  5516. The marginal cost of bitcoin is nearly 2600CNY now.
  5517.  
  5518. [1:18]
  5519. Far less than the price.
  5520.  
  5521. zbingledack [1:19 PM]
  5522. And even if global hashpower _doubles_ in the ensuing few months, so that your income is only $55/sec, you still are making 55x what you were before, just from that same 10x BTC price increase.
  5523.  
  5524. [1:20]
  5525. About $380 to mine a BTC? Wow
  5526.  
  5527. linzheming
  5528. [1:20 PM]
  5529. Difficulty increases rapidly at 10% per difficulty change.
  5530.  
  5531. jonald_fyookball [1:20 PM]
  5532. that's just electricty? not hardware
  5533.  
  5534. linzheming
  5535. [1:21 PM]
  5536. marginal cost.
  5537.  
  5538. zbingledack [1:21 PM]
  5539. Oh yeah, have to figure total costs over time
  5540.  
  5541. linzheming
  5542. [1:21 PM]
  5543. Man power, electricity, and so on.
  5544.  
  5545. jonald_fyookball [1:21 PM]
  5546. how are you defining that
  5547.  
  5548. zbingledack [1:22 PM]
  5549. And startup cost for new entrants
  5550.  
  5551. linzheming
  5552. [1:22 PM]
  5553. And if we consider about 800k CNY/Phash
  5554.  
  5555. jonald_fyookball [1:22 PM]
  5556. gtg bbl
  5557.  
  5558. linzheming
  5559. [1:23 PM]
  5560. In 18month
  5561.  
  5562. zbingledack [1:23 PM]
  5563. If profit margins are already huge, then the effect if price increases aren't so huge as I calculated above.
  5564.  
  5565. linzheming
  5566. [1:23 PM]
  5567. Maybe less than that.
  5568.  
  5569. zbingledack [1:24 PM]
  5570. For example if your costs are $1 per second and your revenue is $10/sec, you're making $9/sec.
  5571.  
  5572. If your revenue goes 10x, to $100/sec, while your costs stay the same at $1/sec, you're now making $99/sec.
  5573.  
  5574. Just a 10x profit increase on a 10x price increase. Until new hashpower comes online.
  5575.  
  5576. [1:25]
  5577. Much less than the 100x increase on a 10x price rise. So current margin matters a lot.
  5578.  
  5579. linzheming
  5580. [1:25 PM]
  5581. All miners doing hedging. That costs if price increases.
  5582.  
  5583. zbingledack [1:25 PM]
  5584. What kind of hedging? (edited)
  5585.  
  5586. [1:26]
  5587. Futures shorting?
  5588.  
  5589. linzheming
  5590. [1:26 PM]
  5591. They will lose part of bitcoin by shorting it using future trading.
  5592.  
  5593. zbingledack [1:26 PM]
  5594. Ah yes
  5595.  
  5596. [1:27]
  5597. So it depends on how heavily they are hedged
  5598.  
  5599. linzheming
  5600. [1:27 PM]
  5601. That helps stabilizing the price.
  5602.  
  5603. [1:28]
  5604. Maybe 30% to 50%
  5605.  
  5606. zbingledack [1:45 PM]
  5607. You mean if the BTC price doubles, the miners only feel a 50% to 70% increase in revenue (or do you mean in profit)?
  5608.  
  5609. [1:46]
  5610. And if it halves they only feel a 15% to 25% loss of revenue (or profit)?
  5611.  
  5612. komakino [3:24 PM]
  5613. joined hardfork by invitation from @klee, along with @wizzardtim. Also, @ola joined, @trevinhofmann joined, @ryanxcharles joined, @clemens joined.
  5614.  
  5615.  
  5616. ----- Today June 14th, 2017 -----
  5617. freetrader [2:46 AM]
  5618. https://blog.bitmain.com/en/uahf-contingency-plan-uasf-bip148/
  5619. blog.bitmain.com
  5620. UAHF: A contingency plan against UASF (BIP148) - blog.bitmain.com
  5621. Definitions UASF: User Activated Soft Fork. Developers add a mandatory rule set to change the node’ software, invalidating certain kinds of previously valid blocks after a flag day. This method requires no mining majority to support or activate a chain-split. The UASF proposal intends to make a 51% attack against the blockchain that has the …
  5622. Today at 12:50 AM
  5623.  
  5624. phoenix
  5625. [2:47 AM]
  5626. it's finally happening damnit
  5627.  
  5628. pesa [2:48 AM]
  5629. in layman's?
  5630.  
  5631. freetrader [2:49 AM]
  5632. The blog article uses quite good layman's terms.
  5633.  
  5634. [2:49]
  5635. Big block HF without re-org risk, and with replay protections so everyone will be able to trade safely.
  5636.  
  5637. [2:50]
  5638. At least 3 dev teams developing implementations for it.
  5639.  
  5640. [2:51]
  5641. One of the conditions of miners doing this is strong market sentiment in favor of a big block Bitcoin chain.
  5642.  
  5643. [2:51]
  5644. There will be no upper limit to block size in the future, but big miners will constrain themselves to starting off with 2MB blocks.
  5645.  
  5646. phoenix
  5647. [2:52 AM]
  5648. and a hard limit at 8MB for now, right ?
  5649.  
  5650. [2:52]
  5651. 2MB is the soft limit
  5652.  
  5653. freetrader [2:52 AM]
  5654. The "hard limit" is actually enforced by configurable setting in client (EB)
  5655.  
  5656.  
  5657. phoenix
  5658. [2:53 AM]
  5659. yep
  5660.  
  5661. freetrader [2:53 AM]
  5662. 2MB is what big miners will generate initially (they are always free to choose what size they put out)
  5663.  
  5664. [2:53]
  5665. The real block size will depend on network demand.
  5666.  
  5667. [2:53]
  5668. Lot's of people using? Blocks get bigger.
  5669.  
  5670. [2:53]
  5671. Nobody using? No need to produce huge blocks.
  5672.  
  5673. [2:54]
  5674. gtg.
  5675. Fun times!
  5676. :popcorn:
  5677.  
  5678.  
  5679. cryptorebel [2:54 AM]
  5680. I like this: "The block size will not be a part of hard-coded consensus rule for us in the future after the fork block. Miners who generate large blocks will be punished by economic incentives, but not limiting the block size." not sure if it means soft limit or hard limit though
  5681.  
  5682. [2:55]
  5683. soft limit I guess since hard limit will be 8MB
  5684.  
  5685. phoenix
  5686. [2:59 AM]
  5687. Yes, this is full on EC.
  5688.  
  5689.  
  5690. freetrader [3:35 AM]
  5691. https://github.com/Bitcoin-UAHF/spec
  5692. GitHub
  5693. Bitcoin-UAHF/spec
  5694. Technical specifications
  5695.  
  5696.  
  5697. [3:36]
  5698. Clients which will want to remain in consensus will need two things:
  5699. 1. let user configure their max blocksize.
  5700. 2. be able to handle the opt-in replay protection scheme published in the spec (it is two-way protection)
  5701.  
  5702. [3:37]
  5703. The replay protection is based on already well-tested code (BIP143, adapted to remove the SegWit aspects).
  5704.  
  5705. [3:37]
  5706. But don't worry, there will be clients with comprehensive tests.
  5707.  
  5708. [3:39]
  5709. I figure that the links to the sources will become public soon enough to give everyone about two months to study, steal code to adapt their own systems, and upgrade their nodes if they decide to follow the fork.
  5710.  
  5711. [3:39]
  5712. Ok, more like 48 days.
  5713.  
  5714. [3:39]
  5715. Now I _really_ have to go, bbl .
  5716.  
  5717. pesa [4:02 AM]
  5718. Interesting how almost all discussion on HF/SegWit/SegWit2X never consider nChain or CSW
  5719.  
  5720. [4:02]
  5721. https://www.reddit.com/r/btc/comments/6h1wpr/segwit2x_a_summary/
  5722. reddit
  5723. SegWit2x: A Summary • r/btc
  5724. Here's what we would **potentially** get following both the softfork and hardfork stages of SegWit2x: - ~4MB blocks. - weight discount...
  5725.  
  5726.  
  5727. [4:02]
  5728. the alternatives are always a mixed set of 'what we know'
  5729.  
  5730. [4:03]
  5731. never accounting for the emergence of a radically new alternative from a radically new faction
  5732.  
  5733. phoenix
  5734. [4:05 AM]
  5735. I'm sorry, but what is there to consider right now ?
  5736.  
  5737. pesa [4:06 AM]
  5738. depends on who you ask
  5739.  
  5740. phoenix
  5741. [4:06 AM]
  5742. I'm asking you
  5743.  
  5744. pesa [4:06 AM]
  5745. all the options above + CSWs assertions on thread private,
  5746.  
  5747. phoenix
  5748. [4:07 AM]
  5749. Code, research, proposals etc ? Are they there to put side by side with everything else that _is_ ? (edited)
  5750.  
  5751. [4:08]
  5752. till they are I can't consider anything, and neither will anyone else.
  5753.  
  5754. pesa [4:08 AM]
  5755. i will :slightly_smiling_face:
  5756.  
  5757. [4:08]
  5758. my point exactly
  5759.  
  5760. [4:09]
  5761. that seems to be the reasoning of Core, pro-Core and pro-UASF supporters
  5762.  
  5763. csw [4:09 AM]
  5764. Nor do you need to.... yet
  5765.  
  5766. [4:09]
  5767. :)
  5768.  
  5769. phoenix
  5770. [4:09 AM]
  5771. thanks craig
  5772.  
  5773.  
  5774. pesa [4:09 AM]
  5775. Just because they can't see it, they assume X alternatives
  5776.  
  5777. [4:10]
  5778. its an easy way to lose 'the game'
  5779.  
  5780.  
  5781. phoenix
  5782. [4:11 AM]
  5783. anyway @pesa, I don't have much more to tell you if you call this reasoning only partial to Core. (edited)
  5784.  
  5785. pesa [4:12 AM]
  5786. not just Core, see thread on r/btc. its everyone who doesnt have the whole picture - partial information
  5787.  
  5788. [4:13]
  5789. you too it seems, as you need hard evidence to consider other laternatives
  5790.  
  5791. [4:14]
  5792. when i saw Jon Matonis announce he's joining nChain, and the sudden emergence of nChain, i knew something was up
  5793.  
  5794.  
  5795. [4:14]
  5796. Jon is not crazy at all. And for a while, he was talking up miners and hashing power
  5797.  
  5798. csw [4:15 AM]
  5799. The best plans are not public until they are...
  5800.  
  5801. pesa [4:15 AM]
  5802. then followed the trail that led me to this thread, and found out nChain has a bagful of patents
  5803.  
  5804. phoenix
  5805. [4:15 AM]
  5806. @csw could you please explain to your disciple some epistemology ?
  5807.  
  5808.  
  5809. csw [4:15 AM]
  5810. 120 or so
  5811.  
  5812. [4:16]
  5813. Busy day... Remind me tomorrow @phoenix
  5814.  
  5815. phoenix
  5816. [4:16 AM]
  5817. :wink:
  5818.  
  5819. klee [5:52 AM]
  5820. https://twitter.com/LukeDashjr/status/874863403067731969
  5821.  
  5822. [5:52]
  5823. I am scared
  5824.  
  5825. brad1121 [5:54 AM]
  5826. I always enjoy a little bit of luke drama
  5827.  
  5828. phoenix
  5829. [6:03 AM]
  5830. ah those promises again, Luke is going full crusader it seems. Deus Vult
  5831.  
  5832. [6:04]
  5833. people are going to lose money because of these assholes
  5834.  
  5835. vlad2vlad [6:16 AM]
  5836. People are going to lose fortunes cause of these assholes.
  5837. 1 reply Today at 6:59 AM View thread
  5838.  
  5839. gregnie [6:17 AM]
  5840. I don’t think so.
  5841.  
  5842. [6:18]
  5843. If the minority chain got attacked, they can’t trade right?
  5844.  
  5845. phoenix
  5846. [6:22 AM]
  5847. if they get blocks in time they might have some time to transfer to exchanges
  5848.  
  5849. [6:22]
  5850. can you imagine the fees though ?
  5851.  
  5852. [6:22]
  5853. the congestion?
  5854.  
  5855. gregnie [6:24 AM]
  5856. Even you have 6 confirmations , you are not safe, and it’s very difficult to transfer.
  5857.  
  5858. [6:27]
  5859. The exchanges won’t accept deposit after the fork, unless the minority chain is stable for a while(maybe a few month).
  5860.  
  5861. phoenix
  5862. [6:27 AM]
  5863. I'm sure several will anticipate this and have coins in exchanges already
  5864.  
  5865. [6:27]
  5866. no exchange will stop trading, it's a golden opportunity for them to make money
  5867.  
  5868. [6:28]
  5869. perhaps it won't be the coins themselves, as many of these won't exist until the fork takes place, so maybe they'll have placeholders or something instead.
  5870.  
  5871. gregnie [6:30 AM]
  5872. yes, they may provide futures for trade. But it’s impossible to accept deposit if it’s not safe enough.
  5873.  
  5874. phoenix
  5875. [6:33 AM]
  5876. lots of planning for them ahead, gonna be a hot summer
  5877.  
  5878. erik.beijnoff [6:59 AM]
  5879. vlad2vlad: People already have in lost opportunity
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement