bytesNNbytes48 for the G1, G2 points (option 5).ValidatorRecord.status_flags: uint64 could also benefit from it. -> bytes8 (edited)hash32 with bytes32.Address: it's unused.the current ValidatorRecord.status_flags: uint64 could also benefit from it. -> bytes64
note: that uint64 is bytes8.
Also, I think it might generally be easier to bitwise manipulate integers in python rather than byte arrays. I don't feel very strongly, but @vbuterin made that argument here https://github.com/ethereum/eth2.0-specs/issues/371#issuecomment-450497143
hash32 (in favour of bytes32).hashN (in favour of bytesN).
Most helpful comment
hash32(in favour ofbytes32).hashN(in favour ofbytesN).