📅 Original date posted:2014-08-08
📝 Original message:Link: https://github.com/bitcoin/bitcoin/pull/4657
It is not necessary to build all functionality into bitcoind, to form
a decentralized network. BitPay's insight open source block explorer
API project requires, and runs on top of, bitcoind. Therefore, at the
same IP address as bitcoind, other services are made available to the
public (scriptPubkey queries, other added-value queries). This results
in a decentralized network of "anyone running a full node and an
insight server", as a subset of the whole P2P net. One then does not
need to trust BitPay's insight server, but may query any number of
insight servers from multiple operators, and survey the results.
Obviously, we want to build this in a generic, vendor-neutral way. As
such, NODE_EXT_SERVICES is advertised via the "addr" P2P message.
Nodes that recognize the NODE_EXT_SERVICES bit may connect to that
node, query a services list via "getextsrv" P2P message, and then take
further action based on the results. The results are quite
straightforward:
service name, service port (or -1 if undefined), list of string
key/value attribs
Services may only advertise added services if and only if the external
services are at the same IP address that is being advertised.
This is not a fully baked proposal by any means, but more of a trial
balloon to get discussion moving.
There is no need to implement all services inside bitcoind...
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 15:25:02
in reply to nevent1q…ess9
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Published at
2023-06-07 15:25:02Event JSON
{
"id": "82cb83f8ff29ae444ef69815010077ebe57d695742474d015de3e6c590b6bf7a",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686151502,
"kind": 1,
"tags": [
[
"e",
"1469c70b65b3d566e17429f93d31db1fc95b8cc6ebff3a3c5370afa0b4c5b71b",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2014-08-08\n📝 Original message:Link: https://github.com/bitcoin/bitcoin/pull/4657\n\nIt is not necessary to build all functionality into bitcoind, to form\na decentralized network. BitPay's insight open source block explorer\nAPI project requires, and runs on top of, bitcoind. Therefore, at the\nsame IP address as bitcoind, other services are made available to the\npublic (scriptPubkey queries, other added-value queries). This results\nin a decentralized network of \"anyone running a full node and an\ninsight server\", as a subset of the whole P2P net. One then does not\nneed to trust BitPay's insight server, but may query any number of\ninsight servers from multiple operators, and survey the results.\n\nObviously, we want to build this in a generic, vendor-neutral way. As\nsuch, NODE_EXT_SERVICES is advertised via the \"addr\" P2P message.\nNodes that recognize the NODE_EXT_SERVICES bit may connect to that\nnode, query a services list via \"getextsrv\" P2P message, and then take\nfurther action based on the results. The results are quite\nstraightforward:\n\nservice name, service port (or -1 if undefined), list of string\nkey/value attribs\n\nServices may only advertise added services if and only if the external\nservices are at the same IP address that is being advertised.\n\nThis is not a fully baked proposal by any means, but more of a trial\nballoon to get discussion moving.\n\nThere is no need to implement all services inside bitcoind...\n\n-- \nJeff Garzik\nBitcoin core developer and open source evangelist\nBitPay, Inc. https://bitpay.com/",
"sig": "6c0c447453ea51e38d327096ae09bbf59c2077b971cfa92d80902b16a743843abad3b3eb7a57f01b4903e6e92d4089015ae21dff1b847c58db46bdb74314ab3a"
}