diff --git a/submission1.md b/submission1.md
new file mode 100644
index 0000000..4067c5b
--- /dev/null
+++ b/submission1.md
@@ -0,0 +1,23 @@
+**Signing commits is a security practice in Git.**
+
+The most common commit signing techniques include ***SSH, GPG, and S/MIME.***
+They are primarily used for authorship verification, allowing contributors to verify the authorship of commits (prove that the commit were indeed made by them).  
+
+Sign tags or commits that are marked as verified assure others that the changes come from a trusted source. 
+
+
+This practice is especially beneficial since it enforces: 
+
+1. **Trustable integrity assurance**
+
+A signed commit guarantess that since you made a commit, no one can modify it (if someone tries to alter a signed commit, the signature will become invalid).  
+
+
+2. **Compliance with security policies**
+   
+This is important in industrial and commercial projects with strict security standards.
+
+3. **Improved collaboration**
+   
+This is crucial, for example, in open-source and collaborative projects.
+
diff --git a/submission2/images/ipfs_peers.png b/submission2/images/ipfs_peers.png
new file mode 100644
index 0000000..9369ebc
Binary files /dev/null and b/submission2/images/ipfs_peers.png differ
diff --git a/submission2/images/ipfs_status.png b/submission2/images/ipfs_status.png
new file mode 100644
index 0000000..3e113e6
Binary files /dev/null and b/submission2/images/ipfs_status.png differ
diff --git a/submission2/submission2.md b/submission2/submission2.md
new file mode 100644
index 0000000..dc9e187
--- /dev/null
+++ b/submission2/submission2.md
@@ -0,0 +1,48 @@
+# Task 1: Set Up an IPFS Gateway Using Docker
+
+## Connected Peers and Bandwidth
+
+**Connected Peers:** 
+![peers](images/ipfs_peers.png)
+
+
+**Bandwidth:** 
+![status](images/ipfs_status.png)
+
+
+## File Hash and Verification URLs
+
+- **File Hash:** 
+
+QmarCyCa387tskCpkJCMEVnEnDsyCsuX9c2np3d1XGWdyk
+  
+- **Verification URLs:**
+- IPFS.io Gateway
+`https://ipfs.io/ipfs/QmarCyCa387tskCpkJCMEVnEnDsyCsuX9c2np3d1XGWdyk`
+
+- Cloudflare IPFS Gateway
+`https://cloudflare-ipfs.com/ipfs/QmarCyCa387tskCpkJCMEVnEnDsyCsuX9c2np3d1XGWdyk`
+
+- Infura IPFS Gateway
+`https://infura-ipfs.io/ipfs/QmarCyCa387tskCpkJCMEVnEnDsyCsuX9c2np3d1XGWdyk`
+
+Or, I can access the file via Local IPFS Node:
+`http://127.0.0.1:8080/ipfs/QmarCyCa387tskCpkJCMEVnEnDsyCsuX9c2np3d1XGWdyk`
+
+
+# Task 2: Set Up Project on Fleek.co
+
+IPFS hash:
+bafybeibihvtzf44cxm2dndgmake5jj4drwkki46gtuekbgr7wme2ws5yui
+
+**IPFS link and domain**
+
+https://ipfs.io/ipfs/bafybeibihvtzf44cxm2dndgmake5jj4drwkki46gtuekbgr7wme2ws5yui/
+
+https://swift-rose-wide.on-fleek.app/
+
+# Notes about IPFS and Fleek
+
+**IPFS (InterPlanetary File System)** is a decentralized network protocol that allows users to store and share files in a distributed manner. Instead of relying on a single central server, files on IPFS are stored across multiple nodes (computers) within the network. This distribution makes files more resilient and resistant to censorship, as they can be retrieved from any node that has a copy of the data.
+
+**Fleek** is a platform that simplifies the deployment of websites and applications on the decentralized web. It seamlessly integrates with IPFS, providing tools to easily host, manage, and deploy projects. Key features include continuous deployment (CD) from Git repositories, IPFS hosting, domain management, and more. Fleek automates the process of deploying updates, making it easier for developers to maintain and distribute their projects.
\ No newline at end of file