From: Mike Hearn <mike@plan99•net>
To: Amir Taaki <zgenjix@yahoo•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] SatoshiDice and Near-term scalability
Date: Sat, 16 Jun 2012 10:30:30 +0200 [thread overview]
Message-ID: <CANEZrP2n0a37vRiyn3nMY92QaUYkmycVV59OObze3xF39u-mGg@mail.gmail.com> (raw)
In-Reply-To: <1339821211.57245.YahooMailNeo@web121006.mail.ne1.yahoo.com>
Joseph is quite accommodating and doesn't want to hurt the network.
That said "asking him to stop" seems like the worst possible solution
possible. His site is quite reasonable.
I think if I fix bitcoinj to have smarter fee code he might stop
attaching a small fee to every TX, but I'm not sure.
On Sat, Jun 16, 2012 at 6:33 AM, Amir Taaki <zgenjix@yahoo•com> wrote:
> Did anyone try sending them an email asking them to stop or offering help to fix their site? What did they say? I'm sure they would try to be accomodating.
>
>
>
> ----- Original Message -----
> From: Jonathan Warren <jonathan@bitcoinstats•org>
> To: bitcoin-development@lists•sourceforge.net
> Cc:
> Sent: Saturday, June 16, 2012 4:35 AM
> Subject: Re: [Bitcoin-development] SatoshiDice and Near-term scalability
>
> Yes, I measure mainnet confirmation times on a regular basis.
> http://bitcoinstats.org/post/tx-confirmation-times-June2012.png
>
> Before fairly recently, fee-paying transactions never took anywhere close to
> this long to be confirmed.
>
> Jonathan Warren
> (Bitcointalk: Atheros)
>
> -----Original Message-----
> From: Jeff Garzik [mailto:jgarzik@exmulti•com]
> Sent: Friday, June 15, 2012 1:17 PM
> To: bitcoin-development@lists•sourceforge.net
> Subject: [Bitcoin-development] SatoshiDice and Near-term scalability
>
> Hard-fork requires a very high level of community buy-in, because it shuts
> out older clients who will simply refuse to consider >1MB blocks valid.
>
> Anything approaching that level of change would need some good, hard data
> indicating that SatoshiDice was shutting out the majority of other traffic.
> Does anyone measure mainnet "normal tx" confirmation times on a regular
> basis? Any other hard data?
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
prev parent reply other threads:[~2012-06-16 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 17:17 Jeff Garzik
2012-06-15 17:52 ` Stefan Thomas
2012-06-16 2:35 ` Jonathan Warren
2012-06-16 4:33 ` Amir Taaki
2012-06-16 8:30 ` Mike Hearn [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=CANEZrP2n0a37vRiyn3nMY92QaUYkmycVV59OObze3xF39u-mGg@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=zgenjix@yahoo$(echo .)com \
/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