Skip to main content

Create a Universal Profile

In this guide, we will learn how to:

Universal Profile example on universalprofile.cloud

We will use the lsp-factory.js library to create a Universal Profile in less than 50 lines of code!

Introduction

Owned Contracts

A Universal Profile is an owned smart contract. Ownership means that such a contract has a separate owner.

The Contract's owner is a blockchain address that can represent anything, such as:

  • one or multiple Externally Owned Accounts (EOAs),
  • a multi-sig wallet, or
  • an other smart contract that can represent anything (a DAO, a DEX, etc...).

Universal Profile smart contract: ownership diagram

For more details, see EIP-173: Contract Ownership Standard

With the Ownable design pattern, a contract can be designed with functionalities that only the owner can perform. The design pattern gives the contract owner more control and privileges.

In the context of Universal Profile, reading data from the contract storage can be done by anyone. But only the owner can:

  • setData(...) = add, edit or remove data from the ERC725Y storage.
  • execute(...) = transferring LYX to addresses, calling other contracts, or create and deploy new contracts (see ERC725X executor)
  • transferOwnership(...) = make an address be the new owner of the Universal Profile.

In this guide, our Universal Profile's owner will be a contract called a Key Manager. The Key Manager is a smart contract that enables granting specific permissions to addresses, so that they can interact with the Universal Profile. For example, transferring LYX on behalf of the Universal Profile.

Learn More

You can implement any complex ownership structure (and fine-grained control) on top of Universal Profiles. The structure includes having a UP owned and controlled by:

  • one or multiple EOAs,
  • one or multiple other smart contracts, or
  • a mixture of both.

For more details, see LSP6 - Key Manager Standard.

Contracts Overview

Universal Profile: overview of deployed contracts

The lsp-factory.js library will help us quickly deploy and set up a Universal Profile with just a few lines of code.

Under the hood, lsp-factory.js performs the following:

  1. Deploy the Universal Profile contracts:
    • Universal Profile (UP) is the core smart contract representing a Universal Profile.
    • Key Manager (KM) is the contract that acts as the owner of a Universal Profile
      to enable other addresses to interact with the UP.
  2. Link a previously deployed Universal Receiver Delegate (URD) smart contract with the deployed UP. The URD reacts to events, such as tokens received or transferred.
  3. Set all the permissions for provided EOA addresses so that they can act on the UP.

➡️   See our lsp-factory.js docs for more details

Learn More

The figure above is our default setup for Universal Profile. However, using a Key Manager as an owner is optional.
You can create a Universal Profile without a Key Manager (or a Universal Receiver Delegate linked to it).

Setup

Before getting started, we will create a new project folder to write all the JavaScript code for this tutorial.
Open a terminal, then create and open a new project folder.

mkdir myUP
cd myUP

Afterward, we have to install all the tools and libraries we need for this tutorial.
Copy and paste the command below in your terminal to install these as npm dependencies.

npm install web3 @lukso/lsp-factory.js --save

Step 1 - Create an EOA

Notice

You should do this step in a temporary file.

As described in the introduction, our first step is to create an EOA that will be used to control our Universal Profile.

Recommendation

Complete "ready to use" JS files are available at the end in the Final Code section.

We can easily create an EOA using the web3.eth.accounts.create() method from web3.js.

Instructions: create a temporary file and add the code snippet below. It will generate an object that contains:

  • a private key (32 bytes / 64 characters long),
  • an address (20 bytes / 40 characters long), and
  • some singing methods like sign
create-eoa.js (temporary file)
const Web3 = require('web3');
const web3 = new Web3();

const myEOA = web3.eth.accounts.create();
console.log(myEOA);

/**
{
address: "0x...",
privateKey: "0x...",
signTransaction: function(tx){...},
sign: function(data){...},
encrypt: function(password){...}
}
*/

Run the script above with Node.js to generate and display your EOA private key and address.

node create-eoa.js

