<unnamed>

Public Key

npub16ywn6evjfsu4q0m94p84sdc7tstu7tguzktfx60dj44ww42yqj7scvjs8h

Profile Code

nprofile1qqsdz8favkfycw2s8aj6sn6cxu09c97095wpt95nd8ke26h824zqf0gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq4xxk2

Publishing to

nostr.wine

relay.damus.io

nos.lol

Last Notes

2023-06-07 15:42:52 UTC

- reply

📅 Original date posted:2015-07-23
📝 Original message:That’s not exactly what’s happened though, is it Cipher? Gavin put forward 20Mb then after analysis and discussion has moved to 8Mb, whereas the other camp of core developers is firmly stuck in the ‘1Mb or bust’ group.
-Rob.
> On 23 Jul 2015, at 17:50, cipher anthem via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> Why not help on a project that actually seems to offer great scalability like the lightning network? There have been great progress there.
>
> Seems like you did your calculations some time ago to prove that your increase is reasonable, yet when others come with different numbers that don't support your position you say it doesn't matter.
>
> Sent: Thursday, July 23, 2015 at 4:28 PM
> From: "Gavin Andresen via bitcoin-dev" <bitcoin-dev at lists.linuxfoundation.org>
> To: "Tom Harding" <tomh at thinlink.com>
> Cc: bitcoin-dev at lists.linuxfoundation.org
> Subject: Re: [bitcoin-dev] Bitcoin Core and hard forks
> On Thu, Jul 23, 2015 at 12:17 PM, Tom Harding via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org <x-msg://14/[email protected]>> wrote:
> On 7/23/2015 5:17 AM, Jorge Timón via bitcoin-dev wrote:
> > they will simply advance the front and start another battle, because
> > their true hidden faction is the "not ever side". Please, Jeff, Gavin,
> > Mike, show me that I'm wrong on this point. Please, answer my question
> > this time. If "not now", then when?
>
> Bitcoin has all the hash power. The merkle root has effectively
> infinite capacity. We should be asking HOW to scale the supporting
> information propagation system appropriately, not WHEN to limit the
> capacity of the primary time-stamping machine.
>
> We haven't tried yet. I can't answer for the people you asked, but
> personally I haven't thought much about when we should declare failure.
>
> Yes! Lets plan for success!
>
> I'd really like to move from "IMPOSSIBLE because... (electrum hasn't been optimized
> (by the way: you should run on SSDs, LevelDB isn't designed for spinning disks),
> what if the network is attacked? (attacked HOW???), current p2p network is using
> the simplest, stupidest possible block propagation algorithm...)"
>
> ... to "lets work together and work through the problems and scale it up."
>
> I'm frankly tired of all the negativity here; so tired of it I've decided to mostly ignore
> all the debate for a while, not respond to misinformation I see being spread
> (like "miners have some incentive to create slow-to-propagate blocks"),
> work with people like Tom and Mike who have a 'lets get it done' attitude, and
> focus on what it will take to scale up.
>
> --
> --
> Gavin Andresen
>
> _______________________________________________ bitcoin-dev mailing list bitcoin-dev at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>_______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150723/a80e6328/attachment.html>