From: Angel Leon <gubatron@gmail.com>
To: Ahmed Zsales <ahmedzsales18@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP [104]: Replace Transaction Fees with Data, Discussion Draft 0.2.9
Date: Mon, 17 Aug 2015 12:52:03 -0400 [thread overview]
Message-ID: <CADZB0_bgqngwyho4VSrozqz45ahakG6OvqpEHX+_gKMzG6YO2g@mail.gmail.com> (raw)
In-Reply-To: <CADr=VrRH2MkvRek5TNidLTuenWGupB07yysh7DgynUghkOyfaA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
>"By increasing the size of blocks, transaction fees may not be available
to supplement mining revenue and so those who do not have access to cheap
or free power to mine;"
why?
wouldn't a bigger block size actually allow for more transactions per
block, therefore more fees to be collected, and the cost spread out among
many more users (thus still keeping tx fees low). If anything, wouldn't
bigger blocksizes are needed to suplement the losses of coinbase rewards
being halfed.
http://twitter.com/gubatron
On Mon, Aug 17, 2015 at 12:39 PM, Ahmed Zsales via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello,
>
> Here we propose a long-term solution to replace mining rewards and
> transactions fees.
>
> BIP [104] is currently a discussion draft only.
>
>
> https://drive.google.com/file/d/0BwEbhrQ4ELzBSXpoUjRkc01QUGc/view?usp=sharing
>
> Views and feedback welcome.
>
> Regards,
>
> Ahmed
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 2525 bytes --]
next prev parent reply other threads:[~2015-08-17 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 16:39 [bitcoin-dev] BIP [104]: Replace Transaction Fees with Data, Discussion Draft 0.2.9 Ahmed Zsales
2015-08-17 16:52 ` Angel Leon [this message]
2015-08-17 17:16 ` Angel Leon
2015-08-17 17:03 ` Jorge Timón
[not found] ` <CADJgMzu-fsB5otn=2WPUKvVfz_1_Fx5HY7g+Lx_9Ak215a_KgA@mail.gmail.com>
[not found] ` <CADr=VrQC2vix=5nOJ5PrzarfUdtvV_xzUc5YStJL05PD8KxAhg@mail.gmail.com>
2015-08-17 18:28 ` Ahmed Zsales
[not found] ` <CADJgMzsoTctgRC1HLRVNtc09abgz+7cFzoKBpf1_otk6LQK4Fg@mail.gmail.com>
2015-08-17 23:57 ` Ahmed Zsales
[not found] <CADr=VrRa7j4Rd__v7HK3hiVD=GGmm1X1LcE25Hn=7AC_rzAreg@mail.gmail.com>
2015-08-22 11:01 ` [bitcoin-dev] BIP 104: " Ahmed Zsales
2015-08-23 6:51 ` Jorge Timón
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=CADZB0_bgqngwyho4VSrozqz45ahakG6OvqpEHX+_gKMzG6YO2g@mail.gmail.com \
--to=gubatron@gmail.com \
--cc=ahmedzsales18@gmail.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