# FAQ ### How do I know my node is producing blocks? After successful authentication you will see "Bioauth flow - authentication complete" and "We've obtained an auth ticket auth\_ticket" in the log few seconds after biometric authentication. \ \ You will also you see "Starting consensus session on top of parent 0x..." in the log. It happens once a 10-15 minutes. ### I forgot to write down my mnemonic, where can I find it? You can find it here if you did not delete the workspace - "$HOME/.local/share/humanode-peer/chains/humanode\_testnet2/keystore". ### Why do I get "Verification failed for block xxx" ? It's a part of consensus. All blocks should be verified. You see this if somebody tries to propose an invalid block. It's not your fault. ### Do mnemonic and address remain the same? Yes, they remain the same. ### Can I run 2 nodes with same IP? Yes, you can share an IP address as long as the peering ports are different. ### If we have so many human nodes, how can this blockchain be fast like BSC/AVAX/SOL? We haven't implemented the final consensus yet, the main slowdown will likely be from it. We will launch another testnet when we're ready with this. Everything else does not contribute to the "blockchain speed" in the common sense of this term. However, we are EVM compatible chain, so we will likely be slower than DAG-based UTXO-only chains. ### Is it possible to run a node without downloading Humanode app? We currently distribute the node only via the desktop app. Before the main net we'll have that option. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://gitbook.humanode.io/docs/help/faq.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.