public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jean-Pierre Rupp <root@haskoin.com>
To: Wladimir <laanwj@gmail.com>,
	 Flavien Charlon <flavien.charlon@coinprism.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Increasing the OP_RETURN maximum payload size
Date: Thu, 20 Nov 2014 15:39:16 -0800	[thread overview]
Message-ID: <546E7BA4.3040708@haskoin.com> (raw)
In-Reply-To: <CA+s+GJAW+dKytucOCyR6-=wfUP_im9cZJaGu8nuhp8vGYX8Qdw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 668 bytes --]

Agree,

There are many legitimate uses for a larger OP_RETURN, and application developers are already complaining that the current size is not enough.  It is about adding value to the blockchain.  I know it can grow the blockchain faster, but so far at 40 bytes Bitcoin hasn't experienced death by bloat, nor that is even close to happen.  I understand starting with a prudent approach, but I think it is safe to increase this without worrying.  Actually I would make it even bigger than 80 bytes.

Cheers

On 17/11/14 02:30, Wladimir wrote:
> Agreed. I'm in favor of increasing OP_RETURN size as well. Don't care
> about the actual size.

-- 
Be Happy :)

[-- Attachment #2: 0x310A8A5B.asc --]
[-- Type: application/pgp-keys, Size: 4648 bytes --]

[-- Attachment #3: root.vcf --]
[-- Type: text/x-vcard, Size: 215 bytes --]

begin:vcard
fn:Jean-Pierre Rupp
n:Rupp;Jean-Pierre
org:Haskoin
email;internet:root@haskoin.com
title:Co-Founder
tel;work:+353862720509
x-mozilla-html:FALSE
url:http://haskoin.com/
version:2.1
end:vcard


      reply	other threads:[~2014-11-20 23:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-16 16:21 [Bitcoin-development] Increasing the OP_RETURN maximum payload size Flavien Charlon
2014-11-16 17:24 ` Luke Dashjr
2014-11-16 18:44   ` Jorge Timón
2014-11-16 19:04     ` Jorge Timón
2014-11-17  3:19       ` Alan Reiner
2014-11-17 10:35         ` Pieter Wuille
2014-11-17 11:20           ` Adam Back
2014-11-17 12:31             ` Chris Pacia
2014-11-17 12:39               ` Pieter Wuille
2014-11-18 22:33                 ` Chris Pacia
2014-11-17 11:43           ` Flavien Charlon
2014-11-17 12:00             ` Pieter Wuille
2014-11-17 12:22             ` Jorge Timón
2014-11-18 17:47             ` Btc Drak
2014-11-19  0:46               ` Flavien Charlon
2014-11-17 10:30 ` Wladimir
2014-11-20 23:39   ` Jean-Pierre Rupp [this message]

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=546E7BA4.3040708@haskoin.com \
    --to=root@haskoin.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=flavien.charlon@coinprism.com \
    --cc=laanwj@gmail.com \
    /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