ed2k URI scheme

<h2 id="general">General</h2>
<p>Many programs, such as <a href="/facts/EMule/7l8DF2UY">eMule</a>, <a href="/facts/MLDonkey/kEPDhcqQ">MLDonkey</a> and the original <a href="/facts/EDonkey2000/VyJlegGg">eDonkey2000</a> client by <i>MetaMachine</i>, which introduced the link type, as well as others using the eDonkey file sharing protocol, can be used to manage files stored in the filesharing network.
</p><p>eD2k links allow a file to be identified from a link in a web browser and to be downloaded thereafter by a client like eMule, <a href="/facts/Shareaza/A3owNbS9">Shareaza</a> or any other compatible software.  This linking feature was one of the first <a href="/facts/Uniform_Resource_Identifier/UjyqxTpA">URIs</a> to be introduced in <a href="/facts/Peer-to-peer/wCCdPb0H">peer-to-peer</a> file sharing, and had a vast effect on the development of the eDonkey network, as it allowed external link sites to provide verified content within the network.  Nowadays, so-called <a href="/facts/Magnet_URI_scheme/dGRRYeXM">Magnet links</a> have replaced eD2k links in practice. They serve a similar role, but are not limited to the eD2k hash and can contain other hashes such as <a href="/facts/SHA-1/LDYCV1je">SHA-1</a> or <a href="/facts/MD5/8WIXb9Dq">MD5</a> for example, which makes it possible to use these links to point to files in several networks (as well as in BitTorrent) at once.
</p><p>eD2k links include file hashes, as these hashes can be used as a <a href="/facts/Unique_identifier/NMcgc7qX">unique identifier</a> for files within the network, so even if the linked-to file has a different name on two computers within the network, the file can be found on both of them, and file chunks can be obtained from both sources. This is done by using a <a href="/facts/Hash_function/rk6MlCt3">hash function</a> on the file to calculate its checksum, depending only from the file content, not from its name.
</p><p>Like other URI protocols, web browsers can be configured to automatically handle ed2k URIs. After installing an <a href="/facts/Comparison_of_eDonkey_software/FUDK2rGm">eD2k client</a>, the eD2k protocol is optionally registered so that clicking on it in the browser automatically starts the download or asks whether the user wants to start downloading.
</p>
<h2 id="file-link-format">File link format</h2>
<p>File links are preceded with the "file" token, which indicates that this is a file link, as opposed to a server, serverlist, nodelist or friend link. The typical eD2k file link also includes the <a href="/facts/Filename/a1QSEJhj">filename</a> and the file size. An example (a link to the 15 MB Purist Edit trailer) is provided below:
</p>
ed2k://|file|The_Two_Towers-The_Purist_Edit-Trailer.avi|14997504|965c013e991ee246d63d45ea71954c4d|/

<p>eD2k links can also include a reference to the <a href="/facts/IP_address/z9V22Sw9">IP address</a> and port of specific clients that are known to share the linked-to file. This is done by adding a list of sources after the main part of the link, like shown in the following example:
</p>
ed2k://|file|The_Two_Towers-The_Purist_Edit-Trailer.avi|14997504|965c013e991ee246d63d45ea71954c4d|/|sources,202.89.123.6:4662|/

