summaryrefslogtreecommitdiff
path: root/85/95a07a323b65959bb28864a324e8f9a38d6d7f
blob: c2b93f6b4783930cd9e0dcdaf4d25e30f1c6c689 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
Return-Path: <jeanpaulkogelman@me.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id D0C637A4
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 24 Jul 2015 01:06:04 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from st11p02im-asmtp001.me.com (st11p02im-asmtp001.me.com
	[17.172.220.113])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4925C149
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 24 Jul 2015 01:06:04 +0000 (UTC)
Received: from [10.52.6.2] (unknown [101.78.135.131])
	by st11p02im-asmtp001.me.com
	(Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31
	2015))
	with ESMTPSA id <0NRY00PUNWDYB440@st11p02im-asmtp001.me.com> for
	bitcoin-dev@lists.linuxfoundation.org;
	Fri, 24 Jul 2015 01:06:03 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure
	engine=2.50.10432:5.14.151,1.0.33,0.0.0000
	definitions=2015-07-24_01:2015-07-22, 2015-07-23,
	1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
	suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam
	adjust=0
	reason=mlx scancount=1 engine=7.0.1-1412110000
	definitions=main-1507240010
Sun-Java-System-SMTP-Warning: Lines longer than SMTP allows found and wrapped.
Content-type: text/plain; charset=gb2312
MIME-version: 1.0 (1.0)
From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
X-Mailer: iPhone Mail (12H143)
In-reply-to: <9E5835B1-4FCC-4CB4-9ABD-F63B9D1C93D9@gmail.com>
Date: Fri, 24 Jul 2015 09:05:58 +0800
Content-transfer-encoding: quoted-printable
Message-id: <470A7E5F-752A-47B6-BACD-916D043646F1@me.com>
References: <CAPg+sBgs-ouEMu=LOVCmOyCGwfM1Ygxooz0shyvAuHDGGZYfJw@mail.gmail.com>
	<CAPg+sBgugLSVEwDLXhgey86_rM2fTjGWXFuXsiZioJKCZiHiNg@mail.gmail.com>
	<CADm_WcbnQQGZoQ92twfUvbzqGwu__xLn+BYOkHPZY_YT1pFrbA@mail.gmail.com>
	<CAPWm=eW8RgrG1CMEAMN4GeiMjZecFvNtZB_Y4rZNeofWSD0=Wg@mail.gmail.com>
	<CADm_WcYCUHs9Qe_T6WJOCUSK6stXYD8v6z5JcGHfRMURoOSFTA@mail.gmail.com>
	<CABm2gDq3JyZx0QCRDbcNSLSOBKdpi4h_7VN1XL8N42U38+eBAA@mail.gmail.com>
	<55B113AF.40500@thinlink.com>
	<CABsx9T1MTc-GmuQyFN1vaFK=CDWV_L214Pi9nR6jLMouQQD0fw@mail.gmail.com>
	<C5A70F53-4779-457A-A06A-686877706F89@gmail.com>
	<CADL_X_exckh5T2BfzPEp26fPR3TD69QarwroDEdS_9wtnKbf+g@mail.gmail.com>
	<6F436293-9E2B-461C-B105-FC4CF9EBFC69@gmail.com>
	<CADL_X_fs3-Zj-9nHu5HXCS=kNFUTJkrUR_8SL+d+M4ziwB66Jw@mail.gmail.com>
	<CABm2gDqFe+_g5Mk=tXCD94x74pu6SiL+XHhMM-T3bBw78m3Mow@mail.gmail.com>
	<D161F6BB-BFB1-4B9F-B024-D60A170F393C@gmail.com>
	<CALqmWPC8PdSPS3chhnjBaTixrvvg0VrEaXzd3OvbXifkMs0DUw@mail.gmail.com>
	<42BF7FEB-320F-43BE-B3D9-1D76CB8B9975@gmai> <l.com@mac.com>
	<D472C05D-7164-4ED1-B571-94415AD8E60F@gmail.com>
	<346D4CE0-E00D-4ABB-B131-EFA1416CB20C@me.com>
	<29363BE6-72A7-4D06-A974-C52BA12FD8BD@gmail.com>
	<55FFBC8F-A3C9-4109-89C7-AC359FBBD478@me.com>
	<9E5835B1-4FCC-4CB4-9ABD-F63B9D1C93D9@gmail.com>
To: Eric Lombrozo <elombrozo@gmail.com>
X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00,MIME_QP_LONG_LINE,
	RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core and hard forks
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jul 2015 01:06:05 -0000

There really isn't any need for a 3rd party here. Those "services" can just b=
e the miners themselves.


jp

> On Jul 24, 2015, at 8:56 AM, Eric Lombrozo <elombrozo@gmail.com> wrote:
>=20
>=20
>> On Jul 23, 2015, at 5:45 PM, Jean-Paul Kogelman <jeanpaulkogelman@me.com>=
 wrote:
>>=20
>> Quality of service as in:
>>=20
>>> X satoshi / kb =3D included in block currently worked on;
>>=20
>>> Y satoshi / kb =3D included in next block;
>>=20
>>> Z satoshi / kb =3D included in block after that, etc.
>>=20
>> Block count starts when transaction is first seen. Miners can set X, Y, Z=
.
>>=20
>> Market develops when miners start setting different values and adding mor=
e transactions to blocks as opposed to other miners with higher settings.
>>=20
>> It basically comes down to the miners themselves if they want a healthy f=
ee market. If they stick to their guns, their influence on the fees will be p=
roportional to their hashing power.
>>=20
>> jp
>=20
>=20
> The scheme I=A1=AFve been considering is the use of services (separate fro=
m miners) that guarantee inclusion for you for some predetermined price and t=
hen do the bidding on your behalf. Via contracts you can guarantee you get i=
ncluded within a certain number of blocks or you receive a full refund=A1=AD=
or even possibly receive compensation for failure to deliver.