nft

With an Open Edition the NFT supply must be infinite in order to list. However the number of NFTs displays as 0 as does the number of Winners. Further more it is set at a fixed price. In this example the fixed price is 0.5 SOL. Rather than display the fixed price number it displays the highest bid. There is no language describing how this auction works in that anyone who bids 0.5 will receive the

Unlock's front-end application (unlock-app) requires the user to login in order to authenticate them. However, the user information is only available while the session is ongoing. Now that unlock actually supports an explicit "log out", it would be useful to cache/persist locally the user's address so that when the user refreshes the page, they don't have to login again. Similarly, when a user v

Hi, Patrick

Can you please only leave the .env.example file and delete the .env one?
Us newbies might end up leaving our mneumonic exposed, because .gitignore does not ignore files that are already there on github.

Thanks for all the top-notch teaching.

Issue To Be Solved

We have accurate template transactions in the transactions folder but not all of them are included in the lib/go/templates package.

Suggest A Solution

• Use the go bindata tool and string replacer to get the template from transactions/ and replace the contract names and addresses with the provided arguments, similar to how it is done with `GenerateCreateCo

Since raw queries only return encrypted keys, it's pointless and will break implementations coming from other networks without letting anyone know.

We should remove it from the next version

Issue To Be Solved

The Top Shot contract was recently upgraded and the docs need to be updated.

Suggest A Solution

• Update the README to mention the changes where applicable
• Give examples for querying set data

They are useful beyond migrations.

nftstorage/nft.storage#97 (review)

First off: Thanks for the toolkit! It's really nice to work with and there have already been some great suggestions for improvement made by other users that I thought about as well when testing a collection.

Something else I'd like to suggest is adding customisation options for metadata as follows:

• Allow customising the name property and do not force the "symbol #N" format here
• Allow