Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLASK] Remove endowment:long-running from documentation #919

Merged
merged 1 commit into from
Sep 19, 2023
Merged

[FLASK] Remove endowment:long-running from documentation #919

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions snaps/concepts/lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,6 @@ AWS lambda functions, snaps are designed to wake up in response to messages/even
when idle.
Snaps have an ephemeral lifecycle: they're here one moment, gone the next.
Also, if MetaMask detects that a snap becomes unresponsive, it shuts the snap down.
This doesn't mean that you can't create long-running snaps, but it does mean that your snaps must
handle being shut down, especially when they're not within the JSON-RPC request/response cycle.

A snap is considered unresponsive if:

Expand Down
18 changes: 0 additions & 18 deletions snaps/reference/permissions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,24 +87,6 @@ You can also use it to connect to Ethereum accounts with `eth_requestAccounts` a
those connected accounts.
:::

### endowment:long-running

:::caution
`endowment:long-running` is deprecated.
:::

A snap that is computationally heavy and can't finish execution within the
[snap lifecycle requirements](../concepts/lifecycle.md) must request the `endowment:long-running` permission.
This permission allows the snap to run indefinitely while processing RPC requests.

Specify this permission in the manifest file as follows:

```json
"initialPermissions": {
"endowment:long-running": {}
},
```

### endowment:network-access

To access the internet, a snap must request the `endowment:network-access` permission.
Expand Down
Loading