Update README.md

README.md

@@ -6,7 +6,7 @@
 1. ResilientDB's core consensus protocol is based on a highly optimized **[PBFT](https://pmg.csail.mit.edu/papers/osdi99.pdf)** [Castro and Liskov, 1998] implementation to achieve agreement among replicas. The core consensus layer is further expanded with the state-of-the-art consensus protocols *[the release is pending]* such as **[GeoBFT](http://www.vldb.org/pvldb/vol13/p868-gupta.pdf)**, **[PoE](https://openproceedings.org/2021/conf/edbt/p111.pdf)**, **[RCC](https://arxiv.org/abs/1911.00837)**, **[RingBFT](https://openproceedings.org/2022/conf/edbt/paper-73.pdf)**, **[PVP](https://arxiv.org/abs/2302.02325)**, **[PoC](https://arxiv.org/abs/2302.02118)**, **[HotStuff](https://arxiv.org/abs/1803.05069)**, **[DAG](https://arxiv.org/pdf/2105.11827.pdf)**.
 2. ResilientDB expects minimum **3f+1** replicas, where **f** is the maximum number of arbitrary (or malicious) replicas.
 3. ReslientDB designates one of its replicas as the **primary** (replicas with identifier **0**), which is also responsible for initiating the consensus.
-4. ResilientDB exposes a wide range of API services such as a **Key-Value**, **Smart Contracts**, **UTXO**, and **Python SDK**.
+4. ResilientDB exposes a wide range of API services such as a **Key-Value**, **Smart Contracts**, **UTXO**, and **Python SDK**. Examples DApp that are being built on ResilientDB are: **[NFT Marketplace](https://nft.resilientdb.com/)** and **[Debitable](https://debitable.resilientdb.com/)**.
 5. To facilitate persistence of chain and chain state, ResilientDB provides durability through  **LevelDB** and **RocksDB**.
 6. To support deployment and maintenance, ResilientDB provides access to a seamless **GUI display** along with accesses to **Grafana** for plotting monitoring data. 
 7. **[Historial Facts]** The ResilientDB project was founded by **[Mohammad Sadoghi](https://expolab.org/)** along with his students ([Suyash Gupta](https://gupta-suyash.github.io/index.html) as the lead Architect, [Sajjad Rahnama](https://sajjadrahnama.com/), [Jelle Hellings](https://www.jhellings.nl/)) at **[UC Davis](https://www.ucdavis.edu/)** in 2018 and was open-sourced in late 2019. On September 30, 2021, we released ResilientDB v-3.0. In 2022, ResilientDB was completely re-written and re-architected ([Junchao Chen](https://github.com/cjcchen) as the lead Architect along with the entire [NexRes Team](https://resilientdb.com/)), paving the way for a new sustainable foundation, referred to as NexRes (Next Generation ResilientDB); thus, on September 30, 2022, NexRes-v1.0.0 was born, marking a new begining for **[ResilientDB](https://resilientdb.com/)**.