Mass Minting in drop page

[yangwao]

we've been briefly chatting about this feature as it would be worth if someone want to buy from one collection right away like 10 pieces and don't want to wait long.

Would be nice to materialize this so we can speed up mints and don't need to wait 1-by-1 minting

Design

after:

• 9171

file: https://www.figma.com/file/JXNtryaNYhY0XJNArzvPQx/Handoff?type=design&node-id=394-6126&mode=design&t=k6t3uvZZb3DCxEFi-11

[exezbcz]

How will the random generation be handled? I don't want to get the same X items in one purchase.

[exezbcz]

done in:

• 9171

[vikiival]

How will the random generation be handled? I don't want to get the same X items in one purchase.

as everything is done currently on the client side the process is fairly simple:

• when user press mint (3)
• the app must generate 3 new generative arts (random input) - so we ensure it is captured.
• metadata is created - pin two directories to IPFS
• sends request to allocate - kodadot/private-workers#44
• workers tries to allocate minimum of (I want, available) - eg. I wanna 3, available to mint 2 - I get 2
• after allocation the mint fn is called
• only if transaction is successful call api to assign metadata

TL;DR Answer to your question is 3 bullet points

[newraina]

sends request to allocate workers tries to allocate minimum of (I want, available) - eg. I wanna 3, available to mint 2 - I get 2 after allocation the mint fn is called

@vikiival Are these tasks dependent on the new fxart worker? or can the waifu worker handle them? Based on the current code, I can't seem to find a method to mass mint using waifu.

[vikiival]

Are these tasks dependent on the new fxart worker? or can the waifu worker handle them?

• https://github.com/kodadot/private-workers/issues/44

needs to be implemented, waifu worker will be deprecated for drops.

However first 3 can be implemented tho

[newraina]

@yangwao Is it possible to grant access to a private-worker for external contributors? if not, hoping that fxart will offer public API doc

[exezbcz]

• the app must generate 3 new generative arts (random input) - so we ensure it is captured.

okay, user might need to wait in the confirmation dialog

something like this.

• instead of the preview there is skeleton loader

[vikiival]

so we ensure it is captured

• instead of the preview there is skeleton loader

You must see the preview. App cannot allow you to mint if you do not have the preview

So it will be 42,43,44

[exezbcz]

so we ensure it is captured

• instead of the preview there is skeleton loader

You must see the preview. App cannot allow you to mint if you do not have the preview

So it will be 42,43,44

The state designed is loading the variation

[yangwao]

@newraina do you still want to work on this one?

[yangwao]

hoping that fxart will offer public API doc

cc @vikiival can you copy needed stuff, please?

[newraina]

do you still want to work on this one?

@yangwao busy this week, someone else could take it on :)

[vikiival]

cc @vikiival can you copy needed stuff, please?

Correct impl is waiting on:

• https://github.com/kodadot/private-workers/issues/44

but we can do it now as:

POST /drops/allocate/:id

Body as already in code

and do

const mints: ArrayOfBodiesForClaim = []
const raffles = await Promise.allSettled(mints.map(mint => claim(mint)))

TL;DR call the same api more times (the CODE above is just a PSEUDOCODE)

[yangwao]

@kodadot/internal-dev free for grabs, should be easy they say, @vikiival will help you assist

[exezbcz]

👀

[hassnian]

👋

[kodabot]

ASSIGNED - @hassnian 🔒 LOCKED -> Tuesday, February 27th 2024, 05:48:59 UTC -> 72 hours

[kodabot]

ASSIGNMENT EXPIRED - @hassnian has been unassigned.