📅 Original date posted:2023-03-24
📝 Original message:
Hi all,
Some time ago I was discussing with ZmnSCPxj about how to handle data
deletion for accountable watchtowers such that the tower doesn't have to
store raw proof of deletion for every single deleted item. The gist is
pretty simple, if I send you data and you hand me proof of reception of
such data, if I ask you to delete the data, now you need to keep proof of
deletion, otherwise, I could claim you are not storing the data we agreed
on initially.
This, unsurprisingly, has led to using accumulators (as ZmnSCPxj originally
suggested) to reduce the data storage requirements (especially on the user
side) while being able to prove additions/deletions.
After chatting with Salvatore Ingala and Calvin Kim about it, I've come to
a point where I think this may be solvable in a rather elegant way, so I
have written a draft of what this may look like wrt watchtowers going,
briefly, from what towers are (and what we mean by accountable) to how
accumulators may help with this issue.
If you're curious about either or both, please give it a look :D
https://gist.github.com/sr-gi/f91f007fc8d871ea96ead9b27feec3d5
--
Sergi.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20230324/dfb16909/attachment.html>;
Sergi Delgado Segura [ARCHIVE] /
npub130…29efq
2023-06-09 13:08:22
in reply to nevent1q…sn8a
Author Public Key
npub1309d5r74zar3uc5hg4jtlywcleqjq3u6p3vv4pcmmfqszetzmkzqf29efqPublished at
2023-06-09 13:08:22Event JSON
{
"id": "d023da082a4896e042d5f990bf9e1b6b7febfc27b0afe2da88f1e8679b324cf4",
"pubkey": "8bcada0fd517471e62974564bf91d8fe4120479a0c58ca871bda41016562dd84",
"created_at": 1686316102,
"kind": 1,
"tags": [
[
"e",
"d0af776cdc77d750b0d96cb9e7a30970fcb6a363793dbb724e04efdadaa83a82",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📅 Original date posted:2023-03-24\n📝 Original message:\nHi all,\n\nSome time ago I was discussing with ZmnSCPxj about how to handle data\ndeletion for accountable watchtowers such that the tower doesn't have to\nstore raw proof of deletion for every single deleted item. The gist is\npretty simple, if I send you data and you hand me proof of reception of\nsuch data, if I ask you to delete the data, now you need to keep proof of\ndeletion, otherwise, I could claim you are not storing the data we agreed\non initially.\n\nThis, unsurprisingly, has led to using accumulators (as ZmnSCPxj originally\nsuggested) to reduce the data storage requirements (especially on the user\nside) while being able to prove additions/deletions.\n\nAfter chatting with Salvatore Ingala and Calvin Kim about it, I've come to\na point where I think this may be solvable in a rather elegant way, so I\nhave written a draft of what this may look like wrt watchtowers going,\nbriefly, from what towers are (and what we mean by accountable) to how\naccumulators may help with this issue.\n\nIf you're curious about either or both, please give it a look :D\n\nhttps://gist.github.com/sr-gi/f91f007fc8d871ea96ead9b27feec3d5\n--\nSergi.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20230324/dfb16909/attachment.html\u003e",
"sig": "156c53ae88c7b219a3032d37faec6b3ac48f13aab95104b52c6a469a690d6fcf09304e68363fc6038c3cfb4b025dfc23b87c0a9877d5772d5dde004b94a49556"
}