See the Web3.js docs for more infos on creating an EOA

Step 2 - Get some LYX

After creating an EOA that will control our Universal Profile in Step 1, we will need to fund our address with some test LYX (the native cryptocurrency of the LUKSO blockchain). You can obtain some free test LYX via the L14 Faucet.

Instructions: visit the faucet website, paste your above-generated address into the input field and request 5 LYX.

➡️ LUKSO L14 Faucet Website

L14 Faucet screenshot

We will look up our address balance in the LUKSO L14 Block Explorer to ensure we have received our test LYX.

Instructions: go to the LUKSO L14 Block Explorer, and search your pasted address at the top right corner.
You should see 5 LYX next to the Balance field.

LUKSO L14 Network Block Explorer (screenshot)

Step 3 - Create our Universal Profile

Notice

You should do the rest of this tutorial in a new file (main.js).

Now that we have created our EOA, we are ready to create our first Universal Profile.

Instructions: create a new file: main.js (it will contain the main runtime script to create our Universal Profile).

3.1 - Load our EOA

We will start by loading our EOA in our main JS file so that we can use it to deploy our Universal Profile.

Instructions: import the private key that you created in step 1.

main.js
const Web3 = require('web3');
const web3 = new Web3();

const PRIVATE_KEY = '0x...'; // your EOA private key (created in step 1)
const myEOA = web3.eth.accounts.privateKeyToAccount(PRIVATE_KEY);

/**
{
address: "0x...",
privateKey: "0x...",
signTransaction: function(tx){...},
sign: function(data){...},
encrypt: function(password){...}
}
*/
Never expose your private key!

Your private key is what enables you to control your EOA. Therefore, it should NEVER be exposed.

For simplicity in this tutorial, we load the EOA using a hardcoded private key (as a literal string).
However, your private key should never be hardcoded in your code.

⚠️ ALWAYS ensure that your private key is stored securely and never exposed.

3.2 - Setup the lsp-factory.js

The next step is to import and set up our lsp-factory.js tool. It will give us access to a .deploy(...) method that we will use to create our Universal Profile.

Instructions: use the code snippet below to set up the lsp-factory.js.

main.js
const { LSPFactory } = require('@lukso/lsp-factory.js');

// Step 3.1 - Load our EOA
const PRIVATE_KEY = '0x...'; // add the private key of your EOA here (created in Step 1)
const myEOA = web3.eth.accounts.privateKeyToAccount(PRIVATE_KEY);

// initialize the LSPFactory with the L14 chain RPC endpoint, chainId and your EOA's private key which will deploy the UP smart contracts
const lspFactory = new LSPFactory('https://rpc.l14.lukso.network', {
deployKey: PRIVATE_KEY,
chainId: 22,
});

3.3 - Deploy our Universal Profile

The final step is to deploy our UP by calling lspFactory.UniversalProfile.deploy(...). This method will deploy and set up the three main contracts shown in the architecture diagram above.

The deploy function takes an object as an argument that contains two elements:

  • controllerAddresses: the EOA address(es) that we will use to control our UP.
  • lsp3Profile: an object that represents your LSP3Profile Metadata.

We keep our LSP3Profile metadata simple in this tutorial. But you can easily add more details about your UP in this object such as profileImage, backgroundImage and avatar. Read how to do this with lsp-factory here

main.js
const { LSPFactory } = require('@lukso/lsp-factory.js');

// Step 3.1 - Load our EOA
// ...

// Step 3.2 - Setup the lsp-factory
// ...

// Step 3.3 - Deploy our Universal Profile
async function createUniversalProfile() {
const deployedContracts = await lspFactory.UniversalProfile.deploy({
controllingAccounts: [myEOA.address], // our EOA that will be controlling the UP
lsp3Profile: {
name: 'My Universal Profile',
description: 'My Cool Universal Profile',
tags: ['Public Profile'],
links: [
{
title: 'My Website',
url: 'https://my-website.com',
},
],
},
});

return deployedContracts;
}

