# Add MsgExec to Allowed ICA Messages List

**URL:** https://forum.osmosis.zone/t/add-msgexec-to-allowed-ica-messages-list/3848
**Category:** Proposal Discussion
**Created:** [August 11, 2025, 12:29pm UTC](https://forum.osmosis.zone/t/add-msgexec-to-allowed-ica-messages-list/3848 "2025-08-11T12:29:38Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![danieljdd](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/danieljdd/32/2427_2.png) [@danieljdd](https://forum.osmosis.zone/u/danieljdd)
#### Post date: [August 11, 2025, 12:29pm UTC](https://forum.osmosis.zone/t/add-msgexec-to-allowed-ica-messages-list/3848/1 "2025-08-11T12:29:38Z")

</div>

# Add `/cosmos.authz.v1beta1.MsgExec` to the Allowed ICA Host Messages

## Summary

This proposal adds `/cosmos.authz.v1beta1.MsgExec` to the ICA host allowlist.  
Osmosis already supports `/cosmos.authz.v1beta1.MsgGrant` and `/cosmos.authz.v1beta1.MsgRevoke` — adding `MsgExec` completes the core Authz set.

## Background

The Interchain Accounts (ICA) module lets a controlled account on one chain perform transactions on another.  
In Osmosis today, ICA hosts can grant and revoke permissions, but they cannot **execute** via `MsgExec`. This is the missing link for many automation and delegation patterns.

We’re integrating [Intento](https://intento.zone/) with Osmosis to enable advanced interchain flows — e.g. DCA, token streaming, auto-compounding, and portfolio rebalancing. Intento executes these flows self-custodially via ICAs, without third-party smart contracts or custody.

### Why `MsgExec` Matters

- **Enables secure delegation inside ICA** — allowing a hosted ICA to run batched, permissioned actions on behalf of a user.

- **Improves efficiency** — one hosted ICA can serve many users, reducing fee overhead and infra complexity.

- **Preserves self-custody** — flows enforce strict granter verification: the `MsgExec` signer must be the flow owner.

This doesn’t introduce new powers for ICAs beyond what regular accounts already have — it simply allows ICAs to use an existing, widely-tested message type.  
We’ve already validated `MsgExec` in Osmosis testnet for:

- **tokenstream.fun** streaming flows

- **StreamSwap** contract calls

## Current Supported Authz Messages in ICA

- `/cosmos.authz.v1beta1.MsgGrant`

- `/cosmos.authz.v1beta1.MsgRevoke`  
_(plus others like MsgSend, MsgTransfer — see [Osmosis ICA host params](https://lcd.osmosis.zone/ibc/apps/interchain_accounts/host/v1/params))_

`MsgExec` lets an authorized account execute transactions granted via Authz.

## Proposal Details

**Add to ICA Allowlist:**

- **Message** : `/cosmos.authz.v1beta1.MsgExec`

- **Function** : Executes any messages previously authorized by the granter.

### Benefits

1. **Parity with other chains** – Neutron, Cosmos Hub, and Injective mainnets already allow this.

2. **Completes Authz support** – grant, revoke, and execute.

3. **Enables advanced automation** – critical for complex cross-chain integrations.

### Risks & Mitigation

- **Complexity** – More allowed types can increase risk, but:

## Implementation Plan

1. **Testnet** – ✅ [Proposal #262 on Osmosis testnet](https://www.mintscan.io/osmosis-testnet/proposals/262) submitted and validated.

2. **Mainnet** – Governance proposal for deployment.

## Conclusion

Adding `MsgExec` to the ICA host allowlist is a high-utility improvement that aligns Osmosis with other IBC chains and unlocks new automation capabilities for integrators.

**References:**

- [Adding authz messages into allowed ICA messages list](https://forum.osmosis.zone/t/adding-authz-messages-into-allowed-ica-messages-list/2573)

- [Adding MsgCreateBalancerPool into approved ICA messages list](https://forum.osmosis.zone/t/adding-msgcreatebalancerpool-into-approved-ica-messages-list/163)

- [Adding Superfluid messages into allowed ICA messages list](https://forum.osmosis.zone/t/adding-superfluid-messages-into-allowed-ica-messages-list/365)

- [Adding Poolmanager messages into allowed ICA messages list](https://forum.osmosis.zone/t/adding-poolmanager-messages-into-allowed-ica-messages-list/402)

---

<div class="post-metadata">

### Author: ![ertemann](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/ertemann/32/793_2.png) [@ertemann](https://forum.osmosis.zone/u/ertemann)
#### Post date: [August 15, 2025, 11:46am UTC](https://forum.osmosis.zone/t/add-msgexec-to-allowed-ica-messages-list/3848/2 "2025-08-15T11:46:16Z")

</div>

Looks good, will vote yes barring any technical concerns from the main Osmosis code contributors. More usecases is better!

---

<div class="post-metadata">

### Author: ![Atlas-Staking](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/atlas-staking/32/2755_2.png) [@Atlas-Staking](https://forum.osmosis.zone/u/Atlas-Staking)
#### Post date: [August 15, 2025, 4:44pm UTC](https://forum.osmosis.zone/t/add-msgexec-to-allowed-ica-messages-list/3848/3 "2025-08-15T16:44:44Z")

</div>

We run validators for both Osmosis and Intento. We will be voting yes and encourage others to do the same.
