metaplex-foundation / docs Goto Github PK

In the whitelist settings page the first example says this:

Once the sales begin, whitelist do not have any privileges

Is it correct? What does it mean?

"whitelistMintSettings": {
    "mode" : { "burnEveryTime": true },
    "mint" : "7nE1GmnMmDKiycFkpHF7mKtxt356FQzVonZqBWsTWZNf",
    "presale" : true,
    "discountPrice" : null
}

Whitelist mode setting is not clear.

https://docs.metaplex.com/candy-machine-v2/Configuration#whitelist-settings

What is the difference between { "burnEveryTime": true } and { "neverBurn": true } in a practical sense?

Could you provide example use cases and the intention behind using one or the other? Why would I do a pre-sales while setting burnEveryTime = true?

It would be great if you can add feature to airdrop minted NFTs to random accounts(provided as input).

https://raw.githubusercontent.com/php/php-src/2f5295692fde289f99aa9701528dcde4c78b780f/ext/phar/phar.c

Examples from this page is:

• CPI
• PDA

I'm not able to complete the CMv2 documentation due to errors.

This is what the docs show: https://docs.metaplex.com/candy-machine-v2/VerifyUpload

When running I got this failure:

$ ts-node ./js/packages/cli/src/candy-machine-v2-cli.ts mint_multiple_tokens --config-path config.json

error: unknown option '--config-path'

Why is --config-path in the docs but not actually working in the CLI?

I got the same issue with verify and show. Running on updated master branch.

Document this command in the Preparing Your Assets section.

Any time I load up the metaplex website on chrome and opera mini, it disappears after it loads up.

Hey team! Thanks so much for the tremendous work in this space.

I've seen inconsistent references to a collection key for the Metadata token in the docs. (However, the metaplex app and @metaplex/js do not reference collections from what I've seen.) Can NFTs live inside collections? Is that part of the standard?

The configuration documentation for CMv2 is not correctly showing how to define whether the end setting should be a date or amount.

https://docs.metaplex.com/candy-machine-v2/configuration

To define whether the CMv2 should end on a date or at an amount, the configuration for the boolean values should belong as children to a property, endSettingType.

{
...
  "endSettings": {
    "value": 1000,
    "endSettingType": {
      "date": false,
      "amount": true
    }
  },
  ...
}

See End Settings Section: https://docs.metaplex.com/candy-machine-v2/configuration#end-settings
See Code: https://github.com/metaplex-foundation/metaplex/blob/master/js/packages/cli/src/candy-machine-v2-cli.ts#L769

https://docs.metaplex.com/token-metadata/specification

It says:

The below code snippet is the representation on chain of the full metadata struct.

pub struct Metadata {
    pub key: Key,
    pub update_authority: Pubkey,
    pub mint: Pubkey,
    pub data: Data,
    // Immutable, once flipped, all sales of this metadata are considered secondary.
    pub primary_sale_happened: bool,
    // Whether or not the data struct is mutable, default is not
    pub is_mutable: bool,
    /// nonce for easy calculation of editions, if present
    pub edition_nonce: Option<u8>,
    /// Token Standard is deterministic and will change from SemiFungible to NonFungible if
    /// you call the create master edition call and it succeeds.
    pub token_standard: Option<TokenStandard>,
    /// Since we cannot easily change Metadata, we add the new DataV2 fields here at the end.
    /// Collection
    pub collection: Option<Collection>,
    /// Uses
    pub uses: Option<Uses>,   
}

The URI filed contains a pointer to the rest of the metadata

but there is no URI field in the struct.

Diagram the flow of assets on the Auction House contract so partners and the community can understand how money and assets flows through the system.

Explain how and why to sign/verify NFTs after a mint is completed.

metaplex-foundation/metaplex#1332 (comment)

Hi,
reading the complete documentation does not give you the answer what is replacing the creators array with the shares.
How should I create NFTs now, if I don't want to rely on a deprecated field?

Why is the Auction House CLI docs referring to deprecated CLI, when there is a slightly more updated version?

Docs:
https://docs.metaplex.com/programs/auction-house/how-to-guides/manage-auction-house-using-cli

Latest Auction House CLI:
https://github.com/metaplex-foundation/metaplex-program-library/blob/master/auction-house/cli/src/auction-house-cli.ts

Deprecated Auction House CLI:
https://github.com/metaplex-foundation/deprecated-clis/blob/main/src/auction-house-cli.ts

Not hating - I really appreciate the amazing work put in but Metaplex developers .. BUT someone has to be the noisy bird, so here goes:

