Peter Todd @Peter Todd - 6mo
Re: the OpenTimestamps grant request, the problem is right now while the protocol scales in theory, the backend does not. It would be quite easy for a bad actor to DoS attack OpenTimestamps out of existence because I simply can't throw servers at the problem: the backend code just doesn't scale. I need funding to put in a bunch of hours to fix this. So far, no luck in finding that; OpenSats is one of a few sources I've tried. Frankly, I suspect that there isn't actually much interest in time-stamping.
This is precisely why we need competent people to analyze Nostr's centralization story properly. More relays is irrelevant with the current protocol. nostr:nevent1qqs2wfg49w2ej4ay53nhxhj0kagx438jg6puxh04kefpup9pykpjnmgppemhxue69uhkummn9ekx7mp0qgsyfhqu9kuu877hhm5j2lkwk5478nuvgza00d3lgmjkkk9px8r57zcrqsqqqqqpnmyfz3
Ironically this reply guys are a really nice example of a problem with Nostr's decentralization claims... nostr:nevent1qqswwej6zrtr7au8h5qk3ptuzfeshzvvm6nmqfyg77qpq6utpu7p6rgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygq3rq8vzf6xwk7xcfmev9trx44yl7jejzvcyty24xqq0rxthyj82upsgqqqqqqszrcew8
nostr:nevent1qqsfp6cjwn7k73jn3merxhd6qz2g7zysga3krkne0yfnkv8jyh4xw4cpzpmhxue69uhkummnw3ezumt0d5hsygxv4fvwxlyeepdute65q298rz75vjz7t57txdzkj8k2hq782h2gespsgqqqqqqsnymmj7 I need funding for that and haven't been able to get it.
Brunswick @Brunswick - 5mo
Do you know of an article that describes the concern you and nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprdmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdakj7qgnwaehxw309amk7apww468smewdahx2tckuej4c have about nostr's lack of decentralization and what other systems to compare it with that meet the standard you are applying to consider it sufficiently decentralized?
Peter Todd @Peter Todd - 19h
Good news: Simple Proof has promised me an initial $20k of funding to work on OpenTimestamps. So far I've partially fixed the scaling issue. I rewrote Riccardo Cassata's Foxglove timestamp request aggregator in modern Rust (the previous version didn't even compile anymore). https://github.com/opentimestamps/foxglove Foxglove is now running live on both my Alice and Bob calendars. This means that I can now scale timestamp _creation_ by throwing servers at the problem. So if someone tries to DoS attack the OpenTimestamps calendars, given enough money to run extra servers, you'll (probably) at least be able to create new time-stamps. Timestamp _verification_ still has a significant scaling problem that needs to be fixed, and this will be a significantly harder challenge to implement. But I'm making progress at least. nostr:nevent1qqsfp6cjwn7k73jn3merxhd6qz2g7zysga3krkne0yfnkv8jyh4xw4cpz9mhxue69uhkummnw3ezuamfdejj7q3qej493cmun8y9h3082spg5uvt63jgtewneve526g7e2urca2afrxqxpqqqqqqzljtltl
