mirror of
https://github.com/bigchaindb/site.git
synced 2024-12-24 02:16:10 +01:00
copy updates
This commit is contained in:
parent
891cd38b89
commit
8a2bd602eb
@ -9,7 +9,7 @@
|
||||
<use xlink:href="/assets/img/sprite.svg#logo"></use>
|
||||
</svg>
|
||||
|
||||
<h1 class="section-title">Introducing BigchainDB. A blockchain database, at scale.</h1>
|
||||
<h1 class="section-title">Introducing BigchainDB. The blockchain database, at scale.</h1>
|
||||
</hgroup>
|
||||
|
||||
<a href="#features" class="scroll btn btn-link btn-sm">Learn More <svg class="icon">
|
||||
|
@ -8,7 +8,7 @@ title: How It Works
|
||||
<div class="row">
|
||||
<header class="section-header">
|
||||
<h1 class="section-title">Features</h1>
|
||||
<p class="section-description">Rather than trying to scale up blockchain technology, the BigchainDB design starts with a "big data" distributed database and then adds blockchain characteristics - decentralized control, immutability and the transfer of digital assets.</p>
|
||||
<p class="section-description">Rather than trying to scale up blockchain technology, BigchainDB starts with a big data distributed database and then adds blockchain characteristics - decentralized control, immutability and the transfer of digital assets.</p>
|
||||
</header>
|
||||
</div>
|
||||
|
||||
@ -20,7 +20,7 @@ title: How It Works
|
||||
<use xlink:href="/assets/img/sprite.svg#icon-graph"></use>
|
||||
</svg>
|
||||
<div class="feature__detail">
|
||||
<h1 class="feature__title">One Million Writes and Counting</h1>
|
||||
<h1 class="feature__title">One Million Writes per Second</h1>
|
||||
<p class="feature__text">Each write is recorded on the blockchain without the need for Merkle Trees or sidechains.</p>
|
||||
</div>
|
||||
</div>
|
||||
@ -98,7 +98,7 @@ title: How It Works
|
||||
</svg>
|
||||
<div class="feature__detail">
|
||||
<h1 class="feature__title">Federation Consensus Model</h1>
|
||||
<p class="feature__text">Decentralized control via a federation of nodes with voting permissions makes for a super-peer P2P network.</p>
|
||||
<p class="feature__text">Decentralized control via a federation of voting nodes makes for a super-peer P2P network.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@ -108,7 +108,7 @@ title: How It Works
|
||||
<use xlink:href="/assets/img/sprite.svg#icon-tree"></use>
|
||||
</svg>
|
||||
<div class="feature__detail">
|
||||
<h1 class="feature__title">Open source</h1>
|
||||
<h1 class="feature__title">Open Source</h1>
|
||||
<p class="feature__text">Open sourced to the community so that everyone can use it and build their own applications on top of it.</p>
|
||||
</div>
|
||||
</div>
|
||||
@ -120,7 +120,7 @@ title: How It Works
|
||||
</svg>
|
||||
<div class="feature__detail">
|
||||
<h1 class="feature__title">Public or Private</h1>
|
||||
<p class="feature__text">A public version via trusted nodes for the world and a private one for specific industry use cases.</p>
|
||||
<p class="feature__text">A public version for the world and a private one for specific industry use cases.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@ -138,7 +138,7 @@ title: How It Works
|
||||
<div class="row">
|
||||
<header class="section-header">
|
||||
<h1 class="section-title">Made for the Decentralization Ecosystem</h1>
|
||||
<p class="section-description">BigchainDB is complementary to decentralized storage, processing and communication building blocks. It can also be used side by side with higher-level decentralized computing platforms and applications, identity protocols, financial asset protocols, IP assets protocols and glue protocols. BigchainDB provides a bridge to an eventually fully decentralized system.</p>
|
||||
<p class="section-description">BigchainDB is complementary to decentralized storage, processing and communication building blocks. It can be used side by side with higher-level decentralized computing platforms and applications, and protocols for identity, financial assets, intellectual property and sidechains. BigchainDB fills a gap in the decentralized stack.</p>
|
||||
</header>
|
||||
</div>
|
||||
<div class="row row--wide stacks">
|
||||
@ -182,16 +182,34 @@ title: How It Works
|
||||
<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>
|
||||
|
||||
<div class="row row--wide">
|
||||
<div class="grid grid--full grid-small--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>Timestamp transactions</strong> to provide receipts and records to facilitate proof-of-purchase, warranty and insurance claims.
|
||||
</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>
|
||||
|
||||
<section class="section section-contribute background--photo">
|
||||
|
Loading…
Reference in New Issue
Block a user