# Frequently Asked Questions: Ignite Builders

**Purpose:**

To create a tracking document of the frequently asked questions we receive from new builders and to use this as a place to consolidate answers and identify re-occuring questions and troubleshooting.

**Questions**

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.

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`

Q: " ignite serve chain " will generate all the binary
A: Yes, check out Cosmos Visor for upgrading binaries.

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

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

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 yourusername folder name`

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

For more details, check out this detailed walkthrough to create front end:
https://hackmd.io/@tendermint-devx/rk5C3KCra

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

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.

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 endoded file this creates. This isn't an exact science, but one way of getting and rough estimate of the transaction size.

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 sepecific to your chain once it has been deployed will be done using the chain's binary.