[tahoe-dev] "Elk Point" design for mutable, add-only, and immutable files

[David-Sarah Hopwood]

David-Sarah Hopwood wrote:
> Brian Warner wrote:
>> David-Sarah Hopwood wrote:
>>> I've designed a new version of the cap protocol I posted a few days
>>> ago, that addresses Brian's comments about roadblock attacks.
>> This is great stuff.
> 
> It's the most fun (well, intellectual fun :-) I've had in ages. Thanks a
> lot for your feedback.
> 
>> The diagram is immensely helpful too. Some comments:
>>
>> * so S+T is the storage-index, and the conservative values make it 210
>>   bits for immutable files and 288 bits for mutable files.
> 
> Correct.

Actually it's the other way round: 210 bits for mutable files,
288 bits for immutable.

(Mutable files can have a smaller value of t because collision resistance
isn't required.)

-- 
David-Sarah Hopwood  ⚥  http://davidsarah.livejournal.com