bee icon indicating copy to clipboard operation
bee copied to clipboard

Add API for receive already signed chunks by client

Open tmm360 opened this issue 3 years ago • 4 comments

Summary

We need a way for upload to a node chunks that was already signed by the client with postage stamps. This primarily permits to publish contents signed with the user's address instead of the node's one.

Motivation

This is useful in all cases where a node is used by more than one user. Currently every published content is signed by node, and so the node owner is the first responsible of uploaded contents, where instead the final user should be.

Moreover, this permits to discharge node from computing load of sign every chunk, distributing it to clients.

Implementation

New API and a chunk validity check have to be implemented. Old APIs can be kept untouched, eventually node's chunk signature can be disabled by options.

Drawbacks

Don't see any.

tmm360 avatar Apr 26 '22 22:04 tmm360

This is a good idea and definitely something like this would be good to have as a feature. The difficulty of this is that if the postage stamps are distributed then it is no longer trivial to know how much data was uploaded with it.

Currently the stamp is managed by a single node therefore the node is trivially able to account for all data that was attached to it and not overcommit. If you detach the stamp from the node and possibly make it distributable between different parties then it would require some kind of extra protocol to be able to track the data in a distributed manner as well. This protocol is missing and although there were some thinking in this space but as far as I know there is no consensus on how to do this at the moment.

agazso avatar May 03 '22 11:05 agazso

@agazso I see, thank you for have pointed me at this issue. I will try to figure out a possibile solution. But in this case, how can nodes verify now that postage stamps are not overloaded?

tmm360 avatar May 03 '22 14:05 tmm360