Unless there are objections I intend to assign myself a BIP number for
a postmortem for this event.
I've already been reaching out to parties involved in or impacted by
the fork to gather information, but I do not intend to begin drafting
for a few days (past expirence has shown that it takes time
As I said, this doesn't help against malicious nodes. But it helps on a case such as today's.
On 3 Jul 2015 10:45 pm, Peter Todd wrote:
On Fri, Jul 03, 2015 at 10:43:14PM -0700, Raystonn wrote:
> The SPV clients should be checking node versions. This is for wallet authors to implement
On Fri, Jul 03, 2015 at 10:43:14PM -0700, Raystonn wrote:
> The SPV clients should be checking node versions. This is for
> wallet authors to implement. End-users should just stay current with their
> chosen wallet software.
Nodes can and do lie about what version they are all the time.
Fact
The SPV clients should be checking node versions. This is for wallet authors to implement. End-users should just stay current with their chosen wallet software.
On 3 Jul 2015 10:40 pm, odinn wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raystonn,
How would an average SPV
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raystonn,
How would an average SPV wallet user know anything about this at all?
They might not know it is even happening, or if they have some idea
that something is wrong, then they wouldn't know what to do.
Say you use Electrum, some older version
On Fri, Jul 03, 2015 at 10:17:38PM -0700, Raystonn wrote:
Yeah, I was really surprised when I found out today that bitcoinj
doesn't implement any of the soft-fork code. There's no excuse for not
doing that frankly. :(
> SPV clients are at risk in scenarios like this. We should
> encourage them
SPV clients are at risk in scenarios like this. We should encourage them to check node versions against the minimum required for safety. This check should be upgraded when new BIPs go into effect. It won't help against malicious nodes. But it will help in cases such as today's.
On 3 Jul 2015 8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"The Wall Street of Bitcoin"
On 07/03/2015 08:30 PM, Peter Todd wrote:
> On Sat, Jul 04, 2015 at 03:17:17AM +, Gregory Maxwell wrote:
>> On Sat, Jul 4, 2015 at 3:11 AM, Raystonn
>> wrote:
>>> We need some analysis on why this has happened. It ap
On Sat, Jul 04, 2015 at 03:17:17AM +, Gregory Maxwell wrote:
> On Sat, Jul 4, 2015 at 3:11 AM, Raystonn wrote:
> > We need some analysis on why this has happened. It appears the larger
> > hashrate is violating BIP66. Thus it appears the network is rejecting this
> > BIP, though potentiall
On Sat, Jul 4, 2015 at 3:11 AM, Raystonn wrote:
> We need some analysis on why this has happened. It appears the larger
> hashrate is violating BIP66. Thus it appears the network is rejecting this
> BIP, though potentially accidentally. If this is an accident, how is such a
> large portion o
We need some analysis on why this has happened. It appears the larger hashrate
is violating BIP66. Thus it appears the network is rejecting this BIP, though
potentially accidentally. If this is an accident, how is such a large portion
of hashrate forking, and what can we do to avoid this in t
On Sat, Jun 27, 2015 at 04:54:00PM -0700, Jeff Garzik wrote:
> Generally agreed w/ all this.
>
> To preserve digital signatures now and in the future, and make mbox
> archives actually useful, a minimum modification policy is needed.
ACK
I'd support making the raw archives public for archiving a
On Wed, Jul 01, 2015 at 09:52:57PM -0700, Mark Friedenbach wrote:
> This is called child pays for parent and there is a three year old pull
> request implementing it:
>
> https://github.com/bitcoin/bitcoin/pull/1647
CPFP probably needs changes to the P2P layer to be able to support RBF
scorched e
On Fri, Jul 3, 2015 at 1:33 AM, Jeremy Rubin <
jeremy.l.rubin.tra...@gmail.com> wrote:
> Moxie looks fantastic! The reason I thought RISC-V was a good selection is
> the very active development community which is pushing the performance of
> the ISA implementations forward. Can you speak to the he
14 matches
Mail list logo
