> For the complete documentation index, see [llms.txt](https://docs.metalex.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metalex.tech/protocol-how-to-guides/gate-with-conditions.md).

# Gate state transitions with conditions

A **condition** is a contract implementing `ICondition`. Conditions gate state transitions on arbitrary onchain checks.

## The interface

```solidity
interface ICondition {
    function checkCondition(
        address _contract,
        bytes4 _functionSignature,
        bytes memory data
    ) external view returns (bool);
}
```

See [Conditions](/protocol-reference/conditions.md) for the built-in conditions (`lexchexCondition`, `NonUSNationalityCondition`, `IssuerApprovalRecertificationCondition`, `OrCondition`), plus the secondary-trading condition family in [`src/libs/conditions/secondary/`](https://github.com/MetaLex-Tech/cybercorps-contracts/tree/develop/src/libs/conditions/secondary/README.md) (eligibility, holding period, holder cap, Reg S distribution compliance, Rule 144 / Section 4(a)(7) disclosure, CFIUS, kill switch, and more).

## Where conditions are attached

Conditions are passed as `address[]` (or `ICondition[]`) into the call that creates the gated thing:

**Scripification / de-scripification** — set when the scrip is deployed:

```solidity
IIssuanceManager(issuanceManager).deployCyberScrip(
    certAddress,
    typeRestrictionHooks,
    certToScripConditions,   // ICondition[] gating scripifyCert
    scripToCertConditions,   // ICondition[] gating convertScripToCert
    /* ...remaining args... */
);
```

**A fundraising round** — in the `Round` built via `RoundLib.setAgreement` (`roundConditions`), and per-EOI in `submitEOI(..., conditions, ...)`.

**A deal** — the `conditions` argument of `DealManager.proposeDeal`.

**Secondary trades** — configured on the DealManager as standing lists rather than per-call arguments, and evaluated at post, accept, *and* finalize:

```solidity
// exemption-pathway conditions (also enables/disables the pathway)
dealManager.setPathwayThresholdConditions(pathway, conditions, enabled);
// fund-specific conditions applying to every offer
dealManager.setSpvThresholdConditions(conditions);
// conditions evaluated only at finalization
dealManager.setClosingConditions(conditions);
```

See [Run a secondary trade](/protocol-how-to-guides/run-a-secondary-trade.md).

## Writing a custom condition

Implement `ICondition`. Because `checkCondition` receives the calling contract, the selector, and arbitrary `data`, you can encode any onchain check:

```solidity
contract MinBalanceCondition is ICondition {
    IERC20  immutable token;
    uint256 immutable minimum;
    constructor(IERC20 t, uint256 m) { token = t; minimum = m; }

    function checkCondition(address, bytes4, bytes memory data)
        external view returns (bool)
    {
        address subject = abi.decode(data, (address));
        return token.balanceOf(subject) >= minimum;
    }
}
```

Deploy it and pass its address wherever the protocol accepts a condition list.

## Related

* [Conditions reference](/protocol-reference/conditions.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.metalex.tech/protocol-how-to-guides/gate-with-conditions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.