Handling different payloads of a SOC

[nugaon]

Summary

Currently, if one uploads multiple payloads for a Single Owner Chunk with different valid stamps, only the lastly uploaded will be available on the network. #4749
This behavior does not benefit node operators even though chunks with valid stamps could be used at storage incentive sampling.

Motivation

If multiple payloads of a SOC was handled on the network, node operators could grow their reserve size by currently not utilized pull syncs and uploaders could access multiple payloads under one SOC by which new feature could emerge on Swarm.

Implementation

Sharky DB may need a refactor to able to store and retrieve chunks by not only their address but by other optional parameter.

The feature requires to implement new chunk request type, one proposed in the GSOC SWIP but it is under open discussion under the SWIP PR what would be the most suitable.

Drawbacks

[nikipapadatou]

needs syncing with research before proceeding.