Latest posts of: Balloon

Show Posts
Pages: [1]

on: April 10, 2015, 07:15:01 AM

Does anyone know any big/popular companies that started their business in Jan 2014?

on: February 27, 2015, 06:24:33 PM

Very useful code! One question though. I wrote my own version which basically just takes in any unconfirmed transaction and write it to a file. And I also tried the json API provided by blockchain.info. * https://blockchain.info/unconfirmed-transactions?format=json * What surprises me is that websocket missed several transactions. Is there any way to make sure that the websocket API will return ALL unconfirmed transactions? Balloon

on: September 12, 2014, 06:32:48 PM

Quote from: andytoshi on September 12, 2014, 06:27:50 PM Yes, except for the SIGHASH_ANYONECANPAY flag (which causes only one input to be signed), the sighash type does not affect which inputs are signed. In all cases, the current script is replaced by the scriptPubKey of the output it's spending, and the remaining scripts are blanked out. An extra oddity is that in the SIGHASH_NONE and SIGHASH_SINGLE cases, the other inputs also have their sequence number blanked out. Thank you for your answer! I'm still a little confused about the sequence number being blanked out. What does that mean? Does that mean the order of the inputs doesn't matter anymore? Balloon

on: September 12, 2014, 06:00:21 PM

I didn't quite understand how SIGHASH_ALL and SIGHASH_NONE deal with other inputs. Do these hashtypes sign all other inputs as well? Or does SIGHASH_ALL sign all inputs and SIGHASH_NONE doesn't? Balloon

on: September 12, 2014, 05:40:51 PM

Quote from: Peter Todd on September 12, 2014, 12:34:18 AM Decentralised asset exchange needs it: https://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg03892.html Thank you for your reply! That's a very interesting idea! I have one question though. Since colored coin is using some kind of input-output matching to trace colors. So bitcoins with the same color should be in the "same" position in inputs and outputs. Say the bitcoins in input0 is "red", then the bitcoins in output0 must also be "red". If I remember this colored coin mechanism correctly, then in the example, if Alice puts colored bitcoins in input0 and 1BTC in output0. Then that 1 BTC would become "red". I'm kind of confused how this problem is solved. Balloon

on: September 11, 2014, 08:04:36 PM

I understand how SIGHASH_SINGLE works, but why we need it? Is there any application that will need this feature?

on: August 13, 2014, 11:50:34 PM

"Bitcoin's micropayment feature has been a killer feature for application like spam email control." I think this has been mentioned a lot. But is there any real implementation or proposal about such idea? Also some other applications like ad-hoc network, paid wifi access, tor, etc. Is there any implementation about them?

on: July 29, 2014, 09:31:38 PM

Quote from: gmaxwell on July 29, 2014, 07:02:16 PM Quote from: Balloon on July 29, 2014, 06:53:41 PM All features and new functionalities described in https://en.bitcoin.it/wiki/Contracts are very fascinating. But when would these features be enabled in Bitcoin? When would these complex transactions become "standard" transactions? When would such features be included in a BIP? They're already included since day one. Many of them have long been standard transactions, but for those who are not they don't need to be standard transactions to use them, develop tools for them, or experiment with them. Since a month ago in Master, practically any script encoded as P2SH IsStandard in any case. Sadly there seems to be fairly little true interest in doing anything advanced or at least in building tools to make things usable to laymen. There is no need to create a BIP for features that already part of the protocol, though if some transaction form becomes common and people might want to make interoperable implementations and at that point writing up a specification to help front end implementations interop might make sense, but it wouldn't be a bitcoin protocol thing. Got it! Most things mentioned by Mike, nLockTime, Oracle, SIGHASH, are already implemented. So the problem is just not so many people are using them? And also not many miners accept these transactions?

on: July 29, 2014, 06:53:41 PM

All features and new functionalities described in https://en.bitcoin.it/wiki/Contracts are very fascinating. But when would these features be enabled in Bitcoin? When would these complex transactions become "standard" transactions? When would such features be included in a BIP?

Pages: [1]