Hello @theguy167,
Welcome to the forum!
We do not use duplication, we uses erasure codes, so any 29 pieces of 80 is enough to recover the segment. The file is encrypted, split to segments (64MiB or less), split to stripes, erasure coded and split to pieces, then uploaded to nodes.
See
All nodes behind /24 subnet of public IPs are treated as a one node for ingress (uploads from the customers), and as a separate ones for egress (downloads by the customers), repair egress traffic, audits and uptime checks.
So, if you go with one node per disk, all these nodes will act as a RAID on the network level. If one disk die, you will lose only this part of the common data, not the whole array, as often happen with a usual RAID5 due to bitrot during rebuild after a one drive failure. It also could affect even zfs, if during rebuild you would get a cascade drive failures due to a higher load during scrub.
I would suggest to read this topic: RAID vs No RAID choice
However, if you already have a RAID for other purposes - you can use it for Storj too.