https://github.com/moleculeprotocol/lit-issue-demo
demonstrates issue with unifiedAccessControlConditions in lit-sdk-v2
https://github.com/moleculeprotocol/lit-issue-demo
web3
Last synced: about 1 year ago
JSON representation
demonstrates issue with unifiedAccessControlConditions in lit-sdk-v2
- Host: GitHub
- URL: https://github.com/moleculeprotocol/lit-issue-demo
- Owner: moleculeprotocol
- Created: 2023-02-01T14:58:34.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-05-22T09:36:10.000Z (about 2 years ago)
- Last Synced: 2025-05-18T04:36:25.488Z (about 1 year ago)
- Topics: web3
- Language: TypeScript
- Homepage: https://shrilling-bed-acoustic.on-fleek.app/
- Size: 1.42 MB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
## Getting Started
Install dependencies:
```bash
yarn install
```
Run the development server:
```bash
yarn dev
```
Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
#### Demo purpose
This is a simple demonstration of an issue with litprotocol v2.1.16.
When using `unifiedAccessControlConditions` with the new typescript v2 sdk, an error is returned `The access control conditions you passed in do not match the ones that were set by the condition creator for this encryptedSymmetricKey.`
This was working in the JS-SDK and is working if only using evmContractConditions.
We suspect that it's related to the optional field `conditionType` as it's not getting logged in the "formattedEVMContractConditions".