|Page Name:||Algorithm and Implementation|
The main property, where the Silktorrent differs from the other similar projects is that its algorithm is modular. The modularity of its implementation is at least as granular as its algorithm.
Silktorrent packets are tar-files that have a name that contains the size of the file and at least one cryptogaphically secure hash of that tar-file. The reason, why tar is used in stead of tar.gz, zip, xz, etc. is that multi-TiB files that consist of only regular patterns, may be all zeros or all ones, can be compressed to a very small file and that kind of file can be used for DoS-attacking computers that run software that unpacks the compression result. The Silktorret packet contains folders "header" and "payload". The folder "header" contains a file "silktorrent_salt.txt" or "silktorrent_salt.blob", which slightly salts also the size of the Silktorrent packet and allows the same payload to be transported by different Silktorrent packets. The idea is that when one package name is blacklisted by censors, the same payload can be distributed by using a different Silktorrent packet.
Optional Silktorrent Packet Header Fields
All of the files in the "header" folder are part of the tar-file and influence the secure hash of the tar-file. Secure hash algorithms do have collisions, but within the limits of those collisions the headers are inseparable from the Silktorrent packet. Silktorrent packet creation software is allowed to add additional, implementation specific, files to the "header" folder, provided that none of the implementation specific files in the "header" folder has a name that starts with the prefix "silktorrent_". The optional, "standard", files in the "header" folder are:
- silktorrent_packet_suggested_deletion_date_t1.txt (TODO: describe format after implementation is ready)
(TODO: Chapter to be completed.)