justusranvier
Legendary

Activity: 1400
Merit: 1069
|
 |
May 08, 2015, 02:10:13 AM |
|
Let's say for example I am a Snowden sympathizer and the government has outlawed payments to Snowden and the government also suspects that I might want to illegally give Snowden payments. In such an environment identifying the creation of a payment channel to Snowden might be enough for the government to determine guilt, regardless of whether or not they identified the actual payments. So if they knew my payment code and Snowden's payment code, could scanning the blockchain history result in identifying the payment channel (not the actual payments).
I understand this situation is a bit of a reach, just trying to understand it though. An observer will see that Snowden received a payment code, but they won't be able to read whose payment code it is. The only way they learn it was you who set up the channel is if they have some other way to trace the coins you used to do it. A good client would be sure to use mixed coins for notification transactions.
|
|
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
May 08, 2015, 02:12:58 AM |
|
When asked if that behavior was typical of OTC IPOs he stated that it was, but only for successful offerings.
“Yeah, new successful offerings. Many simply go down after the first day. Compare it to the first three days of any recent tech IPOs and you should see a similar pattern.”http://www.miningpool.co.uk/gbtc-trading-explodes-order-book-gap-narrowing/
|
|
|
|
|
rocks
Legendary

Activity: 1153
Merit: 1000
|
 |
May 08, 2015, 02:33:47 AM |
|
Let's say for example I am a Snowden sympathizer and the government has outlawed payments to Snowden and the government also suspects that I might want to illegally give Snowden payments. In such an environment identifying the creation of a payment channel to Snowden might be enough for the government to determine guilt, regardless of whether or not they identified the actual payments. So if they knew my payment code and Snowden's payment code, could scanning the blockchain history result in identifying the payment channel (not the actual payments).
I understand this situation is a bit of a reach, just trying to understand it though. An observer will see that Snowden received a payment code, but they won't be able to read whose payment code it is. The only way they learn it was you who set up the channel is if they have some other way to trace the coins you used to do it. A good client would be sure to use mixed coins for notification transactions. OK I think I got it. So both parties can individually control their anonymity then. If Alice only uses mixed coins for a notification transaction she can be confident that she can not be tied to the payment channel. Similarly if Bob correctly handles the received notification transactions he can be confident that he can not be tied to the payment channel. Thanks for the explaination
|
|
|
|
|
justusranvier
Legendary

Activity: 1400
Merit: 1069
|
 |
May 08, 2015, 02:41:56 AM |
|
Similarly if Bob correctly handles the received notification transactions he can be confident that he can not be tied to the payment channel. Everybody should dispose of their notification transactions via dust-be-gone, but regardless the number of transactions that have been sent to a notification address is publicly visible. What's not visible is who sent them, and whether they are real or not.
|
|
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
May 08, 2015, 03:01:52 AM |
|
|
|
|
|
|
solex
Legendary

Activity: 1078
Merit: 1007
100 satoshis -> ISO code
|
 |
May 08, 2015, 03:43:20 AM |
|
wow, thanks so much for this. there are no other Bitcoin devs i trust more than Alan & Gavin. he's helped me immensely over the years as i was one of the only two to donate $500 (top level) to his initial Armory crowdfunding campaign what, 3-4 yrs ago now? for that, i got an Armory USB stick, a teeshirt, a coupla bitcoins (i think), & most importantly his old laptop with a sticker on the back with his name and phone #'s, lol. i'm quite sure he forgot to remove them and i've only ever used the # twice  he's taught me alot about crypto. i've tried to tailor back my contact with him in the last year or so as i know he is way busier than ever and has grown in stature so it didn't even occur to me to ask his opinion on this matter. best thing about him is he's a great guy. i'm so glad you did and hearing his response is reassuring to me that i am pushing the right direction. thanks again. A pleasure, and snap! I donated $500 to Armory dev as well, but it was easier with BTC at $800+ :-) BTW. the quote is from sourceforge, not a personal communication...
|
|
|
|
|
fairlay
|
 |
May 08, 2015, 05:22:55 AM |
|
Hi, we started a market on the question wether or not the block size will be increased by 2016. https://www.fairlay.com/event/category/bitcoin/blockchain/all/Currently the likelihood is only around 10%. Thant means on the other side that you get about 10 times your money back if you predict on the increase and it actually happens.
|
www.fairlay.com - the Bitcoin prediction market - the future of reliable information
|
|
|
molecular
Donator
Legendary

