straightupjac / nft-merkle-allowlist-scaffold Goto Github PK

Can you implement this counter to show how many have been minted below the mint card. For example when you connect it would say "5/300" if 5 out of 300 were minted.
https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/test/utils/Counters.test.js

33 | }
34 | async function checkIfClaimed() {

35 | sampleNFT.methods.claimed(account).call({ from: account }).then((result) => {
| ^
36 | setAlreadyClaimed(result);
37 | }).catch((err) => {
38 | setAlreadyClaimed(false);

Hi, thanks for creating and making public this framework, it is the best I have found so far. I noticed on https://nft-merkle-demo.vercel.app/ that there is only one NFT available for each "minting mechanism". E.g. only one Gift Mintable NFT, one Public Mintable NFT etc..

What I was wondering is whether this is an inherent limitation of this codebase, or if it could be easily modified to add more than one NFT for each minting mechanism?

I would ideally like to use it to list 10k NFTs, without needing to mint them up-front. Is this something I could relatively easily achieve using this codebase? Thank you very much.

Distbit

Is there anyway to map this out in the smart contract? For a custom whitelist?
Example given:
Wallet 1 is allowed to mint 3 NFTs.
Wallet 2 is allowed to mint 11 NFTs.
Wallet 3 is allowed to mint 50 NFTs.
Wallet 4 is allowed to mint1 NFT.
etc...

I keep getting errors saying the private key isn't 32 bytes. If I place in config directly after 0x it will compile.

Another issue is after that I run the deploy script is it says invalid endpoint. could you share an example ENV file populated please?

Thanks!

Describe the bug
A clear and concise description of what the bug is.
[root@VM-0-15-centos web]# yarn dev
yarn run v1.22.17
$ next dev
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info - Loaded env from /root/NFT/nft-merkle-whitelist-scaffold/web/.env
thread '' panicked at 'assertion failed: (left == right)
left: 22,
right: 0', library/std/src/sys/unix/condvar.rs:63:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
error - ./node_modules/next/dist/client/dev/amp-dev.js
Error: failed to process
^C
[root@VM-0-15-centos web]# yarn build
yarn build
yarn run v1.22.17
$ next build
info - Loaded env from /root/NFT/nft-merkle-whitelist-scaffold/web/.env
info - Checking validity of types
info - Creating an optimized production build ..thread '' panicked at 'assertion failed: (left == right)
left: 22,
right: 0', library/std/src/sys/unix/condvar.rs:63:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21
info - Creating an optimized production build
Failed to compile.

./node_modules/next/dist/client/next.js
Error: failed to process assertion failed: (left == right)
left: 22,
right: 0

./node_modules/next/dist/client/router.js
Error: failed to process

./node_modules/next/dist/pages/_error.js
Error: failed to process

./pages/_app.js
Error: failed to process

./pages/index.js
Error: failed to process

Build failed because of webpack errors
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.