Merge pull request #2 from Solicy-App/documentation

Created documentation

docs/Blockchain.md

@@ -0,0 +1,33 @@
+# BigchainDB and Blockchain
+
+BigchainDB is a powerful technology designed for simplicity and speed, built on the foundation of blockchain technology. Let's explore what makes it special:
+
+## Fast Transactions with BigchainDB
+
+BigchainDB, powered by blockchain, is incredibly fast and capable of handling numerous tasks quickly. This makes it perfect for processes that require swift execution.
+
+## Using BigchainDB in the Cloud
+
+Leveraging BigchainDB and its blockchain foundation in the cloud offers several benefits:
+
+### Seamless Expansion
+
+It easily adapts to your growing needs.
+
+### Simplified Management
+
+Maintaining it is straightforward.
+
+### Access Anywhere
+
+You can access it from anywhere, providing flexibility.
+
+# BigchainDB: Power and Security
+
+BigchainDB, built on blockchain technology, is a versatile solution:
+
+- Handles High Workloads: Effortlessly manages substantial tasks.
+- Exceptional Speed: Maintains rapid performance even under heavy workloads.
+- Security and Speed Combined: Offers top-notch security with lightning-fast speed.
+- Data Integrity: Your data is secure and guaranteed to be accurate.
+- Effortless Data Retrieval: Finding information is easy, simplifying the search process.

docs/MoreInfo.md

@@ -0,0 +1,41 @@
+
+## Full Decentralization and Byzantine Fault Tolerance
+
+BigchainDB leverages Tendermint for networking and consensus, providing:
+
+- Byzantine Fault Tolerance (BFT): The system is highly resilient because Tendermint, the technology behind it, ensures BFT. Even if some nodes misbehave or fail, the network remains secure.
+- Local Databases: Each node has its own local MongoDB database. This setup enhances security. If one database is compromised, only that node is affected; others remain unharmed.
+- Changing Block Proposers: The system design periodically changes the node responsible for proposing blocks, making it more secure and less predictable.
+- True Decentralization: In an ideal BigchainDB 2.0 network, each node is owned and operated by a different entity. This results in full decentralization, with no single owner, controller, or point of failure.
+- Global Node Distribution: Nodes should be located in various countries and hosting providers to ensure network robustness. Even if some nodes fail or face issues, the network continues to function.
+- High Fault Tolerance: Up to one-third of the nodes can fail or misbehave, and the network will still operate smoothly. The remaining nodes collaborate to make decisions and keep the system running.
+
+## Immutability 
+
+BigchainDB ensures data immutability using several strategies: 
+
+- No Data Alteration APIs: BigchainDB doesn't provide tools to change or erase stored data, making it resistant to unauthorized modifications. 
+- Local Copies on Every Node: Each node has its own complete copy of the data in separate MongoDB databases. Even if one node fails, others still have the data, preventing data loss. 
+- Cryptographic Signatures: Every transaction is cryptographically signed. If someone tries to change a transaction, the signature changes, which can be detected. Even changing the public key is noticeable since all transactions are signed by known nodes.
+
+## Owner-Controlled Assets 
+
+BigchainDB operates like many other blockchains, where assets are controlled by their owners. 
+
+- User-Defined Assets: BigchainDB allows users to create their own assets as needed, each cryptographically signed by its creator. 
+
+## High Transaction Rate 
+
+BigchainDB is designed to handle a high number of transactions per second, even in challenging conditions. 
+
+## Sybil Tolerance 
+
+In a BigchainDB network, the organization governing the network controls the member list, eliminating the possibility of Sybil attacks.
+
+## Identity Management 
+
+BigchainDB combines the best of blockchains and databases to provide a secure and scalable solution for managing identities.
+
+## BigchainDB Transactions
+
+Creating a BigchainDB transaction is like filling out a form with clear instructions. BigchainDB drivers ensure you follow those instructions to create a valid transaction.

docs/Workflow.md

@@ -0,0 +1,45 @@
+# Workflow
+
+![Alt text](./pictures/pic1.png)
+
+
+
+## Clients
+
+Digital Participants: Clients are the digital participants in the BigchainDB network. They're like the people who connect to a digital gathering.
+
+## Nodes
+
+Network Components: Nodes serve as essential components in the BigchainDB network, much like the various parts that make up a computer.
+
+### Validating Nodes
+
+Verification Enforcers: Validating nodes act as verification enforcers. They ensure transactions meet BigchainDB's rules before accepting them, similar to security personnel checking IDs at a venue.
+
+### Non-validating Nodes
+
+Data Replicators: Non-validating nodes replicate data, similar to creating backup copies to ensure information is always available.
+
+## Transaction Propagation
+
+Information Flow: Transaction propagation is the way information moves within the network, like how news spreads among friends in a social circle.
+
+## Consensus Mechanism
+
+Shared Decision-Making: BigchainDB's consensus mechanism involves shared decision-making, like friends discussing and agreeing on a plan before moving forward.
+
+## Database Storage
+
+Information Storage: Data in BigchainDB is stored systematically, similar to organizing a library catalog.
+
+## Decentralization and Immutability
+
+Shared Trust and Protection: BigchainDB provides shared trust and protection, like a community coming together to safeguard something important.
+
+## Smart Contracts
+
+Automated Actions: Smart contracts automate actions based on predefined conditions, much like a timer turning on lights when it gets dark.
+
+## Data Querying
+
+Information Requests: Clients can request information from the BigchainDB database, just as you might ask for directions when exploring a new place.