Advertisement
xhiggy

Sept 26

Sep 26th, 2017
126
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 130.93 KB | None | 0 0
  1. If eth chain is 300gb and bitcoin 168gb, which is the success?
  2.  
  3.  
  4. [10:38]
  5. I'd actually like to see the tx count inside each, eth could just be inefficient
  6.  
  7.  
  8. spunky
  9. [10:52 PM]
  10. If these ICOs were happening on BCC, I wonder how the tone would change?
  11.  
  12.  
  13. coinstash [10:55 PM]
  14. You have to be pretty smart to create an ICO on BCH. That alone excludes most of them.
  15.  
  16.  
  17.  
  18. [10:57]
  19. https://www.reddit.com/r/CryptoCurrency/comments/729oqc/underpants_gnomes_taking_over_crypto/
  20. reddit
  21. Underpants gnomes taking over crypto • r/CryptoCurrency
  22. According to https://www.coingecko.com/ico?locale=en there are 111 ICOs currently vying for attention with a further 54 opening within the next...
  23.  
  24.  
  25.  
  26. spunky [10:58 PM]
  27. ETH has a web interface for creating a new coin, so I heard. If btc cash had such a thing, would we still hate on ICOs I wonder? I think "Good for you, eth, good for you"
  28.  
  29.  
  30. coinstash [10:58 PM]
  31. Yes, I for one would still hate the majority of ICOs.
  32.  
  33.  
  34. spunky [10:59 PM]
  35. If we had btc cash ico, I might break off a lil' somethin' for it
  36.  
  37.  
  38. primordial
  39. [10:59 PM]
  40. I would like that they were based on BCH sure, at least they would have a sound base. I have never liked or used ETH
  41.  
  42.  
  43.  
  44. spunky [11:07 PM]
  45. Wow, ballsy [https://satoshidice.com/verifygame.html?id=2355]
  46.  
  47.  
  48.  
  49. coinstash [11:07 PM]
  50. @spunky It would depend on the purpose, the team and the plan. But yes, I'd be favourable to investing in a BCC ICO myself.
  51.  
  52.  
  53. [11:08]
  54. Someone risked 30 BCC on the roll of a die? Madness.
  55.  
  56.  
  57. primordial
  58. [11:09 PM]
  59. all they got was 1.5 for risking 30?
  60.  
  61.  
  62. spunky [11:09 PM]
  63. Yes but 94% chance to win
  64.  
  65.  
  66. bitsko [11:09 PM]
  67. low risk. I still couldn't do it
  68.  
  69.  
  70. coinstash [11:09 PM]
  71. 93% chance. Still risky.
  72.  
  73.  
  74. primordial
  75. [11:09 PM]
  76. ah makes sense
  77.  
  78.  
  79. spunky [11:09 PM]
  80. They are now number 1 on the "Big Wins" list
  81.  
  82.  
  83. primordial
  84. [11:09 PM]
  85. still negative long term since the return is only 5%
  86.  
  87.  
  88. coinstash [11:10 PM]
  89. Yeah, and the odds just dropped for everyone else.
  90.  
  91.  
  92.  
  93. [11:13]
  94. @mxmbt2
  95.  
  96.  
  97. mxmbt2 [11:13 PM]
  98. joined general by invitation from coinstash.
  99.  
  100.  
  101.  
  102. spunky
  103. [11:13 PM]
  104. Hi friend
  105.  
  106.  
  107. coinstash [11:14 PM]
  108. @mxmbt2 is from Melbourne, and like to promote Bitcoin. (edited)
  109.  
  110.  
  111. bitsko [11:17 PM]
  112. welcome!
  113.  
  114.  
  115. spunky [11:29 PM]
  116. I am contributing around 25 tx per block at this point hahaha
  117.  
  118. 1 reply 1 day ago View thread
  119.  
  120.  
  121. coinstash [11:31 PM]
  122. Bwahahahahaha
  123. https://www.reddit.com/r/Bitcoin/comments/728npe/i_almost_threw_up_all_over_the_table_when_i_saw/
  124. reddit
  125. I almost threw up all over the table when I saw that photo. How can we fix this? • r/Bitcoin
  126. 56 points and 21 comments so far on reddit
  127.  
  128.  
  129. 3 replies Last reply 1 day ago View thread
  130.  
  131.  
  132. spunky [11:32 PM]
  133. OMG YES!! HAHAHAA
  134.  
  135.  
  136. moonkin48 [11:32 PM]
  137. lol
  138.  
  139.  
  140. spunky [11:32 PM]
  141. Such a fucking baller shot too
  142.  
  143.  
  144. moonkin48 [11:32 PM]
  145. awesome
  146.  
  147.  
  148. spunky [11:32 PM]
  149. His expression like "sup bitches" (edited)
  150.  
  151. 1 reply 1 day ago View thread
  152.  
  153.  
  154. coinstash [11:32 PM]
  155. Anything that makes r/bitcoin puke has to be gold.
  156.  
  157.  
  158. spunky [11:36 PM]
  159. I'll bet they ate it again straight from the table, like a dog
  160.  
  161.  
  162. [11:37]
  163. :vomit: :dogdance: :knife_fork_plate:
  164.  
  165.  
  166. spunky [11:37 PM]
  167. so mature
  168.  
  169.  
  170. spunky
  171. [11:39 PM]
  172. Just scalped 0.5 bcc from satoshi dice, $25 of that is your money, wanna a refund dude? :stuck_out_tongue:
  173.  
  174.  
  175. coinstash [11:39 PM]
  176. Naah, I'm good. If $25 made that much difference I wouldn't have gambled it.
  177.  
  178.  
  179. spunky
  180. [11:40 PM]
  181. You sure? You're talking to a guy who thinks we're all one here :wink:
  182.  
  183.  
  184. coinstash [11:40 PM]
  185. Buy yourself some beers dude.
  186.  
  187.  
  188. spunky
  189. [11:41 PM]
  190. Cool cool, may as well quit while I'm ahead. Thanks for the cash XD
  191.  
  192.  
  193. coinstash [11:42 PM]
  194. Bloody dull since I started sleeping nights again. I miss the overnight rants.
  195.  
  196.  
  197. spunky
  198. [11:43 PM]
  199. Yeah day time in here is pretty boring
  200.  
  201.  
  202. [11:44]
  203. Oh look, a win with no payout tx [https://satoshidice.com/verifygame.html?id=2431]
  204.  
  205.  
  206. [11:44]
  207. Must be some kind of double spend protection
  208.  
  209.  
  210. spunky [11:54 PM]
  211. Oh noes!! I think the site is broken, payouts aren't coming through for everyone
  212.  
  213.  
  214. frido
  215. [11:55 PM]
  216. im getting an error
  217.  
  218.  
  219. [11:55]
  220. mempool something something through electroncash
  221.  
  222.  
  223. spunky
  224. [11:55 PM]
  225. Yes if you place too many unconfirmed bets the actual network rejects you, saying the tx chain is too long in the mempool
  226.  
  227.  
  228. frido [11:56 PM]
  229. ah shit, sorry guys im not normally like that XD
  230.  
  231.  
  232.  
  233. ----- Yesterday September 25th, 2017 -----
  234. lechango [12:27 AM]
  235. anyone think there's any truth to Amazon adding BTC?
  236.  
  237.  
  238. robbot [12:33 AM]
  239. none whatsoever
  240.  
  241.  
  242. [12:33]
  243. _if_ amazon were to do that
  244.  
  245.  
  246. [12:33]
  247. do you think they'd a) tell someone else and let them leak it before they announce it
  248.  
  249.  
  250. shemuel [12:33 AM]
  251. Did McAfee really say that?
  252.  
  253.  
  254.  
  255. robbot [12:33 AM]
  256. b) not announce it even with only a month away from the supposed launch date
  257.  
  258.  
  259. [12:34]
  260. and c) do it right in the middle of two contentious hard forks
  261.  
  262.  
  263. lechango [12:41 AM]
  264. yeah, it really wouldn't make any sense to do it now if they were going to
  265.  
  266.  
  267. frido
  268. [12:42 AM]
  269. tbh fuck that guy
  270.  
  271.  
  272. spunky [12:43 AM]
  273. Fuck McCofee?
  274.  
  275.  
  276. lechango [12:43 AM]
  277. Pretty sure the rumor didn't come from McAfee, correct me if i'm wrong tho
  278.  
  279.  
  280. frido [12:44 AM]
  281. mccaffee didnt say that.
  282.  
  283.  
  284. [12:44]
  285. he's smarter than that.
  286.  
  287.  
  288. phoenix [12:44 AM]
  289. It came from James Altucher afaik
  290.  
  291.  
  292.  
  293. spunky
  294. [12:44 AM]
  295. What a towel
  296.  
  297.  
  298.  
  299. lechango [12:44 AM]
  300. never heard of him
  301.  
  302.  
  303. phoenix
  304. [12:45 AM]
  305. he's a well known writer/investor in the US
  306.  
  307.  
  308. [12:45]
  309. https://en.wikipedia.org/wiki/James_Altucher
  310. Wikipedia
  311. James Altucher
  312. James Altucher is an American hedge fund manager, entrepreneur, best-selling author, venture capitalist, and podcaster. He has founded or co-founded more than 20 companies, including Reset Inc. and StockPickr, and says he failed at 17 of them. He has published eleven books, and he is a frequent contributor to publications, including The Financial Times, TheStreet.com, TechCrunch, Seeking Alpha, Thought Catalog, and The Huffington Post. (79kB)
  313.  
  314.  
  315. lechango [12:46 AM]
  316. ew
  317.  
  318.  
  319. [12:46]
  320. looks like quite the slimy fellow
  321.  
  322.  
  323. spunky
  324. [12:47 AM]
  325. I wonder if you could create a POS system where a third party could "sponsor" a business to support it, earning a little kickback from every purchase.
  326.  
  327.  
  328. [12:48]
  329. Sponsor buys all the equipment and business just needs to plug it in and learn what is a valid tx
  330.  
  331.  
  332. kensalomon [12:48 AM]
  333. Oh that happens with POS these days too I think
  334.  
  335.  
  336. lechango [12:49 AM]
  337. CIA is showing their hand if Amazon really does add BTC pre 2X fork
  338.  
  339.  
  340.  
  341. spunky
  342. [12:50 AM]
  343. Is that right? Hmm, I always thought the bank was the sponsor and the bank took all the kick backs and even charged a monthly fee for the privilege.
  344.  
  345.  
  346. [12:51]
  347. You could even arrange it so the sponsor drops off cash every month, so even if the business doesn't wanna deal with crypto right now, they will always wanna deal with cash. It would be no different to accepting fiat cash. Heh (edited)
  348.  
  349.  
  350. kensalomon [12:51 AM]
  351. Ah yea I was thinking more like renting to own type rental services
  352.  
  353.  
  354. [12:53]
  355. But yea I like the idea POS usually have a lot of time ins to how things work. It’s not like a card reader you can just add support for something and it work, it kind of revises things
  356.  
  357.  
  358. [12:53]
  359. Having written code on at least one type of POS application, it handles the confirmation of a transaction for you unless it’s cash
  360.  
  361.  
  362. spunky [12:54 AM]
  363. POS is kind of a chicken and egg problem, merchant doesn't wanna add it because they think they'll only get 4 tx every 12 months or something. Customer wants to spend but only a handful of merchants support it.
  364.  
  365.  
  366. kensalomon [12:54 AM]
  367. AcceptBitcoin.Cash dude, we need to get more merchants supporting it as payment
  368.  
  369.  
  370. spunky [12:55 AM]
  371. Ayyyeeeee love the design of that site, Semantic UI :heart: :heart:
  372.  
  373.  
  374. kensalomon [12:56 AM]
  375. But yes, I get it. We need more adoption. One day we might hit a critical mass where we don’t need these things but it’s like, “We’re starting a business, we are accepting AMEX, Visa and then Mastetcard or Bitcoin Cash?
  376.  
  377.  
  378. [12:56]
  379.  
  380.  
  381. spunky
  382. [12:56 AM]
  383. I'm more thinking of IRL type scenarios. If such a POS system existed, I could "sponsor" all the places I regularly shop and become their first customer. Defeats the chicken/egg issue
  384.  
  385.  
  386. kensalomon [12:56 AM]
  387. Ah
  388.  
  389.  
  390. [12:56]
  391. You’re overthinking
  392.  
  393.  
  394. [12:57]
  395. You need to first get the manufacturer of it to add support
  396.  
  397.  
  398. [12:57]
  399. Then they won’t care what it is, if they get cash at the end and it has lower fees than Amex or Visa they will gladly take it
  400.  
  401.  
  402. spunky [12:57 AM]
  403. Damn, yeah that would be the silver bullet
  404.  
  405.  
  406. [12:57]
  407. I'm more thinking of bottom up, that would be top down
  408.  
  409.  
  410. kensalomon [12:58 AM]
  411. Trust me they all hate Amex fees but know it’s how you get good customers
  412.  
  413.  
  414. [12:58]
  415. Visa is easy they’re middle of the road fees
  416.  
  417.  
  418. spunky [12:58 AM]
  419. The machine is the property of the merchant bank though, the fee would remain I'm guessing?
  420.  
  421.  
  422. kensalomon [12:59 AM]
  423. But hey, if they get the same money at the end of the month and it’s lower fees, they all would be happy to take that since they already raise prices to account for a certain percentage of transactions to cost a percentage in fees
  424.  
  425.  
  426. spunky [12:59 AM]
  427. Unless you're saying you could get the machine to subvert the banking system, via a plugin in the machine or something? So an open devkit anyone can build plugins for?
  428.  
  429.  
  430. kensalomon [12:59 AM]
  431. I mean, it’s more appealing the lower the fees
  432.  
  433.  
  434. [12:59]
  435. You would probably just have a monthly minimum fee if you don’t do enough processing
  436.  
  437.  
  438. [1:00]
  439. Like a maintenance fee from a bank for an account that sits idle with not enough funds in it, but if it gets enough activity they wave the fee
  440.  
  441.  
  442. [1:00]
  443. Well the company like Bitpay or something processing things might have something like that going on but maybe not
  444.  
  445.  
  446. [1:01]
  447. Ideally the lower the cost to have it running the more likely they are to accept it
  448.  
  449.  
  450. [1:05]
  451. Think of it this way, you’re a small ice cream shop with an iPad register at the front desk that runs square and this silly plastic iPad holders
  452.  
  453.  
  454. [1:07]
  455. Now a person comes in and they have a gift card QR code on their phone, or they scan your QR code and the value of the transaction magically turns to zero either way
  456.  
  457.  
  458. [1:07]
  459. Do you care which they used?
  460.  
  461.  
  462. spunky
  463. [1:08 AM]
  464. Yeah that's what I'm thinking, you could set up a business dedicated to merchant adoption. All infrastructure is owned by said sponsor. Sponsor is notified when a sale happens, sponsor can wire business the money or even drop in with cash. All merchant has to do is say "Yes".
  465.  
  466.  
  467. kensalomon [1:08 AM]
  468. Now what if the one scanning the QR code used Bitcoin Cash?
  469.  
  470.  
  471. [1:09]
  472. What you’re saying might be too much in respect that POS ties into so much you cannot just add a little contraption to a current system and call it a day.
  473.  
  474.  
  475. spunky [1:10 AM]
  476. You could totally build a dedicate device that handles it, purpose built, focused on low friction for the merchant
  477.  
  478.  
  479. kensalomon [1:10 AM]
  480. Your model works if you partner with a traditional bank to offer a good deal to anyone getting a business loan because you need to be in on the ground floor
  481.  
  482.  
  483. spunky [1:11 AM]
  484. Merchant could easily sponsor themselves and handle the backend of things, my experience shows that merchants are already "too busy" to look in to it.
  485.  
  486.  
  487. kensalomon [1:11 AM]
  488. I guess it could but I see it less adoptable
  489.  
  490.  
  491. spunky [1:11 AM]
  492. It creates the right incentives I think. When first good POS system arrives I'm gonna look in to it
  493.  
  494.  
  495. kensalomon [1:12 AM]
  496. I am all for that
  497.  
  498.  
  499. [1:12]
  500. Night now
  501.  
  502.  
  503. [1:16]
  504. Btw, @robbot is apparently working on a POS and hasn’t told me. WTF dude? I want in! (edited)
  505.  
  506.  
  507. coinstash [1:16 AM]
  508. @spunky I'm onto it mate.
  509.  
  510.  
  511. spunky
  512. [1:17 AM]
  513. Hell yeah @coinstash you following me on this tho? Like the whole merchant sponsor thing? I can think of several businesses I would start a conversation with
  514.  
  515.  
  516. coinstash [1:18 AM]
  517. Only model I can see workable is an open source system with the money being made from the conversions. Potential users are too sparsely located for anything else.
  518.  
  519.  
  520. [1:20]
  521. Fucking bank rang back to qualify me for a loan and I hit the wrong button on the phone. FML.
  522.  
  523.  
  524. spunky [1:23 AM]
  525. So long as the solution is cheaper than an iPad I will test the concept
  526.  
  527.  
  528. robbot
  529. [1:31 AM]
  530. >spunky [12:54 AM]
  531. >POS is kind of a chicken and egg problem, merchant doesn't wanna add it because they think they'll only get 4 tx every 12 months or something. Customer wants to spend but only a handful of merchants support it.
  532. (edited)
  533.  
  534.  
  535. [1:31]
  536. dont worry pal im on it
  537.  
  538.  
  539. coinstash [1:43 AM]
  540. After just having a discussion with a loan officer for the NAB and being refused an $80k loan on the basis that I don't have a job (I'm retired) I can't wait for the day when they all collapse and burn. I've been with these arseholes 35 years and can't get $80k. Fuck that.
  541.  
  542.  
  543. [1:44]
  544. Rigid immovable conditions. If they can't make you a slave to the system they don't want you as a customer.
  545.  
  546.  
  547. brad1121
  548. [1:44 AM]
  549. Yea, you wont be able to get a loan anywhere I suspect. Unless you have young working age family who will co-sign
  550.  
  551.  
  552. [1:45]
  553. Investment !== income in their eyes :face_with_rolling_eyes:
  554.  
  555.  
  556. coinstash [1:45 AM]
  557. I have probably one of the highest credit ratings available and want only $80k for a $250k house. The loan officer I spoke to was an utter moron.
  558.  
  559.  
  560. [1:46]
  561. They have $189k of my money in their bank right now.
  562.  
  563.  
  564. rightleftupper [1:46 AM]
  565. A 250k house in Australia?
  566.  
  567.  
  568. brad1121 [1:46 AM]
  569. We dont all live in sydney / melbourne :wink:
  570.  
  571.  
  572. coinstash [1:47 AM]
  573. It's a Public Trustee auction. But they want cash in 42 days guaranteed.
  574.  
  575.  
  576. brad1121 [1:47 AM]
  577. Our 4bed place was ~280
  578.  
  579.  
  580. rightleftupper [1:47 AM]
  581. @brad1121 nice, where abouts?
  582.  
  583.  
  584. brad1121 [1:47 AM]
  585. Regional Vic
  586.  
  587.  
  588. coinstash [1:47 AM]
  589. Ths is 100km north of Brisbane in the middle of a rural area. (edited)
  590.  
  591.  
  592. brad1121 [1:48 AM]
  593. Our place on the gold coast was ~260
  594.  
  595.  
  596. [1:48]
  597. 5 years ago
  598.  
  599.  
  600. coinstash [1:50 AM]
  601. I will never, ever ask a bank for anything again. They can go and get fucked.
  602.  
  603.  
  604. brad1121
  605. [1:51 AM]
  606. My parents couldn't get a 150k loan on ~70k a year in stable company dividends...
  607.  
  608.  
  609. [1:52]
  610. same story basically... Told old, not income. No repayment capacity
  611.  
  612.  
  613. coinstash [1:52 AM]
  614. Brad, I have tried three or four times to get a loan in my life. In every case they claimed it was impossible. If that's the case how is it these refugees and low income earners own houses? (edited)
  615.  
  616.  
  617. brad1121 [1:52 AM]
  618. centrelink is stable income
  619.  
  620.  
  621. [1:52]
  622. you can get a 250k loan on centrelink
  623.  
  624.  
  625. [1:53]
  626. it;s why half the people in my street even have houses
  627.  
  628.  
  629. [1:53]
  630. Centrelink is even better, because the bank can deduct from it automatically before it even gets to you
  631.  
  632.  
  633. coinstash [1:53 AM]
  634. Like I said, I have $189k in the bank and only want $80k so how do they think I can't survive for 11 months on the remaining $19k? (edited)
  635.  
  636.  
  637. brad1121
  638. [1:54 AM]
  639. 110% crock of :poop:
  640.  
  641.  
  642. coinstash [1:54 AM]
  643. In 11 months I get the full pension which is $800 per fortnight. (edited)
  644.  
  645.  
  646. brad1121
  647. [1:54 AM]
  648. They will probably give you that loan then....
  649.  
  650.  
  651. [1:54]
  652. fkcers (edited)
  653.  
  654.  
  655. coinstash [1:54 AM]
  656. Nope, no income no loan. That's EXACTLY what she said.
  657.  
  658.  
  659. brad1121 [1:55 AM]
  660. Not sure about pension, but the dole is income
  661.  
  662.  
  663. coinstash [1:55 AM]
  664. I'm not on the fucking dole, I'm retired. (edited)
  665.  
  666.  
  667. brad1121 [1:55 AM]
  668. Maybe you should go on the dole :facepalm:
  669.  
  670.  
  671. coinstash [1:55 AM]
  672. I don't qualify, I have $189k in the bank ferchissakes. (edited)
  673.  
  674.  
  675. brad1121 [1:56 AM]
  676. Yea tough spot. You could lose it all in an investment into some fancy online money you heard about :wink:
  677.  
  678.  
  679. coinstash [1:56 AM]
  680. My father's estate still owes me $40k and I have $100k in crypto.
  681.  
  682.  
  683. [1:57]
  684. I also own a house in NZ, two vehicles, two yachts and $20k worth of computers.
  685.  
  686.  
  687. brad1121
  688. [1:57 AM]
  689. yea, you're boned dole wise
  690.  
  691.  
  692. coinstash [1:57 AM]
  693. But a bank won't lend me $80k?? FFS. Madness.
  694.  
  695.  
  696. [1:57]
  697. I just told her "you bank people are mad" and hung up.
  698.  
  699.  
  700. brad1121 [1:58 AM]
  701. Tried a broker? Some have access to the less secure loan vendors who will loan to a sheep, they just up the interest rate
  702.  
  703.  
  704. coinstash [1:58 AM]
  705. No, fuck that. I have the credit rating, their conditions are just arbitrary and fuckwitted. (edited)
  706.  
  707.  
  708. [2:00]
  709. So, I'll just forget about this bargain. There will be others. And I'll pay cash and the bank will get nothing. No interest. Zero.
  710.  
  711.  
  712. brad1121
  713. [2:02 AM]
  714. There's another scam market there. The low income earners loans. Lend you money, charge higher interest, mortgage insurance and then harsh repayment rules like u can't pay it off faster.. setting up poor stupid people to default.
  715.  
  716.  
  717. coinstash [2:03 AM]
  718. If I could have gotten a loan in the 70s under those conditions I would have taken it. Instead I paid rent (dead money) for 40 years.
  719.  
  720.  
  721. brad1121
  722. [2:03 AM]
  723. Yea I knew to get out of the rent game asap
  724.  
  725.  
  726. [2:03]
  727. Now I'm the landlord
  728.  
  729.  
  730. coinstash [2:12 AM]
  731. I could have told her that I paid myself $20k out of crypto gains last year, but fuck them. It's none of their business where my money comes from.
  732.  
  733.  
  734. brad1121 [2:16 AM]
  735. 2nd that
  736.  
  737.  
  738. coinstash [2:16 AM]
  739. And because I had no other income it was tax free.
  740.  
  741.  
  742. [2:18]
  743. And I could take another $20k today tax free as well.
  744.  
  745.  
  746. [2:18]
  747. So with the $40k my father's estate still owes me, there's $60k of it already.
  748.  
  749.  
  750. [2:20]
  751. In fact I can get another $10k on my fucking credit card.
  752.  
  753.  
  754. brad1121
  755. [2:20 AM]
  756. Almost there
  757.  
  758.  
  759. coinstash [2:21 AM]
  760. Trouble is I don't have the $40k yet, my stupid sister has been dragging her heels finalizing the accounts since March.
  761.  
  762.  
  763. [2:23]
  764. She also screwed up and paid far too much in taxes. (edited)
  765.  
  766.  
  767. [2:27]
  768. Hopefully it will convert into CGT credits, which I am most happy with.
  769.  
  770.  
  771. [2:28]
  772. But until I see the full accounts I have no idea what she has been doing with the estate paperwork.
  773.  
  774.  
  775. brad1121 [2:35 AM]
  776. Bit irritating I'm sure.
  777.  
  778.  
  779. [2:35]
  780. The wifes work deals with all sorts of mess and rubbish regarding families fighting over estates.
  781.  
  782.  
  783. coinstash [2:36 AM]
  784. I should have received $346k from my father's estate. Due to her mismanagement it looks as if I'll only get $290k
  785.  
  786.  
  787. [2:37]
  788. Apparently the rest went to accountants, lawyers and the ATO.
  789.  
  790.  
  791. rt121212121 [2:37 AM]
  792. Man, you're bumming me out with your family drama. I hate hearing about the mistakes my own family make
  793.  
  794.  
  795. [2:37]
  796. I'm always like "I don't want to hear about how X made a stupid decision they didn't think about"
  797.  
  798.  
  799. coinstash [2:38 AM]
  800. The problem was the will. It was a fucking nightmare.
  801.  
  802.  
  803. otaci [2:39 AM]
  804. this has been resolved, i've received what was due from satoshi dice
  805.  
  806.  
  807.  
  808. rt121212121 [2:39 AM]
  809. Can't you take her to court and get the losses taken out of her share :slightly_smiling_face:
  810.  
  811.  
  812. coinstash [2:39 AM]
  813. Until I have accounts I don't even know what the hell she did.
  814.  
  815.  
  816. rt121212121 [2:40 AM]
  817. Hmm, do I want to put myself through the pain of watching the new social justice star trek.. I kind of feel like I have to see how bad it is in their communist future where there is no bitcoin
  818.  
  819.  
  820. coinstash [2:41 AM]
  821. Don't they have Galactic Credits or something?
  822. 1 reply 1 day ago View thread
  823.  
  824.  
  825. rt121212121 [2:44 AM]
  826. > During an excursion to 1986-era San Francisco, Kirk told Spock about 20th century Earth, saying, "They're still using money. We need to get some."
  827.  
  828.  
  829. [2:44]
  830. > In 2364, Jean-Luc Picard tried to explain to Ralph Offenhouse, a financier from the 20th century, that there would be no need for his services any longer. "A lot has changed in three hundred years," said Picard. "People are no longer obsessed with the accumulation of 'things.' We have eliminated hunger, want, the need for possessions."
  831.  
  832.  
  833. [2:45]
  834. Commies.
  835.  
  836.  
  837. [2:45]
  838. Let's not pretend it wouldn't be a galactic venezuela. In a real future, it'd be bitcoin.
  839.  
  840.  
  841. kokansei [2:50 AM]
  842. If only they had stopped at "hunger and want"
  843.  
  844.  
  845. rt121212121
  846. [2:51 AM]
  847. who has the corner apartment, or the penthouse? which commie is most deserving?
  848. 1 reply 1 day ago View thread
  849.  
  850.  
  851. rt121212121 [2:51 AM]
  852. Or do they only build corner apartments in the tower and penthouse corners at that (edited)
  853.  
  854.  
  855. kokansei [2:51 AM]
  856. Here in the 21st century Western world, we also eliminated hunger and want... With capitalism, bitches
  857.  
  858.  
  859. [2:52]
  860. Just submit to Federation testing, and you will be assigned an appropriate dwelling, citizen
  861.  
  862.  
  863. rt121212121
  864. [2:52 AM]
  865. And appropriate job..
  866.  
  867.  
  868. kokansei [2:53 AM]
  869. Who needs money when you can brownnose your way to success by sucking Picard's dick?
  870.  
  871.  
  872. rt121212121
  873. [2:53 AM]
  874. Try approaching picard from another angle and then you wouldn't have to complain about your nose being brown?
  875.  
  876.  
  877.  
  878. [2:55]
  879. Anyway, bitcorn. :corn:
  880.  
  881.  
  882. hugobits88 [2:56 AM]
  883. Who ever placed 30 BCC on satoshi dice has balls of steel.
  884.  
  885.  
  886. [2:57]
  887. Transactions are on the rise thanks too
  888.  
  889.  
  890. [2:57]
  891. .....
  892.  
  893.  
  894. rt121212121 [2:57 AM]
  895. Hopefully satoshi dice have fixed the bugs with not paying out
  896.  
  897.  
  898. hugobits88 [2:58 AM]
  899. Ye... that does not sound good
  900.  
  901.  
  902. rt121212121 [2:58 AM]
  903. i expect that since @otaci got his payment, it should be fixed (edited)
  904.  
  905.  
  906. hugobits88 [2:58 AM]
  907. Thumbs up then
  908.  
  909.  
  910.  
  911. [2:59]
  912. I'm enjoying the momentum that has been created so far.
  913.  
  914.  
  915. [2:59]
  916. Bitcoin Cash in general.
  917.  
  918.  
  919. otaci [3:03 AM]
  920. hmm, not sure they've fixed the satoshi dice bug, but they are going through their logs and correcting ... this win has no tx at the time i wrote this https://satoshidice.com/verifygame.html?id=2679 (edited)
  921.  
  922.  
  923. [3:04]
  924. (note, its not mine)
  925.  
  926.  
  927. rt121212121 [3:06 AM]
  928. I wonder how profitable it is
  929.  
  930.  
  931. otaci [3:08 AM]
  932. it must be reasonably profitable - "On 18 July 2013, Erik Voorhees announced that SatoshiDice had been sold for 126,315 BTC, or US$12.4 million at the time of the announcement."
  933. 1 reply 1 day ago View thread
  934.  
  935.  
  936. lechango [3:09 AM]
  937. wow, so has someone just been sitting on it until now? Or possibly it was sold again?
  938.  
  939.  
  940. [3:09]
  941. 2% house edge, over time that definitely adds up.
  942.  
  943.  
  944. otaci [3:09 AM]
  945. maybe, dunno ... its bloody addictive
  946.  
  947.  
  948. coinstash [3:10 AM]
  949. US$12.4M ??? That's batshit insane. (edited)
  950.  
  951.  
  952. lechango [3:11 AM]
  953. even more insane is to think Voorhees may still be sitting on that 126K BTC
  954.  
  955.  
  956. hugobits88 [3:11 AM]
  957. Definitely a honey pot
  958.  
  959.  
  960. lechango [3:12 AM]
  961. lol..
  962.  
  963.  
  964. coinstash [3:12 AM]
  965. That's about half a billion today. Christ.
  966.  
  967.  
  968. hugobits88 [3:13 AM]
  969. Voorhees! What a deal!
  970.  
  971.  
  972. [3:15]
  973. Who owns it now?
  974.  
  975.  
  976. [3:18]
  977. Wiki says Voorhees conducted a share buyback
  978.  
  979.  
  980. rightleftupper [3:18 AM]
  981. I don't think anyone knows for sure who bough tit
  982.  
  983.  
  984. [3:18]
  985. > A rumor is out there that the site is operated by and licensed under a Costa Rica company, Blockchain Limitada, however, googling the name shows no results. It's mysterious, but so far I think they are doing a good job.
  986.  
  987.  
  988. [3:18]
  989. >https://bitcointalk.org/index.php?topic=1740448.0
  990. bitcointalk.org
  991. who owns satoshidice
  992. who owns satoshidice
  993.  
  994.  
  995. hugobits88 [3:25 AM]
  996. Has anyone here played around with Openbazaar 2.0?
  997.  
  998.  
  999. Jason C [3:26 AM]
  1000. a little, it only has a few test products last time i checked
  1001.  
  1002.  
  1003. hugobits88 [3:26 AM]
  1004. Could it be used world wide?
  1005.  
  1006.  
  1007. [3:27]
  1008. Including logistics.
  1009.  
  1010.  
  1011. lechango [3:28 AM]
  1012. you'd think there's only a handful of people who'd have 126K+ BTC, even back in 2013
  1013.  
  1014.  
  1015. Jason C [3:28 AM]
  1016. my understanding is it just connects buyers/sellers, providing a platform for sale - shipping still needs to be handled by seller (edited)
  1017.  
  1018.  
  1019. zquestz [3:28 AM]
  1020. sup all
  1021.  
  1022.  
  1023. [3:29]
  1024. seeing huge spikes in traffic for acceptbitcoin.cash :smiley:
  1025.  
  1026.  
  1027.  
  1028. hugobits88 [3:29 AM]
  1029. Wazzup!!
  1030.  
  1031.  
  1032. zquestz
  1033. [3:29 AM]
  1034. watching stats from the sites I helped launch this weekend :smiley:
  1035.  
  1036.  
  1037. hugobits88 [3:32 AM]
  1038. It's an awesome platform. I'll spread the word around my village. Might get a few merchants on-board. I live in a tourist hot spot..
  1039.  
  1040.  
  1041. [3:32]
  1042. A Bitcoin Cash ATM would be perfect in this location.
  1043.  
  1044.  
  1045. zquestz [3:33 AM]
  1046. I would love to see some BCC ATM's show up :smiley:
  1047.  
  1048.  
  1049. [3:33]
  1050. Not seeing them in SF yet
  1051.  
  1052.  
  1053. [3:33]
  1054. a couple that do BTC/ETH
  1055.  
  1056.  
  1057. hugobits88 [3:33 AM]
  1058. It's unfortunately slow in Africa.. we currently have only one ATM in South Africa and it's only Bitcoin
  1059.  
  1060.  
  1061. [3:34]
  1062. Really? A couple!
  1063.  
  1064.  
  1065. [3:35]
  1066. I keep reloading the page to enjoy the Bitcoin spinner.. nice! :+1:
  1067.  
  1068.  
  1069. blockextreme [3:51 AM]
  1070. I guess google believes :stuck_out_tongue: https://www.reddit.com/r/Bitcoin/comments/728npe/i_almost_threw_up_all_over_the_table_when_i_saw/ (edited)
  1071.  
  1072.  
  1073. csw [3:53 AM]
  1074. lol
  1075.  
  1076.  
  1077. blockextreme [3:59 AM]
  1078. csw a lot of folks here asking for the HK conference videos. Its hard to wait :stuck_out_tongue:
  1079.  
  1080. 2 replies Last reply 1 day ago View thread
  1081.  
  1082.  
  1083. frido
  1084. [4:02 AM]
  1085. Soon tm.
  1086.  
  1087.  
  1088. zquestz [4:04 AM]
  1089. has been wanting to see them for sure
  1090.  
  1091.  
  1092. coinstash [4:04 AM]
  1093. Meh. He probably has weird socks on anyhow.
  1094.  
  1095.  
  1096. frido [4:09 AM]
  1097. i got a reply from uber
  1098.  
  1099.  
  1100. [4:09]
  1101. "Send a note our way via the "Help" option in app and we'll connect."
  1102.  
  1103.  
  1104. [4:09]
  1105. https://twitter.com/Crypt0_PimP/status/912173329741643781
  1106. DigitaL_PimP @Crypt0_PimP
  1107. Please consider accepting #BitcoinCash for payments @Uber_Support - it’s fast and secure, with low fees! More @ http://acceptbitcoin.cash
  1108. TwitterYesterday at 12:34 AM
  1109.  
  1110.  
  1111. [4:09]
  1112. #winning boizz
  1113.  
  1114.  
  1115. zquestz [4:10 AM]
  1116. Woot!
  1117.  
  1118.  
  1119. [4:10]
  1120. Servers are humming, both bitcoincash.org and acceptbitcoin.cash are getting good traffic right now :smiley:
  1121.  
  1122.  
  1123. frido [4:11 AM]
  1124. allot of people joining?
  1125.  
  1126.  
  1127. [4:11]
  1128. i mean visiting?
  1129.  
  1130.  
  1131. zquestz [4:11 AM]
  1132. yep, exactly
  1133.  
  1134.  
  1135. [4:12]
  1136. lots of activity in china right now
  1137.  
  1138.  
  1139. [4:14]
  1140. anyhow must get sleep
  1141.  
  1142.  
  1143. [4:14]
  1144. talk to you all later
  1145.  
  1146.  
  1147. frido [4:19 AM]
  1148. GN.
  1149.  
  1150.  
  1151. [4:19]
  1152. Acceptbitcoin.cash fucking rocks.
  1153. RT guys.
  1154.  
  1155.  
  1156. cryptorebel [4:42 AM]
  1157. https://www.reddit.com/r/btc/comments/72azmp/csw_shadow_banned_on_bitcoin_lol_what_did_you/
  1158. reddit
  1159. CSW shadow banned on /bitcoin - LoL - What did you post - evil tech? • r/btc
  1160. 5 points and 0 comments so far on reddit
  1161.  
  1162.  
  1163.  
  1164. hyena [4:56 AM]
  1165. @frido what to think of those merchants who accept bitcoin cash via shapeshift? should such be listed on acceptbitcoin.cash ?
  1166. 3 replies Last reply 1 day ago View thread
  1167.  
  1168.  
  1169. cryptorebel [5:00 AM]
  1170. deadalnix seems to hate malleability doesnt seem to think it has much use case, is he wrong? https://www.reddit.com/r/btc/comments/721rd8/bitcoin_cash_whitepaper_released/dnh6alw/?context=3
  1171. reddit
  1172. Bitcoin Cash Whitepaper released! • r/btc
  1173. 126 points and 109 comments so far on reddit
  1174.  
  1175.  
  1176.  
  1177. [5:01]
  1178. hope he wont be pushing flex trans, i dont like flex trans
  1179.  
  1180.  
  1181. csw [5:02 AM]
  1182. He is wrong
  1183.  
  1184.  
  1185. [5:02]
  1186. And pushing flex trans will fork cash
  1187.  
  1188.  
  1189. [5:02]
  1190. Badically. It is death
  1191.  
  1192.  
  1193.  
  1194. singularity [5:11 AM]
  1195. Stop fudding CSW.
  1196.  
  1197.  
  1198. [5:12]
  1199. It worries me that instantly after BCC forked off of bitcoin you turn up and start using the exact same tactics I saw the blockstream gang use 2-3 years ago.
  1200.  
  1201.  
  1202.  
  1203. joeldalais
  1204. [5:18 AM]
  1205. its not fud
  1206.  
  1207.  
  1208. cryptorebel [5:18 AM]
  1209. we gotta nip this flex trans thing in the bud
  1210.  
  1211.  
  1212. joeldalais
  1213. [5:19 AM]
  1214. malleability has a use, is meant to be used, if you integrate flextrans then you destroy the purpose for which malleability was used in the 1st place
  1215.  
  1216.  
  1217. [5:19]
  1218. there is a weird fascination with "malleability MUST be fixed"
  1219.  
  1220.  
  1221. [5:19]
  1222. it doesn't
  1223.  
  1224.  
  1225.  
  1226. erik.beijnoff [5:20 AM]
  1227. As it is now, flextrans is implemented with a separate tx version. If you need malleability you can use the original tx type.
  1228.  
  1229.  
  1230. Jason C [5:20 AM]
  1231. what's the use case flex trans is enabling?
  1232.  
  1233.  
  1234.  
  1235. cryptorebel [5:21 AM]
  1236. if that is so, is there any danger, including economic danger of being forced off of the original tx type
  1237.  
  1238.  
  1239. erik.beijnoff [5:21 AM]
  1240. There’s always a danger in implementing new features in an existing system.
  1241.  
  1242.  
  1243. rightleftupper [5:21 AM]
  1244. it's too much, too early
  1245.  
  1246.  
  1247. erik.beijnoff [5:22 AM]
  1248. But it’s not forcing anyone off the existing tx type.
  1249.  
  1250.  
  1251. [5:22]
  1252. It’s just a suggested alternative format.
  1253.  
  1254.  
  1255. [5:23]
  1256. Aside, I don’t think anyone is pushing for network adoption of flextrans within a year or two.
  1257.  
  1258.  
  1259. [5:23]
  1260. Not that I am aware of anyways.
  1261.  
  1262.  
  1263. joeldalais
  1264. [5:24 AM]
  1265. within a year should hopefully be fine for csw to reveal more of the stuff he's doing, then hopefully people will see flextrans isn't needed, and in fact would be push us in the opposite of adoption
  1266.  
  1267.  
  1268. [5:24]
  1269. its great it exists, and great they did the work, but here's hoping people are just patient
  1270.  
  1271.  
  1272. erik.beijnoff [5:25 AM]
  1273. I agree. Implementation of new (protocol) features, apart from very minor ones, should be at least a year down the road. (edited)
  1274.  
  1275.  
  1276.  
  1277. joeldalais [5:26 AM]
  1278. one of the things that using malleability correctly will bring is - proper 0-conf - we really do want that
  1279.  
  1280.  
  1281. [5:26]
  1282. and security
  1283.  
  1284.  
  1285. erik.beijnoff [5:27 AM]
  1286. @Jason C to answer your question about the purpose of flextrans, my take on it is this:
  1287.  
  1288.  
  1289. [5:27]
  1290. 1. More compact transactions.
  1291.  
  1292.  
  1293. [5:27]
  1294. 2. More flexible over-the-wire format.
  1295.  
  1296.  
  1297. [5:27]
  1298. 3. Malleability.
  1299.  
  1300.  
  1301. [5:27]
  1302. (I think there was a fourth as well. :slightly_smiling_face: )
  1303.  
  1304.  
  1305. Jason C [5:28 AM]
  1306. how does that benefit the user?
  1307.  
  1308.  
  1309. cryptorebel [5:28 AM]
  1310. quadratic hashing but that was already fixed in Bitcoin Cash
  1311.  
  1312.  
  1313. erik.beijnoff [5:28 AM]
  1314. Compact transactions - increased network performance
  1315.  
  1316.  
  1317. Jason C [5:28 AM]
  1318. is network performance an issue for people?
  1319.  
  1320.  
  1321. brad1121
  1322. [5:29 AM]
  1323. I really dont get the big hooHah with changing the protocol... How often are we changing TCP/IP?
  1324.  
  1325.  
  1326. peggy [5:29 AM]
  1327. How much smaller would transactions be and does any important information get removed?
  1328.  
  1329.  
  1330. rightleftupper [5:29 AM]
  1331. double spend proof
  1332.  
  1333.  
  1334.  
  1335. erik.beijnoff [5:29 AM]
  1336. Improving network performance are changes for improving the network several years down the line. It is not aimed at current network load.
  1337.  
  1338.  
  1339. [5:29]
  1340. Which is tiny.
  1341.  
  1342.  
  1343. [5:30]
  1344. @peggy - I think it is in the area of 15% and no, information does not get removed.
  1345.  
  1346.  
  1347. rightleftupper [5:30 AM]
  1348. oh @joeldalais already mentioned ... scratch that
  1349.  
  1350.  
  1351. erik.beijnoff [5:30 AM]
  1352. Anyways - as I said, it’s a suggestion. I am not aware of any initiatives that are actively pushing for it for the moment.
  1353.  
  1354.  
  1355. csw [5:31 AM]
  1356. BS
  1357.  
  1358.  
  1359. erik.beijnoff [5:32 AM]
  1360. I either don’t see any need for malleability to be “fixed”, so I see no need to implement it for that matter.
  1361.  
  1362.  
  1363. rightleftupper [5:33 AM]
  1364. Bullshit or Blockstream? I can never tell the two apart these days :slightly_smiling_face:
  1365.  
  1366.  
  1367. erik.beijnoff [5:33 AM]
  1368. And with regards to network performance - you don’t have to change the protocol to make wire transfer more efficient. There are other ways to do that. (edited)
  1369.  
  1370.  
  1371. csw [5:33 AM]
  1372. Both
  1373.  
  1374.  
  1375. thedunlap [5:33 AM]
  1376. eh I knew CSW was gonna say that :wink:
  1377.  
  1378.  
  1379.  
  1380. csw [5:33 AM]
  1381. UDP is NOT used by Google, Not by Amazon Prime, NOT by Netflix
  1382.  
  1383.  
  1384. [5:34]
  1385. Not by exchanges
  1386.  
  1387.  
  1388. [5:34]
  1389. Not in high volume trades
  1390.  
  1391.  
  1392. [5:34]
  1393. There are reasons for this
  1394.  
  1395.  
  1396. Jason C [5:35 AM]
  1397. like they use their own networking protocol?
  1398.  
  1399.  
  1400. thedunlap [5:35 AM]
  1401. like they use TCP/IP
  1402.  
  1403.  
  1404.  
  1405. csw [5:35 AM]
  1406. No. HTTP
  1407.  
  1408.  
  1409. [5:35]
  1410. And TCP
  1411.  
  1412.  
  1413. [5:35]
  1414. The network protocol is not the issue everyone is making it to be
  1415.  
  1416.  
  1417.  
  1418. [5:39]
  1419. We DO NOT need Lightning - and it does not work in any event
  1420.  
  1421.  
  1422. [5:40]
  1423. We need to make ON CHAIN used
  1424.  
  1425.  
  1426. [5:40]
  1427. Here is the thing. YOU CANNOT trust TXID anyway as it is ALWAYS malleable - even in SegShit
  1428.  
  1429.  
  1430. [5:41]
  1431. They are discussing 3rd party malleability and this is not the "attack" and merchants always need to consider that a Double spend of an altered TX can occur
  1432.  
  1433.  
  1434. [5:42]
  1435. If they do not, they deserve to be lossed out of existence
  1436.  
  1437.  
  1438. [5:42]
  1439. Threshold Blinding - REAL confidentiality requires it.
  1440.  
  1441.  
  1442. mwilcox [5:43 AM]
  1443. lightning is literally less efficient
  1444.  
  1445.  
  1446. csw [5:43 AM]
  1447. No, it is utter crap based on the WRONG network form
  1448.  
  1449.  
  1450. mwilcox [5:43 AM]
  1451. ya
  1452.  
  1453.  
  1454. csw [5:43 AM]
  1455. That maths I tweeted - it is why it does not work
  1456.  
  1457.  
  1458. mwilcox [5:43 AM]
  1459. all I need is to send a p2p transaction and a copy to majority hashpower
  1460.  
  1461.  
  1462. csw [5:43 AM]
  1463. And why it cannot - it is never economical
  1464.  
  1465.  
  1466. mwilcox [5:43 AM]
  1467. none of this 10 hops nonsense
  1468.  
  1469.  
  1470. [5:44]
  1471. miners need to build the infrastructure
  1472.  
  1473.  
  1474. Jason C [5:44 AM]
  1475. afaict BCC currently has everything it needs to handle plenty transaction volume, only thing stopping it is getting more adoption (which current txn volume is ~3% BTC) (edited)
  1476.  
  1477.  
  1478. mwilcox [5:44 AM]
  1479. btw the whole point of bitcoin is that the transaction was recorded
  1480.  
  1481.  
  1482. csw [5:44 AM]
  1483. 10,000x
  1484.  
  1485.  
  1486. [5:44]
  1487. Not 100
  1488.  
  1489.  
  1490. [5:45]
  1491. 10,000x
  1492.  
  1493.  
  1494. Jason C [5:45 AM]
  1495. yea, dr evil moment
  1496.  
  1497.  
  1498.  
  1499. joeldalais [5:45 AM]
  1500. adoption with bcc is the same as before blockstream got their claws in - create onroads and use cases
  1501.  
  1502.  
  1503. mwilcox [5:45 AM]
  1504. 10,000 is not even crazy
  1505.  
  1506.  
  1507. csw [5:45 AM]
  1508. So, let us stop fucking about andf make this grow
  1509.  
  1510.  
  1511.  
  1512. [5:45]
  1513. There is a train coming before Nov.
  1514.  
  1515.  
  1516. [5:46]
  1517. I do not want more ppl standing watching the light (edited)
  1518.  
  1519.  
  1520. [5:46]
  1521. We have Core for that
  1522.  
  1523.  
  1524. mwilcox [5:46 AM]
  1525. ill be hiring another 100 ppl in next 12mo
  1526.  
  1527.  
  1528.  
  1529. csw [5:47 AM]
  1530. A good interview.
  1531.  
  1532. https://calvinayre.com/2017/09/25/business/beckys-affiliated-calvin-ayre-brilliance-bitcoin-londons-role-appeal-antigua-video/
  1533. CalvinAyre.com
  1534. Becky’s Affiliated: Calvin Ayre on the brilliance of Bitcoin, London’s role and an appeal for Antigua
  1535. Calvin Ayre has chosen to conduct his first video interview dedicated to the subject of Bitcoin here in London with CalvinAyre.com. (148kB)
  1536. Yesterday at 12:11 AM
  1537. 1 reply 1 day ago View thread
  1538.  
  1539.  
  1540. mwilcox [5:47 AM]
  1541. who cares about core tbh, if they want to bet their business on a dying chain thats their loss
  1542.  
  1543.  
  1544. csw [5:47 AM]
  1545. Yes, so lets stop trying to think we need to add shit to compete
  1546.  
  1547.  
  1548. mwilcox [5:47 AM]
  1549. i have put too much effort into explaining things to them
  1550.  
  1551.  
  1552. singularity [5:49 AM]
  1553. @csw does "fixing" malleability invalidate any of the works in your patents?
  1554.  
  1555.  
  1556. mwilcox [5:49 AM]
  1557. thats not how patents work
  1558.  
  1559.  
  1560. csw [5:49 AM]
  1561. No, it makes threshoilding and blinding REALLY a mess
  1562.  
  1563.  
  1564.  
  1565. joeldalais [5:49 AM]
  1566. calvin ayre, bit of a legend
  1567.  
  1568.  
  1569. csw [5:49 AM]
  1570. And the plan was to gift these to Cash
  1571.  
  1572.  
  1573. [5:50]
  1574. REAL confidential TXs
  1575.  
  1576.  
  1577.  
  1578. mwilcox [5:50 AM]
  1579. cash needs to show it can compete purely on block size
  1580.  
  1581.  
  1582. csw [5:50 AM]
  1583. _"In the version 1 of transactions there is a field "NLockTime" and the related sequence numbers in the inputs. Due to NLockTime being superseded by OP_CHECKLOCKTIMEVERIFY, the V4 version of transactions will not add support for any of these fields. Users can still use the version 1 transaction format if she chooses."_
  1584.  
  1585.  
  1586. singularity [5:50 AM]
  1587. @mwilcox Why?
  1588.  
  1589.  
  1590. csw [5:51 AM]
  1591. There are STILL uses of nLocktime
  1592.  
  1593.  
  1594.  
  1595. mwilcox [5:51 AM]
  1596. its a dangerous game if the core chain counterforks
  1597.  
  1598.  
  1599. [5:51]
  1600. its better for it to lose
  1601.  
  1602.  
  1603. csw [5:51 AM]
  1604. Having money that changes protocol on a regular basis is BAD
  1605.  
  1606.  
  1607.  
  1608. [5:51]
  1609. It NEEDS to be stable
  1610.  
  1611.  
  1612. [5:51]
  1613. Bug fixes - good
  1614.  
  1615.  
  1616.  
  1617. mwilcox [5:52 AM]
  1618. @csw I got 0ms sync working today
  1619.  
  1620.  
  1621. [5:53]
  1622. amazing bootstrap
  1623.  
  1624.  
  1625. joeldalais [5:54 AM]
  1626. regarding core, considering they're trying to change the network based on a false assumption, means that if even do fork more after that = gawd knows what fucking mess they'd be left with
  1627.  
  1628.  
  1629. mwilcox [5:55 AM]
  1630. doesnt matter
  1631.  
  1632.  
  1633. [5:55]
  1634. their dominance is threatened by a rising power
  1635.  
  1636.  
  1637. [5:55]
  1638. read your history books :slightly_smiling_face:
  1639.  
  1640.  
  1641. joeldalais [5:55 AM]
  1642. this is mostly the only attention i give them now, for historical records :smile: when cash emerged core died to me
  1643.  
  1644.  
  1645. mwilcox [5:57 AM]
  1646. thats not how bitcoin works
  1647.  
  1648.  
  1649. [5:57]
  1650. core dies when everyone realises
  1651.  
  1652.  
  1653. joeldalais
  1654. [5:58 AM]
  1655. shrug, to me it died, they don't know what they did to their own network and they can't compete with whats coming
  1656.  
  1657.  
  1658. [5:59]
  1659. but ye, i agree it "dies" fully when everyone realises, but i moved past that, time to focus just on growing bitcoin again
  1660.  
  1661.  
  1662.  
  1663. csw [6:02 AM]
  1664. A double spend is ALWAYS 1st party
  1665.  
  1666.  
  1667. [6:02]
  1668. There can be NO double spend by 3rd party
  1669.  
  1670.  
  1671. [6:02]
  1672. Logic 101
  1673.  
  1674.  
  1675. [6:03]
  1676. Malleability cannot result in double spends
  1677.  
  1678.  
  1679. [6:03]
  1680. The first party - in SegShit AND Flextrans can ALWAYS malleate a TX
  1681.  
  1682.  
  1683. csw [6:12 AM]
  1684. _The effect of leaving the signatures out of the calculation of the transaction-id implies that the signatures are also not used for the calculation of the merkle tree. This means that changes in signatures would not be detectable and open an attack vector._
  1685.  
  1686.  
  1687. [6:12]
  1688. This means, you NEED to wait for a block to be formed
  1689.  
  1690.  
  1691. [6:12]
  1692. To have security, you need to not have 0-conf
  1693.  
  1694.  
  1695. [6:12]
  1696. You cannot trust a user NOT to malleate and do an attack
  1697.  
  1698.  
  1699. [6:13]
  1700. This means we kill 0-conf
  1701.  
  1702.  
  1703. [6:13]
  1704. Still sound a good idea? (edited)
  1705.  
  1706.  
  1707.  
  1708. brad1121 [6:19 AM]
  1709. :muchwright: :raised_hands:
  1710.  
  1711.  
  1712. csw [6:20 AM]
  1713. Look at ther TX format
  1714.  
  1715.  
  1716. [6:20]
  1717. https://zander.github.io/posts/Flexible_Transactions/
  1718.  
  1719.  
  1720. [6:22]
  1721. _Transactions can be pruned (removing of signatures) after they have been confirmed. Then the size goes down to an average of 450 bytes or a median of 101 bytes_
  1722.  
  1723.  
  1724. [6:22]
  1725. That is what they keep wanting
  1726.  
  1727.  
  1728. [6:22]
  1729. To kill the Digital Sigs
  1730.  
  1731.  
  1732.  
  1733. [6:22]
  1734. Bitcoin IS a chain of digital Sigs
  1735.  
  1736.  
  1737. [6:23]
  1738. That quote is from Tom's Blog
  1739.  
  1740.  
  1741. shadders [6:30 AM]
  1742. Does he want everyone to run a full archival node? That's the only rationale I can think of for shrinking txs rather than pruning the whole tx once it's irrelevant. (edited)
  1743.  
  1744.  
  1745. hyena [6:34 AM]
  1746. I also had an argument regarding FlexTrans and keeping signatures out. My opinion is that since TX Malleability already has a poor-man's workaround with the help of CPFP we should not introduce radical changes in order to satisfy hypothetical need for a fix to TX malleability so that unicorn software would work if it was ever created in the first place :stuck_out_tongue:
  1747.  
  1748.  
  1749.  
  1750. csw [6:48 AM]
  1751. And onchain.
  1752.  
  1753.  
  1754. [6:48]
  1755. Not lightning
  1756.  
  1757.  
  1758. [6:49]
  1759. Miners are nodes
  1760.  
  1761.  
  1762. [6:49]
  1763. Stop the all must be a node crap
  1764.  
  1765.  
  1766. [6:49]
  1767. Companies are not evil
  1768.  
  1769.  
  1770. [6:49]
  1771. They are just associations of ppl
  1772.  
  1773.  
  1774. blockextreme [6:50 AM]
  1775. People believe in conspiracy because it makes them feels more intelligent.
  1776.  
  1777.  
  1778. hyena [7:07 AM]
  1779. https://twitter.com/govjventura/status/911710251849629696
  1780. speaking of conspiracies ... Jesse Ventura has been briefed on Bitcoin :smile: perhaps he will make another episode of "Conspiracy Theory" featuring Bitcoin
  1781. Jesse Ventura @GovJVentura
  1782. Thank you @rogerkver for explaining #bitcoin to me. https://pbs.twimg.com/media/DKcLoNeV4AApCpX.jpg
  1783. TwitterSep 23rd at 5:53 PM (174kB)
  1784. (edited)
  1785.  
  1786.  
  1787. csw [7:38 AM]
  1788. uploaded this image: image.png
  1789. Add Comment
  1790.  
  1791.  
  1792.  
  1793. csw [7:38 AM]
  1794. _we decided we want to instead just move the signatures._
  1795.  
  1796.  
  1797. [7:41]
  1798. Basically, Flex Trans decides that signatures are not needed
  1799.  
  1800.  
  1801. [7:41]
  1802. It also has this idea that things like nLockTime are obsolete
  1803.  
  1804.  
  1805. [7:41]
  1806. It changes the block as TXs have the sigs removed, hence 0-conf is again less secure
  1807.  
  1808.  
  1809. [7:42]
  1810. https://news.ycombinator.com/item?id=15055444
  1811.  
  1812.  
  1813. [7:42]
  1814. _Flextrans will provide the capability of Lightning Network on Bitcoin Cash as well._
  1815.  
  1816.  
  1817. [7:43]
  1818. Basically, they have segshit and now they want to add crap to Cash
  1819.  
  1820.  
  1821. [7:43]
  1822. _If they’re right, it also means the improvement will set the stage for the Lightning Network_ (edited)
  1823.  
  1824.  
  1825. csw [7:43 AM]
  1826. uploaded this image: image.png
  1827. Add Comment
  1828.  
  1829.  
  1830.  
  1831. csw [7:44 AM]
  1832. And Zander explains how he removes Tech debt with...
  1833.  
  1834.  
  1835. [7:45]
  1836. More technical debt and changes for the sake of changes
  1837.  
  1838.  
  1839. shadders [7:45 AM]
  1840. I agree that concept of sigs not being tied to the merkle tree is an awful idea. But can you explain for us mere mortals how zero conf is compromised by the tx id not being dependent on the sigs?
  1841.  
  1842.  
  1843. csw [7:46 AM]
  1844. Malleability is an issue of 1st party change
  1845.  
  1846.  
  1847. shadders [7:46 AM]
  1848. In terms that the layman can understand and proliferate across the interwebz....
  1849.  
  1850.  
  1851.  
  1852. csw [7:46 AM]
  1853. The issue is when a user signs several TXs
  1854.  
  1855.  
  1856. [7:47]
  1857. And nothing solves that
  1858.  
  1859.  
  1860. [7:47]
  1861. Not even schnoor
  1862.  
  1863.  
  1864. csw [7:47 AM]
  1865. uploaded this image: image.png
  1866. Add Comment
  1867.  
  1868.  
  1869.  
  1870. csw [7:47 AM]
  1871. _Signatures can still be changed by anyone who has access to the corresponding private keys._
  1872.  
  1873.  
  1874.  
  1875. [7:48]
  1876. The ONLY one who can double spend is the person WITH the keys
  1877.  
  1878.  
  1879. [7:48]
  1880. So, not a signle solution helps this
  1881.  
  1882.  
  1883. shadders [7:48 AM]
  1884. would this be more clearly stated as 'the user signs the same tx in several different ways with different resultant tx ids'?
  1885. Craig S Wright
  1886. The issue is when a user signs several TXs
  1887. Posted in #generalYesterday at 7:46 AM
  1888.  
  1889.  
  1890. erik.beijnoff [7:49 AM]
  1891. @shadders just a quick clarifier - in the current implementation of flextrans signatures are a part of the merkle tree; a block is not complete without them and cannot be recreated properly. I don’t know why Zander talk about pruning them, maybe the context is in relation to segwit. I think it’s unfortunate that he does.
  1892.  
  1893.  
  1894. csw [7:49 AM]
  1895. scriptSig malleability is also not a problem (and has uses in contracts) but that is killed by killing these forms of script
  1896.  
  1897.  
  1898. [7:50]
  1899. He has the idea that they can be removed later
  1900.  
  1901.  
  1902. [7:50]
  1903. FT first
  1904.  
  1905.  
  1906. [7:50]
  1907. Prune next
  1908.  
  1909.  
  1910. otaci [7:53 AM]
  1911. Maybe a dummies guide to how to deal with malleability as a developer?
  1912.  
  1913.  
  1914. csw [7:53 AM]
  1915. If we had time, just to have things stable for 6 months, all of this would occur
  1916.  
  1917.  
  1918. [7:53]
  1919. The longer we run about politicing, the less we do
  1920.  
  1921.  
  1922.  
  1923. shadders [7:54 AM]
  1924. The wider community has been conditioned to believe malleability is a fault... It may not have any substantial downside if you're correct... But until people believe it has an upside the public discourse on the subject will be one sided... So please address that... Doesn't have to be a mathematical proof...
  1925.  
  1926.  
  1927. blockextreme [8:06 AM]
  1928. Just a fact nothing but a fact: https://twitter.com/mikerelentless/status/911993165946777605
  1929. Michael Matthews @mikerelentless
  1930. The chart that #Segwit Lovers hate!
  1931.  
  1932. BitcoinCash profitability is steadily rising!
  1933.  
  1934. Just look at the trend lines! Show more…
  1935. TwitterSep 24th at 12:38 PM (56kB)
  1936.  
  1937.  
  1938. hyena [8:33 AM]
  1939. If Bitcoin wishes to maintain its position as the base currency for all the others then it should be extremely conservative with its changes. It's key for success is not those technical bells and whistles but actual stability, simplicity and robustness. Technical debt should be removed but not in a way that makes Bitcoin more complex but in a way that makes the protocol more simple.
  1940.  
  1941.  
  1942. csw [9:00 AM]
  1943. Exactly
  1944.  
  1945.  
  1946. [9:00]
  1947. Get merchants and adoption first
  1948.  
  1949.  
  1950.  
  1951. topolino [9:02 AM]
  1952. @csw - not to interject, but have you seen the community project that I and few others have launched yesterday? https://acceptbitcoin.cash ? (edited)
  1953.  
  1954. 4 replies Last reply 23 hours ago View thread
  1955.  
  1956.  
  1957. topolino [9:03 AM]
  1958. Our goal is to help foster merchant adoption
  1959.  
  1960.  
  1961. [9:03]
  1962. hoping this will be a good tool that the community can use to achieve that (edited)
  1963.  
  1964.  
  1965. csw [9:03 AM]
  1966. Yes, great work !
  1967.  
  1968.  
  1969. topolino [9:04 AM]
  1970. Thanks much! Means a lot! We'll be doing our best onwards.
  1971.  
  1972.  
  1973. blockextreme [9:04 AM]
  1974. Yep great job!
  1975.  
  1976.  
  1977.  
  1978. hyena [9:28 AM]
  1979. who owns bitcoin.cash btw?
  1980.  
  1981.  
  1982. [9:29]
  1983. ... nvm, some squatter --- "We require a minimum offer of $100,000 USD to start any negotiations. Crypto also accepted."
  1984.  
  1985.  
  1986. kensalomon [9:34 AM]
  1987. I snapped up acceptbitco.in before we launched
  1988.  
  1989.  
  1990. hyena [9:38 AM]
  1991. I'm still squatting on rockpaperbitcoin.com :sweat_smile: some day I will develop something for it, some day ... I figured that if https://www.rockpapershotgun.com/ is a rather popular website then my name also has a chance
  1992. rockpapershotgun.com
  1993. Rock, Paper, Shotgun - PC Game Reviews, Previews, Subjectivity |
  1994. Rock, Paper, Shotgun - PC gaming news, previews, reviews, opinion
  1995.  
  1996.  
  1997. coinstash [9:46 AM]
  1998. Nice little breakout there.
  1999.  
  2000.  
  2001. coinstash [9:56 AM]
  2002. Just on new business ideas, I'm inspiring our Filipino friend Neiljon to set up a website selling BCC items similar to the t-shirt / mug / sticker websites already selling their wares. He has solid contacts with manufacturers that can turn out a shirt for $3.00 + shipping so it allows both of us to make a profit. He's doing the web design and I'll be providing the startup capital and business mentoring. (edited)
  2003.  
  2004.  
  2005. [9:59]
  2006. It's also a way for him to get BCC into the Philippines for resale. Right now it's hard to get due to the limited exchanges.
  2007.  
  2008.  
  2009. kensalomon [10:01 AM]
  2010. Nice! He was asking me about that. II think if he's hosting his own content, @robbot mentioend they are planning to offer a sweet low % fee option if you're running your own store and not using their hosting.
  2011.  
  2012.  
  2013. coinstash [10:02 AM]
  2014. Which is his website?
  2015.  
  2016.  
  2017. kensalomon [10:04 AM]
  2018. he co-founded Rocketr.net
  2019.  
  2020.  
  2021. coinstash [10:04 AM]
  2022. Ah OK. I haven't investigated that one yet, will check it out to see if there's something it provides that can work with that idea.
  2023.  
  2024.  
  2025. [10:06]
  2026. Payment processor. Right, that's handy.
  2027.  
  2028.  
  2029. kensalomon [10:07 AM]
  2030. He mentioned in thsis cahannel actually that they have two models now, a free one and a pro account or something that have different fees but they are planning to offer one to site that are usinng their own hosting a plan that takes 1% fee or less I think. I dont want to speak for him but it did sound like it would be a great offer for low margin merchants.
  2031.  
  2032.  
  2033. coinstash [10:08 AM]
  2034. The Voyager $10 a month deal looks awesome.
  2035.  
  2036.  
  2037. kensalomon [10:09 AM]
  2038. talk to @robbot when he wakes up (1-2 hours) if you have any questions,
  2039.  
  2040.  
  2041. coinstash [10:09 AM]
  2042. We will be self hosting so may be able to do better. I'll be interested to hear what he has going for BCC merchants.
  2043.  
  2044.  
  2045. kensalomon [10:10 AM]
  2046. @Tilian your faucet well has dried up
  2047.  
  2048.  
  2049. coinstash [10:10 AM]
  2050. Having all those payment options opens up a world of possibilities.
  2051.  
  2052.  
  2053. kensalomon [10:11 AM]
  2054. yea, if I remember correctly he said 0.5% fees for the self hosted option, but thats not an official statement yet, might change, talk to him though
  2055.  
  2056.  
  2057. [10:11]
  2058. maybe he can let you beta test that track
  2059.  
  2060.  
  2061. coinstash [10:11 AM]
  2062. I like the way you think. :slightly_smiling_face:
  2063.  
  2064.  
  2065. [10:11]
  2066. Even at 2% it's pretty good.
  2067.  
  2068.  
  2069. [10:13]
  2070. And free for Paypal Standard is awesome.
  2071.  
  2072.  
  2073. kensalomon [10:14 AM]
  2074. solid dude too
  2075.  
  2076.  
  2077. coinstash [10:24 AM]
  2078. Yeah, I've seen him here and he seems the kind I'd like to do business with.
  2079.  
  2080.  
  2081. robbot
  2082. [11:26 AM]
  2083. :blush:
  2084.  
  2085.  
  2086. coinstash [11:27 AM]
  2087. Hey buddy. Glad to see you. Just signed up, the service looks neat.
  2088.  
  2089.  
  2090. [11:28]
  2091. Just investigating Stripe Atlas right now, not sure if having a Delaware address would be a good idea taxwise.
  2092.  
  2093.  
  2094. robbot [11:29 AM]
  2095. Hm?
  2096.  
  2097.  
  2098. [11:31]
  2099. Sorry just woke up (interesting people are learning my sleep schedule already @kensalomon ) what do you mean coinstash
  2100.  
  2101.  
  2102. kensalomon [11:32 AM]
  2103. it was easy, you sleep like I want to sleep. going to bed late and sleeping till its basically afternoon
  2104.  
  2105.  
  2106. frido
  2107. [11:34 AM]
  2108. is that really a bad thing :stuck_out_tongue:
  2109.  
  2110.  
  2111. robbot [11:34 AM]
  2112. i think the trick is to just have a healthy dose of depression
  2113.  
  2114.  
  2115.  
  2116. coinstash [11:35 AM]
  2117. Stripe has a service called Atlas where they arrange for a Delaware corporation to be formed. But I don't really like the idea of becoming involved with the US tax system. The business will be a partnership between an Australian (me) and a Filipino. All manufacturing will be done in the Philippines.
  2118.  
  2119.  
  2120. robbot [11:35 AM]
  2121. ah i see
  2122.  
  2123.  
  2124. coinstash [11:36 AM]
  2125. I'll check out their tax rates for businesses first, might be a better deal. Or at least simpler to comply with anyhow.
  2126.  
  2127.  
  2128. robbot [11:37 AM]
  2129. well in any case our new plan we're working on will boast 0.5% fees with no monthly premium
  2130.  
  2131.  
  2132. [11:37]
  2133. so something to keep in mind
  2134.  
  2135.  
  2136. coinstash [11:37 AM]
  2137. Any specific conditions to get that rate?
  2138.  
  2139.  
  2140. robbot
  2141. [11:37 AM]
  2142. just be a self hosted merchant
  2143.  
  2144.  
  2145. coinstash [11:37 AM]
  2146. Cool, 'cos that's exactly what we'll be doing. (edited)
  2147.  
  2148.  
  2149. robbot
  2150. [11:37 AM]
  2151. perfect then
  2152.  
  2153.  
  2154. coinstash [11:39 AM]
  2155. Interestingly I was considering setting up a similar business about 18 months ago, but decided against it in the end. Of all the options rocketr is the best I've seen by a country mile.
  2156.  
  2157.  
  2158. robbot
  2159. [11:39 AM]
  2160. thanks :slightly_smiling_face: just let me kno
  2161.  
  2162.  
  2163. [11:39]
  2164. wait
  2165.  
  2166.  
  2167. [11:40]
  2168. what is a country mile
  2169.  
  2170.  
  2171. [11:40]
  2172. is that longer than a normal mile
  2173.  
  2174.  
  2175. coinstash [11:40 AM]
  2176. A bloody long way. It's an old expression.
  2177.  
  2178.  
  2179. robbot [11:40 AM]
  2180. i think ill start using it
  2181.  
  2182.  
  2183. coinstash [11:40 AM]
  2184. https://www.google.com.au/search?q=country+mile&ie=utf-8&oe=utf-8&client=firefox-b&gfe_rd=cr&dcr=0&ei=dSPJWaDEIYfp8wfD5JyIBA
  2185.  
  2186.  
  2187. robbot [11:41 AM]
  2188. https://english.stackexchange.com/a/32645
  2189. english.stackexchange.com
  2190. Origin of the term 'country mile'?
  2191. A 'country mile' is a term used casually in some areas of the English-speaking world to refer to a very great distance, but what's the origin of the term? Obviously 'mile' refers to what could be ...
  2192.  
  2193.  
  2194.  
  2195. [11:41]
  2196. fun
  2197.  
  2198.  
  2199. coinstash [11:43 AM]
  2200. Yeah. I think the general idea is that walking across hill and dale seems a lot further.
  2201.  
  2202.  
  2203. robbot
  2204. [11:43 AM]
  2205. yeah
  2206.  
  2207.  
  2208. coinstash [11:44 AM]
  2209. So, new option is available ... when?
  2210.  
  2211.  
  2212. robbot
  2213. [11:44 AM]
  2214. soon ^(tm)
  2215.  
  2216.  
  2217. [11:44]
  2218. realistically we should have it ready near the end of the month
  2219.  
  2220.  
  2221. coinstash [11:44 AM]
  2222. Hahahah. You get that a lot here.
  2223.  
  2224.  
  2225. [11:44]
  2226. The other standing joke is "two weeks (tm)"
  2227.  
  2228.  
  2229. robbot
  2230. [11:44 AM]
  2231. haha
  2232.  
  2233.  
  2234. coinstash [11:46 AM]
  2235. Anyhow, I've already set up ETH, BTC and BCH addresses. Considering whether it's worthwhile opening a new Paypal account for this.
  2236.  
  2237.  
  2238. [11:46]
  2239. And Stripe of course. But they want all sorts of data.
  2240.  
  2241.  
  2242. robbot [11:47 AM]
  2243. yeah stripes gonna want a shitload of data
  2244.  
  2245.  
  2246. coinstash [11:50 AM]
  2247. They assume that because I'm in Australia that I have a company and business number and shit. I'll be doing the legals in PH but they currently don't support that. Grrr.
  2248.  
  2249.  
  2250. [11:50]
  2251. So maybe fuck credit cards. Too much hassle with chargebacks anyhow.
  2252.  
  2253.  
  2254. robbot
  2255. [11:51 AM]
  2256. true, though does have much more usage than crypto
  2257.  
  2258.  
  2259. [11:51]
  2260. if you fuck cc's now, definitely still worth looking into in the future
  2261.  
  2262.  
  2263. [11:51]
  2264. at least until rocketr's goal of world-wide crypto integration succeeds
  2265.  
  2266.  
  2267. coinstash [11:52 AM]
  2268. Yeah, true. Then again I'd prefer to inspire people to use real money rather than live off credit anyhow.
  2269.  
  2270.  
  2271. robbot
  2272. [11:52 AM]
  2273. ah so not catering to americans at all thne
  2274.  
  2275.  
  2276. [11:52]
  2277. :joy:
  2278.  
  2279.  
  2280. coinstash [11:52 AM]
  2281. No, evidently not. :slightly_smiling_face:
  2282.  
  2283.  
  2284. [11:53]
  2285. A cc isn't as prevalent here, since we have great bank-issued debit cards usable anywhere.
  2286.  
  2287.  
  2288. [11:54]
  2289. Mine is Visa linked too so I can spend in any country in the world.
  2290.  
  2291.  
  2292. [11:54]
  2293. Of course that gets expensive because they really rip you off with exchange rates.
  2294.  
  2295.  
  2296. kensalomon [11:55 AM]
  2297. Anyone know who snagged the u/acceptbitcoincash reddit account? https://www.reddit.com/user/acceptbitcoincash
  2298. reddit.com
  2299. overview for acceptbitcoincash
  2300. reddit: the front page of the internet
  2301.  
  2302.  
  2303. coinstash [11:55 AM]
  2304. Some bastard jumped on your game Ken?
  2305.  
  2306.  
  2307. robbot
  2308. [11:55 AM]
  2309. man i dont know how every time im on some project
  2310.  
  2311.  
  2312. [11:55]
  2313. i _always_ forget to snag proper social media names
  2314.  
  2315.  
  2316. coinstash [11:56 AM]
  2317. Yeah, someone got my username on Twitter. Bastards.
  2318.  
  2319.  
  2320. kensalomon [11:56 AM]
  2321. anyways, I wanna know, they're talking like they represent the project and about our roadmap but I want to make sure they are actually with us and not just spewing crap that hurts our cause
  2322.  
  2323.  
  2324. coinstash [11:57 AM]
  2325. Yeah, that could be nasty.
  2326.  
  2327.  
  2328. kensalomon [11:57 AM]
  2329. like the reply here: https://www.reddit.com/r/btc/comments/72d3bt/every_day_with_this_bitcoin_cash/dnhjn4w/
  2330. reddit
  2331. Every day with this bitcoin cash • r/btc
  2332. Awesome, will do. Idea - add a 'petition' feature and ask users to sign Then send vendors the results (minus addresses) - could be the tipping...
  2333.  
  2334.  
  2335.  
  2336. robbot
  2337. [11:58 AM]
  2338. i pmed him
  2339.  
  2340.  
  2341. kensalomon [11:58 AM]
  2342. should have been asking to add it as an issue or the user behind this account should have added it as an issue so it would be tracked and discussed
  2343.  
  2344.  
  2345. [11:58]
  2346. I PMd too
  2347.  
  2348.  
  2349. coinstash [11:58 AM]
  2350. Well they are promoting your website, so it doesn't look too bad.
  2351.  
  2352.  
  2353. robbot
  2354. [11:59 AM]
  2355. true but could just be trying to become a voice for it and then take over once people recognize him as an authority in it or something
  2356.  
  2357.  
  2358. [11:59]
  2359. of course its probably more likely that im just paranoid
  2360.  
  2361.  
  2362. coinstash [12:00 PM]
  2363. Just because you're paranoid doesn't mean they won't get you in the end.
  2364.  
  2365.  
  2366. robbot [12:00 PM]
  2367. damn right
  2368.  
  2369.  
  2370. kensalomon [12:01 PM]
  2371. we set standards though, so he/she is not helping us maintain proper tracking, which eventually leads to things falling through the cracks. Also, they do not appear to ask here about things which means they are saying things without any knowledge
  2372.  
  2373.  
  2374. [12:01]
  2375. https://www.reddit.com/r/btc/comments/72cjiv/new_satoshi_bitcoin_cash_wallet_for_ios_android/dnhexvt/
  2376. reddit
  2377. [New] Satoshi Bitcoin Cash Wallet for iOS & Android • r/btc
  2378. Great news! Looking forward to a full (production-ready) release and we would love to add you over at _the Accept Bitcoin Cash initiative_ - ##...
  2379.  
  2380.  
  2381.  
  2382. [12:01]
  2383. that implies we might add them once they add production ready release? No! we added them to our issues list immediately to be added with a note saying they'
  2384.  
  2385.  
  2386. [12:01]
  2387. re in Beta
  2388.  
  2389.  
  2390. coinstash [12:02 PM]
  2391. I'm on a mission to fuck banks up now, after today's fiasco. Tried to get a loan and was refused on the basis that I don't have a steady income. I'm a fucking self-funded retiree.
  2392.  
  2393.  
  2394. kensalomon [12:02 PM]
  2395. also, they seem to spam the same thing, which is fine but we dont want to annoy people and add work for the mods who believe they are us.
  2396.  
  2397.  
  2398. kensalomon [12:03 PM]
  2399. uploaded this image: Okay, I like them now!
  2400. Add Comment
  2401.  
  2402.  
  2403.  
  2404. robbot [12:03 PM]
  2405. color me shocked
  2406.  
  2407.  
  2408. coinstash [12:04 PM]
  2409. Who's the altcoin here? ROFL
  2410.  
  2411.  
  2412. kensalomon [12:07 PM]
  2413. so all the announcement posts they've done have been removed
  2414.  
  2415.  
  2416. coinstash [12:07 PM]
  2417. Rob, I have a thought about currency options. Prices are usually quoted in USD online and yet Paypal and/or Stripe may need to be denominated in local currency.
  2418.  
  2419.  
  2420. [12:09]
  2421. It would be silly for me to quote prices in AUD since nobody would be easily able to calculate what that represents in their head.
  2422.  
  2423.  
  2424. robbot
  2425. [12:09 PM]
  2426. so to clarify, you'd like to display USD but receive AUD?
  2427.  
  2428.  
  2429. [12:10]
  2430. if so, is it possible to just set it up for USD and then allow paypal to convert to aud?
  2431.  
  2432.  
  2433. coinstash [12:10 PM]
  2434. Yup, exactly. Or display EUR and receive AUD. Depends on where I'm targeting sales. (edited)
  2435. 12 replies Last reply 22 hours ago View thread
  2436.  
  2437.  
  2438. coinstash [12:11 PM]
  2439. If I allow Paypal to convert then I get ripped off on the exchange.
  2440.  
  2441.  
  2442. csw [12:11 PM]
  2443. *Malleability*
  2444.  
  2445.  
  2446. [12:11]
  2447. Thing of the day
  2448.  
  2449.  
  2450. [12:12]
  2451. Who knows what this is?
  2452.  
  2453.  
  2454. coinstash [12:12 PM]
  2455. In terms of metallurgy I have a reasonable idea.
  2456.  
  2457.  
  2458. robbot
  2459. [12:12 PM]
  2460. changing txid post submission, yeah?
  2461.  
  2462.  
  2463.  
  2464. csw [12:12 PM]
  2465. Yes.
  2466.  
  2467.  
  2468. [12:12]
  2469. S to -S
  2470.  
  2471.  
  2472. [12:12]
  2473. Due to the symetric nature of EcDSA
  2474.  
  2475.  
  2476. kensalomon [12:13 PM]
  2477. so, you brought it up, got a proposal?
  2478.  
  2479.  
  2480. csw [12:13 PM]
  2481. 3rd Party for that at least
  2482.  
  2483.  
  2484. [12:13]
  2485. Proposal... for what?
  2486.  
  2487.  
  2488. csw [12:13 PM]
  2489. It is not an issue. That is the proposal
  2490.  
  2491. 2 replies Last reply 21 hours ago View thread
  2492.  
  2493.  
  2494. csw [12:13 PM]
  2495. https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki
  2496. GitHub
  2497. bitcoin/bips
  2498. bips - Bitcoin Improvement Proposals
  2499.  
  2500.  
  2501.  
  2502. kensalomon [12:13 PM]
  2503. a fix or for people to stop making it seem like the end of the world
  2504.  
  2505.  
  2506. csw [12:14 PM]
  2507. That addresses ECDSA S and -S by rejecting -s (edited)
  2508.  
  2509.  
  2510. [12:14]
  2511. No, education so they see it is all a lie
  2512.  
  2513.  
  2514. mohrt
  2515. [12:14 PM]
  2516. @kensalomon are you going to grab u/usebitcoincash or should I sqat it? :wink:
  2517.  
  2518.  
  2519. kensalomon [12:15 PM]
  2520. go for it, but really we only got useBitcoinCash as the twitter because it fit the character limit for usernames (edited)
  2521.  
  2522.  
  2523. mohrt
  2524. [12:15 PM]
  2525. oops meant that for accept-bcc-project
  2526.  
  2527.  
  2528. [12:15]
  2529. right, I just dont want in the wrong hands
  2530.  
  2531.  
  2532. kensalomon [12:15 PM]
  2533. true
  2534.  
  2535.  
  2536. deadr0ck [12:15 PM]
  2537. <-- u/acceptbitcoincash
  2538.  
  2539. (we had a little miscommunication)
  2540.  
  2541.  
  2542. coinstash [12:15 PM]
  2543. @mohrt It was YOU!!
  2544.  
  2545.  
  2546. kensalomon [12:15 PM]
  2547. move this back to the project channel, read my last post
  2548.  
  2549.  
  2550. mohrt
  2551. [12:15 PM]
  2552. what was me?
  2553.  
  2554.  
  2555. coinstash [12:15 PM]
  2556. Oh, wait ...
  2557.  
  2558.  
  2559. [12:16]
  2560. @deadr0ck just outed himself as the squatter.
  2561.  
  2562.  
  2563. deadr0ck [12:16 PM]
  2564. lol
  2565.  
  2566.  
  2567. robbot
  2568. [12:16 PM]
  2569. >@csw:
  2570. >No, education so they see it is all a lie
  2571.  
  2572.  
  2573. [12:17]
  2574. yeah good luck with that though
  2575.  
  2576.  
  2577. csw [12:17 PM]
  2578. uploaded this image: image.png
  2579. Add Comment
  2580.  
  2581.  
  2582.  
  2583. csw [12:18 PM]
  2584. I am going to start here.
  2585. 3 replies Last reply 21 hours ago View thread
  2586.  
  2587.  
  2588. kensalomon [12:18 PM]
  2589. yea @csw you cant come here spewing facts and truths, you've behind some evil corporation that wants to influence our already influenced Bitcoin!
  2590. ^Lol
  2591.  
  2592.  
  2593. csw [12:18 PM]
  2594. And work out
  2595.  
  2596.  
  2597. robbot
  2598. [12:18 PM]
  2599. you know what bitcoin cash really needs?
  2600.  
  2601.  
  2602. [12:19]
  2603. hats.
  2604.  
  2605.  
  2606. [12:19]
  2607. hats and girls wearing them on twitter
  2608.  
  2609.  
  2610. [12:19]
  2611. i think thats how corestream got so many no2x retards
  2612.  
  2613.  
  2614. csw [12:19 PM]
  2615. _Arguably, benign malleability is always present in that a given piece of data often has multiple encodings, and any non-malleable scheme can be transformed into a benignly malleable one by applying such an encoding,_
  2616.  
  2617.  
  2618. kensalomon [12:19 PM]
  2619. hats with dragons!
  2620.  
  2621.  
  2622. csw [12:19 PM]
  2623. So, anything they do always has some form of malleability.
  2624.  
  2625.  
  2626. robbot [12:19 PM]
  2627. yes
  2628.  
  2629.  
  2630. coinstash [12:19 PM]
  2631. Naah, we need hot chicks who enjoy having tequila shots done off their boobs. Or maybe that's just my kinky obsession.
  2632.  
  2633.  
  2634. csw [12:20 PM]
  2635. That already started
  2636.  
  2637.  
  2638. [12:20]
  2639. https://news.bitcoin.com/bither-ceo-bitclub-performing-segwit-related-attack-network/
  2640. Bitcoin News
  2641. Bither CEO: Bitclub is Performing Segwit-related Attack Against Network - Bitcoin News
  2642. Wen Hao, CEO of Bither wallet, a Chinese mobile bitcoin wallet, said early Friday morning that the Bitclub pool (which has 4% of the total hashrate) launch
  2643. Mar 10th at 4:31 AM
  2644.  
  2645.  
  2646.  
  2647. robbot [12:20 PM]
  2648. oh?
  2649.  
  2650.  
  2651. coinstash [12:20 PM]
  2652. The tequila shots? Do tell.
  2653.  
  2654.  
  2655. robbot [12:20 PM]
  2656. oh
  2657.  
  2658.  
  2659. [12:20]
  2660. no not the tequila shots
  2661.  
  2662.  
  2663. [12:20]
  2664. my dreams are crushed
  2665.  
  2666.  
  2667. coinstash [12:20 PM]
  2668. Urm ... (disappointment)
  2669.  
  2670.  
  2671. csw [12:21 PM]
  2672. https://youtu.be/OjTqdkusyJw?list=LLo5jhOoq7Snz-TVu-QmY0vg&t=128
  2673. YouTube Gedd Nicholls
  2674. Is Bitcoin Interesting? Up to you...
  2675.  
  2676.  
  2677.  
  2678. robbot
  2679. [12:21 PM]
  2680. YES.
  2681.  
  2682.  
  2683. [12:21]
  2684. yo that girl can have all my bitcoin legacies
  2685.  
  2686.  
  2687. csw [12:22 PM]
  2688. uploaded this image: image.png
  2689. Add Comment
  2690.  
  2691.  
  2692.  
  2693. csw [12:22 PM]
  2694. _ The “attack” involved not only extracting the signature, but also changing R to R’ in the elliptic curve cryptography._
  2695.  
  2696.  
  2697. robbot
  2698. [12:22 PM]
  2699. (i dont hold any bitcoin legacy anymore)
  2700.  
  2701.  
  2702. csw [12:22 PM]
  2703. That is NOT benign malleability, it is a miner crafting their own TXs. Miners CANNOT change other people's R values
  2704.  
  2705.  
  2706. robbot
  2707. [12:22 PM]
  2708. csw was this today
  2709.  
  2710.  
  2711. csw [12:23 PM]
  2712. In Bitcoin, the (r,s) pair is set following BIP 66 to not allow (R, -s)
  2713.  
  2714.  
  2715. [12:23]
  2716. S could in non-DER be changed to -s
  2717.  
  2718.  
  2719. [12:23]
  2720. See above
  2721.  
  2722.  
  2723. [12:23]
  2724. But it cannot have R changed without access to the PRIVATE Key
  2725.  
  2726.  
  2727. [12:23]
  2728. So, this is NOT a malleability attack
  2729.  
  2730.  
  2731. [12:24]
  2732. It was a lie as is all the BS
  2733.  
  2734.  
  2735. coinstash [12:24 PM]
  2736. Misreporting then?
  2737.  
  2738.  
  2739.  
  2740. [12:24]
  2741. Hmmm.
  2742.  
  2743.  
  2744. [12:24]
  2745. FUD.
  2746.  
  2747.  
  2748. csw [12:25 PM]
  2749. Yes.
  2750.  
  2751.  
  2752. [12:25]
  2753. So, where now is this need to change the protocol drastically?
  2754.  
  2755.  
  2756. [12:26]
  2757. Active malleability is something that Blocks solve, when it is in a block, it is not able to be altered
  2758.  
  2759.  
  2760.  
  2761. [12:26]
  2762. Benign malleability is a BIP 66 solution (and it was never an issue in any event) just bad process
  2763.  
  2764.  
  2765. kensalomon [12:26 PM]
  2766. so, BCC devs discussing rolling block generation would also solve? (edited)
  2767.  
  2768.  
  2769. robbot [12:26 PM]
  2770. bcc*
  2771.  
  2772.  
  2773. kensalomon [12:27 PM]
  2774. @robbot BCH please!
  2775.  
  2776.  
  2777. robbot [12:27 PM]
  2778. no. follow bitcoincash.org
  2779.  
  2780.  
  2781. csw [12:27 PM]
  2782. You cannot solve something that is not broken
  2783.  
  2784.  
  2785. robbot [12:27 PM]
  2786. ticker confusion isnt a battle we want to fight
  2787.  
  2788.  
  2789. coinstash [12:27 PM]
  2790. bchpls.com
  2791.  
  2792.  
  2793. robbot [12:27 PM]
  2794. just follow bitcoincash.org
  2795.  
  2796.  
  2797. kensalomon [12:27 PM]
  2798. nice! @coinstash
  2799.  
  2800.  
  2801. robbot [12:27 PM]
  2802. unify under a common flag
  2803.  
  2804.  
  2805. [12:27]
  2806. shit now coinstash has my ip
  2807.  
  2808.  
  2809. [12:28]
  2810. freenode all over again
  2811.  
  2812.  
  2813. csw [12:28 PM]
  2814. So, the change is, a user makes a change to a TX and doublespends.
  2815.  
  2816.  
  2817. coinstash [12:28 PM]
  2818. @robbot How do I have your IP?
  2819.  
  2820.  
  2821. csw [12:28 PM]
  2822. Double spends when you have a private key are not something that can be solved other than to stop RBF and other anti-0-conf ideas
  2823.  
  2824.  
  2825. robbot [12:28 PM]
  2826. oh im kidding, but presumably you could check your access logs now and see my ip
  2827.  
  2828.  
  2829. kensalomon [12:29 PM]
  2830. Just interjecting that I love that BSCore see Malleability as a gaping hole that needs fixing yet RDF is fine
  2831.  
  2832.  
  2833. coinstash [12:29 PM]
  2834. Oh right. I never read those.
  2835.  
  2836.  
  2837. csw [12:29 PM]
  2838. That is just it
  2839.  
  2840.  
  2841. robbot [12:29 PM]
  2842. sometimes i just tail -f my access logs when im out and about so i look like a cool hacker
  2843.  
  2844.  
  2845. csw [12:29 PM]
  2846. Malleability was the false flag used to make things like RBF and segwit seem needed
  2847.  
  2848.  
  2849. [12:31]
  2850. _More generally, if one or more of the signers of the transaction revise their signatures then the transaction remains valid and pays the same amounts to the same addresses, but the txid changes completely because it incorporates the signatures. The general case of changes to signature data (but not the outputs or choice of inputs) modifying the transaction is called scriptSig malleability._
  2851.  
  2852.  
  2853. [12:31]
  2854. https://bitcoincore.org/en/2016/01/26/segwit-benefits/
  2855. Bitcoin Core
  2856. Segregated Witness Benefits
  2857. Segregated Witness Benefits
  2858.  
  2859.  
  2860. [12:31]
  2861. That was called - a changed TX and SegWit does not fix this.
  2862.  
  2863.  
  2864. [12:31]
  2865. Then they say
  2866.  
  2867.  
  2868. [12:31]
  2869. _Segwit prevents third-party and scriptSig malleability by allowing Bitcoin users to move the malleable parts of the transaction into the transaction witness, and segregating that witness so that changes to the witness does not affect calculation of the txid._
  2870.  
  2871.  
  2872. [12:31]
  2873. We have A.
  2874.  
  2875.  
  2876. [12:32]
  2877. We do B
  2878.  
  2879.  
  2880. csw [12:32 PM]
  2881. But, it is done as a magic trick where you do not see that they talk about one senario and address a separate one
  2882. 1 reply 19 hours ago View thread
  2883.  
  2884.  
  2885. coinstash [12:33 PM]
  2886. Hocus Pocus.
  2887.  
  2888.  
  2889. csw [12:33 PM]
  2890. https://blockchain.info/tx/683f45578328242a06bc5c54acbcbe6e70a5435b4561fc8b0570a59ab09f8bfa?show_adv=true
  2891. blockchain.info
  2892. Bitcoin Transaction 683f45578328242a06bc5c54acbcbe6e70a5435b4561fc8b0570a59ab09f8bfa
  2893. View information about a bitcoin transaction 683f45578328242a06bc5c54acbcbe6e70a5435b4561fc8b0570a59ab09f8bfa
  2894.  
  2895.  
  2896. [12:33]
  2897. This is the example used
  2898.  
  2899.  
  2900. [12:34]
  2901. That is why BS Core say it needs fixing
  2902.  
  2903.  
  2904. [12:34]
  2905. The transaction is INTENTIONALLY designed to be able to be signed once and sent in separate forms.
  2906.  
  2907.  
  2908. [12:34]
  2909. That is ALSO not addressed in SegWit
  2910.  
  2911.  
  2912. [12:37]
  2913. *So, the so-called attack*
  2914.  
  2915.  
  2916. [12:38]
  2917. Alice makes a TX and sends it to Bob
  2918.  
  2919.  
  2920. [12:39]
  2921. Bob has control of a LARGE (>50%) of miners (or this is just a probabilistic senario.
  2922.  
  2923.  
  2924. [12:39]
  2925. Bob uses his nodes to accept (r,-s) (which was depreciated in BIP30, BIP66 with DER enforcement)
  2926.  
  2927.  
  2928. [12:40]
  2929. Alice watches for the TX ID to go to BOB and be on the blockchain
  2930.  
  2931.  
  2932. [12:41]
  2933. Alice IGNORES the Bitcoin address that she sent coin to. This will show Alice -> Bob, but she looks only to find the TXID associated with (r,s)
  2934.  
  2935.  
  2936. [12:41]
  2937. Alice decides... oh, this is slow... I will send again and again as I want Bob not to miss out
  2938.  
  2939.  
  2940. [12:42]
  2941. Alice watcher her wallet show unconfirmed TX after unconfirmed TX as her balance goes down
  2942.  
  2943.  
  2944. [12:42]
  2945. But states, "what the Fuck" and keeps sending
  2946.  
  2947.  
  2948. [12:42]
  2949. Bob runs off with the money
  2950.  
  2951.  
  2952. [12:42]
  2953. *So, seem realistic*
  2954.  
  2955.  
  2956. [12:42]
  2957. ???
  2958.  
  2959.  
  2960. coinstash [12:43 PM]
  2961. If Bob keeps insisting he didn't receive it, maybe.
  2962.  
  2963.  
  2964. [12:43]
  2965. And Alice would have to be plenty stupid.
  2966.  
  2967.  
  2968. csw [12:43 PM]
  2969. The TX is STILL recorded as Alice to Bob
  2970.  
  2971.  
  2972. [12:44]
  2973. If she uses Block Explorer, she can show Bob that the TX is there...
  2974.  
  2975.  
  2976. [12:44]
  2977. The assumption is that Bob will be looking for a TXID and that is also what Alice watches and that they ignore all other information
  2978.  
  2979.  
  2980. [12:45]
  2981. When we consider non-benign malleability, that is also known as a double spend. It cannot be changed with FT or SegWit
  2982.  
  2983.  
  2984. coinstash [12:45 PM]
  2985. Well I always search by address so it wouldn't catch me.
  2986.  
  2987.  
  2988. csw [12:45 PM]
  2989. _Before continuing, I want to re-emphasize that Bob can’t change where Alice’s money comes from, where it goes, or how much is sent. These parameters are all cryptographically signed by Alice, using her private key. Bob can really just change the actual txid shown to humans. How does this work exactly?_
  2990.  
  2991.  
  2992. [12:45]
  2993. So, as Core state....
  2994.  
  2995.  
  2996. [12:46]
  2997. *Bob can’t change where Alice’s money comes from, where it goes, or how much is sent.*
  2998.  
  2999.  
  3000. coinstash [12:46 PM]
  3001. In other words, it's so obscure as to not ever need "fixing" at all.
  3002.  
  3003.  
  3004. grabberfish
  3005. [12:47 PM]
  3006. SegWTF.
  3007.  
  3008.  
  3009. csw [12:47 PM]
  3010. And only if the wallet really is fucked
  3011.  
  3012.  
  3013. [12:47]
  3014. And Alice is dumb
  3015.  
  3016.  
  3017. [12:47]
  3018. The Miner attack on Malleability is - a classic double spend.
  3019.  
  3020.  
  3021. [12:47]
  3022. So, NOT solved
  3023.  
  3024.  
  3025. [12:49]
  3026. *Question*
  3027. In a basic TX (not one designed to be malleable with additions and which is easy to ignore), how many possible signature pairs are there for each Sig?
  3028.  
  3029.  
  3030. coinstash [12:50 PM]
  3031. I've seen fudsters saying that the BCC network isn't safe because a double spend would be easy with the low difficulty. Really? That would imply a miner is intent on footbullets for the sake of a few bucks.
  3032.  
  3033.  
  3034. csw [12:51 PM]
  3035. Yes, I have my coffee... my 100 million capital can burn (edited)
  3036.  
  3037.  
  3038. [12:51]
  3039. muhahha
  3040.  
  3041.  
  3042. [12:52]
  3043. So, we need to strip the Signatures.... stated reason, malleability.
  3044.  
  3045.  
  3046. robbot
  3047. [12:52 PM]
  3048. >csw [12:51 PM]
  3049. >Yes, I have my coffee...
  3050.  
  3051.  
  3052. [12:52]
  3053. that makes one of us...
  3054.  
  3055.  
  3056. [12:52]
  3057. wheres my damn latte
  3058.  
  3059.  
  3060. csw [12:52 PM]
  3061. LOL
  3062.  
  3063.  
  3064. coinstash [12:52 PM]
  3065. :coffee: Here
  3066.  
  3067.  
  3068. robbot [12:52 PM]
  3069. oh thank the lord
  3070.  
  3071.  
  3072. csw [12:52 PM]
  3073. Well, I will get you coffee for life for only 25million USD
  3074.  
  3075.  
  3076. [12:52]
  3077. :wink:
  3078.  
  3079.  
  3080. robbot
  3081. [12:52 PM]
  3082. oooh only $25m
  3083.  
  3084.  
  3085. [12:52]
  3086. do you take cash?
  3087.  
  3088.  
  3089. [12:52]
  3090. _bitcoin_ cash?
  3091.  
  3092.  
  3093. csw [12:52 PM]
  3094. BCH
  3095.  
  3096.  
  3097. [12:52]
  3098. :slightly_smiling_face:
  3099.  
  3100.  
  3101. tomothy [12:53 PM]
  3102. so, what's the point of eliminating signatures?
  3103.  
  3104.  
  3105. coinstash [12:54 PM]
  3106. It saves a few bytes.
  3107.  
  3108.  
  3109. tomothy [12:54 PM]
  3110. i mean, even if they introduce centralized authority, will they just re-introduce signatures?
  3111.  
  3112.  
  3113. robbot
  3114. [12:54 PM]
  3115. muh bytes
  3116.  
  3117.  
  3118. [12:54]
  3119. muh nibbles
  3120.  
  3121.  
  3122. kensalomon [12:54 PM]
  3123. makes them have patents around Bitcoin
  3124.  
  3125.  
  3126. tomothy [12:54 PM]
  3127. they're unilateral contracts as is, and fully binding
  3128.  
  3129.  
  3130. csw [12:54 PM]
  3131. NO, they will hold them on their own nodes that the rest of us do not see
  3132.  
  3133.  
  3134. kensalomon [12:55 PM]
  3135. oh, and maybe one day they will introduce showing us the signatures for a fee, for anyone wanting to keep the full chain on a new rPi node
  3136.  
  3137.  
  3138. tomothy [12:55 PM]
  3139. but theoretically, i could run a LN node if i had capital to do so as well, so i would see the txs, but still none of these nodes would be able to pull signature data, since it's gone and the signatures were never recorded
  3140.  
  3141.  
  3142. [12:55]
  3143. i mean, why don't you want signatures EVER viewable again?
  3144.  
  3145.  
  3146. coinstash [12:55 PM]
  3147. Gotta cater for dem satellites ...
  3148.  
  3149.  
  3150. tomothy [12:55 PM]
  3151. is it privacy through obscurity?
  3152.  
  3153.  
  3154. mengerian [12:55 PM]
  3155. @csw Have you looked at Tomas van der Wansem's Malleability fix proposal? https://github.com/tomasvdw/bips/blob/master/malleability-fix.mediawiki
  3156. - Leaves Tx format unchanged, except for re-defining "previous-tx" field for Tx inputs
  3157. - Merkle tree construction remains exactly the same, including Full sig data in Merkle leaf
  3158. GitHub
  3159. tomasvdw/bips
  3160. bips - Collection of Bitcoin Improvement Proposals
  3161.  
  3162. 1 reply 19 hours ago View thread
  3163.  
  3164.  
  3165. csw [12:55 PM]
  3166. Yes @tomothy
  3167.  
  3168.  
  3169. tomothy [12:56 PM]
  3170. i mean, if you take away signatures, you can bring into question the legal status of bitcoin (edited)
  3171.  
  3172.  
  3173. [12:56]
  3174. it' isn't fungible anymore
  3175.  
  3176.  
  3177. mohrt
  3178. [12:56 PM]
  3179. Great info on malleability. Do we have the entire argument captured in an article (say medium.com or?) so we can send folks there when the argument arises? The parrots need to be silenced :wink:
  3180.  
  3181.  
  3182. tomothy [12:56 PM]
  3183. you can't prove person A was person A and in fact paid person B
  3184.  
  3185.  
  3186. csw [12:56 PM]
  3187. @mengerian Why?
  3188.  
  3189.  
  3190. [12:56]
  3191. I am working on getting it all together
  3192.  
  3193.  
  3194.  
  3195. [12:57]
  3196. There are just so many false ideas to get fixed
  3197.  
  3198.  
  3199. [12:57]
  3200. It is taking time
  3201.  
  3202.  
  3203. mohrt
  3204. [12:57 PM]
  3205. thanks for that (edited)
  3206.  
  3207.  
  3208. tomothy [12:57 PM]
  3209. it's like borrowing someones gun, shooting yourself in the foot, and then yelling at the person to say that it's broke
  3210.  
  3211.  
  3212. [12:57]
  3213. bad analogy maybe but, none of this makes sense
  3214.  
  3215.  
  3216. [12:58]
  3217. except if you own the hospital and treatment and are the only hospital in town
  3218.  
  3219.  
  3220. [12:58]
  3221. but hey, remember to donate to LukeJR
  3222.  
  3223.  
  3224. [12:58]
  3225. because...?
  3226.  
  3227.  
  3228. csw [12:58 PM]
  3229. @mengerian That BIP seems ok, but for why? It is a fix for something that is easy to fix without all the changes and that does not address the real issue
  3230.  
  3231.  
  3232. tomothy [12:58 PM]
  3233. :trollface:
  3234.  
  3235.  
  3236. mengerian [12:58 PM]
  3237. Why do the Mallleability fix? Some of the miners seem to want it, I'm not sure precisely why.
  3238.  
  3239.  
  3240. robbot [12:59 PM]
  3241. `agendas`
  3242.  
  3243.  
  3244. csw [12:59 PM]
  3245. They have been taught the lie
  3246.  
  3247.  
  3248. mengerian [12:59 PM]
  3249. But at least that proposal leaves the construction of the Merkle tree unchanged
  3250.  
  3251.  
  3252. csw [12:59 PM]
  3253. Hardly a one of them understands that this idea is *Nonintentional malleability becomes impossible.* - but the attack is INTENTIONAL
  3254.  
  3255.  
  3256. [1:01]
  3257. _Preventing scriptSig malleability is being considered as well. Currently transactions with anything other than data push operations in their scriptSig are considered non-standard and are not relayed, and eventually this rule may extend to enforcing that the stack have exactly one item after execution. However doing that may interfere with later extensions to Bitcoin._
  3258.  
  3259.  
  3260. mengerian [1:01 PM]
  3261. Yeah, the originator of the Tx could still mine a block full of "malleated" sigs
  3262.  
  3263.  
  3264. csw [1:02 PM]
  3265. This is the other thing.
  3266.  
  3267.  
  3268. [1:02]
  3269. BS CORE have MAST and Alpha
  3270.  
  3271.  
  3272. [1:02]
  3273. They have been teaching us that scripts that can change are BAD
  3274.  
  3275.  
  3276. [1:02]
  3277. They want to have all the scripting as they have things to lock you into sidechains
  3278.  
  3279.  
  3280. tomothy [1:03 PM]
  3281. they want to break bitcoin
  3282.  
  3283.  
  3284. csw [1:03 PM]
  3285. Tomas does not and cannot fix non-benign malleability
  3286.  
  3287.  
  3288. mengerian [1:03 PM]
  3289. I don't have a strong opinion about malleability, but I like Tomas' approach because it makes the minimal change needed
  3290. So at least that way it can be evaluated more easily
  3291.  
  3292.  
  3293. csw [1:04 PM]
  3294. It is only when a block is mined that this is never possible
  3295.  
  3296.  
  3297. [1:04]
  3298. Before, it is probabilistic
  3299.  
  3300.  
  3301. [1:04]
  3302. Tomas van der Wansem has the best approach to a change that should not be made.
  3303.  
  3304.  
  3305. mengerian [1:04 PM]
  3306. Ha ha :slightly_smiling_face:
  3307.  
  3308.  
  3309. csw [1:05 PM]
  3310. Tomas of course also makes a form that is not compatible with later script use
  3311.  
  3312.  
  3313. [1:06]
  3314. Right now, if a TX has anything other than data push operations in their scriptSig are considered non-standard and are not relayed
  3315.  
  3316.  
  3317. [1:06]
  3318. But, this can be fixed and changed in Cash
  3319.  
  3320.  
  3321. [1:06]
  3322. BS Core DID NOT want to have script as this would make sidechains and Alpha of no use
  3323.  
  3324.  
  3325. [1:07]
  3326. That does not preclude this from being something that Cash again does, as scripts are NOT spam if you pay for it
  3327.  
  3328.  
  3329. [1:07]
  3330. And miners *EARN MORE*
  3331.  
  3332.  
  3333. [1:07]
  3334. Special TXs can be costed at a higher rate
  3335.  
  3336.  
  3337. [1:07]
  3338. This, miners make fees
  3339.  
  3340.  
  3341. [1:07]
  3342. Cash is cheap, script and contracts cost
  3343.  
  3344.  
  3345. [1:08]
  3346. Here is the other thing... the thing core say is crap...
  3347.  
  3348.  
  3349. [1:08]
  3350. Implement Business rules
  3351.  
  3352.  
  3353. [1:09]
  3354. If an exchange has a withdraw, do not just assume when a client states they are not paid that the TX was not sent!
  3355.  
  3356.  
  3357. [1:09]
  3358. OR.
  3359.  
  3360.  
  3361. [1:09]
  3362. Move funds to a pay address
  3363.  
  3364.  
  3365. [1:11]
  3366. So, Alice has 10 BCH in wallet A1
  3367. She needs to pay 5 BCH to Bob later on. She can move 5 BCH to Alice's own wallet, A2
  3368.  
  3369. Now, she cannot spend more than 5 BCH as the TX will only allow the amount she holds to be spent.
  3370.  
  3371.  
  3372. [1:12]
  3373. If Alice is tricked (stupid girl) into sending a second amount from A2 to Bob, she does this, but the wallet only has 5BCH
  3374.  
  3375.  
  3376. [1:12]
  3377. Hence, it fails if the other is in a block
  3378.  
  3379.  
  3380. [1:12]
  3381. Issue solved.
  3382.  
  3383.  
  3384. [1:14]
  3385. Adding these *Malleability fixes* kills off a lot of script uses that we can have working again now that we are not seeing coloured coins and document signing and gambling as spam!
  3386.  
  3387.  
  3388.  
  3389. robbot [1:14 PM]
  3390. okay
  3391.  
  3392.  
  3393. [1:14]
  3394. my latte has arrived
  3395.  
  3396.  
  3397. [1:14]
  3398. thank the gods
  3399.  
  3400.  
  3401. csw [1:14 PM]
  3402. lol
  3403.  
  3404.  
  3405. robbot [1:15 PM]
  3406. >now that we are not seeing coloured coins and document signing and gambling as spam!
  3407.  
  3408.  
  3409. mengerian [1:15 PM]
  3410. I don't understand how the Malleability fix kills off the other use cases, I'll have to research it more.
  3411.  
  3412.  
  3413. robbot [1:15 PM]
  3414. i swear to god if any of you start calling this kind of shit spam i will punch you in the throat
  3415.  
  3416.  
  3417. coinstash [1:16 PM]
  3418. Love my SatoshiDice. :slightly_smiling_face:
  3419.  
  3420.  
  3421. lunar [1:16 PM]
  3422. @bitsko can we get a pastebin of the Malleability stuff, for the record.
  3423. 12 replies Last reply 18 hours ago View thread
  3424.  
  3425.  
  3426. mengerian [1:16 PM]
  3427. But at least Tomas' proposal is a "minimal" approach, so it lets us understand the change in isolation without all the other changes that Flex Trans makes
  3428.  
  3429.  
  3430. csw [1:16 PM]
  3431. @mengerian
  3432. It means that data that can be validly changed in script (and hence that alters the TXID) is not valid
  3433.  
  3434.  
  3435. [1:17]
  3436. Yes, it is a minimal approach, but to ensure we cannot easily enable scripting and all its ability again
  3437. That leads us right into the Core path
  3438.  
  3439.  
  3440. [1:18]
  3441. They get Alpha and sidechains
  3442.  
  3443.  
  3444. [1:18]
  3445. We have... low value TXs and no more
  3446.  
  3447.  
  3448. [1:18]
  3449. Hence, I am starting to try and educate people as to what Malleability really is
  3450.  
  3451.  
  3452. mengerian [1:18 PM]
  3453. Yeah, I think part of the motivation is to enable Lightning-type off chain stuff
  3454.  
  3455.  
  3456. csw [1:19 PM]
  3457. And it is ONLY benign malleability that can be changed by others
  3458.  
  3459.  
  3460. [1:19]
  3461. And the values are s or -s
  3462.  
  3463.  
  3464. [1:19]
  3465. Then only allow DER S sigs
  3466.  
  3467.  
  3468. [1:19]
  3469. Detect and ignore -s
  3470.  
  3471.  
  3472. coinstash [1:19 PM]
  3473. @lunar Just pasted it to the #library
  3474.  
  3475.  
  3476.  
  3477. mengerian [1:20 PM]
  3478. Any approach lets the originator change the script.
  3479. It only makes subsequent Tx's that refer to it become non-valid
  3480.  
  3481.  
  3482. csw [1:20 PM]
  3483. Allice can ALWAYS try and doublespend
  3484.  
  3485.  
  3486. kensalomon [1:20 PM]
  3487. we have a Library channel?
  3488.  
  3489.  
  3490. csw [1:21 PM]
  3491. Sighash, Anyone can pay
  3492.  
  3493.  
  3494. robbot
  3495. [1:21 PM]
  3496. we've been found
  3497.  
  3498.  
  3499. [1:21]
  3500. execute order 66
  3501.  
  3502.  
  3503.  
  3504. mengerian [1:21 PM]
  3505. I believe Cash already enforces the strict DER
  3506.  
  3507.  
  3508. csw [1:21 PM]
  3509. They do
  3510.  
  3511.  
  3512. [1:21]
  3513. So, 99.99% of the issue is not a Cash issue that we are solving....
  3514.  
  3515.  
  3516. [1:22]
  3517. https://bitcoin.org/en/developer-guide#term-sighash-anyonecanpay
  3518. bitcoin.org
  3519. Developer Guide - Bitcoin (15kB)
  3520.  
  3521.  
  3522. robbot
  3523. [1:22 PM]
  3524. hm
  3525.  
  3526.  
  3527. [1:22]
  3528. someone should reach out to bitcoin.org and let them know their B is facing the wrong way
  3529.  
  3530.  
  3531. csw [1:22 PM]
  3532. So, you use SIGHASH_ANYONECANPAY and chain the TX that way
  3533.  
  3534.  
  3535. [1:22]
  3536. TX0 -> TX1 -> TX2
  3537.  
  3538.  
  3539. [1:22]
  3540. All SIGHASH_ANYONECANPAY
  3541.  
  3542.  
  3543. [1:23]
  3544. @mengerian
  3545. What in that is the attack?
  3546.  
  3547.  
  3548. [1:25]
  3549. To answer:
  3550.  
  3551. 1. Added TXs over the value are added and the original output is fulfilled and a lucky miner earns more
  3552. 2. A random party pays first and stops Allice needing to pay whilst having the TX go to her
  3553.  
  3554.  
  3555. [1:25]
  3556. I call that the random run up and pay for another persons purchase attack
  3557.  
  3558.  
  3559. [1:25]
  3560. In it, a person randomly runs over, dumbs cash on the table and runs off leaving you to leave the store without having paid and the store to be happy
  3561.  
  3562.  
  3563. mengerian [1:26 PM]
  3564. "This ensure that the HF activates STRICTENCODING (just standard right now, not consensus)"...
  3565. https://github.com/Bitcoin-ABC/bitcoin-abc/commit/e49826c1fcc36e5ae26de0ad4d06e2063a759e73
  3566. GitHub
  3567. Reject non replay protected transactions after the fork. · Bitcoin-ABC/bitcoin-abc@e49826c
  3568. Summary: This ensure that the HF activates STRICTENCODING (just standard right now, not consensus) and it'll reject any transaction not using SIGHASH_FORKID after the fork. To make sure we get a cl...
  3569.  
  3570.  
  3571.  
  3572. [1:30]
  3573. The only "attack" I know of was when BitClub mined some blocks where they purposely malleated all the transactions.
  3574. ViaBTC Complained about it.
  3575. But I'm not sure how serious of a problem the attack was. It seemed like more of an annoyance than a serious problem
  3576.  
  3577.  
  3578. csw [1:31 PM]
  3579. It was also changing R to -R
  3580.  
  3581.  
  3582. [1:31]
  3583. That means they altered their own TX
  3584.  
  3585.  
  3586. [1:31]
  3587. A miner can always try and doublespend or change their own TX
  3588.  
  3589.  
  3590. mengerian [1:32 PM]
  3591. Oh I was under the impression they altered other people's Txs
  3592.  
  3593.  
  3594. [1:32]
  3595. I can't see how you could prevent people from altering their own Txs
  3596.  
  3597.  
  3598. csw [1:33 PM]
  3599. uploaded this image: image.png
  3600. Add Comment
  3601.  
  3602.  
  3603.  
  3604. csw [1:33 PM]
  3605. Only the originator can alter the R value in a TX
  3606.  
  3607.  
  3608. [1:34]
  3609. To change (R, s) to have -R means that you need to have access to the private key
  3610.  
  3611.  
  3612. mengerian [1:35 PM]
  3613. Hmm, I thought they had altered ViaBTC transactions. Maybe I was mistaken
  3614. 2 replies Last reply today at 3:32 AM View thread
  3615.  
  3616.  
  3617. csw [1:35 PM]
  3618. There was another "Attack" as well.
  3619.  
  3620.  
  3621. [1:35]
  3622. But that was not really an attack either
  3623.  
  3624.  
  3625. lechango [1:36 PM]
  3626. also perpetuated by Bitclub, correct?
  3627.  
  3628.  
  3629.  
  3630. csw [1:36 PM]
  3631. And again, S to -S just means checking
  3632.  
  3633.  
  3634. [1:36]
  3635. Oh...
  3636.  
  3637.  
  3638. [1:36]
  3639. How did you guess
  3640.  
  3641.  
  3642. [1:36]
  3643. Everyone's fav miner it seems
  3644.  
  3645.  
  3646. lechango [1:36 PM]
  3647. Shillhard really is trying it seems
  3648.  
  3649.  
  3650. csw [1:37 PM]
  3651. So, if all miners BUT Bitclub accept S and reject -S...
  3652.  
  3653.  
  3654. [1:37]
  3655. The change to reject -S is a "softfork" and miners can override this.
  3656.  
  3657.  
  3658. primordial
  3659. [1:40 PM]
  3660. https://medium.com/@bithernet/bitclub-why-are-you-doing-malleability-attack-now-6faa194b2146
  3661. Medium
  3662. BitClub, why are you doing Malleability Attack now?
  3663. Hi BitClub,
  3664. Reading time
  3665. ----------------
  3666. 1 min read
  3667.  
  3668. Mar 10th at 1:31 AM
  3669.  
  3670.  
  3671. csw [1:41 PM]
  3672. So, if DER changes such as BIP 66 were mandatory (which BS Core did not want as this is a HF and does not allow their story)
  3673.  
  3674.  
  3675. [1:42]
  3676. If a miner does the "attack"
  3677.  
  3678.  
  3679. [1:42]
  3680. They lose a block
  3681.  
  3682.  
  3683. [1:43]
  3684. Now, one of the examples P Wullie uses is:
  3685.  
  3686. F' P1 CHECKSIG NOT fails (changed)
  3687.  
  3688.  
  3689. [1:43]
  3690. F is any invalid but DER-compliant signature (including 0, the empty string). F' is any invalid and non-DER-compliant signature.
  3691.  
  3692.  
  3693. [1:45]
  3694. Now... How many times do you want to accept a script that is:
  3695.  
  3696. Sig PubKey CHECKSIG NOT
  3697.  
  3698.  
  3699. [1:46]
  3700. That NOT is generally a give away and is constructed to fail...
  3701.  
  3702.  
  3703. lechango [2:02 PM]
  3704. Is this true @csw? Did you kill dave for his keys? https://www.reddit.com/r/Bitcoin/comments/72df1f/every_seemingly_illogical_action_and_statement_by/ :stuck_out_tongue:
  3705. reddit
  3706. Every seemingly illogical action and statement by Ver, Wright, and Jihan makes sense if u assume they need low fees to wash stolen coins • r/Bitcoin
  3707. I make the conjecture Ver helped karples steal the mt gox coins and wright stole kleinmans Bitcoins and possibly killed him over them.
  3708.  
  3709.  
  3710.  
  3711.  
  3712. mohrt [2:05 PM]
  3713. looks like the BS crettins stooped to a new low
  3714.  
  3715.  
  3716. kensalomon [2:06 PM]
  3717. I saw that earlier today and then questioned myself, Why am I on r/bitcoin?
  3718.  
  3719.  
  3720. csw [2:13 PM]
  3721. I was in Australia. Dave in Florida
  3722.  
  3723.  
  3724. [2:13]
  3725. Dave had his own drive
  3726.  
  3727.  
  3728. [2:13]
  3729. Only Dave has access to Dave's drive
  3730.  
  3731.  
  3732. klee
  3733. [2:14 PM]
  3734. How many coins are missing from you Hal & Dave, can you disclose?
  3735.  
  3736.  
  3737. lechango [2:14 PM]
  3738. pretty fucked up to insinuate that he would kill an already dying man..
  3739.  
  3740.  
  3741. csw [2:14 PM]
  3742. Hal, no.
  3743.  
  3744.  
  3745. [2:14]
  3746. Dave, 330,000k
  3747.  
  3748.  
  3749. [2:14]
  3750. approx
  3751.  
  3752.  
  3753. klee [2:14 PM]
  3754. (Had to ask :grin: )
  3755.  
  3756.  
  3757. [2:14]
  3758. Damn
  3759.  
  3760.  
  3761. bitwho [2:14 PM]
  3762. They is no* low point bitcoin shills won't go (edited)
  3763.  
  3764.  
  3765. csw [2:15 PM]
  3766. Dave's AES key can be cracked in 20 years easily
  3767.  
  3768.  
  3769. bitwho [2:16 PM]
  3770. assuming some one has them right?
  3771.  
  3772.  
  3773. csw [2:16 PM]
  3774. or so
  3775.  
  3776.  
  3777. bitwho [2:16 PM]
  3778. his wife has it correct
  3779.  
  3780.  
  3781. csw [2:16 PM]
  3782. Brother
  3783.  
  3784.  
  3785. bitwho [2:16 PM]
  3786. kk
  3787.  
  3788.  
  3789. csw [2:16 PM]
  3790. Well, unless he had others do copies
  3791.  
  3792.  
  3793. [2:16]
  3794. Then...
  3795.  
  3796.  
  3797. [2:17]
  3798. So, basically, coin-join is good other than when it is for business people...
  3799.  
  3800.  
  3801. [2:17]
  3802. So, these BS Core ppl want to have fungible coins but only for those THEY choose
  3803.  
  3804.  
  3805. klee
  3806. [2:20 PM]
  3807. https://twitter.com/kristovatlas/status/912377748764667904
  3808. Kristov Atlas 🇺🇲 @kristovatlas
  3809. Important vuln in Bitcoin Armory client for large HODLers who used the SSS functionality. Fix requires fund sweep https://bitcointalk.org/index.php?topic=2199659.0
  3810. TwitterYesterday at 2:06 PM
  3811.  
  3812.  
  3813. [2:22]
  3814. https://twitter.com/futurism/status/912368756457971713
  3815. Futurism @futurism
  3816. They believe their system could process more than a million qubits. https://buff.ly/2jXDzPe
  3817. TwitterYesterday at 1:30 PM
  3818.  
  3819.  
  3820. bitwho [2:22 PM]
  3821. i guess i was trying to figure out if you meant "cracked by whom control the back up wallet" or cracked by anyone out there
  3822. Craig S Wright
  3823. Dave's AES key can be cracked in 20 years easily
  3824. Posted in #generalYesterday at 2:15 PM
  3825.  
  3826.  
  3827. mohrt [2:25 PM]
  3828. One would think you have to have physical access to the key to crack and know if its a 128, 192 or 256 bit length (?)
  3829.  
  3830.  
  3831. csw [2:26 PM]
  3832. That would be Dave's brother
  3833.  
  3834.  
  3835. mohrt [2:27 PM]
  3836. so it is known for a fact the USB key exists, and someone has possession of it (not lost/stolen/misplaced) ?
  3837.  
  3838.  
  3839. [2:28]
  3840. or, its just an assumption
  3841.  
  3842.  
  3843. csw [2:29 PM]
  3844. It is a Aluminium cased HDD
  3845.  
  3846.  
  3847. [2:29]
  3848. 3.5"
  3849.  
  3850.  
  3851. [2:29]
  3852. External
  3853.  
  3854.  
  3855. [2:29]
  3856. Silver.
  3857.  
  3858.  
  3859. mohrt [2:30 PM]
  3860. so that has a wallet.dat file with said AES
  3861.  
  3862.  
  3863. csw [2:31 PM]
  3864. The entire drive is protected
  3865.  
  3866.  
  3867. klee [2:31 PM]
  3868. Good project for 2pda
  3869.  
  3870.  
  3871. [2:31]
  3872. No?
  3873.  
  3874.  
  3875. csw [2:31 PM]
  3876. LOL
  3877. Only that Dave's brother Ira owns it
  3878.  
  3879.  
  3880. [2:31]
  3881. So that would be theft
  3882.  
  3883.  
  3884. klee [2:32 PM]
  3885. :smiling_imp:
  3886.  
  3887.  
  3888. [2:32]
  3889. :innocent:
  3890.  
  3891.  
  3892. newliberty [2:55 PM]
  3893. It runs the edges of Dodd-Frank violation, according to recent guidance.
  3894. http://www.dfi.wa.gov/documents/credit-unions/compliance-manual/udaap-overview.pdf
  3895. FTC may get interested.
  3896.  
  3897.  
  3898. jonald_fyookball [3:10 PM]
  3899. i get why its not a problem but why is mallaebility useful
  3900.  
  3901.  
  3902. csw [3:14 PM]
  3903. Scripts
  3904.  
  3905.  
  3906. [3:15]
  3907. Script mallability and SigHash types allows yhings such as secure high speed trades settled in 10 mins
  3908.  
  3909.  
  3910. [3:15]
  3911. It allows derivatives
  3912.  
  3913.  
  3914. [3:15]
  3915. It allows financial instruments to be created
  3916.  
  3917.  
  3918. [3:16]
  3919. All things Core wants on Alpha and encourages their shills to hate
  3920.  
  3921.  
  3922. [3:18]
  3923. Parallel processes
  3924.  
  3925.  
  3926. [3:18]
  3927. Bonds
  3928.  
  3929.  
  3930. [3:18]
  3931. Option contracts
  3932.  
  3933.  
  3934. [3:18]
  3935. Loans and owner tokens
  3936.  
  3937.  
  3938. [3:18]
  3939. Without Eth
  3940.  
  3941.  
  3942. lechango [3:18 PM]
  3943. sounds like a good topic for the next Nchain blog post or CoinGeek
  3944.  
  3945.  
  3946. csw [3:18 PM]
  3947. Getting there
  3948.  
  3949.  
  3950. [3:18]
  3951. Long year
  3952.  
  3953.  
  3954. [3:19]
  3955. Much to do
  3956.  
  3957.  
  3958. robbot [3:31 PM]
  3959. tippr updated
  3960.  
  3961.  
  3962. robbot
  3963. [3:32 PM]
  3964. now if tippr is banned from a subreddit, it will pm the user being tipped instead of posting. since it cant, yknow, post
  3965.  
  3966. 3 replies Last reply 18 hours ago View thread
  3967.  
  3968.  
  3969. lunar [3:32 PM]
  3970. https://localbitcoins.com/blog/bitcoin-bcash/
  3971.  
  3972.  
  3973. [3:32]
  3974. "Instead of providing support for Bcash, we have decide to compensate customers who held Bitcoin on their LocalBitcoins account at the time of the air-drop on August 1st. The Bcash that LocalBitcoins held has been sold and credited to customers at it's corresponding value. We did this by converting all Bcash to Bitcoins, and sharing all of the converted Bitcoins between the users who held a Bitcoin balance on their accounts at the time of the creation of Bcash. Open trades that had any balance at the time were also taken into consideration, based on who received the Bitcoin after the trade was completed or closed."
  3975.  
  3976.  
  3977. slackbot Custom Response [3:32 PM]
  3978. At least I'm not as stupid as people calling Bitcoin Cash _bcash_
  3979.  
  3980.  
  3981. lunar [3:32 PM]
  3982. don't shoot the messenger slackbot :wink:
  3983.  
  3984.  
  3985. slackbot Custom Response [3:32 PM]
  3986. Do androids dream of electric sheep?
  3987. 2 replies Last reply today at 3:50 AM View thread
  3988.  
  3989.  
  3990. robbot
  3991. [3:32 PM]
  3992. yes
  3993.  
  3994.  
  3995. [3:32]
  3996. duh
  3997.  
  3998.  
  3999. [3:33]
  4000. >LocalBitcoins has decided against supporting Bcash, for various reasons.
  4001.  
  4002.  
  4003. slackbot Custom Response [3:33 PM]
  4004. To bcash or not to bcash? How about Bitcoin Cash instead?
  4005.  
  4006.  
  4007. robbot [3:33 PM]
  4008. yeah mostly to keep the money
  4009.  
  4010.  
  4011. kensalomon [3:33 PM]
  4012. yea we dont know how much they sold at
  4013.  
  4014.  
  4015. robbot [3:33 PM]
  4016. yeah. sure theyre giving out the bitcoin cash now but they essentially held it interest free for two months
  4017.  
  4018.  
  4019. [3:33]
  4020. >The processing fee for this conversion is 0.0002 BTC per account
  4021.  
  4022.  
  4023. lunar [3:33 PM]
  4024. if you had a bank account and they converted your $ into € without your permission at a loss, would that be liable ?
  4025.  
  4026.  
  4027. robbot
  4028. [3:34 PM]
  4029. processing fee????
  4030.  
  4031.  
  4032. [3:34]
  4033. what a load of shit
  4034.  
  4035.  
  4036. kensalomon [3:34 PM]
  4037. hey, its bitcoin, whoever owns the keys owns the coin
  4038.  
  4039.  
  4040. [3:34]
  4041. will this cause more on-chain transactions to happen?
  4042.  
  4043.  
  4044. [3:34]
  4045. cause backlog core chain mempool is getting fucked
  4046.  
  4047.  
  4048. lunar [3:35 PM]
  4049. its an asset in their custody. Law still applies.
  4050.  
  4051.  
  4052. [3:35]
  4053. dear sir we've converted your apple shares into enron stock
  4054.  
  4055.  
  4056.  
  4057. kensalomon [3:36 PM]
  4058. and it cost you $20
  4059.  
  4060.  
  4061.  
  4062. lunar [3:39 PM]
  4063. and anything under 20$ we just stole from you.
  4064.  
  4065.  
  4066. csw [3:39 PM]
  4067. Well. We may have to make a decentralised local bch
  4068.  
  4069.  
  4070.  
  4071. lechango [3:40 PM]
  4072. some sort of reputation system with people who can apply to act as escrow agents?
  4073.  
  4074.  
  4075. [3:42]
  4076. and get rewarded for doing so obviously, they can set their own rates
  4077.  
  4078.  
  4079. bitsko [3:42 PM]
  4080. if anyone is opposed to the days messages here in #general being released in pastebin form tomorrow on say, bitco.in or reddit please PM me. I hope to spark discussion on malleability with this discussion if the participants do not mind...
  4081. 3 replies Last reply 15 hours ago View thread
  4082.  
  4083.  
  4084. robbot [3:43 PM]
  4085. i have no problem
  4086.  
  4087.  
  4088. kensalomon [3:44 PM]
  4089. Would it perhaps be possible to build our own Local Bitcoins style site but the site and the vendor have partial keys to the funds? So that transactions like selling forked coins cannot go through because neither party has full control?
  4090.  
  4091.  
  4092. robbot [3:45 PM]
  4093. oh my lord
  4094.  
  4095.  
  4096. robbot
  4097. [3:45 PM]
  4098. my girl made grilled cheese with chicken in it using garlic bread
  4099. 1 reply 17 hours ago View thread
  4100.  
  4101.  
  4102. robbot [3:45 PM]
  4103. and made some tomato soup to go with it
  4104.  
  4105.  
  4106. robbot
  4107. [3:46 PM]
  4108. after this joint its like heaven
  4109.  
  4110. 1 reply 17 hours ago View thread
  4111.  
  4112.  
  4113. kensalomon [3:46 PM]
  4114. didnt know this was @robbot food corner
  4115.  
  4116.  
  4117. robbot
  4118. [3:46 PM]
  4119. wait till you discover my cooking youtube channel
  4120.  
  4121.  
  4122. kensalomon [3:46 PM]
  4123. but that does sound delicious
  4124.  
  4125.  
  4126. lechango [3:47 PM]
  4127. mhmm, sounds goods, I just ate a garlic bagel sandwich, tomato soup would have been nice
  4128.  
  4129.  
  4130. go1dfish [3:47 PM]
  4131. That's the best qualification for a mod
  4132.  
  4133.  
  4134. kensalomon [3:52 PM]
  4135. seems people have squatted the URLS but local bitcoin cash would be nice.
  4136.  
  4137.  
  4138. lechango [3:56 PM]
  4139. I really like the idea of anyone being able to be arbitrator and can set their own rates and earn reputation for each trade
  4140.  
  4141.  
  4142. [3:57]
  4143. most of the time they'll not have to do anything if there's no disputes
  4144.  
  4145.  
  4146. [3:58]
  4147. there's no way around having some amount of trust involved when dealing with fiat on one end
  4148.  
  4149.  
  4150. lunar [4:00 PM]
  4151. Unless you could make it truly trustless, you're going to need a decent reputation system, perhaps combined with a collateral deposits from larger vendors?
  4152.  
  4153.  
  4154. kensalomon [4:01 PM]
  4155. Not to disrupt this thought but maybe lets not remake localbitcoins, lets consider what we would like to do differently to make it better than the original (edited)
  4156.  
  4157.  
  4158. lechango [4:02 PM]
  4159. as far as a name goes, since localbitcoins.cash is taken, how about proximity.cash ?
  4160.  
  4161.  
  4162. [4:02]
  4163. kinda a cool name?
  4164.  
  4165.  
  4166. robbot
  4167. [4:03 PM]
  4168. i like it but the problem is that people are stupid and cant spell
  4169.  
  4170.  
  4171. lechango [4:03 PM]
  4172. haha yeah lol
  4173.  
  4174.  
  4175. robbot
  4176. [4:03 PM]
  4177. you start throwing words like proximity around and they'll never remember how to get to your site
  4178.  
  4179.  
  4180. lechango [4:03 PM]
  4181. it's not that hard a word lol, but I get ya
  4182.  
  4183.  
  4184. [4:05]
  4185. cashforcash.com is for sale
  4186.  
  4187.  
  4188. kensalomon [4:06 PM]
  4189. cashfor.cash?
  4190.  
  4191.  
  4192. robbot
  4193. [4:06 PM]
  4194. oh my shit
  4195.  
  4196.  
  4197. [4:06]
  4198. i like it
  4199.  
  4200.  
  4201. rowdy_beaver [4:07 PM]
  4202. nearby.cash ?
  4203.  
  4204.  
  4205. robbot [4:07 PM]
  4206. i like that too
  4207.  
  4208.  
  4209. kensalomon [4:07 PM]
  4210. Its like chicken in a grilled cheese made of garlic bread? (edited)
  4211.  
  4212.  
  4213. robbot [4:07 PM]
  4214. no
  4215.  
  4216.  
  4217. [4:07]
  4218. nothing is like that
  4219.  
  4220.  
  4221. [4:07]
  4222. god damn that was good
  4223.  
  4224.  
  4225. [4:07]
  4226. i only with my stomach was bigger so i could eat more
  4227.  
  4228.  
  4229. rowdy_beaver [4:08 PM]
  4230. @robbot got me hungry... back after a bite
  4231.  
  4232.  
  4233. kensalomon [4:09 PM]
  4234. cashfor.cash is available on Namecheap for $4.06 apparently....
  4235.  
  4236.  
  4237.  
  4238. gsam [5:25 PM]
  4239. #aside - This might be useful for this Slack's administrators https://twitter.com/paul__walsh/status/902971961453580289
  4240. Paul Walsh 🎣🚨 @Paul__Walsh
  4241. I just published “How crypto communities can stay more safe from phishing attacks on Slack — Beta release #2” https://medium.com/@Paul__Walsh/how-crypto-communities-can-stay-more-safe-from-phishing-attacks-on-slack-beta-release-2-d9e1cb787f8b
  4242. TwitterAug 30th at 3:11 PM
  4243.  
  4244.  
  4245. bitwho [6:34 PM]
  4246. Inmight be late to the party with this but localbitcoin sold their bitcoincash? Are they legally allowed to do this?
  4247. 2 replies Last reply 15 hours ago View thread
  4248.  
  4249.  
  4250. bitwho [6:35 PM]
  4251. I would be pissed if they did that to my coins :/
  4252.  
  4253.  
  4254. lechango [6:52 PM]
  4255. I don't think there's any rules saying they can't, they deal in Bitcoin, they have no obligation to provide any other forks to their clients. It would be even more shitty if they never even gave BTC compensation
  4256.  
  4257.  
  4258. rt121212121 [7:03 PM]
  4259. kiwi coin in nz did that
  4260.  
  4261.  
  4262. [7:03]
  4263. no bcc, no compensation
  4264.  
  4265.  
  4266. roger_murdock [7:57 PM]
  4267. https://www.reddit.com/r/btc/comments/72g8o9/measuring_maximum_sustained_transaction/
  4268. reddit
  4269. "Measuring maximum sustained transaction throughput on a global network of Bitcoin nodes” [BU/nChain/UBC proposal for Scaling Bitcoin Stanford] • r/btc
  4270. 3 points and 6 comments so far on reddit
  4271.  
  4272.  
  4273.  
  4274.  
  4275. [7:58]
  4276. (BU/nChain/UBC proposal for Scaling Bitcoin Stanford)
  4277.  
  4278.  
  4279. robbot [8:37 PM]
  4280. https://twitter.com/tipprbot/status/912476061207863296
  4281. tippr @tipprbot
  4282. Free #BitcoinCash now that it's #TippingTuesday. Check it out https://www.reddit.com/r/btc/comments/72gm44/tipping_tuesday_come_experience_what_a_peertopeer/
  4283. TwitterYesterday at 8:37 PM
  4284.  
  4285.  
  4286. lechango [8:43 PM]
  4287. I feel kinda dirty for taking a a dollar of BCC from him when there's other newbies who could benefit more. But hey, hard to turn down free money
  4288.  
  4289.  
  4290. cryptorebel [8:44 PM]
  4291. its cool, can always re-tip
  4292.  
  4293.  
  4294. lechango [8:46 PM]
  4295. indeed
  4296.  
  4297.  
  4298. zquestz [8:51 PM]
  4299. free bcc isn't something I turn down =P
  4300.  
  4301.  
  4302. [8:51]
  4303. but I am hoping to retip to other users anyways
  4304.  
  4305.  
  4306. lechango [8:54 PM]
  4307. same here, I've been lazy, I need to fund up my tippr wallet and get at it
  4308.  
  4309.  
  4310. cryptorebel [8:56 PM]
  4311. we should try to post the twitter link on /r/bitcoin
  4312.  
  4313.  
  4314. lechango [9:01 PM]
  4315. I feel like there's got to be a way to circumvent the tippr ban on /r/bitcoin
  4316.  
  4317.  
  4318. [9:02]
  4319. I suppose you could just PM users with private keys
  4320.  
  4321.  
  4322. kensalomon [9:02 PM]
  4323. simple, PM tippr, is that enabled @robbot?
  4324.  
  4325.  
  4326. lechango [9:04 PM]
  4327. I guess there's no way to make it effective, any public reply stating they've been tipped will be removed
  4328.  
  4329.  
  4330. cryptorebel [9:04 PM]
  4331. he said it would still be classified as spam
  4332.  
  4333.  
  4334. kensalomon [9:04 PM]
  4335. then you have no choice but to see if that username corresponds to a twitter account and tip them there
  4336.  
  4337.  
  4338. cryptorebel [9:05 PM]
  4339. maybe if we implement segwitcoin, then they cant ban it
  4340.  
  4341.  
  4342. [9:05]
  4343. but still nobody will really use segwitcoin because its high fees
  4344.  
  4345.  
  4346. kensalomon [9:05 PM]
  4347. eh, i'm banned on r/bitcoin
  4348.  
  4349.  
  4350. cryptorebel [9:05 PM]
  4351. but then we could illustrate why they are banning a bitcoin tip bot
  4352.  
  4353.  
  4354. kensalomon [9:05 PM]
  4355. so it wouldnt matter no matter what
  4356.  
  4357.  
  4358. cryptorebel [9:06 PM]
  4359. they allowed doge tipping before
  4360.  
  4361.  
  4362. [9:06]
  4363. is doge tipping allowed
  4364.  
  4365.  
  4366. kensalomon [9:06 PM]
  4367. no alts!
  4368.  
  4369.  
  4370. rt121212121 [9:06 PM]
  4371. If the tip withdrawal fee comes out of their segwitcoin tip balance, and they can't cash out until they've got enough, then that's one way
  4372.  
  4373.  
  4374. kensalomon [9:23 PM]
  4375. I got this one for the lulz......accepttruebitco.in
  4376.  
  4377.  
  4378. [9:23]
  4379. have fun
  4380.  
  4381.  
  4382. [9:24]
  4383. just remember if you link to the site it helps our SEO if you use the real URL
  4384.  
  4385.  
  4386. zquestz [10:40 PM]
  4387. ok so is everything in master that you need to deploy?
  4388.  
  4389.  
  4390. [10:40]
  4391. oops
  4392.  
  4393.  
  4394. [10:40]
  4395. saw ken, but this is general :wink:
  4396.  
  4397.  
  4398. robbot
  4399. [11:02 PM]
  4400. https://www.reddit.com/r/btc/comments/72gm44/tipping_tuesday_come_experience_what_a_peertopeer/
  4401. reddit
  4402. Tipping Tuesday - Come experience what a peer-to-peer electronic cash system looks like! [26/09/2017] • r/btc
  4403. Post in this thread and I'll send you some bitcoin (cash), as long as the balance in my /u/tippr account lasts. If you want to withdraw your...
  4404.  
  4405.  
  4406.  
  4407. [11:03]
  4408. lol only 77% upvoted
  4409.  
  4410.  
  4411. [11:03]
  4412. hatboys: REEEEEEEEEEEEEEEEE
  4413.  
  4414.  
  4415.  
  4416. coinstash [11:21 PM]
  4417. Well I don't feel too bad about not being able to get a loan any more. The bidding started $50k above my top price and the property was passed in unsold at $465k which means the Australian property market is utterly delusional.
  4418.  
  4419.  
  4420.  
  4421. [11:24]
  4422. I can get the same in the Philippines with a harbour view for $115k.
  4423.  
  4424.  
  4425. rt121212121 [11:27 PM]
  4426. I am sure the Phillipines is a lovely place.. but it's not quite the same
  4427.  
  4428.  
  4429. coinstash [11:28 PM]
  4430. No, the house in the Philippines doesn't need $100k spent on it to be livable.
  4431.  
  4432.  
  4433. spunky [11:29 PM]
  4434. Sounds like you were just a victim of underquoting
  4435.  
  4436.  
  4437. coinstash [11:30 PM]
  4438. Seriously, would you spend half a million on this?
  4439. https://www.realestate.com.au/property-House-qld-Beachmere-126268814 (edited)
  4440.  
  4441.  
  4442. spunky [11:32 PM]
  4443. That is a lovely space, if I'm honest, I probably would
  4444.  
  4445.  
  4446. rt121212121
  4447. [11:32 PM]
  4448. Depends on the cost of property nearby and the appeal of living in that location
  4449.  
  4450.  
  4451. [11:32]
  4452. I find the place depressing though
  4453.  
  4454.  
  4455. spunky
  4456. [11:33 PM]
  4457. Median property price is $350, so 500k is probably a bit excessive
  4458.  
  4459.  
  4460. coinstash [11:33 PM]
  4461. The kitchen and bathroom are both horrible, and all that cream brick veneer screams out for a rendering job. Yuck.
  4462.  
  4463.  
  4464. spunky
  4465. [11:34 PM]
  4466. Yeah you'd put 100k to rennovate it, install a pool and turn it in to a 600k livable property
  4467.  
  4468.  
  4469. coinstash [11:35 PM]
  4470. Yeah but it would have to be worth $1M at the end to make it worthwhile.
  4471.  
  4472.  
  4473. spunky
  4474. [11:35 PM]
  4475. It wouldn't go higher than 700k, so 500k is excessive yet again
  4476.  
  4477.  
  4478. coinstash [11:35 PM]
  4479. Now, contrast this at PHP 4.7M (about AU$115k):
  4480. http://www.islandsproperties.com/properties/houseandlots/min-pue-rh-6141/index.htm (edited)
  4481.  
  4482.  
  4483. spunky
  4484. [11:37 PM]
  4485. Are the papasans included?
  4486.  
  4487.  
  4488. coinstash [11:38 PM]
  4489. Fully furnished. Check out the additional photos of the view over the harbour.
  4490.  
  4491.  
  4492. spunky
  4493. [11:39 PM]
  4494. Yeah, if I was unencumbered and that was a possibility, I would totally do that instead. The hell with the lifestyle tradeoffs
  4495.  
  4496.  
  4497. coinstash [11:39 PM]
  4498. And it's built of solid stone by an English builder. (edited)
  4499.  
  4500.  
  4501. [11:40]
  4502. The only snag is that foreigners can't own land in PH otherwise I'd already own it. (edited)
  4503.  
  4504.  
  4505. spunky [11:41 PM]
  4506. Go bag yourself a nice filipino then lol
  4507.  
  4508.  
  4509. coinstash [11:42 PM]
  4510. High price to pay for a bachelor. And they can rip you off ...
  4511.  
  4512.  
  4513. [11:42]
  4514. Current owner got around it by putting the ownership in the name of a daughter of a friend who happens to be a judge.
  4515.  
  4516.  
  4517. spunky
  4518. [11:43 PM]
  4519. Why don't you move to Coober Pedy and buy a dugout
  4520.  
  4521.  
  4522. coinstash [11:43 PM]
  4523. Why don't you get a rat up your arse
  4524.  
  4525.  
  4526. [11:43]
  4527. :slightly_smiling_face:
  4528.  
  4529.  
  4530. spunky [11:43 PM]
  4531. HBahahahaha
  4532.  
  4533.  
  4534. coinstash [11:45 PM]
  4535. Yeah, I could afford a humpy in Broken Hill but there's a reason they only cost $50k
  4536.  
  4537.  
  4538. spunky [11:45 PM]
  4539. I mean, you want a property that backs on to a river, with boat parking ffs... that's gonna fetch some kind of premium
  4540.  
  4541.  
  4542. coinstash [11:46 PM]
  4543. It ain't worth an extra $250k over the real value.
  4544.  
  4545.  
  4546. [11:46]
  4547. I can get a 3 storey hotel in NZ for $75k, right opposite a river.
  4548.  
  4549.  
  4550. spunky
  4551. [11:47 PM]
  4552. Yeah you're talking to the wrong guy, houses in Canberra cost $400k starting price. Not sure how we got here but hey, it is what it is
  4553.  
  4554.  
  4555. coinstash [11:48 PM]
  4556. Canberra has always been 15% over market, captive audience.
  4557.  
  4558.  
  4559. spunky
  4560. [11:48 PM]
  4561. Yeah and under supply so I hear
  4562.  
  4563.  
  4564. [11:49]
  4565. Could trade my house for a whole street of NZ hotels by the sounds of it
  4566.  
  4567.  
  4568. [11:50]
  4569. Own the whole street, then charge whatever I want, get myself a top hat and monocle... muahahaha
  4570.  
  4571.  
  4572. [11:51]
  4573. Anyway now is not the right time to be buying, we are entering the 9th year since the last fin crisis
  4574.  
  4575.  
  4576. [11:52]
  4577. People are getting cocky, asking 500k for properties clearly only worth 350k
  4578.  
  4579.  
  4580. [11:52]
  4581. Boom/bust cycle lasts 9 years, bout time we had a lil shake up
  4582.  
  4583.  
  4584.  
  4585.  
  4586. ----- Today September 26th, 2017 -----
  4587. coinstash [12:02 AM]
  4588. I'll be shaking it right out of Australia as soon as I can apply for the pension.
  4589.  
  4590.  
  4591. rt121212121 [12:10 AM]
  4592. Any set destination?
  4593.  
  4594.  
  4595. coinstash [12:11 AM]
  4596. Just want to see as much as possible. Asia, then more of Europe. Yacht trip round the world.
  4597.  
  4598.  
  4599. [12:12]
  4600. I'll have to drop into EnZed to mow the lawn too I suppose.
  4601.  
  4602.  
  4603. hyena [3:03 AM]
  4604. wouldn't openbazaar be suitable as a localbitcoins alternative?
  4605.  
  4606.  
  4607. cryptorebel [3:05 AM]
  4608. there is also a wallet app similar to localbitcoins, i think mycelium local trader i think isnt it
  4609.  
  4610.  
  4611. hyena [3:07 AM]
  4612. `Firefox can't find the server at github.com.` anyone else experiencing this at the moment?
  4613.  
  4614.  
  4615. lechango [3:08 AM]
  4616. nope, loading fine for me
  4617.  
  4618.  
  4619. hyena [3:08 AM]
  4620. ok thanks for the info... perhaps something with the vpn, I'm using airVPN
  4621.  
  4622.  
  4623. lechango [3:14 AM]
  4624. this guy can't be serious. Implement replay protection on 2X by creating >1MB transactions. Am I missing something or this superbly stupid? https://github.com/btc1/bitcoin/issues/123
  4625. GitHub
  4626. Opt-in, two-way replay protection using a well known P2SH · Issue #123 · btc1/bitcoin
  4627. I think there might be a way to implement opt-in, two-way replay protection purely from the 2x side. First we come up with a well known P2SH that's more expensive to spend than create (in terms of ...
  4628.  
  4629.  
  4630.  
  4631. kyuupichan [3:28 AM]
  4632. That was my understanding too. ViaBTC had a tx chain and it was broken. @deadalnix knows the details I think but didn’t answer when I asked what happened.
  4633.  
  4634.  
  4635. spunky [3:32 AM]
  4636. @lechango it is a novel solution, although crazy AF. Note the repo hasn't been touched since Jul 22 so that issue list is just a forum at this point
  4637.  
  4638.  
  4639. frido
  4640. [3:32 AM]
  4641. https://imnotdead.co.uk/blog/richard-heart
  4642. I'm Not Dead
  4643. Richard Heart - Spam, ICOs, and Death Threats
  4644. It's pretty safe to say that I was becoming a fan of Richard Heart. And then shit hit the fan. (145kB)
  4645. +1 15 replies Last reply today at 4:08 AM View thread
  4646.  
  4647.  
  4648. frido [3:33 AM]
  4649. shit got real.
  4650.  
  4651.  
  4652. otaci [3:35 AM]
  4653. Bitcoin Core - test network for Bitcoin Cash.
  4654.  
  4655.  
  4656. [3:35]
  4657. Like it?
  4658.  
  4659.  
  4660. csw [3:37 AM]
  4661. If they all do >1MB... they might even get 1 TX a block
  4662.  
  4663.  
  4664.  
  4665. spunky [3:40 AM]
  4666. uploaded this image: richard-heart-spam-king.jpg
  4667. Add Comment
  4668.  
  4669.  
  4670.  
  4671. spunky
  4672. [3:41 AM]
  4673. Oops, that image was supposed to go here
  4674.  
  4675.  
  4676. thedunlap [3:42 AM]
  4677. Can someone feel me in on what happened with Viabtc? How did someone changing a transactionid (I'm assuming through malleability) invalidate a transaction chain?
  4678.  
  4679.  
  4680. thedunlap [3:42 AM]
  4681. *fill
  4682. 1 reply Today at 3:48 AM View thread
  4683.  
  4684.  
  4685. csw [4:00 AM]
  4686. See above.
  4687.  
  4688.  
  4689. [4:00]
  4690. There is a softfork for malleability
  4691.  
  4692.  
  4693. [4:00]
  4694. This was ignored by a certain BTC club
  4695.  
  4696.  
  4697. [4:01]
  4698. The nature of signatures in EcDSA is they have two values:
  4699.  
  4700. (R, S) and (R, -S)
  4701.  
  4702.  
  4703. [4:02]
  4704. Anyone with the public key can calculate -S from S given the modulus (set in Bitcoin for the curve) and the public key - exposed to miners on sending a TX
  4705.  
  4706.  
  4707. [4:02]
  4708. The change there was to make a change and create a block using -S in place of S (edited)
  4709.  
  4710.  
  4711. [4:02]
  4712. That is it. That is the GREAT attack
  4713.  
  4714.  
  4715. [4:03]
  4716. The coin amounts and addresses they are paid to do not change
  4717.  
  4718.  
  4719. lechango [4:05 AM]
  4720. So because of that, the transactions in that block was seen as invalid by some nodes?
  4721.  
  4722.  
  4723. tomtomtom7 [4:06 AM]
  4724. Negative S is not allowed as per BIP 66.
  4725.  
  4726.  
  4727. lechango [4:06 AM]
  4728. So I missed this, was this on the BTC or BCC chain?
  4729.  
  4730.  
  4731. csw [4:06 AM]
  4732. It is not supposed to be allowed
  4733.  
  4734.  
  4735. [4:06]
  4736. DER encoding was set in BIP 66 as a soft fork
  4737.  
  4738.  
  4739. [4:07]
  4740. https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki
  4741. GitHub
  4742. bitcoin/bips
  4743. bips - Bitcoin Improvement Proposals
  4744.  
  4745.  
  4746.  
  4747. tomtomtom7 [4:07 AM]
  4748. BIP 66 can be seen as the first attempt to fix malleability. But then some argued that there were more forms, such as changing the push-data opcode.
  4749.  
  4750.  
  4751. csw [4:08 AM]
  4752. That is Script Malleability
  4753.  
  4754.  
  4755. [4:08]
  4756. And 66 was sofforked in place of a 62 harder fork
  4757.  
  4758.  
  4759. tomtomtom7 [4:08 AM]
  4760. Yes. But because there are multiple ways to malleate the input scripts (not just the sigs), the idea of softforking out all forms was abandoned
  4761.  
  4762.  
  4763. [4:09]
  4764. Though I think it may be possible to fix it that way.
  4765.  
  4766.  
  4767. csw [4:09 AM]
  4768. And, As I wewnt over last night, there are 3 forms of malleability
  4769.  
  4770.  
  4771. [4:09]
  4772. And only one of these, bengin malleability is addressed
  4773.  
  4774.  
  4775. [4:10]
  4776. And for that matter, non-benign malleability cannot be addressed other than reverting away from RBF as Cash has done
  4777.  
  4778.  
  4779.  
  4780. spunky
  4781. [4:10 AM]
  4782. 69 tx in latest block, hurr durr, sixty nine
  4783.  
  4784.  
  4785. csw [4:10 AM]
  4786. As for methods - BIP 66 "Examples" Covered this
  4787.  
  4788.  
  4789. spunky
  4790. [4:12 AM]
  4791. So just to clarify for laymen, this bug was introduced by RBF?
  4792.  
  4793.  
  4794. csw [4:12 AM]
  4795. No, the attack was
  4796.  
  4797.  
  4798. [4:13]
  4799. Before RBF, if you malleated, the TX was still paid.
  4800.  
  4801.  
  4802. [4:13]
  4803. Now, with RBF, the user can change the TX as a double spend.
  4804.  
  4805.  
  4806. [4:15]
  4807. 1. Alice pays Bob
  4808. 2. Bob chains a TX to Charles
  4809. 3. Bob watches for the TXID he has used
  4810. 4. Alice malleates the TX and replaces it using RBF
  4811. 5. Bob now has a payment to Charlie that fails.
  4812.  
  4813. Only works with RBF
  4814.  
  4815.  
  4816. lechango [4:16 AM]
  4817. stupid question, is RBF compatible with segwit transactions?
  4818.  
  4819.  
  4820. csw [4:16 AM]
  4821. IF
  4822. Bob has a sighash anycanpay
  4823.  
  4824. Then without RBF, the payment from Allice can be chained with malleability
  4825.  
  4826.  
  4827. [4:17]
  4828. Altering the R,S pair to R,-S means nothing and the payment from Bob to Charle goes through
  4829.  
  4830.  
  4831. [4:17]
  4832. Yes RBF is SegShit compatible
  4833.  
  4834.  
  4835. [4:19]
  4836. *The attack... if you call it this for sighash anycanpay....*
  4837.  
  4838.  
  4839. [4:19]
  4840. Mallory jumps in and sends money into Bob's TX before Allice
  4841.  
  4842.  
  4843. [4:19]
  4844. Alice keeps her money or sends to Bob
  4845.  
  4846.  
  4847. [4:20]
  4848. Bob sends to Charlie and either has funds from Alice or not
  4849.  
  4850.  
  4851. [4:20]
  4852. Alice, Bob and Charle have their money
  4853.  
  4854.  
  4855. [4:20]
  4856. But EITHER Alice or Bob has a refund from Mallory
  4857.  
  4858.  
  4859. thedunlap [4:20 AM]
  4860. I believe I understand how malleability can break chained transactions that are not yet comitted to the blockchain, but in relation to ViaBTC, did they have an entire mined block that was rejected because of the -s exploit?
  4861.  
  4862.  
  4863. csw [4:20 AM]
  4864. I call it the haha I paid for your purchase and run off attack
  4865.  
  4866.  
  4867.  
  4868. lechango [4:21 AM]
  4869. lol, that is quite the "attack"
  4870.  
  4871.  
  4872. [4:21]
  4873. the "pay it forward" attack
  4874.  
  4875.  
  4876. csw [4:22 AM]
  4877. No, it was not a lost block
  4878.  
  4879.  
  4880.  
  4881. lechango [4:23 AM]
  4882. the transactions were just invalid so it's like it was an empty block? or what
  4883.  
  4884.  
  4885. csw [4:23 AM]
  4886. As noted last night, this was an issue with TXID and ViBTC systems - not bitcoin, their business systems
  4887.  
  4888.  
  4889. [4:24]
  4890. ViaBTC Should have used separate addresses for each deposit. Then, they could have mapped the payment to the user.
  4891.  
  4892.  
  4893. lechango [4:25 AM]
  4894. So what motivation or message were they trying to spread by doing this?
  4895.  
  4896.  
  4897. csw [4:25 AM]
  4898. ViaBTC needed to suspend deposits and withdrawls
  4899.  
  4900.  
  4901. [4:25]
  4902. It was a result of poor accounting practices
  4903.  
  4904.  
  4905. lechango [4:26 AM]
  4906. Other exchanges that re-used deposit addresses were not also affected?
  4907.  
  4908.  
  4909. csw [4:26 AM]
  4910. The Attack was designed to cause a few issues - some know what business process failures an exchange has
  4911.  
  4912.  
  4913. [4:26]
  4914. Exchanges that map TXID and not the actual address deposit can be impacted
  4915.  
  4916.  
  4917. lechango [4:27 AM]
  4918. ah ok
  4919.  
  4920.  
  4921. csw [4:27 AM]
  4922. Malleability does not change the to nor from address nor the amount paid
  4923.  
  4924.  
  4925. [4:28]
  4926. Right now, if a TX has anything other than data push operations in their scriptSig are considered non-standard and are not relayed
  4927. But, this can be fixed and changed in Cash
  4928. BS Core DID NOT want to have script as this would make sidechains and Alpha of no use
  4929. That does not preclude this from being something that Cash again does, as scripts are NOT spam if you pay for it
  4930. And miners *EARN MORE*
  4931. Special TXs can be costed at a higher rate
  4932.  
  4933. This, miners make fees
  4934.  
  4935. Cash is cheap, script and contracts cost
  4936.  
  4937. Here is the other thing... the thing core say is crap...
  4938.  
  4939. Implement Business rules
  4940.  
  4941. If an exchange has a withdraw, do not just assume when a client states they are not paid that the TX was not sent!
  4942.  
  4943. OR.
  4944.  
  4945. Move funds to a pay address
  4946.  
  4947. So, Alice has 10 BCH in wallet A1
  4948. She needs to pay 5 BCH to Bob later on. She can move 5 BCH to Alice's own wallet, A2
  4949.  
  4950. Now, she cannot spend more than 5 BCH as the TX will only allow the amount she holds to be spent.
  4951.  
  4952. If Alice is tricked (stupid girl) into sending a second amount from A2 to Bob, she does this, but the wallet only has 5BCH
  4953.  
  4954. Hence, it fails if the other is in a block
  4955.  
  4956. Issue solved. (edited)
  4957.  
  4958.  
  4959. [4:29]
  4960. *So, the Business rule attack is...* (edited)
  4961.  
  4962.  
  4963. [4:30]
  4964. Find an exchange that has not implemented recommended practices.
  4965. Malleate a TX
  4966. Say you did not get a payment
  4967. Request the exchange send again
  4968.  
  4969.  
  4970. [4:30]
  4971. *Basically* something that banks solved in the 1700s
  4972.  
  4973.  
  4974. [4:31]
  4975. Validate the ledger and not the TXID (edited)
  4976.  
  4977.  
  4978.  
  4979. [4:33]
  4980. If you use a deterministic address for deposits, that is, you map each one separately (as any good exchange will do)
  4981. And you only pay based on amounts added
  4982. Then, this is not an issue.
  4983.  
  4984.  
  4985. hyena [4:35 AM]
  4986. the argument for TXID mapping is that it makes bookkeeping simple, because issuing a new address for each client/payment request would require the business to integrate with bitcoin wallet which could technically be too hard :stuck_out_tongue:
  4987.  
  4988.  
  4989. csw [4:36 AM]
  4990. It is also a factor that if an exchange has poor practice in one area, it will in others. So, I am brutal here. The exchange SHOULD have good practice or it SHOULD be allowed to fail.
  4991.  
  4992. No blaming myths. Reality bites
  4993.  
  4994.  
  4995. [4:36]
  4996. And they do not need to hold keys, just monitor the deposits
  4997.  
  4998.  
  4999. [4:36]
  5000. And, they also should have a delay time in adding and removing funds. It is not a bank, it is an exchange
  5001.  
  5002.  
  5003. [4:37]
  5004. And sending notification of a withdrawal and having time for the user to block it is a basic security control
  5005.  
  5006.  
  5007. [4:39]
  5008. So, the Malleability fix is an excuse *AT BEST* to have BAD systems last longer and get bigger before they crash and burn
  5009.  
  5010.  
  5011.  
  5012. [4:39]
  5013. And they WILL crash and burn if they do not fix process and FUD the way out of it
  5014.  
  5015.  
  5016. hyena [4:40 AM]
  5017. my proposed solution for businesses that do not want to issue a new address for each customer --- just have one cold storage address for payments, but require slightly different amount of bitcoins from each customers (add a random number of satoshis in the range of 0-999 to the end of the requested amount). so if you have 2 customers who both have to pay you 1 bitcoin, ask the first one to send you 1.00000157 and the second one 1.00000521. that way you can poll for confirmed payments using your favorite block explorer, and the receiving address can be a cold storage address. yes this is a kludgy hack, but it works very well, cryptograffiti.info has been using this for 3 years and I wouldn't want to change it
  5018.  
  5019.  
  5020. csw [4:43 AM]
  5021. https://bitcoin.org/en/developer-guide#term-signature-hash
  5022. bitcoin.org
  5023. Developer Guide - Bitcoin (15kB)
  5024.  
  5025.  
  5026. [4:43]
  5027. SIGHASH_ALL|SIGHASH_ANYONECANPAY
  5028.  
  5029.  
  5030. [4:44]
  5031. If you create a payment address that is used - you can also pre-sign TXs even with cold storage
  5032.  
  5033.  
  5034. [4:48]
  5035. Steps
  5036.  
  5037. Exchange makes a TX with:
  5038.  
  5039. Input -
  5040. Exchange_Address - 1000 Sat
  5041.  
  5042. OutPut -
  5043. Exchange_Address - 1,000,010,00 Sat (just over 1 BTC)
  5044.  
  5045. To be valid, the others need to send funds and add them to this TX.
  5046.  
  5047. As the output is to the exchange address and it is SIGHASH_ALL|SIGHASH_ANYONECANPAY
  5048.  
  5049. It means that the exchange can send this and it is ALWAYS valid
  5050.  
  5051.  
  5052. [4:48]
  5053. That is, it is a TX that can be used and re-used
  5054.  
  5055.  
  5056. [4:50]
  5057. The user either taks on a
  5058. SIGHASH_NONE|SIGHASH_ANYONECANPAY
  5059.  
  5060. Which is like a blank cheque
  5061.  
  5062.  
  5063. [4:51]
  5064. Or better a SIGHASH_SINGLE to sign the output
  5065.  
  5066.  
  5067. [4:51]
  5068. These are combined and the exchange is paid.
  5069.  
  5070.  
  5071. [4:51]
  5072. *Rather than change Bitcoin*
  5073. How about learning how the system works...
  5074.  
  5075.  
  5076.  
  5077. [4:52]
  5078. @hyena had a *wonderful* post of real quality on CPFC (edited)
  5079.  
  5080.  
  5081. [4:52]
  5082. child pays for parent (edited)
  5083.  
  5084.  
  5085. [4:52]
  5086. If this was coupled with SigHash flags
  5087.  
  5088.  
  5089. hyena [4:52 AM]
  5090. you mean CPFP? :smile: child pays for parent
  5091.  
  5092.  
  5093. csw [4:53 AM]
  5094. He would have a tremendously effective system to chain TXs
  5095.  
  5096.  
  5097. [4:53]
  5098. Keeping you on your toes and I need more espresso (edited)
  5099.  
  5100.  
  5101. hyena [4:54 AM]
  5102. yeah yeah, typical trick from a true professor's handbook, just checking if the students pay attention :joy:
  5103.  
  5104.  
  5105. csw [4:54 AM]
  5106. This is a write-up on what Bitculb was doing:
  5107. https://medium.com/@bithernet/bitclub-why-are-you-doing-malleability-attack-now-6faa194b2146
  5108. Medium
  5109. BitClub, why are you doing Malleability Attack now?
  5110. Hi BitClub,
  5111. Reading time
  5112. ----------------
  5113. 1 min read
  5114.  
  5115. Mar 10th at 1:31 AM
  5116.  
  5117.  
  5118. [4:56]
  5119. _The blockchain.info site is almost down (cannot query the data of the blocks mined by you), this can make their users confusing too._
  5120.  
  5121. I do not agree with that claim
  5122.  
  5123.  
  5124. [4:56]
  5125. If users watch their address they will see the TX hit when the block is released
  5126.  
  5127.  
  5128. [4:56]
  5129. What happened was Bitclub malleated but also hid the changes
  5130.  
  5131.  
  5132. [4:57]
  5133. So, a block would be released and it would have a malleated TX and not the one with the original TXID
  5134.  
  5135.  
  5136. [4:57]
  5137. The payment was still there and in your block.
  5138.  
  5139.  
  5140. [4:57]
  5141. Again, only an issue if you have bad business processes.
  5142.  
  5143.  
  5144. [4:58]
  5145. ViaBTC have fixed this from what I hear, so that is good
  5146.  
  5147.  
  5148. [4:58]
  5149. But it should not have been an issue in the first place...
  5150.  
  5151.  
  5152. [4:59]
  5153. Oh... and this is the issue with *SoftForks*
  5154.  
  5155.  
  5156. [4:59]
  5157. Bitclub used a -s
  5158.  
  5159.  
  5160. [4:59]
  5161. As Tom stated, this is a no no - but a miner can mine a block and ignore Softfork rules and still be allowed
  5162.  
  5163.  
  5164. [5:00]
  5165. In a hard fork, this would not be an issue as Bitclub would have dropped the malleated TX in a block and all other miners would have orphaned it
  5166.  
  5167.  
  5168. [5:01]
  5169. Again... Softforks are good for the Core BS narative
  5170.  
  5171.  
  5172. [5:01]
  5173. Not Bitcoin
  5174.  
  5175.  
  5176.  
  5177. hyena [5:02 AM]
  5178. the core wallet uses unconfirmed outputs when there are not enough confirmed funds in the wallet, and this can cause giant mess for businesses who allow withdrawals that depend on long unconfirmed TX chains. let's suppose the first TX gets malleated, so none of the customers receive their deposits :stuck_out_tongue: tech support hell, and crafting your own TXs with `createrawtransaction` seems to be avoided due to the paranoia of messing something up with the fees and such
  5179.  
  5180.  
  5181. csw [5:02 AM]
  5182. Yes, but this is a Core BS issue
  5183.  
  5184.  
  5185. [5:02]
  5186. Not a Bitcoin issue
  5187.  
  5188.  
  5189. [5:03]
  5190. Core failed to make a robust wallet
  5191.  
  5192.  
  5193.  
  5194. [5:03]
  5195. Not that maleation is the issue
  5196.  
  5197.  
  5198. [5:03]
  5199. On top of that, they added RBF
  5200.  
  5201.  
  5202. hyena [5:04 AM]
  5203. yes, malleation is not the issue, the issue is the wallet that lacks of proper RPC to absolutely deny using unconfirmed funds as inputs for new TXs
  5204.  
  5205.  
  5206. csw [5:06 AM]
  5207. This is ALSO the issue with why there is :
  5208. no ETF in the US
  5209. SEC warnings
  5210. PBoC warnings
  5211.  
  5212.  
  5213. [5:06]
  5214. Basically, it is not malleability - it is making a good product that is going to make Bitcoin succeed
  5215.  
  5216.  
  5217. [5:06]
  5218. But BS Core do not want this. They seek to stay _underground_. No banks, no businesses and no companies
  5219.  
  5220.  
  5221. [5:07]
  5222. Hence, they are not trying to fix the business process issues, they want these
  5223.  
  5224.  
  5225. [5:08]
  5226. http://agbrief.com/news/blockchain-and-disruptive-tech-and-startups-sigma17
  5227. AGB
  5228. Blockchain and disruptive tech and startups at SiGMA17
  5229. SiGMA will host Malta’s largest gaming exhibition yet, along with eleven conferences at the Malta Fairs and Conventions Centre from November 22-25. (53kB)
  5230. Yesterday at 7:24 AM
  5231.  
  5232.  
  5233. [5:08]
  5234. On a different note
  5235.  
  5236.  
  5237. lechango [5:10 AM]
  5238. nice, looking forward to seeing that talk if it's recorded. Talking bigger picture stuff I assume?
  5239.  
  5240.  
  5241. janko33 [5:14 AM]
  5242. @csw What about future txids. Mulitsig with nLockTime
  5243.  
  5244.  
  5245. [5:16]
  5246. @csw Changing the signature is always possible if you have the key. With segwit only the witness data is changed. However for a normal tx, the txid is changed.
  5247. Let say we do a pure 2 of 2 multisig. But you want to make sure that in case I disappear you can get a refund after a certain time
  5248. So you let me sign the refund tx (locktimed) which is based on the multi sig funding tx which is NOT YET included in the chain
  5249. This refund tx needs the txid of the funding multi sig TX.
  5250. The problem is that if I manage to include our multi sig funding tx with a replaced signature (first party malleabililty), then we still have a 2 of 2 multisig but your refund tx will never be valid.
  5251. With segwit your refund tx will be still valid since the agreement does not depend on my signature of the funding tx
  5252.  
  5253.  
  5254. csw [5:16 AM]
  5255. If you have the key, SegWit TXs can also be altered
  5256.  
  5257.  
  5258. [5:17]
  5259. _Mulitsig with nLockTime_
  5260.  
  5261. SIGHASH_ALL|SIGHASH_ANYONECANPAY
  5262.  
  5263.  
  5264. [5:18]
  5265. SegWit, FT etc etc do nothing to stop non-benign malleability
  5266.  
  5267.  
  5268. [5:18]
  5269. In fact, it is an issue only if:
  5270. 1. The miner doublespends
  5271. 2. RBF allows the user to doublespend
  5272.  
  5273.  
  5274. [5:19]
  5275. _This refund tx needs the txid of the funding multi sig TX._
  5276.  
  5277. Not at all. SIGHASH_ALL|SIGHASH_ANYONECANPAY
  5278.  
  5279.  
  5280. [5:19]
  5281. *Question*
  5282. If a random party screws up your refund by paying the refund BEFORE you... do you care?
  5283.  
  5284.  
  5285. [5:20]
  5286. Next, CLTV is there, so is CSV. They are incorporated into script, like it or not
  5287.  
  5288.  
  5289. [5:20]
  5290. So, you can use these for the refund you propose
  5291.  
  5292.  
  5293. csw [5:22 AM]
  5294. @janko33
  5295. This is a business process issue and comes to learning and implementing how to use the features in Bitcoin rather than changing Bitcoin to fit the square peg in a round hole.
  5296.  
  5297. You have a square hole. People just do not use it.
  5298.  
  5299. 4 replies Last reply today at 7:27 AM View thread
  5300.  
  5301.  
  5302. hyena [5:25 AM]
  5303. I'd prefer a round hole though, personally :wink:
  5304.  
  5305.  
  5306. csw [5:26 AM]
  5307. Oh and @janko33 http://zander.github.io/posts/Flexible_Transactions/
  5308. nLockTime is depreciated... so your TX is screwed if not already in the chain
  5309.  
  5310.  
  5311. [5:26]
  5312. @hyena
  5313.  
  5314.  
  5315. [5:26]
  5316. I like choice
  5317.  
  5318.  
  5319. [5:27]
  5320. I like the option of a round or a square hole
  5321.  
  5322.  
  5323. [5:28]
  5324. We would need to see what was implemented, but it is a possible that it could be killed off.
  5325. Craig S Wright
  5326. Oh and @janko33 http://zander.github.io/posts/Flexible_Transactions/
  5327. nLockTime is depreciated... so your TX is screwed if not already in the chain
  5328. Posted in #generalToday at 5:26 AM
  5329.  
  5330.  
  5331. hyena [5:28 AM]
  5332. I'm just personally more fit for round holes, and curves in general :stuck_out_tongue:
  5333.  
  5334.  
  5335. janko33 [5:29 AM]
  5336. I was not using flextrans in my example just normal versus segwit
  5337.  
  5338.  
  5339. csw [5:29 AM]
  5340. As long as the curves are not too curvy
  5341.  
  5342.  
  5343. [5:29]
  5344. Just right works :wink:
  5345.  
  5346.  
  5347. hyena [5:29 AM]
  5348. :joy:
  5349.  
  5350.  
  5351. spunky
  5352. [5:29 AM]
  5353. Deprecated not depreciated
  5354.  
  5355.  
  5356.  
  5357. csw [5:29 AM]
  5358. Yep
  5359.  
  5360.  
  5361. janko33 [5:33 AM]
  5362. @csw The process was this: Create multi a sig address, only the public address only the public keys are needed
  5363. You want to have agreement for a refund BEFORE you pay to the multi sig.
  5364. In order to do that you need the details of the utxo generated by the funding tx (e.g. double escrow).
  5365. But this will depend on signatures.
  5366. Txid should not depend on random signatures. But there are now and there used in every tx.
  5367. In order to send fund you make a reference to a utxo
  5368.  
  5369.  
  5370. csw [5:34 AM]
  5371. So... one of the things that FT and SegShit _fix_
  5372.  
  5373. *Sighash flags based masking*, Sighash flags can be used to ignore certain parts of a script when signing.
  5374.  
  5375. This also means that the use cased for several functions that cxan be added and created again (such as ones Mike H started) such as Lighthouse are also killed off
  5376.  
  5377.  
  5378. [5:35]
  5379. @janko33
  5380. SIGHASH_ALL|SIGHASH_ANYONECANPAY
  5381.  
  5382.  
  5383. [5:35]
  5384. In the next few days a video will be out on CoinGeek from HK
  5385.  
  5386.  
  5387. [5:36]
  5388. This is where I start discussing thresholds and Blinding
  5389.  
  5390.  
  5391. [5:36]
  5392. You can do all that and not even use P2SH
  5393.  
  5394.  
  5395. [5:36]
  5396. No changes to Bitcoin needed
  5397.  
  5398.  
  5399. janko33 [5:38 AM]
  5400. @csw How can you alter a segwit tx. The actual tx (changing only the txid but nothing else), not the witness?
  5401. How do you alter the txid of a segwit tx?
  5402.  
  5403.  
  5404. csw [5:38 AM]
  5405. The parties recreate
  5406.  
  5407.  
  5408. [5:38]
  5409. But I am not interested in SegShit, so I will not be going into it more
  5410.  
  5411.  
  5412. janko33 [5:39 AM]
  5413. that was the main argument.. that txid cannot be changed.. only witness changes..
  5414.  
  5415.  
  5416. csw [5:40 AM]
  5417. Basically, I will not go into segwit problems further as I have no interest in segwit solutions being made.
  5418.  
  5419.  
  5420. [5:41]
  5421. SegWit does not address same party malleability
  5422.  
  5423.  
  5424. [5:41]
  5425. Do not fall for that
  5426.  
  5427.  
  5428. janko33 [5:44 AM]
  5429. @csw Ok so how will my problem be solved without using txid, because that is malleable?
  5430.  
  5431.  
  5432. [5:44]
  5433. You want to have agreement for a refund BEFORE you pay to the multi sig.
  5434.  
  5435.  
  5436. [5:44]
  5437. and I need to make a reference to a utxo
  5438.  
  5439.  
  5440. csw [5:44 AM]
  5441. In the case you note, you have a multi-sig address and you require collusion. So, the issue is not a malleability case. In fact of point, you do not need to create the TX in the manner you did you achieve the results.
  5442.  
  5443.  
  5444. [5:45]
  5445. No @janko33
  5446. I know I keep stating this:
  5447.  
  5448. SIGHASH_ALL|SIGHASH_ANYONECANPAY
  5449.  
  5450.  
  5451. [5:45]
  5452. And there is scripting with CLTV / CSV
  5453.  
  5454.  
  5455. janko33 [5:45 AM]
  5456. ok will look up for that
  5457.  
  5458.  
  5459. csw [5:45 AM]
  5460. All that can be done in script WITHOUT segwit
  5461.  
  5462.  
  5463. [5:45]
  5464. And easier
  5465.  
  5466.  
  5467. janko33 [5:49 AM]
  5468. can you go more in detail.. I have a hunch that maybe there is the devil hiding :wink: So I just need to create a tx with SIGHASH_ALL and CLTV to have future refund tx working? (edited)
  5469.  
  5470.  
  5471. brad1121
  5472. [5:59 AM]
  5473. A lot to catch up on I see.... see you all in 15min
  5474.  
  5475.  
  5476. peggy [6:02 AM]
  5477. http://www.zerohedge.com/news/2017-09-25/new-wu-tang-coin-raises-money-buy-martin-shkrelis-copy-once-upon-time-shaolin
  5478. zerohedge.com
  5479. New "Wu Tang Coin" Raises Money To Buy Martin Shkreli's Copy Of "Once Upon A Time In Shaolin"
  5480. The goal of the project is to release the album for free on the internet. The company says coin holders will be compensated with (24kB)
  5481.  
  5482.  
  5483. [6:03]
  5484. Where do I send my money?
  5485.  
  5486.  
  5487. brad1121 [6:18 AM]
  5488. What a good read
  5489.  
  5490.  
  5491. janko33 [6:30 AM]
  5492. @csw and to refence the UTXO I can use address of the tx, not the TXid as the UTXO is TXid, txOutIndex, CoinValue, height, coinbase, script, address (edited)
  5493.  
  5494.  
  5495. coinstash [6:53 AM]
  5496. @peggy Rap? Seriously?
  5497.  
  5498.  
  5499. spunky
  5500. [6:54 AM]
  5501. Not just any rap, coinstash... it's an album that no one has ever heard.
  5502.  
  5503.  
  5504. [6:55]
  5505. Pretty sure it was purchased by DPR, then later seized. Not sure how it re-entered society.
  5506.  
  5507.  
  5508. coinstash [6:57 AM]
  5509. My point is, I guess, that it's rap. I mean, it's probably best that no-one has heard it.
  5510.  
  5511.  
  5512. spunky [7:04 AM]
  5513. https://youtu.be/KmGnl7quDbY?t=19s
  5514. YouTube Comedy Central UK
  5515. Chappelle's Show | Wu-Tang Financial
  5516.  
  5517.  
  5518.  
  5519. csw [7:17 AM]
  5520. uploaded this image: image.png
  5521. Add Comment
  5522.  
  5523.  
  5524.  
  5525. kensalomon [7:19 AM]
  5526. so, are you saying a softfork is never a good thing? or just that they should be the extreme and the norm be HF?
  5527.  
  5528.  
  5529. csw [7:21 AM]
  5530. The later
  5531.  
  5532.  
  5533.  
  5534. kensalomon [7:32 AM]
  5535. So to grossly oversimplify, SF can only do so much so they lead to stagnation of the protocol and technology but HF give us the potential to actually make improvements to Bitcoin
  5536.  
  5537.  
  5538. [7:33]
  5539. Right
  5540.  
  5541.  
  5542. joeldalais [7:34 AM]
  5543. the system was built with the intention that HF's would be the norm as needed
  5544.  
  5545.  
  5546. csw [7:34 AM]
  5547. SF can be overridden (as with the ViaBTC - BitcoinClub thing)
  5548.  
  5549.  
  5550. [7:35]
  5551. The issue is not Bitcoin Club are bad, it is that the system was not being used
  5552.  
  5553.  
  5554. [7:35]
  5555. If this was a HF, then they would not have made the malleated TXs
  5556.  
  5557.  
  5558. kensalomon [7:36 AM]
  5559. Got it
  5560.  
  5561.  
  5562. [7:36]
  5563. So, Core bad, pretty much anyone else....not as bad as Core wants you to think
  5564.  
  5565.  
  5566. csw [7:36 AM]
  5567. Do not blame people, create a system that does not rely on trusting them
  5568.  
  5569.  
  5570. [7:37]
  5571. RBF was bad...
  5572.  
  5573.  
  5574. [7:37]
  5575. Very bad
  5576.  
  5577.  
  5578. kensalomon [7:38 AM]
  5579. Yea the concept for Core chain to increase your fee makes somewhat sense and would have a need but it feels like they added more malleability (I know I’m using it wrong) with RBF than they ever solved
  5580.  
  5581.  
  5582. [7:38]
  5583. And RBF does more than just change the fee
  5584.  
  5585.  
  5586. csw [7:40 AM]
  5587. There is no real use to change the fee
  5588.  
  5589.  
  5590. kensalomon [7:41 AM]
  5591. in a properly working chain
  5592.  
  5593.  
  5594. csw [7:41 AM]
  5595. If the block was not congested, it would never have been an issue
  5596.  
  5597.  
  5598. kensalomon [7:41 AM]
  5599. but on Core, they want a fee market
  5600.  
  5601.  
  5602. [7:41]
  5603. yea, we're on the same page, upping a fee even as a thought should've meant we need more capacity not we need to pay more
  5604.  
  5605.  
  5606. csw [7:46 AM]
  5607. The Core BS argument is that in 120 years, TXs will need to be priced such that Bitcoin can survive.
  5608.  
  5609.  
  5610. [7:46]
  5611. First, 120years is a LONG time
  5612.  
  5613.  
  5614. [7:47]
  5615. Next, 5 billion people sending 0.10USD in fees a day over 50 ave TXs and 100,000 large Banks and Corps sending $10 a day in fees for contracts (and this is just the start) adds to more than the Core Fee market
  5616.  
  5617.  
  5618. kensalomon [7:47 AM]
  5619. second, if you process more transactions, everyone is better off, so fees can stay low if blocks can hold more
  5620.  
  5621.  
  5622. csw [7:48 AM]
  5623. Yep
  5624.  
  5625.  
  5626. kensalomon [7:48 AM]
  5627. yea, they're playing with projections when we need a solution to things we face today
  5628.  
  5629.  
  5630. csw [7:49 AM]
  5631. That alone is approx $3,500,000 USD a block in fees
  5632.  
  5633.  
  5634. [7:49]
  5635. So, where is the block reward needed?
  5636.  
  5637.  
  5638. kensalomon [7:52 AM]
  5639. What block size are we assuming? Or just talking widespread saturation of bitcoin usage by businesses and people before 120 years
  5640.  
  5641.  
  5642. csw [7:53 AM]
  5643. As large as it needs to be
  5644.  
  5645.  
  5646. [7:53]
  5647. But, remember this Moore's law thing
  5648.  
  5649.  
  5650. [7:54]
  5651. We end up with smal;l blocks as the systems get bigger
  5652.  
  5653.  
  5654. [7:54]
  5655. 1k was large once
  5656.  
  5657.  
  5658. kensalomon [7:55 AM]
  5659. Yea okay, I know Moore’s law is live and well but do you think it will hold 20 more years? 50? 120?
  5660.  
  5661.  
  5662. joeldalais [7:55 AM]
  5663. yes
  5664.  
  5665.  
  5666. csw [7:55 AM]
  5667. 2600
  5668.  
  5669.  
  5670. [7:56]
  5671. That is about when light speed becomes an issue
  5672.  
  5673.  
  5674. kensalomon [7:56 AM]
  5675. Also, and I guess this has no point if people don’t need to run nodes, but even businesses don’t upgrade internet plans more than once every two or three years so doesn’t that slow down the effect of Moore’s law if user adoption is delayed
  5676.  
  5677.  
  5678. csw [7:56 AM]
  5679. Right now, we have 20 years to catch up with the tech that is not commercial but has been created
  5680.  
  5681.  
  5682. kensalomon [8:00 AM]
  5683. What’s the rate of losing the over development? 1 year for every 5?
  5684.  
  5685.  
  5686. kensalomon [8:08 AM]
  5687. Or is it a slow trickle as we have years we advance a lot and a few of stagnation where we catch up?
  5688.  
  5689.  
  5690. csw [8:09 AM]
  5691. Logistic
  5692.  
  5693.  
  5694. [8:09]
  5695. And we are already behind at 8mb
  5696.  
  5697.  
  5698. kensalomon [8:10 AM]
  5699. Oh we’re talking about just in the Blockchain and supporting technology?
  5700.  
  5701.  
  5702. joeldalais [8:11 AM]
  5703. adoption/growth (edited)
  5704.  
  5705.  
  5706. kensalomon [8:18 AM]
  5707. @csw I just saw your tweet about a huge block being compressed. That’s fucking awesome. I had been thinking scaling might mean coming up with a new form of transaction that’s smaller so it fits more per block but compression makes a ton of sense. Who doesn’t compress data in motion. I feel so stupid now
  5708.  
  5709.  
  5710. [8:18]
  5711. For not seeing that before
  5712.  
  5713.  
  5714. csw [8:19 AM]
  5715. Peter has done this up to 1000TPS level on 2k USD hosts
  5716.  
  5717.  
  5718. [8:19]
  5719. My testing in 2014/2015 was what is now a 20k machine to get 50,000TPS
  5720.  
  5721.  
  5722. [8:20]
  5723. In 5 years, we would expect Moore's law to have 50,000TPS on a 2,500 USD host
  5724.  
  5725.  
  5726. kensalomon [8:20 AM]
  5727. If only we could implement that right now on BCH. Make our 8 MB less than Core chain blocks before soft fork
  5728.  
  5729.  
  5730. csw [8:20 AM]
  5731. And if we have 50k TPS in 5 years I will be more than happy
  5732.  
  5733.  
  5734. [8:21]
  5735. The block is still 8MB
  5736.  
  5737.  
  5738. kensalomon [8:21 AM]
  5739. So it compressed three orders of magnitude
  5740.  
  5741.  
  5742. csw [8:21 AM]
  5743. The xthin sending is larger
  5744.  
  5745.  
  5746. kensalomon [8:21 AM]
  5747. Xthin?
  5748.  
  5749.  
  5750. csw [8:21 AM]
  5751. It needs to decompress to validate
  5752.  
  5753.  
  5754. kensalomon [8:22 AM]
  5755. I know the block is the same size but when in transit it is less in size
  5756.  
  5757.  
  5758. csw [8:22 AM]
  5759. https://medium.com/@peter_r/towards-massive-on-chain-scaling-presenting-our-block-propagation-results-with-xthin-da54e55dc0e4
  5760. Medium
  5761. Towards Massive On-Chain Scaling: Presenting Our Block Propagation Results With Xthin
  5762. Part 1 of 5: Methodology
  5763. Reading time
  5764. ----------------
  5765. 4 min read
  5766.  
  5767. (51kB)
  5768. May 30th, 2016 at 11:17 AM
  5769.  
  5770.  
  5771. kensalomon [8:22 AM]
  5772. So you need the block compressed, and a checksum to validate before decompressing and validating
  5773.  
  5774.  
  5775. csw [8:22 AM]
  5776. Most TXs will already be at the node/miner
  5777.  
  5778.  
  5779. [8:23]
  5780. So, you need a method to index it and allign
  5781.  
  5782.  
  5783. [8:23]
  5784. That is what xThin does
  5785.  
  5786.  
  5787. [8:23]
  5788. and the result is smaller block sending
  5789.  
  5790.  
  5791. [8:23]
  5792. Basically, it allows Visa level scaling now
  5793.  
  5794.  
  5795. kensalomon [8:23 AM]
  5796. So you’re saying, the block just needs to send the full block if you’re downloading the chain, otherwise the node can just realign the transactions it has in Mempool
  5797.  
  5798.  
  5799. csw [8:24 AM]
  5800. Yes
  5801.  
  5802.  
  5803. kensalomon [8:24 AM]
  5804. I like it
  5805.  
  5806.  
  5807. [8:24]
  5808. So a node can say which it needs
  5809.  
  5810.  
  5811. [8:24]
  5812. And the other nodes share that
  5813.  
  5814.  
  5815. csw [8:24 AM]
  5816. And you can still checkpoint data and download from a hash that you have validated
  5817.  
  5818.  
  5819. kensalomon [8:25 AM]
  5820. Is xthin implemented now?
  5821.  
  5822.  
  5823. [8:25]
  5824. In a PR at least, or test net
  5825.  
  5826.  
  5827. csw [8:27 AM]
  5828. In Unlimited
  5829.  
  5830.  
  5831. [8:27]
  5832. BU has it and it does not require a major change
  5833.  
  5834.  
  5835. kensalomon [8:27 AM]
  5836. Unlimited nodes already do this? Or test
  5837.  
  5838.  
  5839. csw [8:27 AM]
  5840. It is also Backward compatible (edited)
  5841.  
  5842.  
  5843. kensalomon [8:27 AM]
  5844. Sounds like it should be
  5845.  
  5846.  
  5847. csw [8:27 AM]
  5848. You can choose it and scale or not
  5849.  
  5850.  
  5851. kensalomon [8:28 AM]
  5852. So, soft fork?
  5853.  
  5854.  
  5855. [8:28]
  5856. Or not even a fork
  5857.  
  5858.  
  5859. csw [8:28 AM]
  5860. NO, overlay
  5861.  
  5862.  
  5863. [8:28]
  5864. It is not a fork, it is a means to send
  5865.  
  5866.  
  5867. [8:28]
  5868. So, not a fork,
  5869.  
  5870.  
  5871. [8:28]
  5872. but a change to how some nodes send
  5873.  
  5874.  
  5875. kensalomon [8:29 AM]
  5876. Seems to make an RPi node was easier than it is now with Core
  5877.  
  5878.  
  5879. [8:29]
  5880. Makes me giggle
  5881.  
  5882.  
  5883. csw [8:30 AM]
  5884. No
  5885.  
  5886.  
  5887. [8:30]
  5888. RPs crash
  5889.  
  5890.  
  5891. [8:30]
  5892. Too little ram
  5893.  
  5894.  
  5895. kensalomon [8:30 AM]
  5896. That is a fatal flaw I always hated about RPi
  5897.  
  5898.  
  5899. csw [8:33 AM]
  5900. And they do not hold many connections open
  5901.  
  5902.  
  5903. [8:33]
  5904. So, more centralised
  5905.  
  5906.  
  5907. [8:33]
  5908. 100,000,000,000 RasPis is more centralised than 1000 server hosts
  5909.  
  5910.  
  5911. [8:33]
  5912. That seems hard for people to get
  5913.  
  5914.  
  5915. [8:33]
  5916. But this is the network
  5917.  
  5918.  
  5919. [8:34]
  5920. And the graph theory for this is well developed
  5921.  
  5922.  
  5923. brad1121
  5924. [8:35 AM]
  5925. Really needs to be a blockchain for dummies book series. Naturally one that BS has had nothing to do with. Hence they will be part of the target audience
  5926.  
  5927.  
  5928. shemuel [8:36 AM]
  5929. Great info this morning. :rocket::popcorn:
  5930.  
  5931.  
  5932. joeldalais
  5933. [8:36 AM]
  5934. " We consider a blockchain to be a type of DLT where records are collated into “blocks” and linked
  5935. using a cryptographic signature." - FCA terminology for what a blockchain is, see, even they *get it* where blockstream/core doesn't.
  5936.  
  5937.  
  5938.  
  5939. [8:37]
  5940. and some others..
  5941.  
  5942.  
  5943. [8:37]
  5944. dlt = distributed ledger technology
  5945.  
  5946.  
  5947. kensalomon [8:38 AM]
  5948. Can that book series be distributed with a hardware wallet in the shape of a bank building?
  5949.  
  5950.  
  5951. brad1121
  5952. [8:38 AM]
  5953. Lol
  5954.  
  5955.  
  5956. kensalomon [8:38 AM]
  5957. The title, being your own bank for dummies
  5958.  
  5959.  
  5960. [8:39]
  5961. Though Blockchain can be used for other things
  5962.  
  5963.  
  5964. [8:40]
  5965. OMG! Let’s make a “My first Blockchain” baby book....
  5966.  
  5967.  
  5968.  
  5969. [8:41]
  5970. Every crypto nerd would buy it
  5971.  
  5972.  
  5973. [8:41]
  5974. Mae can send a copy to LukeJr
  5975.  
  5976.  
  5977. [8:42]
  5978. And other Core
  5979.  
  5980.  
  5981. csw [8:44 AM]
  5982. Visa has tested 80,000 TPS
  5983.  
  5984.  
  5985. [8:45]
  5986. Mastercard 52,000 Tps
  5987.  
  5988.  
  5989. blockextreme [8:45 AM]
  5990. What happen with viabtc?
  5991.  
  5992.  
  5993. [8:45]
  5994. offtopic*
  5995.  
  5996.  
  5997. [8:46]
  5998. I mean not the exchange but the fuzz you guys are talking about
  5999.  
  6000.  
  6001. kensalomon [8:47 AM]
  6002. Not sure but it sounds like they accidentally mined malleated transactions into a block because the soft fork didn’t restrict them from this and so soft forks are bad....totally fucked that up but I tried
  6003.  
  6004.  
  6005. [8:50]
  6006. The basics though are a block was mined that would’ve been rejected if not soft fork
  6007.  
  6008.  
  6009. [8:50]
  6010. But hard fork
  6011.  
  6012.  
  6013. blockextreme [8:59 AM]
  6014. any source of that happening?
  6015.  
  6016.  
  6017. otaci [9:01 AM]
  6018. I was expecting a flood of messages on reddit but not seen anything yet. Anyone got something?
  6019.  
  6020.  
  6021. blockextreme [9:05 AM]
  6022. Would be nice to use that info
  6023.  
  6024.  
  6025. tomothy [9:42 AM]
  6026. Csw, is there an alternative forum besides Reddit/bitcointalk that you've thought about writing this stuff on? Slack sucks for catching up. I'm mainly thinking bulletin board because that's what I'm used to but and something not Reddit. I think the type of medium influences discussion. I.e. twitter, vs Reddit, vs slack, vs bulletin board/forum. Could just be me. Just wondering.
  6027.  
  6028.  
  6029. kensalomon [9:44 AM]
  6030. Yours.org?
  6031.  
  6032.  
  6033. libitx [9:44 AM]
  6034. If there's interest for such a thing, I'd be happy to set up and run a bitcoin cash Discourse forum
  6035.  
  6036.  
  6037. csw [9:45 AM]
  6038. We have papers coming
  6039.  
  6040.  
  6041. [9:45]
  6042. Most things like reddit etc just attract trolls
  6043.  
  6044.  
  6045. kensalomon [9:47 AM]
  6046. I think you mean "The internet attracts trolls"
  6047.  
  6048.  
  6049.  
  6050. otaci [9:47 AM]
  6051. https://bitco.in/forum/ ?
  6052. bitco.in
  6053. Bitcoin Forum
  6054. Bitcoin Forum is a community of developers, academics, and entrepreneurs dedicated to promoting and improving Bitcoin. (2kB)
  6055.  
  6056.  
  6057.  
  6058. csw [9:48 AM]
  6059. Limited time right now. Much happening in the background (edited)
  6060.  
  6061.  
  6062. [9:48]
  6063. and the more you guys take this and run with it, the better
  6064.  
  6065.  
  6066. otaci [9:55 AM]
  6067. These guys won't use bitcoin as a settlement layer https://www.coindesk.com/barclays-joins-cls-blockchain-consortium-search-swift-alternative/
  6068. CoinDesk
  6069. Barclays Joins CLS Blockchain Consortium in Search of Swift Alternative - CoinDesk
  6070. Barclays has become the latest major financial institution to join the foreign exchange-focused blockchain consortium CLS.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement