[User-Story] Global Pinning

[mortelli]

Rationale

Users need to be able to guarantee their content is available through the Swarm network. They need to be able to either take this responsibility upon themselves or invoke a 3rd party to provide this service.

User-Story

As a node operator, I want to be able to provide and retrieve content marked as globally pinned by my own or other nodes.

Additionally, I want my node to automatically request a re-upload of pinned resources to the global pinners in the case that they go missing.

Epic links

N/A

Acceptance criteria

• User is able to define which resources they want to globally pin or unpin through an API
  • This information needs to persist upon restart
  • It should be clear if the pinning was successfull or not
• User is able to provide & consume information about global pinners (specifics TBD)
• Node should request re-upload of missing globally pinned resources (without a direct action from the user)

Requirements

• This implementation is experimental, and therefore will not be merged to master.
• Trojan Chunks will have to be implemented as a way of requesting re-uploads of missing globally pinned resources.
• A new, minimal PSS will have to be defined as the global pinning API (of sorts) so the old one must be renamed.
• A way for nodes to signal that they are globally pinning a resource must be implemented, as well as a way to consume this information.

Work estimate

1-2 sprints.

Related Issues

• Phase 0
• Phase 1
• Phase 2
• Phase 3
• all global pinning issues

References

• @vojtechsimetka's Global pinning IOVlabs user story

[mortelli]

up to discussion whether this should be an epic and individual stories should be created (don't mind either way)

@Eknir