Activity: 2800
Merit: 1023
|
 |
May 08, 2015, 05:25:30 AM |
|
Do you guys think March 2016 is a bit late? I do.
Maybe we could divert the discussion to 'when should the 20 mb fork be done', like it sometimes works with children: "Do you want daddy to brush your teeth or would you rather want mommy to do it?"
|
PGP key molecular F9B70769 fingerprint 9CDD C0D3 20F8 279F 6BE0 3F39 FC49 2362 F9B7 0769
|
|
|
molecular
Donator
Legendary

Activity: 2800
Merit: 1023
|
 |
May 08, 2015, 06:19:05 AM |
|
after reading Mike Hearn - Crash Landing, I'm thinking: what would it take to achieve this bad situation right now? An additional 5 tps injected into the network with minimal fee would do it, no? so why not... - go short
- open bitcoin transaction spam floodgates (at cost)
- watch hysteria on internetz
- wait for price to crash
- close part of short
- watch 20 mb block limit implemented in a hurry
- close rest of short
- profit

|
PGP key molecular F9B70769 fingerprint 9CDD C0D3 20F8 279F 6BE0 3F39 FC49 2362 F9B7 0769
|
|
|
Odalv
Legendary

Activity: 1414
Merit: 1000
|
 |
May 08, 2015, 07:59:34 AM |
|
Single transaction can contain 10 kB of script => 10 kB of data
|
|
|
|
|
Zangelbert Bingledack
Legendary

Activity: 1036
Merit: 1000
|
 |
May 08, 2015, 10:35:09 AM |
|
I'm not too worried about the blocksize debate now that I know even Peter Todd supports an increase "eventually." To me this says the first sign of actual delays and price impact will see all these guys change their tune.
|
|
|
|
|
afbitcoins
Legendary

Activity: 2101
Merit: 1061
|
 |
May 08, 2015, 10:37:27 AM |
|
I don't know enough about the block size limits really but is increasing it just kicking the can down the road. Can we just keep doing that? A bit like how USA used to keep increasing the debt ceiling
|
|
|
|
|
Odalv
Legendary

Activity: 1414
Merit: 1000
|
 |
May 08, 2015, 10:49:16 AM |
|
I don't know enough about the block size limits really but is increasing it just kicking the can down the road. Can we just keep doing that? A bit like how USA used to keep increasing the debt ceiling
Increasing block size limits is not solution. It is "brute force" ... we are only buying time. 1B people will require 4 GB block size limit.
|
|
|
|
|
inca
Legendary

Activity: 1176
Merit: 1000
|
 |
May 08, 2015, 11:02:07 AM |
|
I don't know enough about the block size limits really but is increasing it just kicking the can down the road. Can we just keep doing that? A bit like how USA used to keep increasing the debt ceiling
Increasing block size limits is not solution. It is "brute force" ... we are only buying time. 1B people will require 4 GB block size limit. Buying time allows alternate solutions to be properly reviewed and tested. Downtime and network issues are not conducive to the adoption wave we know is coming with the next price hump.
|
|
|
|
|
Spaceman_Spiff
Legendary

Activity: 1638
Merit: 1001
₪``Campaign Manager´´₪
|
 |
