📅 Original date posted:2013-11-06 📝 Original message:On Wed, Nov 6, 2013 at ...

Tier Nolan [ARCHIVE] /

npub1g6v…l5wd

2023-06-07 15:09:12

in reply to nevent1q…eu46

📅 Original date posted:2013-11-06
📝 Original message:On Wed, Nov 6, 2013 at 5:50 AM, Matt Corallo <bitcoin-list at bluematt.me>wrote:

> Relay node details:
> * The relay nodes do some data verification to prevent DoS, but in
> order to keep relay fast, they do not fully verify the data they are
> relaying, thus YOU SHOULD NEVER mine a block building on top of a
> relayed block without fully checking it with your own bitcoin validator
> (as you would any other block relayed from the P2P network).
>

Wouldn't this cause disconnects due to misbehavior?

A standard node connecting to a relay node would receive
blocks/transactions that are not valid in some way and then disconnect.

Have you looked though the official client to find what things are
considered signs that a peer is hostile? I assume things like double
spending checks count as misbehavior and can't be quickly checked by a
relay node.

Maybe another bit could be assigned in the services field as "relay". This
means that the node doesn't do any checking.

Connects to relay nodes could be command line/config file only. Peers
wouldn't connect to them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131106/2ac17bfa/attachment.html>;

Author Public Key

npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd

Show more details

Published at

2023-06-07 15:09:12

Kind type

1 Short Text Note

Event JSON

{ "id": "db9c2d824ec0053d3dd8284f126f100eda1b2a8fbdb62d3c66bf733b7da7c5f7", "pubkey": "46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e", "created_at": 1686150552, "kind": 1, "tags": [ [ "e", "1a98a3cfd54df3ed479efd51703516524134bdfd6bb00267750e15ea4fca3178", "", "root" ], [ "e", "0be89554d7976b9aea15d95d10e1470c4869af274a0e71200d89e549a0fad37a", "", "reply" ], [ "p", "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11" ] ], "content": "📅 Original date posted:2013-11-06\n📝 Original message:On Wed, Nov 6, 2013 at 5:50 AM, Matt Corallo \u003cbitcoin-list at bluematt.me\u003ewrote:\n\n\u003e Relay node details:\n\u003e * The relay nodes do some data verification to prevent DoS, but in\n\u003e order to keep relay fast, they do not fully verify the data they are\n\u003e relaying, thus YOU SHOULD NEVER mine a block building on top of a\n\u003e relayed block without fully checking it with your own bitcoin validator\n\u003e (as you would any other block relayed from the P2P network).\n\u003e\n\nWouldn't this cause disconnects due to misbehavior?\n\nA standard node connecting to a relay node would receive\nblocks/transactions that are not valid in some way and then disconnect.\n\nHave you looked though the official client to find what things are\nconsidered signs that a peer is hostile? I assume things like double\nspending checks count as misbehavior and can't be quickly checked by a\nrelay node.\n\nMaybe another bit could be assigned in the services field as \"relay\". This\nmeans that the node doesn't do any checking.\n\nConnects to relay nodes could be command line/config file only. Peers\nwouldn't connect to them.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131106/2ac17bfa/attachment.html\u003e", "sig": "07982c4ad9c0a3877690fe06d4a0964d32e319bd75f57f0a95004cad8bf9a1ad16fae859f68dddc95a262edd3c82ff14b2be76e424aaccc69cf5cdd0e72ff987" }