decentralized storage (storj.io) is a great use case

The Privilege Escalation attack vector can be avoided by using a capability-based security model, ala: https://storj.io/blog/2019/12/secure-access-control-in-the-d...

How is this relevant? AFAICT AWS Policy statements are capabilities. Each policy statement denotes both actions and resources, and that policy is then granted to another identity/resource.

As noted by other comments the parent article focuses on capabilities that grant definition of capabilities. It shouldn't be surprising that principals can use that to establish further capabilities in the absence of other restrictions.

I'm the author here. If you have any questions on secure access control vs ACL, I'm happy to share my thoughts.

Storj has spent the last year rebuilding the entire network after hiring JT Olio (Director of Engineering) Ben Golub (Interim CEO, previously CEO of Docker).

The V3 Network is leaps and bounds more performant and economical than the V2 Network. It is compatible with the S3 bucket-object store and is an easy shift for applications already using S3 as an object store layer. You can speed test it vs S3 using the ./cmd/s3-benchmark tool in our distro.

Try it out for yourself: https://storj.io/blog/2019/01/getting-started-with-the-storj...