public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: CANNON <cannon@cannon-ciota.info>
To: adan@stampery.com,
	"Adán Sánchez de Pedro Crespo" <adan@stampery.co>,
	"Bitcoin Protocol Discussion"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Why SegWit Anyway?
Date: Sat, 25 Nov 2017 15:41:44 +0000	[thread overview]
Message-ID: <22ba8756-c661-8504-8de3-108626066df0@cannon-ciota.info> (raw)
In-Reply-To: <15502d41-61f2-9a17-a4cf-03cd20a87368@stampery.com>

On 11/21/2017 01:16 PM, Adán Sánchez de Pedro Crespo via bitcoin-dev wrote:
> 2. SegWit signatures can be cheaper to verify (linear instead of
> quadratic). Prior to this, DoS attacks were possible by using forged
> transactions including signatures which could take several minutes to
> verify.

Where can I find more resources on this described DoS attack?
And how does SegWit prevent this if using SegWit transactions are not enforced?

Thanks


  reply	other threads:[~2017-11-25 15:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 17:24 [bitcoin-dev] Why SegWit Anyway? Praveen Baratam
2017-11-20 17:39 ` Ariel Lorenzo-Luaces
2017-11-20 17:45 ` Johnson Lau
     [not found]   ` <CAAUFj10ZRQrtEzB_2wp-WS8Q-FGcSegpc_Z6kqvqnDLzNn=DrA@mail.gmail.com>
     [not found]     ` <CAAUFj11_Vh2K4MrmuBre5KaX6F16Jg3PYAsj6SSfzoYYRz_WyA@mail.gmail.com>
2017-11-20 18:04       ` Dan Bryant
2017-11-21 13:10         ` Steve Shadders
2017-11-21 13:16         ` Adán Sánchez de Pedro Crespo
2017-11-25 15:41           ` CANNON [this message]
2017-11-20 18:07   ` Praveen Baratam
2017-11-20 19:58     ` Johnson Lau
2017-11-20 18:59 ` Gregory Maxwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22ba8756-c661-8504-8de3-108626066df0@cannon-ciota.info \
    --to=cannon@cannon-ciota.info \
    --cc=adan@stampery.co \
    --cc=adan@stampery.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox