> For the complete documentation index, see [llms.txt](https://docs.unich.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unich.com/unich-network/kyc-requirements/pending-fc-specific-cases.md).

# Pending FC — Specific Cases

FC generated through the following activity types remains pending until the relevant KYC conditions are met:<br>

1. &#x20;**Mining from a non-KYC Node.** FC mined by a Node whose owner has not completed KYC remains pending. \
   → Complete KYC to make your mined FC available.<br>
2. **Meets with non-KYC Nodes.** FC accumulated through Peer Meet Mining Rate with non-KYC Nodes remains pending. \
   → Complete Peer Meets with KYC-verified Nodes to ensure your FC available.<br>
3. **Meet with an Anchor Node.** FC accumulated through the Mining Rate received when meeting an Ambassador remains pending if either Node has not completed KYC.\
   → Complete Peer Meets with KYC-verified Ambassador to ensure your mined FC available.<br>
4. **Network Expansion — referred Nodes without KYC.** FC from Network Expansion activity linked to non-KYC referred Nodes remains pending. \
   → Encourage your referred Nodes to complete KYC.<br>
5. **Network Expansion — referred Nodes meeting non-KYC Nodes.** FC accumulated when a referred Node completes a Peer Meet with a non-KYC Node remains pending. \
   → Guide your referred Nodes to meet only with KYC-verified Nodes.<br>
6. **Trust Circle with non-KYC members.** Mining Rate generated through a Trust Circle that includes non-KYC members remain pending.\
   → All members of a Trust Circle should be KYC-verified.<br>
7. **Trust Circle members meeting non-KYC Nodes.** FC accumulated when a Trust Circle member completes a Peer Meet with a non-KYC Node remains pending.\
   → Remind members to complete Peer Meets with KYC-verified Nodes only.<br>
8. **Anchor Node activity involving non-KYC Nodes.** FC accumulated through the Anchor Node Badge remains pending if the Ambassador has not completed KYC.\
   → Complete KYC to make your FC available at TGE.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://docs.unich.com/unich-network/kyc-requirements/pending-fc-specific-cases.md?ask=<question>
```

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.