Skip to content

Commit 72b422d

Browse files
committed
why Fabric
Horton comments addressed Levi comments addressed Fixed references to chain. chain -> channel starting new patch set, sorry Ferris comments addressed replaced dummy file [ci skip] Change-Id: I3c9ab9c60b0ff1f279b0927568f6caf965520ac4 Signed-off-by: Nick Gaski <[email protected]>
1 parent 945c4f7 commit 72b422d

File tree

1 file changed

+40
-1
lines changed

1 file changed

+40
-1
lines changed

docs/whyfabric.md

+40-1
Original file line numberDiff line numberDiff line change
@@ -1 +1,40 @@
1-
coming soon ...
1+
# Why Fabric?
2+
3+
Hyperledger Fabric (hereafter referred to as Fabric) is a blockchain platform
4+
designed to allow the exchange of an asset or the state of an asset to be consented
5+
upon, maintained, and viewed by all parties in a permissioned group. A key characteristic
6+
of Fabric is that the asset is defined digitally, with all participants simply agreeing
7+
on its representation/characterization. As such, Fabric can support a broad range of
8+
asset types; ranging from the tangible (real estate & hardware) to the intangible
9+
(contracts and IP).
10+
11+
The technology is based on a standard blockchain concept - a shared, replicated ledger.
12+
However, Fabric is based on a permissioned network, meaning all participants are
13+
required to be authenticated in order to participate and transact on
14+
the blockchain. Moreover, these identities can be used to govern certain levels of
15+
access control (e.g. this user can read the ledger, but cannot exchange or transfer assets). This
16+
dependence on identity is a great advantage in that varying consensus algorithms (e.g.
17+
BFT based or Kafka) can be implemented in place of the more compute-intensive Proof-of-Work and
18+
Proof-of-Stake varieties. As a result, permissioned networks tend to provide higher
19+
throughput and performance.
20+
21+
Once an organization is granted access to the blockchain network, it then has the ability
22+
to create and maintain a private channel with other specified members. For example,
23+
let's assume there are four organizations trading jewels. They may decide to use
24+
Fabric because they trust each other, but not to an unconditional extent. They can
25+
all agree on the business logic for trading the jewels, and can all maintain a global
26+
ledger to view the current state of their jewel market (call this the consortium channel).
27+
Additionally, two or more of these organizations might decide to form an alternate
28+
private blockchain for a certain exchange that they want to keep confidential
29+
(e.g. price X for quantity Y of asset Z). They can perform this trade without affecting
30+
their broader consortium channel, or, if desired, this private channel can broadcast some
31+
level of reference data to their consortium channel.
32+
33+
This is powerful! This provides for great flexibility and potent capabilities, along with
34+
the interoperability of multiple blockchain ledgers within one consortium. This is the
35+
first of its kind and allows organizations to curate Fabric to support the myriad use
36+
cases for different businesses and industries. Hyperledger Fabric has already been
37+
successfully implemented in the banking, finance, and retail industries.
38+
39+
We welcome you to the Hyperledger Fabric community and are glad to hear your architectural
40+
and business needs, and help determine how Fabric can be leveraged to support your use case.

0 commit comments

Comments
 (0)