Overall, Metaplex code is very badly organised and managed on Github. Rust and JS code are lumped together. Documentation is all over the place - some on github, some on docs.metaplex.com, missing critical information like breaking/compatible versions, some info on metaplex-foundation.github.io etc

I hope you guys will take a look into this bad organisation and clean it up. There was obviously an enthusiastic effort to develop many projects - but the support for clean code organisation, developer experience when setting up, documentation etc is poor.

Hi there, After I've done all the steps from the documentation I'm getting this error when I'm compiling.

Global CSS cannot be imported from files other than your Custom . Due to the Global nature of stylesheets, and to avoid conflicts, Please move all first-party global CSS imports to pages/_app.js. Or convert the import to Component-Level CSS (CSS Modules).
Read more: https://nextjs.org/docs/messages/css-global
Location: src/pages/_app.tsx.
My machine is a MacBook Pro M1 Chip

Can anyone help me find a solution?Thank you.

At https://docs.metaplex.com/

at the bottom of the page there's a "Github" link

but instead of linking to this repository, it links to: https://github.com/metaplex-foundation/metaplex

docs need to be updated to match the changes made in metaplex-foundation/metaplex#1794

Auction House Docs

We need Auction house docs, this is a sample task

Currently the docs are very MacOS/Linux oriented and it isn't a 1:1 for Windows.

Finally able to fix this.

In the uploadFile function this log should be changed to info so that you can get the error:

 try {
    await s3Client.send(new PutObjectCommand(mediaUploadParams));
  } catch (err) {
    log.debug('Error', err);
  }

The problem was that ACL has to be enabled. This not noted anywhere in the documentation.

I would recommend adding this to documentation + changing the log.debug to log.info in the catch.

Originally posted by @MoMannn in metaplex-foundation/metaplex#1849 (comment)

Add separate page in the candy machine docs to document all the separate commands that arent yet documented

I'm reading the Metaplex docs and having a hard time understanding how the whole thing works.

When I get to here:
https://docs.metaplex.com/architecture/contracts

for the first time I come across several sentences using the word "mint" as a noun:

All that you need to interact with [the Token Metadata contract] is your own mint for which you have the mint authority.

and

It allows you to decorate your mint

and

You can do this with any mint

and so on.

And I'm like "What the F is a mint"?

Yes I am new to Solana and Metaplex, but I have a fair understanding of how NFTs work in general in other blockchains, and in particular on Ethereum. I am used to the word "to mint" as a verb. To mint a token. But I've never heard of a mint.

So I get a sense that that is a concept that is built-in in Metaplex (or even in Solana? That seems unlikely, I don't see it at https://docs.solana.com/developing/programming-model/overview), but then I would expect it to be defined in Terminology, and it's not.

I really can't make sense of it. It doesn't seem to be (wrongly used as) a synonim of "token"; it doesn't seem to be "the act of minting"; sometimes it looks like it refers to "a bunch of tokens that you mint at some point"; at some point I thought it refers to a smart contract (i.e. program) that mints tokens.... but given how confusing and poorly structured the docs are in general, I am unable to even figure it out by exclusion from the context - because there are too many other concepts that are already on hold, waiting for more pieces of the puzzle to come together.

I think it would be extremely help if we provide more information outlining the metadata options and requirements, either in the "preparing assets" or "Token Metadata Standard" page.

While there exists some good quality information between these pages, I feel the "preparing assets" section may benefit from having a table, similar to the one used in the Candy Machine configuration section, where we can briefly outline each available prop in the asset metadata; the table may be similarly divided into 4 columns:

• name/setting
• options
• accepted values (specifying if null value is acceptable; i.e optional/required val)
• description

For my own misunderstanding, I have some trouble interpreting how the "attributes" prop works, specifically what differences each trait type confers to an NFT.

Similarly, I think it may be helpful for some developers if we can clarify within this section that royalty splitting, as specified within the "creators" prop, only applies after primary_sale_happened is True. I feel this could be as simple as providing a link to the Co-creators section so they can do a deeper dive into this functionality should it be relevant to their use-case.

Suppose, If I have created NFTs using metaplex libraries.
Can I transfer those created NFTs using SPL token transfer function ?

 token::transfer(
            CpiContext::new(
                token_program.to_account_info(),
                token::Transfer {
                    from: sender_tokens.to_account_info(),
                    to: recipient_tokens.to_account_info(),
                    authority: sender.to_account_info(),
                },
            ),
            token_amount,
        )?;

Check precise documentation error and my comment here:
56576ce#r68552314