Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update supported chains list #283

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

spacesailor24
Copy link
Contributor

@spacesailor24 spacesailor24 commented May 15, 2024

Updates the list of supported chains for cayenne, habanero, and manzano

Copy link

netlify bot commented May 15, 2024

Deploy Preview for lit-dev-docs ready!

Name Link
🔨 Latest commit ca36e22
🔍 Latest deploy log https://app.netlify.com/sites/lit-dev-docs/deploys/66467c5d14eca50008cb97a7
😎 Deploy Preview https://deploy-preview-283--lit-dev-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@spacesailor24 spacesailor24 changed the title Add amoy to support chains for cayenne Add amoy and blast to supported chains for cayenne May 16, 2024
@spacesailor24 spacesailor24 changed the title Add amoy and blast to supported chains for cayenne Add amoy, blast, blastSepolia to supported chains for cayenne May 16, 2024
@spacesailor24 spacesailor24 changed the title Add amoy, blast, blastSepolia to supported chains for cayenne Update supported chains list May 16, 2024
@spacesailor24 spacesailor24 requested a review from DashKash54 May 16, 2024 22:04
@a1ttech
Copy link
Contributor

a1ttech commented May 21, 2024

Under supported chains you wrote 'access control and PKP' but this isn't entirely accurate? I think these chains are explicitly only supported for 'access control' whereas PKP signing is only natively supported on eth + cosmos right now (via the SDK packages) though there are workarounds using Lit Actions+ which i think we can reference.

I think we should add this caveat under the 'Programmable Key Pairs' header and then all the supported chains (with the tabs per network) should only be for access control

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants