mleku on Nostr: there has been some chatter recently mostly involving #gitcitadel people talking ...
there has been some chatter recently mostly involving #gitcitadel people talking about the fact that nostr relays are essentially distributed database servers, of a new kind that pushes more of the subscription and authentication part to the front
i'm of the opinion that as shitcoins slowly die, because they are over-replicated distributed databases without a built in subscription protocol, that a nostr-like distributed data protocol is growing out of the nostr design
bitcoin will become the authoritative anchor for these decentralised data stores, and small, low bandwidth, ad-hoc federated blockchains will become directory servers, that use bitcoin as their security, anchoring their state in short messages stored in op_return, or maybe witness data, or both, and these will become directories that store information about where categories and users (as in decentralised web services) are storing their data on a growing network of nostr-like relays
nostr protocol will have to be refined for this use case, as it was originally conceived primarily as a decentralised replacement of the centralised, distributed data systems used by current generation social networks. they will need a simpler interface (ie, HTTP based) and where currently there is one spec for data, there will evolve a simpler, coordinating data storage interface that treats database records as events and relays will have user-programmable replication schemes where the relay acts as a client to other relays, and using auth-proxying and data storage proxying protocols, will become the place where all kinds of data are stored, protected by auth-required access, and enabled by clients being able to use relays as proxies.
probably the main thing that i see coming is that nostr relays will become partially also proxies for clients to fan out their requests to multiple data stores, providing a replication state programmable by the smart contracts running on these low bandwidth, data-only pBFT blockchains, and client applications, that read and write to the relays, with the blockchains becoming the directories.
i know it probably will be difficult for most to understand what i'm talking about, but the reason for this to become the dominant paradigm of internet services is that it separates application logic and data storage logic, and enables a continuum of scaling that has low friction for applications that become used a lot, to scale up their back end without having to change any of their application logic.
Published at
2025-06-04 09:55:23Event JSON
{
"id": "80593c6f7a8201c81a42884299502838123b857173d92a75a8e759b4f2e6e834",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1749030923,
"kind": 1,
"tags": [
[
"t",
"gitcitadel"
]
],
"content": "there has been some chatter recently mostly involving #gitcitadel people talking about the fact that nostr relays are essentially distributed database servers, of a new kind that pushes more of the subscription and authentication part to the front\n\ni'm of the opinion that as shitcoins slowly die, because they are over-replicated distributed databases without a built in subscription protocol, that a nostr-like distributed data protocol is growing out of the nostr design\n\nbitcoin will become the authoritative anchor for these decentralised data stores, and small, low bandwidth, ad-hoc federated blockchains will become directory servers, that use bitcoin as their security, anchoring their state in short messages stored in op_return, or maybe witness data, or both, and these will become directories that store information about where categories and users (as in decentralised web services) are storing their data on a growing network of nostr-like relays\n\nnostr protocol will have to be refined for this use case, as it was originally conceived primarily as a decentralised replacement of the centralised, distributed data systems used by current generation social networks. they will need a simpler interface (ie, HTTP based) and where currently there is one spec for data, there will evolve a simpler, coordinating data storage interface that treats database records as events and relays will have user-programmable replication schemes where the relay acts as a client to other relays, and using auth-proxying and data storage proxying protocols, will become the place where all kinds of data are stored, protected by auth-required access, and enabled by clients being able to use relays as proxies.\n\nprobably the main thing that i see coming is that nostr relays will become partially also proxies for clients to fan out their requests to multiple data stores, providing a replication state programmable by the smart contracts running on these low bandwidth, data-only pBFT blockchains, and client applications, that read and write to the relays, with the blockchains becoming the directories.\n\ni know it probably will be difficult for most to understand what i'm talking about, but the reason for this to become the dominant paradigm of internet services is that it separates application logic and data storage logic, and enables a continuum of scaling that has low friction for applications that become used a lot, to scale up their back end without having to change any of their application logic.",
"sig": "5993d66a04eb10323f2263341c21d265f7c5a3520c0902b63acaa6731bdf965b97ce6b3ce8f8d4b7c78ebcb4fb8e4d7a3c32f83989a79ef32b10ea57d2aa0290"
}