May 08, 2015, 11:04:09 AM |
|
I don't know enough about the block size limits really but is increasing it just kicking the can down the road. Can we just keep doing that? A bit like how USA used to keep increasing the debt ceiling
Increasing block size limits is not solution. It is "brute force" ... we are only buying time. 1B people will require 4 GB block size limit. Maybe 'buying some time' is quite crucial for coming up with and developing the necessary solutions, and it's not 'kicking the can down the road' knowing the issue will never be properly addressed. Although I don't fully understand the lightning network and its risks/tradeoffs, the presentation slides suggest 133MB blocks would be sufficient for unlimited transactions for 7 billion users. That would be freaking awesome, and solve the scaling problem imho (but again, I don't understand it deeply enough). EDIT: Inca beat me to it  .
|
|
|
|
|
solex
Legendary

Activity: 1078
Merit: 1007
100 satoshis -> ISO code
|
 |
May 08, 2015, 11:08:37 AM |
|
I don't know enough about the block size limits really but is increasing it just kicking the can down the road. Can we just keep doing that? A bit like how USA used to keep increasing the debt ceiling
Increasing block size limits is not solution. It is "brute force" ... we are only buying time. 1B people will require 4 GB block size limit. Maybe 'buying some time' is quite crucial for coming up with and developing the necessary solutions, and it's not 'kicking the can down the road' knowing the issue will never be properly addressed. Although I don't fully understand the lightning network and its risks/tradeoffs, the presentation slides suggest 133MB blocks would be sufficient for unlimited transactions for 7 billion users. That would be freaking awesome, and solve the scaling problem imho (but again, I don't understand it deeply enough). EDIT: Inca beat me to it  . Likewise. And the lightning network is mostly paperwork today, but could be fully operational in 3 years time. Gavin's can-kick would more than cover that period, without a monumental snafu, PR disaster, price collapse, in the meantime.
|
|
|
|
lebing
Legendary

Activity: 1288
Merit: 1002
Enabling the maximal migration
|
 |
May 08, 2015, 11:21:13 AM |
|
Likewise. And the lightning network is mostly paperwork today, but could be fully operational in 3 years time. Gavin's can-kick would more than cover that period, without a monumental snafu, PR disaster, price collapse, in the meantime.
Agree with you guys. I'm really at a loss over this whole discussion. Not extending the limit at some point in the near future is maybe the worst thing we could do. That being said, why do you figure it will take 3 years for lightning to be operational?
|
Bro, do you even blockchain? -E Voorhees
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
May 08, 2015, 11:55:48 AM |
|
Likewise. And the lightning network is mostly paperwork today, but could be fully operational in 3 years time. Gavin's can-kick would more than cover that period, without a monumental snafu, PR disaster, price collapse, in the meantime.
Agree with you guys. I'm really at a loss over this whole discussion. Not extending the limit at some point in the near future is maybe the worst thing we could do. That being said, why do you figure it will take 3 years for lightning to be operational? Not being a software engineer, I can only guess. But in the presentations I've listened to, Rusty Russell has said there will be not 1 but 2 soft forks required to implement lightning. Given Bitcoin's resistance to change it doesn't seem unreasonable that it would take that long even though I agree with you it seems a bit excessive. I'm sure there are several other factors as well that prolong the process.
|
|
|
|
|
lebing
Legendary

Activity: 1288
Merit: 1002
Enabling the maximal migration
|
 |
May 08, 2015, 12:01:30 PM |
|
I'm not too worried about the blocksize debate now that I know even Peter Todd supports an increase "eventually." To me this says the first sign of actual delays and price impact will see all these guys change their tune.
i seriously hope that we dont see any delays. That would mean we dragged our feet far too long and now have to rush to clean up the mess. I think its really great that Mike and Gavin are getting out ahead of this change to try and get consensus before it might even be a possibility.
|
Bro, do you even blockchain? -E Voorhees
|
|
|
solex
Legendary

Activity: 1078
Merit: 1007
100 satoshis -> ISO code
|
 |
May 08, 2015, 12:35:27 PM Last edit: May 08, 2015, 12:53:21 PM by solex |
|
Likewise. And the lightning network is mostly paperwork today, but could be fully operational in 3 years time. Gavin's can-kick would more than cover that period, without a monumental snafu, PR disaster, price collapse, in the meantime.
Agree with you guys. I'm really at a loss over this whole discussion. Not extending the limit at some point in the near future is maybe the worst thing we could do. That being said, why do you figure it will take 3 years for lightning to be operational? OK. Complex systems always have unexpected delays, and 3 years is a guesstimate. LN needs to be coded, tested, and installed on a global network of servers, primed with payment nodes (not sure how it bootstraps), and then actually taking a useful tx loading off the main-chain (leaving aside the politics behind soft-forks). This is not a quick task. Perhaps it will surprise and be available sooner. edit: got the details on the soft-forks: Note that the scheme requires some solution to malleability to allow chains of transactions to be built (this is a common theme, so likely to be mitigated in a future soft fork), but Gregory Maxwell points out that it also wants selective malleability, so transactions can be replaced without invalidating the HTLCs which are spending their outputs. Thus it proposes new signature flags, which will require active debate, analysis and another soft fork.
http://rusty.ozlabs.org/?p=477
|
|
|
|
|