Luke Champine

I think at this point it's probably best to keep things simple. If we support HD keys on the hardware wallet but not in `siad`, it would probably confuse users....

I'm reversing what I said earlier about unlock conditions: it's ok to require them. At the end of the day, if you want to spend an output, you need to...

That should still be possible. The chunk index translates to the index of a blob entry. The only difference is that currently, "chunk" always means `MinPieces * SectorSize` bytes, while...

The Index has a slice of `IndexBlobs`. Each `IndexBlob` corresponds to one of the RS pieces. So the piece index is the index in the `IndexBlobs` slice. To access chunk...

No. Each .sia correspond to one file.

@rudibs: easiest would be to allow them to be any valid Go string (UTF-8). However, they should strictly be interpreted as filenames, not paths. Escaping should be performed in order...

I'm thinking about this section above: >Another important calculation is determining the upload progress of a given file. Implemented naively, this would be an O(n) operation as well. We will...

Discussion with @rudibs convinced me to remove the `Filename` field from `IndexBlob`. He also approved of the decision to omit the original filename from the Index. This could cause issues...

Another thought: should the order and/or names of files in the tar archive be specified? We could impose a strict ordering, such as: the Index must always come first, and...

I'm not completely sure what you mean by "empty index", but it may be the case that a `BlobEntry` will be zeroed out to begin with, and filled in later....