From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Useful bitcoin patches...
Date: Sun, 10 Jul 2011 16:30:53 -0400 [thread overview]
Message-ID: <201107101630.55518.luke@dashjr.org> (raw)
In-Reply-To: <1310325132.2230.20.camel@Desktop666>
On Sunday, July 10, 2011 3:12:12 PM Matt Corallo wrote:
> On Sun, 2011-07-10 at 14:42 -0400, Luke-Jr wrote:
> > For the "3diff" version, I extracted and made proper git branches for
> > each logical part:
> > hub_mode
>
> No, no, no, no, no. This has been discussed several times and provides
> little to no advantage for miners and has the potential to severely harm
> the network.
I just said it exists. I don't expect anyone to promote or merge it.
> > In addition, I also consider these branches valid candidates for merging:
> > coinbaser (popens a given command and reads coinbase outputs from
> > stdout)
>
> Seems like you are the only one who would benifit here, as noone else
> but eligius changes coinbase output to a random set.
I suspect because they haven't figured out how. Take it or leave it.
> > minfee_modes (internal function changes to allow specifying different
> > fees for relay, send, or accept-in-block)
>
> We don't need something that just generically changes the functions to
> allow whatever fee you want, we need something more generalized to allow
> more custom settings, not just blind accept if fee is x per kb or
> something. Sipa has suggested various things that should allow for more
> fee control by the users while still preventing users from sending
> transactions that lock their coins in limbo.
This is a step in that direction, at least, by providing the mode as input.
Since 0.4 is moving to Qt, perhaps moving GetMinFee to QtScript is
appropriate.
> > \-- eligius_relay (relay lower fees only Eligius will accept)
> > \-- eligius_sendfee (send lower fees only Eligius will accept)
>
> No, and no. Just because you are willing to accept lower fees doesn't
> mean the incentives are right to prevent DDoS. The fees aren't there to
> support the miners (not for a while, at least) they are there to prevent
> stupid users from DDoSing and just generally wasting everyone else's
> resources for no reason.
Again, take it or leave it, but in the meantime you're asking for trouble from
users who feel they're being forced to pay more than they have to. Or perhaps
rather than trouble, that decision will increase awareness of other clients
that don't try to control the users. That could be good too.
next prev parent reply other threads:[~2011-07-10 20:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 3:23 Jeff Garzik
2011-07-01 16:03 ` Christian Decker
2011-07-01 16:23 ` Gregory Maxwell
2011-07-01 16:25 ` Matt Corallo
2011-07-01 18:59 ` Luke-Jr
2011-07-10 18:42 ` Luke-Jr
2011-07-10 19:12 ` Matt Corallo
2011-07-10 20:30 ` Luke-Jr [this message]
[not found] ` <1310335963.2230.29.camel@Desktop666>
[not found] ` <201107101846.09997.luke@dashjr.org>
2011-07-10 22:58 ` Matt Corallo
2011-08-04 20:29 ` Luke-Jr
2011-08-04 20:42 ` Luke-Jr
2011-08-04 23:43 ` Jeff Garzik
2011-08-05 3:01 ` Luke-Jr
2011-09-03 15:27 ` [Bitcoin-development] Last try: Fixes for 0.4 Luke-Jr
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=201107101630.55518.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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