Upgrading from Share Modal v2

This is a brief summary of how to move from the (EVM only) Access Control Conditions format used in the old Lit Share Modal to the new Unified Access Control Condition format used in the new v3 build. More information on Unified Access Control Conditions can be found here

There are two changes to be aware: first, the additions of a conditionType property within each individual condition of itself defines what kind of AuthSig is required to register it, and, second, a change in the syntax of the object passed to the saveSigningConditions and getSignedToken methods in the litNodeClient.

New conditionType property

Within the individual conditions, a new conditionType property has been added. The share modal currently supports Solana and EVM chains, which use the values 'solRpc' and 'evmBasic' to differentiate.

Old (EVM only) Access Control Conditions format for checking a wallet with address 0x50e2dac5e78B5905CB09495547452cEE64426db2.

const accessControlConditions = [
  {
    contractAddress: '',
    standardContractType: '',
    chain: 'ethereum',
    method: '',
    parameters: [
      ':userAddress',
    ],
    returnValueTest: {
      comparator: '=',
      value: '0x50e2dac5e78B5905CB09495547452cEE64426db2'
    }
  }
]

New Unified Access Control Conditions format far same condition as above. Note the addition of the conditionType property.

const unifiedAccessControlConditions = [
  {
    conditionType: 'evmBasic',
    contractAddress: '',
    standardContractType: '',
    chain: 'ethereum',
    method: '',
    parameters: [
      ':userAddress',
    ],
    returnValueTest: {
      comparator: '=',
      value: '0x50e2dac5e78B5905CB09495547452cEE64426db2'
    }
  }
]

The new format can also be used to denote Solana conditions. Note the change of the conditionType to 'solRpc'. Here is an example of checking for a wallet with address 88PoAjLoSqrTjH2cdRWq4JEezhSdDBw3g7Qa6qKQurxA.

const unifiedAccessControlConditions = [
  {
    conditionType: 'solRpc',
    method: "",
    params: [
      ":userAddress"
    ],
    chain: 'solana',
    returnValueTest: {
      key: "",
      comparator: "=",
      value: "88PoAjLoSqrTjH2cdRWq4JEezhSdDBw3g7Qa6qKQurxA",
    },
  },
  }
]

Conditions from different chains can be combined using AND/OR operators. This example checks for ownership of an EVM wallet of address 0x50e2dac5e78B5905CB09495547452cEE64426db2 OR ownership of a Solana wallet with address 6XmeyeYtSd31Eby2syaRkpXKY2GMMd3n3MEwTM5B7riD.

const unifiedAccessControlConditions = [
  {
    conditionType: 'evmBasic',
    contractAddress: '',
    standardContractType: '',
    chain: 'ethereum',
    method: '',
    parameters: [
      ':userAddress',
    ],
    returnValueTest: {
      comparator: '=',
      value: '0x50e2dac5e78B5905CB09495547452cEE64426db2'
    }
  }
  { operator: 'or' },
  {
    conditionType: 'solRpc',
    method: ',
    params: [
      :userAddress'
    ],
    chain: 'solana',
    returnValueTest: {
      key: ',
      comparator: '=',
      value: '6XmeyeYtSd31Eby2syaRkpXKY2GMMd3n3MEwTM5B7riD'
    }
  }
]

saveSigningCondition syntax change

Old (EVM only) Access Control Condition format for saving conditions:

var ethAuthSig = await LitJsSdk.checkAndSignAuthMessage({
  chain: "ethereum",
});

await litNodeClient.saveSigningCondition({
  accessControlConditions: accessControlConditions,
  authSig: ethAuthSig,
  resourceId,
});

New Unified Access Control Conditions format. The new format passes in a different AuthSig for each condition type under a specific property name. Note too, the change from accessControlConditions to unifiedAccessControlConditions. Here is an example of what it would look like to save conditions that used both Solana and EVM condition types.

Note: if saving only EVM conditions, only an 'ethereum' AuthSig is required. Likewise, if only Solana conditions are saved, only a 'solana' AuthSig is required.

var solAuthSig = await LitJsSdk.checkAndSignAuthMessage({
  chain: "solana",
});

var ethAuthSig = await LitJsSdk.checkAndSignAuthMessage({
  chain: "ethereum",
});

await litNodeClient.saveSigningCondition({
  unifiedAccessControlConditions,
  authSig: {
    solana: solAuthSig,
    ethereum: ethAuthSig, // note that the key here is "ethereum" for any and all EVM chains.  If you're using Polygon, for example, you should still have "ethereum" here.
  },
  resourceId,
});

getSignedToken syntax change

The getSignedToken method changes in the same way as saveSigningCondition.

var solAuthSig = await LitJsSdk.checkAndSignAuthMessage({
  chain: "solana",
});

var ethAuthSig = await LitJsSdk.checkAndSignAuthMessage({
  chain: "ethereum",
});

await litNodeClient.getSignedToken({
  unifiedAccessControlConditions,
  authSig: {
    solana: solAuthSig,
    ethereum: ethAuthSig,
  },
  resourceId,
});

More information on Unified Access Control Conditions can be found here