> For the complete documentation index, see [llms.txt](https://shepherd-1.gitbook.io/shepherd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shepherd-1.gitbook.io/shepherd/additional-info/faqs.md).

# FAQs

<details>

<summary><strong>Do I need compiled artifacts in my zip file?</strong></summary>

No, Shepherd can work from source files alone. However, including compiled artifacts (ABI, bytecode) can speed up validation and improve accuracy.

</details>

<details>

<summary><strong>Can I test cross-contract scenarios?</strong></summary>

Yes! When prompted "Add another contract chunk?", enter **Y** and include all related contracts in your hypothesis. Shepherd will analyze interactions across multiple contracts.

</details>

<details>

<summary><strong>What if my tunnel requires authentication?</strong></summary>

Use a tunnel service that supports authentication tokens, or set up a secure proxy that handles auth and forwards to your local environment. Include auth details in your tunnel URL if supported by your provider.

</details>

<details>

<summary><strong>How detailed should my hypothesis be?</strong></summary>

More detail = better results. Include specific function names, attacker capabilities, initial conditions, and expected outcomes. Aim for 3-5 sentences minimum.

</details>

<details>

<summary><strong>Can I save my session and come back later?</strong></summary>

Currently, sessions are active only while running. Export your results before ending a session. You can restart with the same zip file and hypothesis later.

</details>

<details>

<summary><strong>What programming languages does Shepherd support?</strong></summary>

Shepherd is optimized for Solidity smart contracts. Support for other blockchain languages may vary.

</details>

<details>

<summary><strong>How long does a typical analysis take?</strong></summary>

Simple hypotheses: 1-5 minutes. Complex cross-contract scenarios: 5-15 minutes. Time varies based on codebase size and hypothesis complexity.

</details>

<details>

<summary><strong>Can I run multiple sessions simultaneously?</strong></summary>

Check your Shepherd plan limits. Some configurations allow parallel sessions.

</details>

<details>

<summary><strong>What should I do if I find a critical vulnerability?</strong></summary>

Export the full report immediately, notify your security team, and avoid deploying affected contracts until patched. Consider running additional focused tests on the vulnerable area.

</details>

<details>

<summary><strong>How do I interpret confidence levels?</strong></summary>

High confidence means Shepherd successfully executed the exploit. Medium means likely exploitable but needs manual verification. Low means potential issue requiring further investigation.

</details>

<details>

<summary>Why did my run end abruptly before it even started?</summary>

If your run ended before it even started, it just means we ran out of tokens:cry:. Please be patient and fill your email into the report box. If not, please contact us ASAP.<br>

</details>

### Got More Questions?:

**Get in touch with us at:**

<i class="fa-telegram">:telegram:</i> [Telegram](https://t.me/pbooony)