Phases in drop page

[exezbcz]

okay, next drop will be experimental again

• phases are not dynamic, since its not ready on the backend - probably won't be
• it will be switched from phase to phase based on items minted.
• its the first iteration, i don't care much about the spacing, etc.
• It should be mainly usable, and not full of bugs, The correct phase at correct time is the most important

one thing that is also needed for this drop is:

• Holder of drop page iteration #8886

Design

• updated in handoff file: https://www.figma.com/file/JXNtryaNYhY0XJNArzvPQx/Handoff?type=design&node-id=394-6126&mode=design&t=3s7RGwwjGd1GHvRF-11

Phase 1

• usually, there will be some sort of presale, in our case, holder of the motherboard
• its the same part you know from the mentioned Holder of drop page iteration #8886
  

Phase 2

• will be public mint, after predefined number of items gets minted in the presale, it is switched to this state.

• this one is also the one we are using

General

• each phase has its progress indicator - number of items for upcoming drop will be set by @vikiival
• when one phase is open, its the default one and cannot be collapsed.
• on the other hand, the secondary (not active) phase can be opened
  
• it will show the progress bar and the requirements

all possible states are hopefully there, like this one:

• presale open, and the user clicked on the public sale
• it will show him this:
  

[hassnian]

phases are not dynamic, since its not ready on the backend - probably won't be

@vikiival how much of the backend is ready

[JustLuuuu]

Two important questions:
if I have 2 motherboards will I be able to mint 2 NFTs in a private sale? - this is very important to know and properly communicate with people minting. If no the we MUST have a message - only 1 NFT mint per account is possible or something like that. (Reminder: it is still not possible to mint two NFTs with chroma lattice - people were complaining)

If the motherboard will be used once can it be used again - just remember how it was with chroma lattice. We REALLY want to avoid issues while minting last time. Chromma Lattice is still not minted out

[exezbcz]

@JustLuuuu yeah, imo it is not possible due to some bugs.

with that I am more and more considering leaving it free, or make the phases without the holder of

so it will go like this:

1. free
2. paid

[vikiival]

how much of the backend is ready

I will add holder of so it's possible to get from backend.
I havent touch phases :), but you can

[hassnian]

👋

[kodabot]

ASSIGNED - @hassnian 🔒 LOCKED -> Thursday, January 18th 2024, 22:09:17 UTC -> 36 hours

[vikiival]

I will add holder of so it's possible to get from backend.

@hassnian api now return field holds that will tell you if it is holder of the collection

[hassnian]

@vikiival can we get a ahk test drop , thanks

[vikiival]

@vikiival can we get a ahk test drop , thanks

Yes flatwhite is obtainable only if you hold coretime

[hassnian]

@vikiival for the second phase "public sale" which will be paid , we need the price field

atm flatwhite returns '0' can you update that

also running this flatwhite

      const cb = api.tx.nfts.mint
      const args = [
        collectionId.value,
        collectionRes.items,
        accountId.value,
        {
          ownedItem: null,
          mintPrice: price.value,
        },
      ]

args

[
    "311",
    4,
    "DYc9cY7q7UA3Rq97HtiobrLNbMbZgepATJtn3fzPE2jf5v6",
    {
        "ownedItem": null,
        "mintPrice": "0"
    }
]

throws

works fine for coretime what am i missing ?

thanks

[vikiival]

Yes flatwhite is obtainable only if you hold coretime

For flatwhite you need to be pass the idem id you are elegible to claim

[
    "311",
    4,
    "DYc9cY7q7UA3Rq97HtiobrLNbMbZgepATJtn3fzPE2jf5v6",
    {
        "ownedItem": "3", // sn of coretime that I am holding
        "mintPrice": null
    }
]

[vikiival]

@vikiival for the second phase "public sale" which will be paid , we need the price field

atm flatwhite returns '0' can you update that

Phases are not implemented atm but you or @Jarsen136 can pick it up:

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

[hassnian]

@vikiival got it

do we want phases for this next drop ?

btw don't have access to private workers

[kodabot]

ASSIGNMENT EXPIRED - @hassnian has been unassigned.

[yangwao]

btw don't have access to private workers

you should have meanwhile @hassnian