Re: Query Hit bitprint

Quoting mark W <[email protected]> from ml.gnutella.dev-forum:
:Actually HUGE specs shows the presence of bitprint :
:http://rfc-gnutella.sourceforge.net/src/draft-gdf-huge-0_94.txt
:
:format of it:
:urn:bitprint:[32-character-SHA1].[39-character-TigerTree]

Bitprints occupy more space in packets, and SHA1 has been good enough
for now.  That's why all the servents I know use SHA1 in query hits,
but offer a X-Thex-URI header during HTTP exchanges, leading to the
TTH data from which you can derive the root Tiger Tree Hash (TTH) and
therefore the bitprint.

Raphael