Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds an example that uses SIWS to auth a user, with any custom JS logic in the lit action. We use a single access control condition that simply checks that
:currentIpfsCid == generatedIpfsCid. Therefore, you're trusting the logic of the Lit Action itself to check whatever conditions you want.In this example, we just set this additional check to "true", but a dev would implement their own checks here. Therefore, this example gets the dev to a spot where everything works, they have an authed solana wallet address, and they can just write the extra JS they need to check anything they want using the solana wallet. They can check balances, run contract calls, hit things with fetch() or use solana RPC.
I created this for Beacon to help them get their custom solana access control conditions working.