[Bitcoin-ml] Risks of Segregated Witness

[Jameson Lopp]

Sure, if you need to store signatures for some reason then you should
either upgrade your node or find a different source from which to retrieve
signatures. I expect there will be plenty of 3rd party APIs from which you
can retrieve the signatures if for some reason you can't run your own
upgraded node.

I'm still not a legal expert, but it sounds like those who are dispute that
portion of the claim as well.
http://www.coindesk.com/bitcoin-legal-experts-nchain-segwit-criticisms-flawed/

- Jameson

On Jun 28, 2017 8:37 AM, "Tom Zander via bitcoin-ml" <bitcoin-ml at lists.
linuxfoundation.org> wrote:

> On Tuesday, 27 June 2017 20:43:58 CEST Jameson Lopp via bitcoin-ml wrote:
> > Note that signature pruning is not even an option yet in Core.
>
> From one point of view, you are correct.
>
> But isn't it so that when a non-SegWit client downloads a block or an
> uncomfirmed transaction, they don't download the signatuers?
>
> I'd argue that has essentially the same effect from a legal POV since the
> argument was that you should store it.
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
> _______________________________________________
> bitcoin-ml mailing list
> bitcoin-ml at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-ml
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-ml/attachments/20170628/eb0bd6ad/attachment.html>