Skip to main content

Encryption Keys

Encryption keys facilitate secure data transfer between accounts on the dWallet Network by ensuring that sensitive information remains confidential during transmission.

Each address on the dWallet Network is associated with a unique encryption key. When an external party intends to send encrypted data to a particular account, they use the recipient’s encryption key to encrypt the data. The recipient is then the sole entity capable of decrypting and accessing this information, ensuring secure, end-to-end encryption.

For instance, when transferring a dWallet, the sender must securely transmit the dWallet's user secret share. Ownership of a dWallet is determined by possession of the dWallet's user secret share, meaning that transferring this secret share effectively transfers ownership of the dWallet between accounts.

This approach enables the encryption and secure transmission of any data across the dWallet Network, preserving privacy and security.

Prerequisites​

Before interacting with the dWallet Network, a keypair and a client are required. The example below demonstrates how to connect a client to the Alpha Testnet.

import {DWalletClient} from '@dwallet-network/dwallet.js/client';
import {Ed25519Keypair} from '@dwallet-network/dwallet.js/keypairs/ed25519';
import {requestSuiFromFaucetV0 as requestDwltFromFaucetV0} from '@dwallet-network/dwallet.js/faucet';

// Necessary functions to work with encryption keys.
import {
    createDWallet,
    getOrCreateEncryptionKey,
    storeEncryptionKey,
    setActiveEncryptionKey,
    EncryptionKeyScheme,
    createActiveEncryptionKeysTable
} from "@dwallet-network/dwallet.js/signature-mpc";

// Create a new DWalletClient object that points to the desired network.
// Create a new DWalletClient object pointing to the network you want to use.
const client = new DWalletClient({
    transport: new SuiHTTPTransport({
        url: 'https://fullnode.alpha.testnet.dwallet.cloud',
        WebSocketConstructor: WebSocket as never,
    }),
});
const keypair = new Ed25519Keypair();

// Get tokens from the Testnet faucet server.
const response = await requestDwltFromFaucetV0({
    // connect to Testnet
    host: 'http://faucet.alpha.testnet.dwallet.cloud/gas',
    recipient: keypair.toSuiAddress(),
});

The Encryption Keys Table​

The dWallet Network maintains a mapping of addresses to their associated encryption keys, called the EncryptionKeysTable. To send encrypted data to an account, one can query the recipient’s encryption key from this table and use it to secure the transmitted data.

The encryption key allows any user on the network to send encrypted data to a specific account. However, only the recipient, who possesses the private key that generated the encryption key, can decrypt and access the transmitted data.

Note: In the future we will create a unified encryption keys table for all users on the network.

Users can create their own encryption keys table as follows:

const encryptionKeysTable = await createActiveEncryptionKeysTable(client, keypair);
const activeEncryptionKeysTableID = encryptionKeysTable.objectId;

Creating an Encryption Key​

Once a keypair is generated on the network, the next step is to create an EncryptionKey associated with it.

const senderEncryptionKeyObj = await getOrCreateEncryptionKey(keypair, client, activeEncryptionKeysTableID);

Storing the Encryption Key in the Encryption Keys Table​

After generating the EncryptionKey, it must be stored in the EncryptionKeysTable. This process enables other network users to send encrypted data to the address, ensuring that only the owner can decrypt the incoming information.

const pubKeyRef = await storeEncryptionKey(
    senderEncryptionKeyObj.encryptionKey,
    EncryptionKeyScheme.Paillier,
    keypair,
    client,
);

Setting the active Encryption Key​

It is possible to maintain multiple encryption keys for a single account. To specify which encryption key should be used by other network participants when sending encrypted data, we must designate an active encryption key.

await setActiveEncryptionKey(
    client,
    keypair,
    pubKeyRef?.objectId!,
    activeEncryptionKeysTableID,
);

At this point, the designated EncryptionKey is set as active, enabling other users on the dWallet Network to securely send encrypted data that only the owner of the EncryptionKey can decrypt.