|
Title: Does someone here own 1CAU5ynvE... Post by: vuce on June 16, 2012, 10:11:29 PM If anyone does I would very much like to hear from you :)
(it's kind of important, as an answer I would need could turn a paper that is due tomorrow upside down) Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: rjk on June 16, 2012, 11:01:05 PM Well I for one am not going to bother digging through all my addresses to see if it's in there, unless I have a good reason to. So maybe we could have a little bit of background on this request?
Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: PocketCoin on June 16, 2012, 11:02:11 PM Yeah this sounds like a waste of time to look considering i don't know what this has to do with turning in a paper
Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: mb300sd on June 16, 2012, 11:04:00 PM Well, the input transaction is a double spend, that might be interesting.
http://blockchain.info/tx-index/9492537/8fd2a66e4256dfaf57a74d8c01a2955d2ad3937c810b43278f507c02e4834ada Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: vuce on June 16, 2012, 11:27:17 PM Yeah this sounds like a waste of time to look considering i don't know what this has to do with turning in a paper The paper is on commitcoin implementation, which this double spend is a part of. If this is what I fear it is it might uncover a vulnerability in the protocol that authors shrug off as being practically unexploitable. Anyway it's not like someone could do this by accident so if you don't know you did it don't bother checking. Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: finkleshnorts on June 16, 2012, 11:56:07 PM Yeah this sounds like a waste of time to look considering i don't know what this has to do with turning in a paper The paper is on commitcoin implementation, which this double spend is a part of. If this is what I fear it is it might uncover a vulnerability in the protocol that authors shrug off as being practically unexploitable. Anyway it's not like someone could do this by accident so if you don't know you did it don't bother checking. sub Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: vuce on June 17, 2012, 12:04:06 AM What's with all the sub comments? :) Anyway, after some thinking it's probably just an address collision due to my own stupidity.
Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: rjk on June 17, 2012, 12:06:37 AM What's with all the sub comments? :) Anyway, after some thinking it's probably just an address collision due to my own stupidity. You mentioned a potential protocol vulnerability, so of course many people are interested.Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: error on June 17, 2012, 12:07:29 AM What's with all the sub comments? :) Anyway, after some thinking it's probably just an address collision due to my own stupidity. People don't know they can click "Notify" at the bottom right to subscribe to the thread. Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: vuce on June 17, 2012, 12:08:56 AM What's with all the sub comments? :) Anyway, after some thinking it's probably just an address collision due to my own stupidity. You mentioned a potential protocol vulnerability, so of course many people are interested.Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: rjk on June 17, 2012, 12:09:08 AM What's with all the sub comments? :) Anyway, after some thinking it's probably just an address collision due to my own stupidity. People don't know they can click "Notify" at the bottom right to subscribe to the thread. Just to make this clear, this is commitcoin protocol vulnerability, not bitcoin one. Still interesting nonetheless.Title: Re: Does someone here own 1CAU5ynvEzWAT1QunB77vBKGBAMvF2MEGi? Post by: finkleshnorts on June 17, 2012, 11:27:32 PM What's with all the sub comments? :) Anyway, after some thinking it's probably just an address collision due to my own stupidity. People don't know they can click "Notify" at the bottom right to subscribe to the thread. Wow, why didn't I figured this out earlier? Thank you. No more subs from me. |