remove use cases section

This commit is contained in:
Matthias Kretschmann 2016-11-04 15:52:50 +01:00 committed by GitHub
parent 00fdf345f0
commit 223f87720c
1 changed files with 0 additions and 33 deletions

View File

@ -181,39 +181,6 @@ js: page-features.min.js
</div>
</section>
<section class="section section-usecases background--darker">
<div class="row">
<header class="section-header">
<h1 class="section-title">Use Cases</h1>
<p class="section-description">Many BigchainDB use cases are like traditional blockchain use cases, except focused on situations where higher throughput, more capacity, lower latency, better querying, or richer permissioning is necessary.</p>
</header>
</div>
<div class="row row--wide">
<div class="grid grid--full grid-small--half grid-medium--third grid--gutters">
<div class="grid__col">
<strong>Store contracts and transactions</strong> side-by-side on BigchainDB in a format that is readable by humans and computers.
</div>
<div class="grid__col">
<strong>Create and move assets</strong> in real-time. The owner fully controls their asset and transfers, unlike traditional systems.
</div>
<div class="grid__col">
<strong>Track supply chains</strong> to detect and prevent fraud. Every RFID tag in existence could be entered on a BigchainDB.
</div>
<div class="grid__col">
<strong>Track intellectual property</strong> from the registration claim, to licensing and seeing how it's used. BigchainDB gives perfect provenance to digital artifacts.
</div>
<div class="grid__col">
<strong>Generate certificates of authenticity (COAs)</strong> for any asset to maintain and raise its value.
</div>
<div class="grid__col">
<strong>Radically improve database reliability</strong> by leveraging the inherent consensus algorithm to mitigate single points of failure, making it harder for hackers to get in.
</div>
</div>
</div>
</section>
{% include section-testimonials.html %}
<section class="section section-contribute background--photo">