bigchaindb/site
1
0
Fork 0
mirror of https://github.com/bigchaindb/site.git synced 2024-11-22 01:36:55 +01:00
Code Releases Activity

add use cases to features pages

Browse Source
This commit is contained in:
Matthias Kretschmann 2016-02-08 14:56:47 +01:00
parent 6d692b92bb
commit ed2ce3486d
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
_src/features.html
View File

@ -161,6 +161,23 @@ title: How it works
</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>
<ul>
<li>Legally-binding contracts can be stored directly on the BigchainDB next to the transaction, in a format that is readable by humans and computers.</li>
<li>Creation and real-time movement of high-volume assets. Only the owner of the asset can move the asset, rather than the network administrator like in previous database systems. This capability reduces costs, minimizes transaction latency, and enables new applications.</li>
<li>Tracking high-volume physical assets along whole supply chain. BigchainDB can help reduce fraud, providing massive cost savings. Every RFID tag in existence could be entered on a BigchainDB.</li>
<li>Tracking intellectual property assets along the licensing chain. BigchainDB can reduce licensing friction in channels connecting creators to audiences, and gives perfect provenance to digital artifacts. A typical music service has 38 million songs—BigchainDB could store this information in a heartbeat, along with licensing information about each song and information about use by subscribers.</li>
<li>Time stamping, receipts, and certification. BigchainDB reduces legal friction by providing irrefutable evidence of an electronic action. And, BigchainDB is big enough that supporting information like receipts and certificates of authenticity (COAs) can be stored directly on it, rather than linking to the document or storing a hash.</li>
<li>Improving database reliability by creating resistance to single points of failure. This reliability helps move past the status quo where a single hack leads to massive data loss, like in Target, Sony, or the OPM.</li>
</ul>
</div>
</section>
<section class="section section-timeline background--photo">
<div class="row">