jerryfane / ord-launcher Goto Github PK

Implement whitelist

Collection creators can upload a whitelist.json file on their IPFS folder (correct format still to be defined). This json file can contain information of: (1) Whitelisted address (2) Mint time (3) Mint allocation (4) Mint price?

The Ordinals Launcher can load the whitelist file, and have images be shown to whitelist users in a similar approach as #5

Keep in mind that users can still self-inscribe if they managed to get assets from IPFS, then it's up to the collection creator to track the correct inscriptions onchain.

To avoid changes in the whitelist file, it's possible to inscribe the hash of the whitelist file onchain before the mint start.

Non-Image Assets (HTMLs)

In case of format='html' we need to replace img gallery with iframes. Need to make sure that the htmls loaded on IPFS can properly load recursive /content/ Otherwise, collection creators should upload their recursive /content/ assets on IPFS as well

Launch at time X in the future

Can be easily implemented with an additional parameter on the template, like launchStart in epoch. Then compare with the /blocktime ord recursive endpoint. If launch is not started yet, we won't show images

I would like to add this project to the dashboard

https://ordinals.com/content/4987f34f99095044e2eb2c93121cde4bc32ef73be88e283737d6c3b4077c18b1i0

Mempool Checker in the Verify button

We're currently using Ordinals bot Hash checker API, which only check for confirmed transactions.

We can implement the Mempool checker in one of the following approaches:

1. Wait for Ordinalsbot to implement the mempool checks on their API. This is on their features list, but no ETA provided. This would be the simplest approach
2. Wait for Geniidata to integrate mempool data in their queries. Users would be able to check if a specific hash is being inscribed in the mempool. This is on their features list, but no ETA provided. Not very user friendly, but simple to implement.
3. Run a full node and implement an API connected to the full node checking for hashes in the mempool. Complex and costly approach, with a lot of burdens: (1) Need to run a full node 24/7 (2) Big enough to manage good loads of users (3) Develop API on top of the full node. Maybe this can be provided with a premium subscription on the tool ?