oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-01 07:45:40 +01:00
Code Releases Activity

Removing all mentions of MPC

Browse Source
This commit is contained in:
Jamie Hewitt 2024-08-14 13:22:14 +01:00
parent 2e30e4e009
commit 55de2502fb
2 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
developers/ocean-node/README.md
View File

@ -6,7 +6,7 @@ description: The new Ocean stack
Ocean Nodes are a vital part of the Ocean Protocol core technology stack. The Ocean Nodes monorepo that replaces the three previous components: [Provider](../old-infrastructure/provider/), [Aquarius](../old-infrastructure/aquarius/) and [subgraph](../old-infrastructure/subgraph/). It has been designed to significantly simplify the process of starting the Ocean stack - it runs everything you need with one simple command. Ocean Nodes are a vital part of the Ocean Protocol core technology stack. The Ocean Nodes monorepo that replaces the three previous components: [Provider](../old-infrastructure/provider/), [Aquarius](../old-infrastructure/aquarius/) and [subgraph](../old-infrastructure/subgraph/). It has been designed to significantly simplify the process of starting the Ocean stack - it runs everything you need with one simple command.
It integrates multiple services for secure and efficient data operations, utilizing technologies like libp2p for peer-to-peer communication and multi-party computation (MPC) for secure data handling. Its modular and scalable architecture supports various use cases, from simple data retrieval to complex compute-to-data (C2D) tasks. It integrates multiple services for secure and efficient data operations, utilizing technologies like libp2p for peer-to-peer communication. Its modular and scalable architecture supports various use cases, from simple data retrieval to complex compute-to-data (C2D) tasks.
The node is structured into separate layers, including the network layer for communication, and the components layer for core services like the Indexer and Provider. This layered architecture ensures efficient data management and high security. The node is structured into separate layers, including the network layer for communication, and the components layer for core services like the Indexer and Provider. This layered architecture ensures efficient data management and high security.

1
developers/ocean-node/node-architecture.md
View File

@ -22,7 +22,6 @@ The Node stack is divided into the following layers:
* Multiple ways of storing URLs: * Multiple ways of storing URLs:
* Choose one node and use that private key to encrypt URLs (enterprise approach). * Choose one node and use that private key to encrypt URLs (enterprise approach).
* Choose several nodes, so your files can be accessed even if one node goes down (given at least one node is still alive). * Choose several nodes, so your files can be accessed even if one node goes down (given at least one node is still alive).
* Use MPC to divide the key among multiple nodes (so no one node has the entire key).
* Supports multiple C2D types: * Supports multiple C2D types:
* Light Docker only (for edge nodes). * Light Docker only (for edge nodes).
* Ocean C2D (Kubernetes). * Ocean C2D (Kubernetes).