While this is not imperative to the operation of a BitTorrent tracker, the bencode package doesn't persist ordering through reads/writes. This means that it will inconsistently calculate the infohash of a given torrent file if you try to do something similar to this gist.
While this is not imperative to the operation of a BitTorrent tracker, the bencode package doesn't persist ordering through reads/writes. This means that it will inconsistently calculate the infohash of a given torrent file if you try to do something similar to this gist.