Does SegWit require any change in using send/receive API?

waxwing

sr. member

Activity: 469

Merit: 253

Quote from: RocketSingh on May 12, 2016, 12:50:57 PM

Quote from: gmaxwell on March 18, 2016, 05:19:26 PM

Quote from: rizzlarolla on March 18, 2016, 01:48:05 PM

Quote from: gmaxwell on March 18, 2016, 11:03:32 AM

Quote from: RocketSingh on March 18, 2016, 05: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?

No, only if that API did something weird.

Is the API doing "something weird" predictable?

The prediction is it wouldn't.

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.

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?

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.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: RocketSingh on May 12, 2016, 12:50:57 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?

p.s. I'm sorry if my Q does not make sense. But, I'm getting a little confused here.

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.

RocketSingh

legendary

Activity: 1662

Merit: 1050

Quote from: gmaxwell on March 18, 2016, 05:19:26 PM

Quote from: rizzlarolla on March 18, 2016, 01:48:05 PM

Quote from: gmaxwell on March 18, 2016, 11:03:32 AM

Quote from: RocketSingh on March 18, 2016, 05: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?

No, only if that API did something weird.

Is the API doing "something weird" predictable?

The prediction is it wouldn't.

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.

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?

p.s. I'm sorry if my Q does not make sense. But, I'm getting a little confused here.

gmaxwell

staff

Activity: 4284

Merit: 8808

Quote from: rizzlarolla on March 18, 2016, 01:48:05 PM

Quote from: gmaxwell on March 18, 2016, 11:03:32 AM

Quote from: RocketSingh on March 18, 2016, 05: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?

No, only if that API did something weird.

Is the API doing "something weird" predictable?

The prediction is it wouldn't.

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.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: rizzlarolla on March 18, 2016, 01:48:05 PM

Quote from: gmaxwell on March 18, 2016, 11:03:32 AM

Quote from: RocketSingh on March 18, 2016, 05: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?

No, only if that API did something weird.

Is the API doing "something weird" predictable?

Nope. You only know it if the service running the API announces that something will change or if it suddenly changes and now nothing works.

rizzlarolla

hero member

Activity: 812

Merit: 1001

Quote from: gmaxwell on March 18, 2016, 11:03:32 AM

Quote from: RocketSingh on March 18, 2016, 05: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?

No, only if that API did something weird.

Is the API doing "something weird" predictable?

gmaxwell

staff

Activity: 4284

Merit: 8808

Quote from: RocketSingh on March 18, 2016, 05: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?

No, only if that API did something weird.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: RocketSingh on March 18, 2016, 05: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?

It depends on whether blockcypher changes their API but it shouldn't matter unless you are getting raw transactions and verifying then.

RocketSingh

legendary

Activity: 1662

Merit: 1050

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?

Topic: Does SegWit require any change in using send/receive API? (Read 1438 times)