</a></p></header><divclass="features"><divclass="feature"><h2>Performance</h2><p>Leveraging Nim's performance makes these components significantly faster than their non-Nim counterparts</p></div><divclass="feature"><h2>Security</h2><p>Originally designed to power the world's programmable money, Ethereum, these components have been built with security in mind from day 0</p></div><divclass="feature"><h2>Portability</h2><p>Each library is independent - whether it's a cryptocurrency wallet or a mobile game, your project can easily make use of them.</p></div></div><divclass="theme-default-content custom content__default"><h1id="how-the-documentation-is-organized"><ahref="#how-the-documentation-is-organized"class="header-anchor">#</a> How the Documentation is organized</h1><p>Documentation is organized into four categories: tutorials, overviews, API references and how-to guides.</p><ul><li>Tutorials take you by the hand through a series of steps to put a library / module to use. Start here if you’re new to a library.</li><li>Overviews discuss key topics and concepts at a fairly high level and provide useful background information and explanation. Those are the things you usually see in READMEs of repos.</li><li>API references contain technical reference for APIs and other aspects of a module's machinery. They describe how it works and how to use it but assume that you have a basic understanding of key concepts. These are auto-generated from the code, and depend heavily on the programmer's verbosity and the technical writer's persistence.</li><li>How-to guides are recipes. They guide you through the steps involved in addressing key problems and use-cases. They are more advanced, shorter, and more specific than tutorials and assume some previous knowledge.</li></ul><h2id="get-started"><ahref="#get-started"class="header-anchor">#</a> Get Started</h2><p>Use the search field in the header, or find a desired library in the sections below. Each library has its own documentation with a full API reference and guides. If you'd like to contribute to these docs with your own work or some corrections, please file issues or PRs <ahref="https://github.com/status-im/nimbus-libs-site"target="_blank"rel="noopener noreferrer">in the Github repo<span><svgxmlns="http://www.w3.org/2000/svg"aria-hidden="true"focusable="false"x="0px"y="0px"viewBox="0 0 100 100"width="15"height="15"class="icon outbound"><pathfill="currentColor"d="M18.8,85.1h56l0,0c2.2,0,4-1.8,4-4v-32h-8v28h-48v-48h28v-8h-32l0,0c-2.2,0-4,1.8-4,4v56C14.8,83.3,16.6,85.1,18.8,85.1z"></path><polygonfill="currentColor"points="45.7,48.7 51.3,54.3 77.2,28.5 77.2,37.2 85.2,37.2 85.2,14.9 62.8,14.9 62.8,22.9 71.5,22.9"></polygon></svg><spanclass="sr-only">(opens new window)</span></span></a>.</p><divclass="theorem"><pclass="title"><ahref="/lib/nim-libp2p/">libp2p</a><spanclass="badge tip"style="vertical-align:top;"data-v-15b7b770>libp2p</span><spanclass="badge tip"style="vertical-align:top;"data-v-15b7b770>networking</span><spanclass="badge warn"style="vertical-align:top;"data-v-15b7b770>development</span></p><p>nim-libp2p is an implementation of the libp2p modular peer-to-peer networking stack based on Chronos</p></div><divclass="theorem"><pclass="title"><ahref="/lib/nim-chronicles/">Chronicles</a><spanclass="badge tip"style="vertical-align:top;"data-v-15b7b770>logging</span><spanclass="badge tip"style="vertical-align:top;"data-v-15b7b770>stable</span></p><p>Chronicles is a library for structured logging. It adheres to the philosophy that log files shouldn't be based on formatted text strings, but rather on well-defined event records with arbitrary properties that are easy to read for both humans and machines.</p></div><divclass="theorem"><pclass="title"><ahref="/lib/nimcrypto/">Nimcrypto</a><spanclass="badge tip"style="vertical-align:top;"data-v-15b7b770>cryptography</span><spanclass="badge warn"style="vertical-align:top;"data-v-15b7b770>development</span></p><p>Nimcrypto is Nim's cryptographic library. It implements
