StevenB on Nostr: Here's a proof of concept that allows storing a signed hash in the feed. ...
Here's a proof of concept that allows storing a signed hash in the feed.
https://svelte.dev/playground/134809f1af4d4651a35516502432cf3b?version=5.20.2
If you're on the backup server's approved npub list, they can store it for you for redundancy, otherwise they can reject the feed.
The app can then fetch the feed and verify the hash against the feed.
If the redundant server acted maliciously and modified the feed prior to storing it, like in the Stolen Feed example in which the value address changes, then the app would flag it as an unauthorized change and fetch the feed from the next server in the redundancy list.
https://svelte.dev/playground/134809f1af4d4651a35516502432cf3b?version=5.20.2
If you're on the backup server's approved npub list, they can store it for you for redundancy, otherwise they can reject the feed.
The app can then fetch the feed and verify the hash against the feed.
If the redundant server acted maliciously and modified the feed prior to storing it, like in the Stolen Feed example in which the value address changes, then the app would flag it as an unauthorized change and fetch the feed from the next server in the redundancy list.