createUniversalProfile().then((deployedContracts) => {
console.log(deployedContracts);
});

/**
{
LSP0ERC725Account: {
address: '0x...',
receipt: {
to: null,
from: '0x...',
contractAddress: '0x...',
blockNumber: ...,
transactionHash: '0x...',
gasUsed: [BigNumber],
blockHash: '0x...',
...
}
},
LSP6KeyManager: {
address: '0x646e989A0840CE4c3bac39d535Af736db2371107',
receipt: {
...
}
},
}
*/
Learn more

Adding more details to our Universal Profile (e.g., links, profile images, background images) will be our next tutorial! 🎨

Visualize our new Universal Profile

If the deployment is successful, we can access the address of our newly created Universal Profile from the returned value.

main.js
async function createUniversalProfile() {
const deployedContracts = await lspFactory.UniversalProfile.deploy({
// deployment details omitted for brevity
// see Step 3.3 above
});

const myUPAddress = deployedContracts.LSP0ERC725Account.address;
console.log('my Universal Profile address: ', myUPAddress);
// my Universal Profile address: 0x...

return deployedContracts;
}

createUniversalProfile();

// my Universal Profile address: 0xFD296cCDB97C605bfdE514e9810eA05f421DEBc2

We can now visualize our UP on the universalprofile.cloud website by adding the address of the deployed UP in the URL, after the / (slash), as follow:

https://universalprofile.cloud/{your-up-address}

Universal Profile example on universalprofile.cloud

You can also see the contracts created by the lsp-factory.js library on the LUKSO L14 Block explorer:

https://blockscout.com/lukso/l14/address/{your-eoa-address}/transactions

The figure below describes each transaction performed by the lsp-factory.js. It also shows how transactions
are mapped to the Contracts Overview diagram introduced at the beginning of this guide.

lsp-factory.js: contract deployed on L14 and transactions flow

Congratulations 🥳

You have successfully created your first Universal Profile!

➡️ Continue with the following tutorial to learn How to edit your Universal Profile.

⬇️ Look a the code snippet below to help you debug.

Final Code

Below is the complete code snippet of this guide, with all the steps compiled together.

create-eoa.js
const Web3 = require('web3');
const web3 = new Web3();

const myEOA = web3.eth.accounts.create();
console.log(myEOA);

/**
{
address: "0x...",
privateKey: "0x...",
signTransaction: function(tx){...},
sign: function(data){...},
encrypt: function(password){...}
}
*/
main.js
const Web3 = require('web3');
const { LSPFactory } = require('@lukso/lsp-factory.js');

const web3 = new Web3();

// Step 3.1 - Load our Externally Owned Account (EOA)
const PRIVATE_KEY = '0x...'; // add the private key of your EOA here (created in Step 1)
const myEOA = web3.eth.accounts.privateKeyToAccount(PRIVATE_KEY);

// Step 3.2
// Initialize the LSPFactory with the L14 RPC endpoint and your EOA's private key, which will deploy the UP smart contracts
const lspFactory = new LSPFactory('https://rpc.l14.lukso.network', {
deployKey: PRIVATE_KEY,
chainId: 22,
});

// Step 3.3 - Deploy our Universal Profile
async function createUniversalProfile() {
const deployedContracts = await lspFactory.UniversalProfile.deploy({
controllingAccounts: [myEOA.address], // our EOA that will be controlling the UP
lsp3Profile: {
name: 'My Universal Profile',
description: 'My Cool Universal Profile',
tags: ['Public Profile'],
links: [
{
title: 'My Website',
url: 'https://my-website.com',
},
],
},
});

const myUPAddress = deployedContracts.LSP0ERC725Account.address;
console.log('my Universal Profile address: ', myUPAddress);

return deployedContracts;
}

createUniversalProfile();

// my Universal Profile address: 0xFD296cCDB97C605bfdE514e9810eA05f421DEBc2