From: "Jorge Timón" <jtimon@jtimon•cc>
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: Sun, 23 Aug 2015 08:51:12 +0200 [thread overview]
Message-ID: <CABm2gDr+UvB2740MEoc2osA2KnFdiw4LVzqqVq_HxVORPaKGxA@mail.gmail.com> (raw)
In-Reply-To: <CADr=VrRPpfBRt-V6yCgzqptyGtUM5wGH_8pSwMCWY54SfQxm5w@mail.gmail.com>
Again, did you got a bip number asigned or did you self-assigned it yourself?
On Sat, Aug 22, 2015 at 1:01 PM, Ahmed Zsales via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hello,
>
> In response to public and private comments and feedback, we have updated
> this working draft.
>
> https://drive.google.com/file/d/0BwEbhrQ4ELzBOUVtOHJQdlhvUmc/view?usp=sharing
>
> Update highlights:
>
> 1. Specific clarifications on replacing the Coinbase subsidy and
> supplementing and not replacing transaction fees.
>
> 2. Clarification on block chain overhead. The value of data mining is on a
> bell curve, so year six data will be removed every year.
>
> 3. Added references to an ability to create global, national and regional
> Bitcoin Price Indices for popular baskets of goods transacted with Bitcoin.
>
> 4. Added references for an ability to use structured block chain data for
> Bitcoin capacity and fork planning.
>
> 5. Removed references to price speculation.
>
> 6. Added preferences for deployment dates of January 2017 or January 2018.
>
> 7. Moving towards BIP format after discussion and evaluation period.
> Technical content will increase in due course and discussion content will be
> removed.
>
> Further views and feedback welcome.
>
> Regards,
>
> Ahmed
>
>
> On Mon, Aug 17, 2015 at 5:23 PM, Ahmed Zsales <ahmedzsales18@gmail•com>
> 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
>
next prev parent reply other threads:[~2015-08-23 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADr=VrRa7j4Rd__v7HK3hiVD=GGmm1X1LcE25Hn=7AC_rzAreg@mail.gmail.com>
2015-08-22 11:01 ` Ahmed Zsales
2015-08-23 6:51 ` Jorge Timón [this message]
2015-08-17 16:39 [bitcoin-dev] BIP [104]: " Ahmed Zsales
2015-08-17 16:52 ` Angel Leon
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
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=CABm2gDr+UvB2740MEoc2osA2KnFdiw4LVzqqVq_HxVORPaKGxA@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=ahmedzsales18@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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