migrating to w3up

[sudeepdino008]

• Have a look at README.md for how web3.storage works now with UCAN authentication system.
• given the go-w3up library is under heavy development; we decided to use mature w3cli tool, invocating it from golang code.
• bunch of input parameters change for ipfs-pinner now.
• ipfs-pinner is now configured to upload to a space within an account (as opposed to uploading within an account, as before). This means that if we decide to have separate spaces (e.g. separate spaces for brp/bsp), we would need different ipfs-pinner instances to run.

[noslav]

docker compose files need to be modified to accept the new env vars replacing the old ones

[noslav]

There has to be explicit directions to the validators for -

1. downloading the proof.out file

2. moving this file to the volume being assigned in the rudder docker-compose-mbase/mbeam.yml run, for example sudo mv /home/blockchain/rudder/proof.out ~/.ipfs/proof.out for line https://github.com/covalenthq/rudder/blob/4fa0103a1f0be45af36a0fb4a3bcf6da12c6f4bd/docker-compose-mbase.yml#L9

    volumes:
      - ~/.ipfs:/root/.ipfs/

and then set the docker env

Environment="W3_DELEGATION_FILE=/root/.ipfs/proof.out"

so that the docker instance can find the proof.out file within the mounted volume

3. Setting both W3_AGENT_KEY and W3_DELEGATION_FILE in their systemd definitions which is being used to run ipfs-pinner or rudder

[sudeepdino008]

docker compose files need to be modified to accept the new env vars replacing the old ones

no docker compose file in this repo. If you meant those in rudder, then yes that's been done.