Mint via Contracts

You can mint a PKP NFT from the PKP contract on Chronicle Yellowstone - Lit's custom EVM rollup testnet - using:

1. The Lit explorer
2. The Lit relayer (sign up for an API key here)
3. The contracts directly using the contracts-sdk (Here is the handy helper contract on Chronicle Yellowstone to mint and assign auth methods. You can view all of the deployed contract addresses here).

The NFT represents root ownership of the PKP. The NFT owner can grant other users (via a wallet address) or grant Lit Actions the ability to use the PKP to sign and decrypt data. They also have the ability to assign additional authentication methods, described at the bottom of the page.

Installing the required packages

yarn add @lit-protocol/lit-node-client
yarn add @lit-protocol/lit-auth-client
yarn add @lit-protocol/contracts-sdk
yarn add @lit-protocol/constants
yarn add @lit-protocol/providers

Initializing your LitContract instance

import { LitContracts } from '@lit-protocol/contracts-sdk';

// if no signer is provided, it will attempt to use window.etheruem
const contractClient = new LitContracts({ signer });
await contractClient.connect();

Minting a PKP and adding permitted scopes

Permitted scopes are a crucial part of defining the capabilities of authentication methods. They determine what actions an authentication method can perform within the system. For instance, the SignAnything scope allows an auth method to sign any data, while the PersonalSign scope restricts it to signing messages using the EIP-191 scheme.

You can also set scopes: [] which will mean that the auth method can only be used for authentication, but not authorization. This means that the auth method can be used to prove that the user is who they say they are, but cannot be used to sign transactions or messages. You can read more about Auth Method scopes here.

The following code block demonstrates how to mint a PKP with specific permitted scopes:

import { AUTH_METHOD_SCOPE, AUTH_METHOD_TYPE } from '@lit-protocol/constants';

const authMethod = {
  authMethodType: AUTH_METHOD_TYPE.EthWallet,
  accessToken: JSON.stringify(authSig),
};

const mintInfo = await contractClient.mintWithAuth({
  authMethod: authMethod,
  scopes: [
        // AUTH_METHOD_SCOPE.NoPermissions,
        AUTH_METHOD_SCOPE.SignAnything, 
        AUTH_METHOD_SCOPE.PersonalSign
    ],
});

// output:
{
  pkp: {
      tokenId: string;
      publicKey: string;
      ethAddress: string;
  };
  tx: ethers.ContractReceipt;
}

Minting PKPs using the Lit relayer

The relayer is an open source project, and we run one for your use. The source code is available here. If you want to use our Relayer, you'll need a free API key which you can get by filling out this form.

Authenticating using signMessage Callback

If you wish to sign with an ethers wallet type or signer you may use the signMessage callback to implement a signing callback for the SIWE message.

import { LitNodeClient } from '@lit-protocol/lit-node-client';
import { LitRelay } from '@lit-protocol/lit-auth-client';
import { AUTH_METHOD_SCOPE, AUTH_METHOD_TYPE, PROVIDER_TYPE, LIT_RPC, LIT_NETWORK } from '@lit-protocol/constants';
import { EthWalletProvider } from '@lit-protocol/providers';
import * as ethers from 'ethers';

const litNodeClient = new LitNodeClient({
  litNetwork: LIT_NETWORK.DatilDev,
  debug: true
})
await litNodeClient.connect();

const litRelay = new LitRelay({
  relayUrl: LitRelay.getRelayUrl(LIT_NETWORK.DatilDev),
  relayApiKey: 'test-api-key',
});

const ethWalletProvider = new EthWalletProvider({ relay: litRelay, litNodeClient });

const ethersWallet = new ethers.Wallet(
  'Your Ethereum Private Key', // Replace with your private key
  new ethers.providers.JsonRpcProvider(LIT_RPC.CHRONICLE_YELLOWSTONE)
);

const authMethod = await ethWalletProvider.authenticate({
  signMessage: (message: string) => {
    return await ethersWallet.signMessage(message);
  }
});

const options = {
  permittedAuthMethodScopes: [[AUTH_METHOD_SCOPE.SignAnything]],
};

const mintTx = await litRelay.mintPKPWithAuthMethods([authMethod], options);

Authenticating using Web3 Provider

In the case where you wish to generagte a signature from a browser extension wallet (MetaMask, Brave Wallet, etc) you may simply call authenticate which calls checkAndSignAuthMessage.

import { LitNodeClient } from '@lit-protocol/lit-node-client';
import { LitRelay } from '@lit-protocol/lit-auth-client';
import { EthWalletProvider } from '@lit-protocol/providers';
import { AUTH_METHOD_SCOPE, AUTH_METHOD_TYPE, PROVIDER_TYPE } from '@lit-protocol/constants';
import { Wallet } from 'ethers';

const litNodeClient = new LitNodeClient({
  litNetwork: LIT_NETWORK.DatilDev,
  debug: true
})
await litNodeClient.connect();

const litRelay = new LitRelay({
  relayUrl: LitRelay.getRelayUrl(LIT_NETWORK.DatilDev),
  relayApiKey: 'test-api-key',
});

const ethWalletProvider = new EthWalletProvider({ relay: litRelay, litNodeClient });

const authMethod = await authProvider.authenticate({chain: "ethereum"});

// -- setting scope for the auth method
// <https://developer.litprotocol.com/v3/sdk/wallets/auth-methods/#auth-method-scopes>
const options = {
  permittedAuthMethodScopes: [[AUTH_METHOD_SCOPE.SignAnything]],
};

const mintTx = await litRelay.mintPKPWithAuthMethods([authMethod], options);

Demos:

1. Minting a PKP with an auth method and permitted scopes (Easy)

2. Minting a PKP with an auth method and permitted scopes (Advanced)

3. Minting a PKP with no permissions, then add permitted scopes

4. Minting a PKP using the relayer, adding permitted scopes, and getting session sigs

   info

   Not finding the answer you're looking for? Share your feedback on these docs by creating an issue in our GitHub Issues and Reports repository or get support by visiting our Support page.