From: Tamas Blummer <tamas@bitsofproof.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] On OP_RETURN in upcoming 0.9
Date: Mon, 24 Feb 2014 19:13:29 +0100 [thread overview]
Message-ID: <449F9E79-7B1B-4821-93C3-F1DC1B5B1DEA@bitsofproof.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 452 bytes --]
It costs at least 5430 satoshis to create an output at the moment.
Is the same spam limit applied if the script is OP_RETURN?
If not, I would be concerned od opening a cheap spam.
Tamas Blummer
On Mon, Feb 24, 2014 at 11:39 AM, Wladimir <laanwj@gmail.com> wrote:
>
> And if this is not abused, these kind of transactions become popular, and
> more space is really needed, the limit can always be increased in a future
> version.
>
> Wladimir
>
[-- Attachment #1.2: Type: text/html, Size: 818 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next reply other threads:[~2014-02-24 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 18:13 Tamas Blummer [this message]
2014-02-24 22:35 ` [Bitcoin-development] On OP_RETURN in upcoming 0.9 Mark Friedenbach
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=449F9E79-7B1B-4821-93C3-F1DC1B5B1DEA@bitsofproof.com \
--to=tamas@bitsofproof.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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