|
6 | 6 | FaCoins, |
7 | 7 | FaLightbulb, |
8 | 8 | FaCode, |
| 9 | + FaCubes, |
9 | 10 | } from "react-icons/fa"; |
10 | 11 | import merkletree from "../assets/merkle-trees-and-proofs.png"; // Ensure the path is correct |
11 | 12 |
|
@@ -140,22 +141,39 @@ const ProjectIntroduction = ({ className }) => { |
140 | 141 | {/* Diagram or Additional Information */} |
141 | 142 | <div className="bg-white p-4 rounded-md shadow-md"> |
142 | 143 | <h3 className="flex items-center text-xl sm:text-2xl font-bold mb-4 bg-gray-100 text-black px-3 py-1 rounded-md border-1 border-gray-200 hover:bg-gray-300 transition-colors duration-300 shadow"> |
143 | | - <FaCode className="mr-2 text-green-400" /> |
| 144 | + <FaCubes className="mr-2 text-green-400" /> |
144 | 145 | Understanding Merkle Trees |
145 | 146 | </h3> |
146 | 147 | <img |
147 | 148 | src={merkletree} |
148 | 149 | alt="Merkle Tree Diagram" |
149 | 150 | className="w-full h-auto mb-4 rounded-md" |
150 | 151 | /> |
151 | | - <p className="text-md sm:text-lg leading-relaxed"> |
| 152 | + <p className="text-md leading-relaxed"> |
152 | 153 | Merkle trees are a fundamental component of blockchain |
153 | 154 | technology, providing a way to efficiently verify data |
154 | 155 | integrity. Each leaf node represents a block of data, and parent |
155 | 156 | nodes are hashes of their respective child nodes. This structure |
156 | 157 | allows for quick verification of any individual piece of data |
157 | 158 | within the tree. |
158 | 159 | </p> |
| 160 | + <p className="text-md leading-relaxed mt-4"> |
| 161 | + In the context of STAC (SpatioTemporal Asset Catalog), Merkle |
| 162 | + trees enable the verification of entire catalogs, collections, |
| 163 | + and items by deriving a root hash that represents all underlying |
| 164 | + elements. The root hash is computed by recursively hashing |
| 165 | + metadata from all related items, collections, and catalogs in |
| 166 | + ascending order. This ensures that even a small change in any |
| 167 | + underlying component will result in a completely different root |
| 168 | + hash, making tampering easily detectable. |
| 169 | + </p> |
| 170 | + <p className="text-md leading-relaxed mt-4"> |
| 171 | + Using this approach, users can validate the integrity and |
| 172 | + provenance of STAC data, ensuring it has not been altered or |
| 173 | + corrupted. The root hash acts as a cryptographic fingerprint for |
| 174 | + the entire dataset, providing confidence in the reliability of |
| 175 | + the geospatial information. |
| 176 | + </p> |
159 | 177 | </div> |
160 | 178 | </div> |
161 | 179 | </div> |
|
0 commit comments