> For the complete documentation index, see [llms.txt](https://docs.simulacrum.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simulacrum.network/synthetic-blockchain/organization/effects.md).

# Effects

**Effects** are any side effects that need to be handled asynchronously. For example if a user provides a bounty for the execution of a specific action, the bounty will be placed into an Effect that is released as soon as someone executes the Effect and provides the required proof of execution necessary to release the funds. This can be something like a limit order, where an **Effect** is created with some expiry to buy an asset at a specific price, and the Effect is only finalized when the limit order is executed.

More to follow on Effects, but they greatly expand the usability of the protocol beyond a single chain.

```
struct Effect {
    bytes32 id;
    uint256 index;
    bytes32 targetChain;
    bytes32 ownerId;
    bytes32 descriptor; // describes the type of the effect
    bytes args;
    bytes bounty;
    EffectStatus status;
}

enum EffectStatus {
    PENDING,
    COMPLETED,
    CANCELLED
}
```


---

# 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.simulacrum.network/synthetic-blockchain/organization/effects.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.