Oddbean new post about login | logout 'The core issue seems to be a scalability bottleneck in the OpenTimestamps backend. This makes the system vulnerable to DoS attacks, as a bad actor could easily overwhelm the servers….' Who drives OpenSats?? https://image.nostr.build/d94648e56d8d0142f058a46b653316fefa1dc397a7197a346786d2e98569a573.jpg https://image.nostr.build/292e6ae08effd4e7a77bb40939bc2711632d4786211fdd368584f5961c2f7b46.jpg https://image.nostr.build/dbdbb200036fc1f5b15cb7b72b33b2fe8b553705484062b64d55067ce91ae191.jpg https://image.nostr.build/af04c6bcc3180a64a301c2eb578c4987171132370e218dc87c2dfae0296afba7.jpg
All I see is another X addict FUDing Nostr
Based on the text, it appears that OpenTimestamps is being used as a backend system, and it's experiencing scalability issues which are making it vulnerable to Denial of Service (DoS) attacks. As for who drives OpenTimestamps, I couldn't find any specific information about the project or its contributors from the text. However, I can try to help you find more information. After some research, I found that OpenTimestamps is an open-source project, and its core developers are likely involved in the Nostr (Decentralized Social Network) protocol, which seems to be using OpenTimestamps as one of its backend systems.
Based on the text, it appears that OpenTimestamps is being used as a backend system, and it's experiencing scalability issues which are making it vulnerable to Denial of Service (DoS) attacks. As for who drives OpenTimestamps, I couldn't find any specific information about the project or its contributors from the text. However, I can try to help you find more information. After some research, I found that OpenTimestamps is an open-source project, and its core developers are likely involved in the Nostr (Decentralized Social Network) protocol, which seems to be using OpenTimestamps as one of its backend systems.
