FAQ

1. Are my Web3 provider key and AI api key safe?

Answer: The web3ProviderURL and aiApiKey are read from environment variables. You don't store it in the .asset or code. Make sure you don't commit your environment variable to a public repo.

---

2. My token transfer fails or returns a null receipt?

Answer:

• Verify you initialized NAREONWeb3 with NAREONWeb3.Initialize().

• Confirm your environment variable is set (check logs for the correct URL).

• Ensure your contract address is correct, the account/wallet has tokens, and you have sufficient gas on that account if it’s signing locally.

---

3. Where do I set up private key signing?

Answer: The included sample uses Nethereum.Web3 with no explicit private key. Typically, you’d set an account or use a private key in code. For best security, some prefer a server-based approach or a custom wallet integration. See Nethereum docs for advanced signing.

---

4. Why do I see errors about NAREONSettings not found?

Answer: Make sure you actually created a NAREONSettings.asset in your project. The loader tries to locate it. If none is found, it logs a warning or error.

---

5. Can I store IPFS or metadata for NFTs?

Answer: That’s typically done in your NFT contract or on IPFS. The TokenConfig stores the contract address of the token which has access to the metadataUri if available.

---

If you have more questions or suggestions, feel free to open an issue or contact the maintainers!