<p>On eMule, the link often contains also an <a href="/facts/AICH/et19fF6x">AICH</a> <a href="/facts/Merkle_tree/uGFY5mNA">top hash</a> |h=H52BRVWPBBTAED5NXQDH2RJDDAKRUWST| to help recover the file in case of corruption during file transfer.
</p>
<h3>eD2k hash algorithm</h3>
<p>The eD2k hash function is a <a href="/facts/Hash_list/f7p7fe86">root hash</a> of a list of <a href="/facts/MD4/V3dLUpRk">MD4</a> <a href="/facts/Hash_function/rk6MlCt3">hashes</a>. It gives a different result than a simple usage of the MD4 algorithm.
</p><p>The file data is divided into full <i>chunks</i> of 9500 KiB (9728000 bytes) plus a remainder chunk, and a separate 128-bit MD4 checksum is computed for each. If the file is greater than 9500 KiB (which means that there is more than one chunk), the eD2k hash is computed by concatenating the chunks' MD4 checksums in order and hashing the result again using MD4. Otherwise, the MD4 hash of the only chunk of the file is used with no further modifications.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a>
</p><p>This method of hashing allows the recipient to verify that a hash list corresponds to an original eD2k file hash, without the need to actually have the file present on disk.
</p><p>In the past, there has  been some ambiguity for files whose size is a multiple of the chunk size (9500 KiB). Old versions of some eD2k hash tools computed file hashes with an additional 0-byte chunk at the end. This is because an ambiguity of the term <i>remainder chunk</i> which can be interpreted as either <i>the last chunk</i> or a <i>non-full chunk at the end</i>. Following the latter interpretation, some implementations added a zero byte chunk in case the last chunk of a file was a complete one. This practice is discouraged however and the first interpretation is used as a standard nowadays to prevent some files from having different hashes depending on the algorithm implementation used to calculate their hash.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a>
</p>
<h3>AICH</h3>
<p class="note">Main article: <a href="/facts/EMule/7l8DF2UY">eMule § Basic concepts</a></p>
<p>The AICH (Advanced Intelligent Corruption Handling) is an eMule extension. It subdivides the 9500 KiB chunk into 180-KiB blocks and builds a <a href="/facts/Merkle_tree/uGFY5mNA">Merkle tree</a> out of the SHA1 hashes of the 53 blocks, so that the root hash of each block is called a <i>block hash</i>. The block hashes further feed into a Merkle tree, the root hash of which is the actual AICH root hash. The smaller block size allows eMule clients to more precisely identifify locations of corruption.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a>
</p>
<h2 id="server-links">Server links</h2>
<p>A server link is a reference to an eDonkey2000 server; clicking on such a link typically adds it to the server list. Server links are indicated by the server token at the beginning of the link and have the following format:
</p>
ed2k://|server|IP|PORT|/

<ul><li>IP – IP of the server to connect to.</li>
<li>PORT – Port where the server is listening for incoming eD2k connections</li></ul>
<p>Example:
</p>
ed2k://|server|207.44.222.51|4242|/

<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Magnet_URI_scheme/dGRRYeXM">Magnet URI scheme</a></li>
<li><a href="/facts/Metalink/WUj8QYzh">Metalink</a></li>
<li><a href="/facts/Named_data_networking/hAt3XFWW">Named data networking</a></li></ul>

<h2 id="external-links">External links</h2>
<ul><li><a href="http://forum.emule-project.net/index.php?showtopic=46944">emule forum guides</a> How to remove the ed2k link protocol association in windows.</li>
<li><a href="http://wiki.amule.org/wiki/Ed2k_link">aMule wiki: ed2k link</a>.</li>
<li><a href="http://www.emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=422">emule project</a> Ed2k link formats supported by emule client.</li>
<li><a href="http://ed2k-tools.sourceforge.net/ed2k_hash.shtml">ED2K tools - ED2K_Hash</a>  Tool to create ED2K hashes.</li>
<li><a href="http://phantomp2p.com">Phantom P2P</a> eD2k Links Provider</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>emule source, method CKnownFile::CreateFromFile. <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>"Ed2k-hash - MLDonkey". mldonkey.sourceforge.net. Retrieved 23 April 2018. <a href="http://mldonkey.sourceforge.net/Ed2k-hash" target="_blank">http://mldonkey.sourceforge.net/Ed2k-hash</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>"Corruption Handling". www.emule-project.net. <a href="http://www.emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=589" target="_blank">http://www.emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=589</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
</ol>

ed2k URI scheme open-in-new

ed2k URI scheme