aa on Nostr: Thanks for the response! I would have thought it was just policy and not consensus ...
Thanks for the response! I would have thought it was just policy and not consensus since the problematic block has not been validated in full yet. Given a valid new block header, my node will ignore any other header of the same height, even though it does not know that the first block received is fully valid, just that the header is. Assuming an implementation in which blocks of the same height can be validated in parallel, all this means is changing what the node does in the event of a tie from “first seen” to “first validated”. What am I missing?
Published at
2024-10-20 21:45:04Event JSON
{
"id": "8f75a3b7d83196b9ec3791cc7a23e142fa03bce3703badd3ac3d1b96cbbc4d78",
"pubkey": "390b5334739c171d82c84fe7c853462d7607537187f2a0695ede3b297a5b988c",
"created_at": 1729460704,
"kind": 1,
"tags": [
[
"e",
"415605e272e72282d8867295e1e26fc4bf80d26f3b4c3e23502aa3ab46d33a6e",
"",
"root"
],
[
"e",
"fab7f397aceae3c62472bf0ca49cc5359a81dc44b6609605d3e23310c8c1913f",
"wss://nostr.vulpem.com",
"reply"
],
[
"p",
"f728d9e6e7048358e70930f5ca64b097770d989ccd86854fe618eda9c8a38106"
]
],
"content": "Thanks for the response! I would have thought it was just policy and not consensus since the problematic block has not been validated in full yet. Given a valid new block header, my node will ignore any other header of the same height, even though it does not know that the first block received is fully valid, just that the header is. Assuming an implementation in which blocks of the same height can be validated in parallel, all this means is changing what the node does in the event of a tie from “first seen” to “first validated”. What am I missing?",
"sig": "859f35ba8ca19f9bbbbcf38b2525387e0e8583b5de4c640d11ddcd43560e78ae1d023c6f69b0c896addc5ee418f75d2f33322dcb82f34a23e3b266a76076da78"
}
