nugaon

> 1. the reserve changes must be reverted (and handled in a future PR that fixes the chunkstore to be able to store multiple payloads of a SOC). different payloads...

> 1. the reserve changes must be reverted (and handled in a future PR that fixes the chunkstore to be able to store multiple payloads of a SOC). chunkstore overwrites...

@istae please do not force push to the PR and do not commit directly (create another PR based on this).

> There would need to be some mechanism to prevent to many nodes switching at the same time - and possibly therefore also "landing" in the same neighbourhoods. maybe even...

investigated the beekeeper test error and it turned out swap protocol also uses libp2p header exchange. I uploaded the fix [here](https://github.com/ethersphere/bee/commit/bb10d9c93209a0f37c72db63d4a86b870ad12453)

I think it would be useful on other blockchain transactions as well such as purchasing postage batches. I'm unsure about how important is to have different limits on phases, I...

it is not a key for single owner chunk, it is a key for the encrypted data. The intention behind choosing the name to use the same as the one...

the key is the same for encrypting and for decrypting, naming it differently may complicate API usage. as you mentioned correctly, you cannot encrypt the metadata of SOC but its...

> Here I see two possibilities: 1) SOC's payload key is provided by user, and so an unique parameter name needs to be found, or 2) it is calculated from...

maybe is it connected to p2p headers? because only swap protocol uses that which can cause this issue.