Table of Content


Transaction Request Form

Transactions relate to your application’s access to read from and write data into PDAs. When an organisation submits an application for review, it is asking for Dataswyft to set up the correct contracts for its app’s users to accept. Following this acceptance, access and usage to PDAs will be automatically enabled by Dataswyft . Please speak to your Dataswyft account manager who can help you work through the required Transaction Request Form.

Transactions set-up

Transactions set-up is an important function of Dataswyft’s stewardship of the server owner’s data. Apps can only read and write data for which they have obtained permissions through contract, and only when permissions are confirmed will the APIs for a server owner's PDA be enabled to store and receive data.

Types of Transaction Contracts

There are four types of transaction contracts:

Contract 1 - App Namespace Permissions:

Every app that’s integrating with decentralized data servers (DDS) is a “renter” within the server owner’s database. The app owner would require permission to CRUD (Create/Read/Update/Delete) access into its own namespace (we often call this namespace a data account). When filling out the Contract 1 Transaction Request Form, application owners need to provide the data attributes their app will be collecting and storing into their namespace, along with its purpose.

Type of permission: The right for CRUD access into the app’s namespace

Contract 2 - Other Namespace Permissions:

This contract provides permissions for an app to READ data in a namespace other than its own (e.g. Facebook). When filling out the Contract 2 Permissions Request Form, application owners need to provide the data attributes their app will be requesting from other namespaces, along with its purpose and duration. This permission is often tied to a Data Pass.

Type of permission: The right to read data from other namespaces on the PDA. Note: reading data from other namespaces requires a technical process called a data debit.

Contract 3 - Tool Processing Permissions:

This contract provides permissions for an app to have CRUD access and PROCESS data through a PDA Function (aka SHE function) that processes data within a PDA and outputs new data into the SHE Function namespace within the server database. In filling out the Contract 3 Permissions Request Form, application owners need to provide information about the data that is used by their function.

Type of permission: The right for a tool or function to have CRUD access and PROCESS data within a PDA and output/write new data into the SHE Function namespace within the PDA

See Computation API to learn more about PDA Function