The problem Gatekeeping Protocol solves

Gatekeeping protocol as your event entry manager

POAPs are overkill and highly unscalable at the same time. We wanted to create something that is easy for the event organisers to use, which doesn't involve the usual web3 jargon and has more than just a option to airdrop/mint NFTs . Presenting Gatekeeping Protocol,
The event organizers can choose from a wide range of gated mechanisms that we provide, for them to gatekeep as they want.

Gatekeeping protocol as a subscription manager

We take the idea of using NFTs as proof of attendance and extend it to using the same token as proof of subscription, thus extending the legs of POAP into the domain of subscription models. Some of these models include minting soul bound NFTs, NFT that can be sublet to others for a price.

Gatekeeping protocol as a boring POAP dispenser

In addition to all the other cool features that we provide, we also act as POAP dispenser, which is just a fancy way of explaining account whitelisting.

Protocol structure

• The protocol right now consists of 3 different type of subscription model / event management structures. All three of them are maintained by the Gatekeeper contract. This contract creates the NFT collection or whitelisting database as needed. It also acts as a lens to view all relevant data

• Soul-bound NFT contract. This acts as the key to the gates which have issued an NFT

• Rentable NFT contract. These keys have a lessor-tenant relationship. The original keys can be rented out to other accounts for borrowing the utility. Best usecase for these kind of NFTs are OTT subscriptions

Deployed on Valist : https://gateway.valist.io/ipfs/bafybeiefhpqeg65gfkktwtz2kb7zugypacl6za3iu5tprrfns3bo6vqqpe

Challenges we ran into

Most of the challenges we faced, were in fact during sponsor integrations, since a lot of the sponsoring organizations are also in their early stages.

• We had trouble integrating biconomy to create meta transactions, and push protocol's notification systems, but eventually succeeded with the respective teams' help.
• We couldn't implement Account abstraction as there was surprisingly little about it in the docs.
• We planned on creating an SDK but the time turned out to be too less.