📅 Original date posted:2013-03-13
📝 Original message:On Wed, Mar 13, 2013 at 09:14:03PM +0000, Luke-Jr wrote:
> On Wednesday, March 13, 2013 9:06:44 PM Andy Parkins wrote:
> > On Wednesday 13 Mar 2013 12:56:29 Luke-Jr wrote:
> > > Here's a simple proposal to start discussion from...
> >
> > It seems to me that the biggest failure was not the development of two
> > chains, but the assurance to users (by the client) that their transactions
> > were confirmed.
>
> These are both the same thing.
The idea of the client detecting/warning about not-trivial forking
seems worthwhile too, though, assuming it doesn't already (AIUI it
doesn't).
I don't know if there's any automatic monitoring for forks, but if not
I would assume that the core devs and/or Bitcoin Foundation would be
planning to put some in place. But there's no reason I can see why
end users clients should't be warning of such situations, too, when
they can (obviously they won't always be aware of the fork).
roy
Roy Badami [ARCHIVE] /
npub1tr…0f95j
2023-06-07 11:39:05
in reply to nevent1q…t8ds
Author Public Key
npub1trckpcxmceskq4cykxgwxm63n8ugrjrpu5mk83c90e4upsf7d9gqf0f95jPublished at
2023-06-07 11:39:05Event JSON
{
"id": "a9f95f830b423ed4ae21aff43b72c0aec8a4851294cab0b947a6a964229f0247",
"pubkey": "58f160e0dbc661605704b190e36f5199f881c861e53763c7057e6bc0c13e6950",
"created_at": 1686137945,
"kind": 1,
"tags": [
[
"e",
"02fd249c82d4dd10181a617a5dadf9d8b2d27a405e04f833fafa551fe0bc94b8",
"",
"root"
],
[
"e",
"a0d7857f8d51e26dee770d11571c566f7c5f69b6c8e2a994bbcd1dca8e915994",
"",
"reply"
],
[
"p",
"6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1"
]
],
"content": "📅 Original date posted:2013-03-13\n📝 Original message:On Wed, Mar 13, 2013 at 09:14:03PM +0000, Luke-Jr wrote:\n\u003e On Wednesday, March 13, 2013 9:06:44 PM Andy Parkins wrote:\n\u003e \u003e On Wednesday 13 Mar 2013 12:56:29 Luke-Jr wrote:\n\u003e \u003e \u003e Here's a simple proposal to start discussion from...\n\u003e \u003e \n\u003e \u003e It seems to me that the biggest failure was not the development of two\n\u003e \u003e chains, but the assurance to users (by the client) that their transactions\n\u003e \u003e were confirmed.\n\u003e \n\u003e These are both the same thing.\n\nThe idea of the client detecting/warning about not-trivial forking\nseems worthwhile too, though, assuming it doesn't already (AIUI it\ndoesn't).\n\nI don't know if there's any automatic monitoring for forks, but if not\nI would assume that the core devs and/or Bitcoin Foundation would be\nplanning to put some in place. But there's no reason I can see why\nend users clients should't be warning of such situations, too, when\nthey can (obviously they won't always be aware of the fork).\n\nroy",
"sig": "e10a5372bab8ad4f66fb233ec83e345a89d643a9d0bba88706add45298f2420bca4f56f858cc83eb032bb9e8822a98dc916d8414818f5eb776475033bfc8a375"
}