# Ignite FAQ

We offer an easy way to navigate to common issues when installing and using Ignite CLI. If you don’t see the answer to your question here, please reach out to us on Discord

## FAQ Categories

* [Installation](#Installation)
* [Access Permissions](#Access-Permissions)
* [Scaffolding](#Scaffolding)
* [Binary Issues](#Binary)
* [Serving](#Serving)
* [Config Files](#Config-Files)
* [Wallets](#Wallets)
* [Front End](#Front-End)
* [Networking Commands](#Networking-Commands)
* [Git Related Issues](#Git-Related-Issues)
* [Cosmos SDK](#Cosmos-SDK)

## Installation

Q: How do I install Ignite CLI?
A: Please follow this tutorial here:
[Install Ignite Tutorial](https://docs.ignite.com/welcome/install)

Q: How do I install golang?
A: You can install the latest version of golang here:
[Download Golang](https://go.dev/doc/install)

Q: How do I know which architecure I have?
A: You can simply type "arch" in your command line to see your chip architecture.

Q: Scaffolding a new chain with v0.27.2 and got this error using go 1.19.13
A: Remove your go installation and install v1.21.4 and should work fine.

## Access Permissions

Q: I am having getting a Permission Denied error:
A: This is most likely due to your settings, you can attempt to overrule this with the "sudo"(super user do) command. If it happens when trying to access a folder, you can fix it with this command:

` sudo chown -R your_username folder_name`

Q: Where are my keys? For example, when I do ignite account create Jack

It does create an account... but where?

For example when I complied my own binary and tried Checkersd keys list it didn't show me my Jack account:

A: You would create your account keys with your checkersd binary, not Ignite. checkersd is the binary for your blockchain, so you would not use Ignite for that. Ignite helps you get your chain off the ground, then most of the commands specific to your chain once it has been deployed will be done using the chain's binary.

## Scaffolding

Q: How do I scaffold a blockchain with Ignite?
A: You can see the scaffolding options with "ignite scaffold chain --help", to scaffold a chain called "mychain" the command would be?

`ignite scaffold chain mychain`

Q: Why are alice and Bob's address Cosmos, how can I change that?
A: Use the --address-prefix flag when scaffolding a chain. To scaffold a chain with the address prefix "gold", we would use this commmand

`ignite scaffold chain gold --address-prefix gold `

## Binary

Q: I received the following error when using my blogd binary. Is there a solution?
exec: "blogd": executable file not found in $PATH

A: You need to ensure the app's binary is on your system path. For Linux systems, it is a hidden file usually located in your home directoy. If you are using bash, the file is called .bash_profile or .bashrc. For Mac, it is usually .zshrc

To edit these, use the following command from the directory the file folder is located. In this example, we will edit the .bash_profile

nano .bash_profile
#copy and past this command into the file:
export PATH=$PATH:~/go/bin
#close and save the file
source .bash_profile
#Now try to use the binary
blogd --help

## Serving

Q: How can I get some logs in console
A: You can use the -v, --verbose flag when running ignite chain serve

`ignite chain serve --verbose`

## Config Files
Q: How can I edit my config file prior to building the binary?
A: You need to create your .app folder. To do so, the commands would be:

ignite scaffold chain planet
cd planet
ignite chain init

Your config files will now be generated and located at '.planet/config'.

## Wallets
Q: Can I export my private key for alice or bob, rather than use the mnemonic?

A: Yes, though it is not recommended outside of a testing environment. To export Bob's keys here would be the process.

ignite scaffold chain blog
cd blog
ignite chain serve
#open a new window
blogd keys export bob --unarmored-hex --unsafe 
#Select 'y' to awknowledge it is unsafe. 

## Front End

Q: How do I generate a Type Script Client for my application?

A: The quick answer is, you can generate the ts-client it seems by scaffolding vue. Here is how I did it.

ignite scaffold chain awesome --address-prefix awesome
cd awesome
ignite scaffold vue
ignite generate composables --clear-cache
export VITE_ADDRESS_PREFIX=awesome
ignite chain serve

In another window from home directory:
cd awesome
cd vue
npm install
npm run dev

Q: When I attempt to scaffold a Front End application (Vue, React, etc) I see a bunch of warnings after running the "npm install" command, what should I do?
A: It is up to you, but you can try to "npm run dev" and see if your front end will launch. Or you can try the "npm audit fix" or "npm audit force --force" to fix the issues. If that doesnt work, please be sure to upgrade the latest version of Ignite and try again.

Or, you can see the official docs page here:
https://docs.ignite.com/clients/typescript

## Networking Commands
Q: How do you launch a multi-node testnet with the Ignite Networking Commands?
A: You would be wise to follow this tutorial here:
[Ignite Network Tutorial](https://docs.ignite.com/network/introduction)

## Git Related Issues

Q: I am getting the error message "Git add tester: open /path/to/my/Library/Application Support/Code/1.83-main.sock: operation not supported on socket"
A: This seems related to the .git folder in your project directory. For this example, our project directory/chain name is "tester"

To fix it:

#cd into your project directory
cd tester
rm -rf .git
git init
sudo ignite scaffold chain tester

## Cosmos SDK

Q: How large are Comos SDK Transactions?
A: If you are referring to size in terms of data, one way to estimate it is to create the transaction then encode it and look at the files size. For example:

exampled tx example create-post foo bar --from alice --generate-only > tx.json

exampled tx encode tx.json > encoded

Then look at the properties of the encoded file this creates. This isn't an exact science, but one way of getting and rough estimate of the transaction size.

If you do not find the answer to your questions here, please reach out to us on discord. We would be happy to help!

Join us on Discord:
https://discord.com/invite/ignite

Official Ignite Docs:
https://docs.ignite.com/

Official Ignite Github:
https://github.com/ignite/cli

Follow us on Twitter:
https://twitter.com/ignite_com