Describe the enhancement

All repos have .gitignore files, make sure they all have .env and .encryptedKey.json in them. As well as node_modules

In our codebase, we currently use multiple HTTP client packages: fetch, node-fetch, cross-fetch and axios...
This is adding unnecessary complexity (cognitive load as these API differ slightly), extra build time, heavier bundles... etc.

We should normalize to only use fetch is nos supported by all major browsers and node.js natively (as of 18... which we don't support yet but would

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.

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

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

Issue To Be Solved

We current have a go package for getting transaction templates, but we should also have a javascript package so users of the contracts can import and use the correct versions without having to copy and paste.

Suggest A Solution

Create a lib/go/javascript/templates package that does a similar thing to the lib/go/templates package.
It should use the transactions and

Prevent user from minting when has insufficient balance, other actions send/consume/list/buy been solved in action component

Mind test on

• classic
• simple mint

Originally posted by @yangwao in kodadot/nft-gallery#65 (comment)

Enumerating all the proxies in a doc would be nice! There are so many. Even if it happens in the doc str of the method, that is fine. Else, we may need contracts.md userguide (in docs/userguides). If you go that route, you don't have to thoroughly create it, just initialize it, add the enumeration, and we will fill it in later with non-relevant details to this PR.

_Originally posted by @unp