Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Signatures and credentials are verified at every request to access private data. If the owner of the signature is allowed to access, the data is returned. Any other outcome will generate an error.

Private Data Sharing Patterns

The specification doesn’t dictate how private data should be shared and disseminated by the Node, the network layer of FinP2P enables the implementation of either a Push or a Pull pattern, or a combination of both to private data sharing.


In a Pull data sharing model, the data is stored only on the Primary Node private store and not replicated over to other nodes private stores, when a Primary Node wants to share data with other nodes, he can notify those nodes by utilizing the network layer pub-sub capability, when other nodes will require to read the private data, they will issue a request-response network call to the Primary Node in order to retrieve the private data.


In a Push data sharing model, the data is stored on the Primary Node private store and also replicated on all of the nodes private store whom the Primary Node shared the data with, in this model the Primary Node will utilize the network layer pub-sub capability in order to push the data into the nodes he desire to share the data with, any change or update to the shared data will be pushed by the Primary Node to all nodes which the piece of data is shared with.

Use Cases 

Asset Information Sharing

Financial institutions who bring assets into the network (their Primary Assets) need to have distribution control over which other institution’s users may see and transact with the asset. This distribution control may be required at the asset level.


Organizations can then discover which assets are being shared, and by whom, and decide if they want to offer them to their users. Once the asset data is shared, an organization can subscribe to get updates on changes, or it can pull data by sending P2P requests.

User Information Sharing

In this use case a user form Organization A wants to Buy assets managed by Organization B. In order to verify the buyer and its legal situation, Organization B sends a request to get user information from Organization A. If the request fails, the user will not be able to transact with the assets.