a node interacts with the p2p network and influences what things propagate faster or slower into node mempools.
this is both in relaying transactions, blocks, as well as whether it will accept a new block that it would otherwise reject (this can only happen to the best block, once a confirmation piles on top the node must accept it or be forked off the network).
if other nodes don't like your relay policies they can black list your node's p2p address, but on the whole it does influence the network in important ways because the transactions that get filtered the least get into blocks before the others can propagate.
it's a very soft power thing, and only really has an impact on latency of transactions getting to a miner who mints a block, or when the size of the network mempool starts to purge small fee transactions, these relays also affect the transactions that can get into blocks because they will preferentially relay the others. in this way also you can do a service to the network by enlarging your mempool so that typical default configurations that would drop transactions would see them propagated again by those who didn't.
it's not a "vote" per se, it's more like, you have an impact on what is more likely to get into a block sooner, and when the mempool is full, what transactions will be dropped and which won't.
mleku
npub1fj…mleku
2025-06-02 17:52:18
in reply to nevent1q…fv20
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2025-06-02 17:52:18Event JSON
{
"id": "2281c5ac708007f19178556fc905309344f1937aaee7a34c018685166ef93902",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1748886738,
"kind": 1,
"tags": [
[
"e",
"699eb515c5cc2ed58d2d09005e2f37ae0850ba84fcbfbe60d62c312b2c6cbb39",
"",
"root",
"fea186c2a4678dbc437704eed2160846e8a781e5fb17056e9bb333840d5bdef2"
],
[
"e",
"e284aa5b72eb73ec6a0b7ba843c95c00b60b7d170323b59a7fd164b8deedb7d7",
"wss://theforest.nostr1.com/",
"reply",
"fea186c2a4678dbc437704eed2160846e8a781e5fb17056e9bb333840d5bdef2"
],
[
"p",
"04c915daefee38317fa734444acee390a8269fe5810b2241e5e6dd343dfbecc9"
],
[
"p",
"bdf02ee67066fdeba255e1ac77d67ad95048ded50eb885a01cab39156e4282df"
],
[
"p",
"fea186c2a4678dbc437704eed2160846e8a781e5fb17056e9bb333840d5bdef2"
]
],
"content": "a node interacts with the p2p network and influences what things propagate faster or slower into node mempools.\n\nthis is both in relaying transactions, blocks, as well as whether it will accept a new block that it would otherwise reject (this can only happen to the best block, once a confirmation piles on top the node must accept it or be forked off the network).\n\nif other nodes don't like your relay policies they can black list your node's p2p address, but on the whole it does influence the network in important ways because the transactions that get filtered the least get into blocks before the others can propagate.\n\nit's a very soft power thing, and only really has an impact on latency of transactions getting to a miner who mints a block, or when the size of the network mempool starts to purge small fee transactions, these relays also affect the transactions that can get into blocks because they will preferentially relay the others. in this way also you can do a service to the network by enlarging your mempool so that typical default configurations that would drop transactions would see them propagated again by those who didn't.\n\nit's not a \"vote\" per se, it's more like, you have an impact on what is more likely to get into a block sooner, and when the mempool is full, what transactions will be dropped and which won't.",
"sig": "f44291dea1a2ab8433d2721b886eed65c092398048024e55c0421132d010af760d520ac39d5d0b94bd9cce1c6f02dbff8e00ce1f92d298a9d7e07055dc3d56bc"
}