## Problem Statement

- Parahain to Parachain communication currently relies on the relay chain for message passing. i.e The relay chain currently forms a bottleneck in parachain messaging. This is highly inefficient and relieving the relay chain of this burden will not only allow for higher Parachain messaging throughput, but also parachain better scalability with async backing on the horizon.

- HRMP (The current transport protocol), necessitates the intervention of governance to establish communication channels between related chains. While this ensures a certain level of security and verification, it also adds a layer of complexity and time consumption. We believe parachain interoperability should be the juridisction of the governance of the parachains involved, not the relay chain.

- For chains to effectively interoperate with each other they must be able to read the state of that counterparty chain. This approach to interoperability are currently open & unasnwered questions today in the ecosystem: [Support custom storage proof from the relay-chain](https://github.com/paritytech/cumulus/issues/320), [META: Parachains Reading Storage of One Another](https://github.com/paritytech/polkadot/issues/5087)

## Solution

ISMP (Interoperable State Machine Protocol) is designed to improve and secure cross-chain communication and operations by facilitating "GET-like" and "POST-like" requests between all substrate based chains under the security of the Polkadot Relay chain. By leveraging state proofs, it relieves the relay chain of the burden of message passing, contributing significantly to the scalability of parachains. It’s GET-like request protocol facilitates for the first time in the ecosystem [state reads of sibling parachains](https://github.com/paritytech/polkadot/issues/5087), [as well as the relay chain](https://github.com/paritytech/cumulus/issues/320), unlocking [new](https://twitter.com/ingoruebe/status/1684218666286473216?s=20) [kinds](https://twitter.com/XCAstronaut/status/1684275154334126080?s=20) of [applications](https://twitter.com/lolmcshizz/status/1686363770740752384?s=20).

Inspired by HTTP, aiming to become a similar standard for interoperability in the multi-chain environment. It's designed as a substrate-based pallet to ease integration with parachains and standalone chains, Following a [successful w3f grant delivery](https://twitter.com/PolytopeLabs/status/1686344692017852416) for the preliminary functionally which enables Parachain interoperability.

You can find a link to ISMP repository here: https://github.com/polytope-labs/ismp-substrate.

Relevant discussion links:

- [Polkadot Forum discussion](https://forum.polkadot.network/t/state-proof-based-parachain-parachain-messaging)
- [Polkadot decoded devrel stream](https://youtu.be/LFt_gwV6hDM?t=5331)
- [The Kusamarian Interview](https://twitter.com/TheKusamarian/status/1685721362768269313?s=20)
- [Polkadot interoperability keynote at ParisDotComm](https://youtu.be/KFebUUPbEPw?t=6872)


## Ecosystem Use Cases

With the ability to read each other's state comes a new wave of applications unlocked by the ISMP stack

- Parachain messaging independent of cumbersome HRMP channel proposals.
- Unopinionated messaging format for parachains.
- Liquid Staking derivatives based on relay chain stake (Acala, Bifrost)
- [Multi asset transaction fee collection for Parachains using 30 day Twap prices from Hydradx.](https://twitter.com/lolmcshizz/status/1686363770740752384?s=20)
- [Request user’s Klit DID on the Klit Parachain from any chain.](https://twitter.com/ingoruebe/status/1684218666286473216?s=20)
- and many more

## The proposal

We have fully extended ISMP to facilitate messaging between; Standalone(solo) chains, Parachains & Relay chains. It is fully EVM compatible, enabling cross chain solidity smart contract communication among other ISMP-enabled EVM compatible (substrate based) chains. This messaging is powered by an offchain relayer implementation, engineered to be chain-agnostic and extensible to multiple ecosystems. 


This proposal is for a retroactive payment by Polkadot Treasury to cover development costs incurred. This funding will allow us continue further research and development for our next major milestones, a [zk bridge to ethereum](https://research.polytope.technology/zkcasper) that turns polkadot into a [message passing platform for it's rollups](https://twitter.com/rphmeier/status/1686164113242697728?s=20).

You can find the details of the proposal [here](https://docs.google.com/document/d/1Sv5hYfzW8KIHuqTVLXmQDXrQzPioCml7Yy7g9S-_O84/edit?usp=sharing).

We look forward to your support.

Thank you for reading!

## Problem Statement

- Parahain to Parachain communication currently relies on the relay chain for message passing. i.e The relay chain currently forms a bottleneck in parachain messaging. This is highly inefficient and relieving the relay chain of this burden will not only allow for higher Parachain messaging throughput, but also parachain better scalability with async backing on the horizon.

- HRMP (The current transport protocol), necessitates the intervention of governance to establish communication channels between related chains. While this ensures a certain level of security and verification, it also adds a layer of complexity and time consumption. We believe parachain interoperability should be the juridisction of the governance of the parachains involved, not the relay chain.

- For chains to effectively interoperate with each other they must be able to read the state of that counterparty chain. This approach to interoperability are currently open & unasnwered questions today in the ecosystem: [Support custom storage proof from the relay-chain](https://github.com/paritytech/cumulus/issues/320), [META: Parachains Reading Storage of One Another](https://github.com/paritytech/polkadot/issues/5087)

## Solution

ISMP (Interoperable State Machine Protocol) is designed to improve and secure cross-chain communication and operations by facilitating "GET-like" and "POST-like" requests between all substrate based chains under the security of the Polkadot Relay chain. By leveraging state proofs, it relieves the relay chain of the burden of message passing, contributing significantly to the scalability of parachains. It’s GET-like request protocol facilitates for the first time in the ecosystem [state reads of sibling parachains](https://github.com/paritytech/polkadot/issues/5087), [as well as the relay chain](https://github.com/paritytech/cumulus/issues/320), unlocking [new](https://twitter.com/ingoruebe/status/1684218666286473216?s=20) [kinds](https://twitter.com/XCAstronaut/status/1684275154334126080?s=20) of [applications](https://twitter.com/lolmcshizz/status/1686363770740752384?s=20).

Inspired by HTTP, aiming to become a similar standard for interoperability in the multi-chain environment. It's designed as a substrate-based pallet to ease integration with parachains and standalone chains, Following a [successful w3f grant delivery](https://twitter.com/PolytopeLabs/status/1686344692017852416) for the preliminary functionally which enables Parachain interoperability.

You can find a link to ISMP repository here: https://github.com/polytope-labs/ismp-substrate.

Relevant discussion links:

- [Polkadot Forum discussion](https://forum.polkadot.network/t/state-proof-based-parachain-parachain-messaging)
- [Polkadot decoded devrel stream](https://youtu.be/LFt_gwV6hDM?t=5331)
- [The Kusamarian Interview](https://twitter.com/TheKusamarian/status/1685721362768269313?s=20)
- [Polkadot interoperability keynote at ParisDotComm](https://youtu.be/KFebUUPbEPw?t=6872)


## Ecosystem Use Cases

With the ability to read each other's state comes a new wave of applications unlocked by the ISMP stack

- Parachain messaging independent of cumbersome HRMP channel proposals.
- Unopinionated messaging format for parachains.
- Liquid Staking derivatives based on relay chain stake (Acala, Bifrost)
- [Multi asset transaction fee collection for Parachains using 30 day Twap prices from Hydradx.](https://twitter.com/lolmcshizz/status/1686363770740752384?s=20)
- [Request user’s Klit DID on the Klit Parachain from any chain.](https://twitter.com/ingoruebe/status/1684218666286473216?s=20)
- and many more

## The proposal

We have fully extended ISMP to facilitate messaging between; Standalone(solo) chains, Parachains & Relay chains. It is fully EVM compatible, enabling cross chain solidity smart contract communication among other ISMP-enabled EVM compatible (substrate based) chains. This messaging is powered by an offchain relayer implementation, engineered to be chain-agnostic and extensible to multiple ecosystems. 


This proposal is for a retroactive payment by Polkadot Treasury to cover development costs incurred. This funding will allow us continue further research and development for our next major milestones, a [zk bridge to ethereum](https://research.polytope.technology/zkcasper) serving as a [message passing platform for it's rollups](https://twitter.com/rphmeier/status/1686164113242697728?s=20).

You can find the details of the proposal [here](https://docs.google.com/document/d/1Sv5hYfzW8KIHuqTVLXmQDXrQzPioCml7Yy7g9S-_O84/edit?usp=sharing).

We look forward to your support.

Thank you for reading!

[Retroactive] Polytope Labs: ISMP Research & Development

## Problem Statement

- Parahain to Parachain communication currently relies on the relay chain for message passing. i.e The relay chain currently forms a bottleneck in parachain messaging. This is highly inefficient and relieving the relay chain of this burden will not only allow for higher Parachain messaging throughput, but also parachain better scalability with async backing on the horizon.

- HRMP (The current transport protocol), necessitates the intervention of governance to establish communication channels between related chains. While this ensures a certain level of security and verification, it also adds a layer of complexity and time consumption. We believe parachain interoperability should be the juridisction of the governance of the parachains involved, not the relay chain.

- For chains to effectively interoperate with each other they must be able to read the state of that counterparty chain. This approach to interoperability are currently open & unasnwered questions today in the ecosystem: [Support custom storage proof from the relay-chain](https://github.com/paritytech/cumulus/issues/320), [META: Parachains Reading Storage of One Another](https://github.com/paritytech/polkadot/issues/5087)

## Solution

ISMP (Interoperable State Machine Protocol) is designed to improve and secure cross-chain communication and operations by facilitating "GET-like" and "POST-like" requests between all substrate based chains under the security of the Polkadot Relay chain. By leveraging state proofs, it relieves the relay chain of the burden of message passing, contributing significantly to the scalability of parachains. It’s GET-like request protocol facilitates for the first time in the ecosystem [state reads of sibling parachains](https://github.com/paritytech/polkadot/issues/5087), [as well as the relay chain](https://github.com/paritytech/cumulus/issues/320), unlocking [new](https://twitter.com/ingoruebe/status/1684218666286473216?s=20) [kinds](https://twitter.com/XCAstronaut/status/1684275154334126080?s=20) of [applications](https://twitter.com/lolmcshizz/status/1686363770740752384?s=20).

Inspired by HTTP, aiming to become a similar standard for interoperability in the multi-chain environment. It's designed as a substrate-based pallet to ease integration with parachains and standalone chains, Following a [successful w3f grant delivery](https://twitter.com/PolytopeLabs/status/1686344692017852416) for the preliminary functionally which enables Parachain interoperability.

You can find a link to ISMP repository here: https://github.com/polytope-labs/ismp-substrate.

Relevant discussion links:

- [Polkadot Forum discussion](https://forum.polkadot.network/t/state-proof-based-parachain-parachain-messaging)
- [Polkadot decoded devrel stream](https://youtu.be/LFt_gwV6hDM?t=5331)
- [The Kusamarian Interview](https://twitter.com/TheKusamarian/status/1685721362768269313?s=20)
- [Polkadot interoperability keynote at ParisDotComm](https://youtu.be/KFebUUPbEPw?t=6872)


## Ecosystem Use Cases

With the ability to read each other's state comes a new wave of applications unlocked by the ISMP stack

- Parachain messaging independent of cumbersome HRMP channel proposals.
- Unopinionated messaging format for parachains.
- Liquid Staking derivatives based on relay chain stake (Acala, Bifrost)
- [Multi asset transaction fee collection for Parachains using 30 day Twap prices from Hydradx.](https://twitter.com/lolmcshizz/status/1686363770740752384?s=20)
- [Request user’s Klit DID on the Klit Parachain from any chain.](https://twitter.com/ingoruebe/status/1684218666286473216?s=20)
- and many more

## The proposal

We have fully extended ISMP to facilitate messaging between; standalone(solo) chains, Parachains & relay chains. It is EVM compatible, enabling cross chain solidity smart contract communication among EVM compatible substrate based chains. This messaging is powered by an offchain relayer implementation, designed to be chain agnostic and extensible to multiple ecosystems. 


This proposal is for a retroactive payment by Polkadot Treasury to cover development costs incurred. This funding will allow us continue further research and development for our next major milestones, a [zk bridge to ethereum](https://research.polytope.technology/zkcasper) serving as a [message passing platform for it's rollups](https://twitter.com/rphmeier/status/1686164113242697728?s=20).

You can find the details of the proposal [here](https://docs.google.com/document/d/1Sv5hYfzW8KIHuqTVLXmQDXrQzPioCml7Yy7g9S-_O84/edit?usp=sharing).

We look forward to your support.

Thank you for reading!

## Problem Statement

- Parahain to Parachain communication currently relies on the relay chain for message passing. i.e The relay chain currently forms a bottleneck in parachain messaging. This is highly inefficient and relieving the relay chain of this burden will not only allow for higher Parachain messaging throughput, but also parachain better scalability with async backing on the horizon.

- HRMP (The current transport protocol), necessitates the intervention of governance to establish communication channels between related chains. While this ensures a certain level of security and verification, it also adds a layer of complexity and time consumption. We believe parachain interoperability should be the juridisction of the governance of the parachains involved, not the relay chain.

- For chains to effectively interoperate with each other they must be able to read the state of that counterparty chain. This approach to interoperability are currently open & unasnwered questions today in the ecosystem: [Support custom storage proof from the relay-chain](https://github.com/paritytech/cumulus/issues/320), [META: Parachains Reading Storage of One Another](https://github.com/paritytech/polkadot/issues/5087)

## Solution

ISMP (Interoperable State Machine Protocol) is designed to improve and secure cross-chain communication and operations by facilitating "GET-like" and "POST-like" requests between all substrate based chains under the security of the Polkadot Relay chain. By leveraging state proofs, it relieves the relay chain of the burden of message passing, contributing significantly to the scalability of parachains. It’s GET-like request protocol facilitates for the first time in the ecosystem [state reads of sibling parachains](https://github.com/paritytech/polkadot/issues/5087), [as well as the relay chain](https://github.com/paritytech/cumulus/issues/320), unlocking [new](https://twitter.com/ingoruebe/status/1684218666286473216?s=20) [kinds](https://twitter.com/XCAstronaut/status/1684275154334126080?s=20) of [applications](https://twitter.com/lolmcshizz/status/1686363770740752384?s=20).

Inspired by HTTP, aiming to become a similar standard for interoperability in the multi-chain environment. It's designed as a substrate-based pallet to ease integration with parachains and standalone chains, Following a [successful w3f grant delivery](https://twitter.com/PolytopeLabs/status/1686344692017852416) for the preliminary functionally which enables Parachain interoperability.

You can find a link to ISMP repository here: https://github.com/polytope-labs/ismp-substrate.

Relevant discussion links:

- [Polkadot Forum discussion](https://forum.polkadot.network/t/state-proof-based-parachain-parachain-messaging)
- [Polkadot decoded devrel stream](https://youtu.be/LFt_gwV6hDM?t=5331)
- [The Kusamarian Interview](https://twitter.com/TheKusamarian/status/1685721362768269313?s=20)
- [Polkadot interoperability keynote at ParisDotComm](https://youtu.be/KFebUUPbEPw?t=6872)


## Ecosystem Use Cases

With the ability to read each other's state comes a new wave of applications unlocked by the ISMP stack

- Parachain messaging independent of cumbersome HRMP channel proposals.
- Unopinionated messaging format for parachains.
- Liquid Staking derivatives based on relay chain stake (Acala, Bifrost)
- [Multi asset transaction fee collection for Parachains using 30 day Twap prices from Hydradx.](https://twitter.com/lolmcshizz/status/1686363770740752384?s=20)
- [Request user’s Klit DID on the Klit Parachain from any chain.](https://twitter.com/ingoruebe/status/1684218666286473216?s=20)
- and many more


We have fully extended ISMP to facilitate messaging between; standalone(solo) chains, Parachains & relay chains. It is EVM compatible, enabling cross chain solidity smart contract communication among EVM compatible substrate based chains.

This submission is to propose a retroactive payment by Polkadot Treasury to cover development costs incurred.

You can find the details of the proposal [here](https://docs.google.com/document/d/1Sv5hYfzW8KIHuqTVLXmQDXrQzPioCml7Yy7g9S-_O84/edit?usp=sharing).

We look forward to your support.

Thank you for reading!

## Problem Statement

- Parahain to Parachain communication currently relies on the relay chain for message passing. i.e The relay chain currently forms a bottleneck in parachain messaging. This is highly inefficient and relieving the relay chain of this burden will not only allow for higher Parachain messaging throughput, but also parachain better scalability with async backing on the horizon.

- HRMP (The current transport protocol), necessitates the intervention of governance to establish communication channels between related chains. While this ensures a certain level of security and verification, it also adds a layer of complexity and time consumption. We believe parachain interoperability should be the juridisction of the governance of the parachains involved, not the relay chain.

- For chains to effectively interoperate with each other they must be able to read the state of that counterparty chain. This approach to interoperability are currently open & unasnwered questions today in the ecosystem: [Support custom storage proof from the relay-chain](https://github.com/paritytech/cumulus/issues/320), [META: Parachains Reading Storage of One Another](https://github.com/paritytech/polkadot/issues/5087)

## Solution

ISMP (Interoperable State Machine Protocol) is designed to improve and secure cross-chain communication and operations by facilitating "GET-like" and "POST-like" requests between all substrate based chains under the security of the Polkadot Relay chain. By leveraging state proofs, it relieves the relay chain of the burden of message passing, contributing significantly to the scalability of parachains. It’s GET-like request protocol facilitates for the first time in the ecosystem [state reads of sibling parachains](https://github.com/paritytech/polkadot/issues/5087), [as well as the relay chain](https://github.com/paritytech/cumulus/issues/320), unlocking [new](https://twitter.com/ingoruebe/status/1684218666286473216?s=20) [kinds](https://twitter.com/XCAstronaut/status/1684275154334126080?s=20) of [applications](https://twitter.com/lolmcshizz/status/1686363770740752384?s=20).

Inspired by HTTP, aiming to become a similar standard for interoperability in the multi-chain environment. It's designed as a substrate-based pallet to ease integration with parachains and standalone chains, Following a [successful w3f grant delivery](https://twitter.com/PolytopeLabs/status/1686344692017852416) for the preliminary functionally which enables Parachain interoperability.

You can find a link to ISMP repository here: https://github.com/polytope-labs/ismp-substrate.

Relevant discussion links:

- [Polkadot Forum discussion](https://forum.polkadot.network/t/state-proof-based-parachain-parachain-messaging)
- [Polkadot decoded devrel stream](https://youtu.be/LFt_gwV6hDM?t=5331)
- [The Kusamarian Interview](https://twitter.com/TheKusamarian/status/1685721362768269313?s=20)
- [Polkadot interoperability keynote at ParisDotComm](https://youtu.be/KFebUUPbEPw)


## Ecosystem Use Cases

With the ability to read each other's state comes a new wave of applications unlocked by the ISMP stack

- Parachain messaging independent of cumbersome HRMP channel proposals.
- Unopinionated messaging format for parachains.
- Liquid Staking derivatives based on relay chain stake (Acala, Bifrost)
- [Multi asset transaction fee collection for Parachains using 30 day Twap prices from Hydradx.](https://twitter.com/lolmcshizz/status/1686363770740752384?s=20)
- [Request user’s Klit DID on the Klit Parachain from any chain.](https://twitter.com/ingoruebe/status/1684218666286473216?s=20)
- and many more


We have fully extended ISMP to facilitate messaging between; standalone(solo) chains, Parachains & relay chains. It is EVM compatible, enabling cross chain solidity smart contract communication among EVM compatible substrate based chains.

This submission is to propose a retroactive payment by Polkadot Treasury to cover development costs incurred.

You can find the details of the proposal [here](https://docs.google.com/document/d/1Sv5hYfzW8KIHuqTVLXmQDXrQzPioCml7Yy7g9S-_O84/edit?usp=sharing).

We look forward to your support.

Thank you for reading!

Propose and approve a spend of treasury funds.

- `origin`: Must be `SpendOrigin` with the `Success` value being at least `amount`.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The destination account for the transfer.

NOTE: For record-keeping purposes, the proposer is deemed to be equivalent to the
beneficiary.

- Parachain communication currently relies on the relay chain, which is inefficient.
- ISMP is a protocol designed to improve cross-chain communication and scalability.
- ISMP allows for state reads of sibling parachains and the relay chain.
- ISMP enables new applications and use cases in the ecosystem.
- The proposal is for funding to continue development of ISMP and other milestones.

#102 [Retroactive] Polytope Labs: ISMP Research & Development

No Active Proposals