0xgeel / loopgate Goto Github PK

Context

• Currently, we lean on using the InjectedConnector to get users with GameStop Wallets to connect. This shows up as 'Browser Wallet'. This may sometimes be confusing, especially if they have multiple browser wallets.

Solution

• We could look into WAGMI's connectors in order to extend the InjectedConnector to create a GameStop Wallet Connector.

See:

• https://wagmi.sh/examples/custom-connector
• https://github.com/wagmi-dev/wagmi/pull/414/files

Additional context

Context

• This project is intended to be accessible to others. Currently, you need to have a good grasp on (web) development and infrastructure to get it going.

Solution

• Find a workflow that makes the token gating solution more accessible to non tech nerds. Document this, and create good docs/ (with images) to help others out.

Context

• Provide insights in the resilience of LoopGate by introducing logs.

Solution

• LogFlare's free tier and the Pino OS software. See: https://github.com/Logflare/pino-logflare

Describe the bug
On step 4.3 of the LoopGate GitBook, when attempting to compile for a local instance, the following error occurs:

"./node_modules/connectkit/build/index.es.js:5:0
Module not found: Package path ./connectors/walletConnectLegacy is not exported from package C:\Users\tnguy\Documents\SpaceCatWebsite\TokenGate-1\node_modules\wagmi (see exports field in C:\Users\tnguy\Documents\SpaceCatWebsite\TokenGate-1\node_modules\wagmi\package.json)

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./src/pages/_app.tsx"

Potentially this is an issue with the WalletConnectLegacy soon to no longer be supported? See wagmi link:
https://wagmi.sh/core/connectors/walletConnectLegacy

I've tried a few suggestions from stack exchange and looking at the wagmi.sh website for how to deal with their breaking updates but to no avail.

To Reproduce
Steps to reproduce the behavior:
I've followed the GitBook steps for creating my own instance without deviation (as far as I can tell). I am using VS Code on Win 11.

Expected behavior
Expected to compile properly and a local instance of my tokengate to be available.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 11
• Browser: Chrome

Context

Currently, all CIDs are unlocked upon connecting with your wallet. This has impact on the UX, as the page load for 3 NFTs already can take up to 1.8 seconds. Also, it does not give the creator an easy way to share one individual token-gated piece.

In addition to the overview, we could add individual pages for unlockables.

• Using NextJS' API pages function.
• Re-writing the Pinata logic

Suggestions and ideas are very welcome! 🙏

I'm not sure how feasible this is, but it'd be amazing to have this available as a WordPress plugin. That's definitely a plugin I'd pay money for! There are two plugins right now for WordPress that offer this functionality: ethpress and "WordPress NFT Token Gating &
Web3 Wallet login". Ethpress requires the manual installation of some sus looking libraries that I'd rather not mess with, and the other one is crazy expensive and offers way more than i think most people who are looking for this kind of functionality actually need.

Context

Currently, the only unlock criteria is owning NFTs. A Unlockable can be unlocked by the user holding NFTs with nftIds specified in the array. While this is a good start, there is value in unlocking content based on other criteria.

Here are ideas for other unlock criteria:

• Holding any of the nftIds specified in the array.
• Holding a NFT minted on a certain tokenAddress.
• Holding multiple NFTs minted on a certain tokenAddress.

Suggestions and ideas are very welcome! 🙏