POAPMAN

Identifying a gap with Creator Management I wanted to explore the POAP eco system and API and see if there was a way to reduce friction and improve creator experience. I also wanted to reimagine how the POAP ecosystem might better manage create administration beyond using "PoapID" and "Secret".

I built a Dapp hosted on IPFS/IPNS mapping to a custom .xyz domain. It was important to me this was decentralised and late on involved refactoring from NextJS to React to use a hash router to realise. The POAP Creator Management Dapp "POAPMANager" heavily integrates with the POAP API to enable Create, Read and Update operations to POAPs the administrator adds or creates in the Dapp. The unique aspect of this Dapp is the creator can add the "ID" and "SECRET" to compile a full record of all the POAPs they have created which required customisation.

I have also detailed a further roadmap of additional features that would be great to add to the Dapp alongside potential upgrade initiatives that the protocol could consider to move POAP administration on chain using a Poap Creator Token strategy and outlined that logic which I hoped to build a simple POC for too.