|
Title: Does SegWit require any change in using send/receive API? Post by: RocketSingh on March 18, 2016, 10:21:45 AM I am using blockcypher send/receive API in certain services and accept Tx with 1+ confirmations. Post SegWit, do I need any change to be made at my end?
Title: Re: Does SegWit require any change in using send/receive API? Post by: achow101 on March 18, 2016, 11:40:45 AM I am using blockcypher send/receive API in certain services and accept Tx with 1+ confirmations. Post SegWit, do I need any change to be made at my end? It depends on whether blockcypher changes their API but it shouldn't matter unless you are getting raw transactions and verifying then.Title: Re: Does SegWit require any change in using send/receive API? Post by: gmaxwell on March 18, 2016, 04:03:32 PM I am using blockcypher send/receive API in certain services and accept Tx with 1+ confirmations. Post SegWit, do I need any change to be made at my end? No, only if that API did something weird.Title: Re: Does SegWit require any change in using send/receive API? Post by: rizzlarolla on March 18, 2016, 06:48:05 PM I am using blockcypher send/receive API in certain services and accept Tx with 1+ confirmations. Post SegWit, do I need any change to be made at my end? No, only if that API did something weird.Is the API doing "something weird" predictable? Title: Re: Does SegWit require any change in using send/receive API? Post by: achow101 on March 18, 2016, 06:49:16 PM I am using blockcypher send/receive API in certain services and accept Tx with 1+ confirmations. Post SegWit, do I need any change to be made at my end? No, only if that API did something weird.Is the API doing "something weird" predictable? Title: Re: Does SegWit require any change in using send/receive API? Post by: gmaxwell on March 18, 2016, 10:19:26 PM I am using blockcypher send/receive API in certain services and accept Tx with 1+ confirmations. Post SegWit, do I need any change to be made at my end? No, only if that API did something weird.Is the API doing "something weird" predictable? I mean, if you're using a third party API then at any point they could make you add an argument "moon moon fish moon"... but there is no reason for them to do that; likewise for segwit. Title: Re: Does SegWit require any change in using send/receive API? Post by: RocketSingh on May 12, 2016, 05:50:57 PM I am using blockcypher send/receive API in certain services and accept Tx with 1+ confirmations. Post SegWit, do I need any change to be made at my end? No, only if that API did something weird.Is the API doing "something weird" predictable? I mean, if you're using a third party API then at any point they could make you add an argument "moon moon fish moon"... but there is no reason for them to do that; likewise for segwit. p.s. I'm sorry if my Q does not make sense. But, I'm getting a little confused here. Title: Re: Does SegWit require any change in using send/receive API? Post by: achow101 on May 12, 2016, 07:49:10 PM Reading a little about SegWit, what I understood that SegWit addresses will be different from usual addresses. So, how a fund sent to a normal address from a SegWit address will be determined by the API? Your question is not clear. What are you asking about? The API's node will have to be segwit compatible in order to understand the outputs.p.s. I'm sorry if my Q does not make sense. But, I'm getting a little confused here. Title: Re: Does SegWit require any change in using send/receive API? Post by: waxwing on May 13, 2016, 09:30:45 PM I am using blockcypher send/receive API in certain services and accept Tx with 1+ confirmations. Post SegWit, do I need any change to be made at my end? No, only if that API did something weird.Is the API doing "something weird" predictable? I mean, if you're using a third party API then at any point they could make you add an argument "moon moon fish moon"... but there is no reason for them to do that; likewise for segwit. p.s. I'm sorry if my Q does not make sense. But, I'm getting a little confused here. As I understand it, there is no as-yet agreed on address format for "pure" segwit (p2wpkh, p2wsh), but segwit can be done in p2sh (see bip 141), so initially a segwit-supporting wallet can receive funds from a non-segwit-supporting wallet using p2sh addresses. Edit: well, but knightdk's answer still applies if you are talking about APIs. I was just trying to interpret what you were really asking. |