Saxemberg has voted NAY on the Kusama referendum 606. Sol-XCM | A typed interface for interoperability from Solidity. All core improvements to the sdk, sdk tooling and non-Kusama specific referenda with significant amounts should be submitted to Polkadot's Opengov.

[@SAXEMBERG/Governance](HcEbeTviCK33EddVN3mfJ6WymWLyKfFuekjhjn5PFirjJ5F-kusama) 

Other observations include the fact that other bridging applications seem better suited for end users and applications like ISMP / Hyperbridge, Snowbridge which are easier to interact and able to carry messages to/from Assethub for applications without the need to interact with XCM directly. For now only parachains and core services use XCM, if there were demand for XCM - EVM for end users and applications, signaling from these parachains/future JAM projects becomes necessary. Tooling without demand has proven to be one of the least impactful ways to give grants, at least some initial demand from current and proposed projects is needed. A Kusama step is no longer needed as it no longer fulfills the role of alpha chain for any project so a direct deployment to Polkadot is recommended without this intermediate step, specially when longer and continued funding is required (potentially after 2-3 months). Polkadot referenda also enjoy of a longer decision period which makes it better suited for amounts such as these. In case it is a Kusama-only application, a discouragement from this approach is in order as Kusama currently lacks a role outside of Polkadot-sdk tests from Parity and no other team is using it or planning to support it in the future in a significant way. At 168k p/a, this amount makes it better suited for Polkadot Opengov as large expenditures on Kusama should be discouraged for now.  Due to the faster approval window that Kusama has, we prefer the resubmission of a referendum if needed.

Disclaimer Kusama:
Our Kusama modeling is highly experimental and includes more than 2000 non-linguistic parameters so these are only verbal observations also included in the vote calculations and they are not an extensive review of the full rationale behind this vote. 

I agree that interoperability with XCM is a key differentiator that needs to be exploited, for Solidity developers a tool like this one will be a must have.  
It would be nice to see this tool evolving into some kind of extensible "Paraspell for Solidity" and provide higher level abstractions to make interaction with foreign chains a breeze, e.g. a solidity dev shouldn't need a master to do a multi-hop XCM that takes some funds from KAH to a Polkadot parachain like Hydration swap and bring back to KAH.

The Nexus voted NAY.

While Sol-XCM presents an interesting approach for interoperability, the proposal lacks key safeguards, as no external audit, no maintenance plan, and limited current demand on Kusama.
We consider this funding premature and better suited for a future Polkadot submission.

We support the vision, but not this version

Le Nexus remains open to any questions or discussions on OpenGov proposals. Join our DV Office English channel on [Discord](https://discord.gg/XhbageNP4n)

Dear Proposer,

Thank you for your proposal. Our **first** vote on this proposal is **NAY**. Below is the evaluation of our [voting policy v0.3](https://docs.permanence.io/voting_policy/voting_policy_v0.3.html) on this referendum:

```
MEDIUM SPENDER
--------------
8 available members
🟢 0 • 🔴 2 • ⚪️ 2
✓ ≥50.0% required participation met
✘ Ayes ≤50.0% of all votes
▶ Aye/abstain conditions not met
🔴 NAY
```

Below is a summary of our members' comments:

> The proposal aimed to introduce a tool that generated a typed interface for Solidity contracts to enhance interoperability on Kusama and later Polkadot. Voters recognized that the project could potentially ease inter-contract communication by offering a SCALE encoding library generator. However, concerns were raised regarding the proposed budget, with several viewpoints suggesting that the $42K request was too high, preferring a more cost-efficient approach. Some participants expressed uncertainty about the project's full scope and questioned the actual labor required, while also noting that the concept deserved exploration despite its financial ask. Consequently, the overall stance favored a NAY vote based primarily on pricing concerns and scope ambiguity.

The full discussion can be found in our [internal voting](https://voting.opensquare.io/space/permanence/proposal/QmZLVrZHQTUK3SjvWjAR5cNap7o1XLwkcwELa8Ee8jqgK7).

Please feel free to contact us through the links below for further discussion.

Kind regards, Permanence DAO Decentralized Voices Cohort V Delegate 📅 [Book Office Hours](https://cal.com/permanencedao/office-hours) 💬 [Public Telegram](https://t.me/permanencedao) 🌐️ [Web](https://permanence.io) 🐦 [Twitter](https://twitter.com/permanencedao) 🗳️ [Delegate](https://kusama.subsquare.io/user/EicAs5s99x17qZcQzJMiBCfada9rGyEC6njfiBX3j2EPr9W/votes)

Dear Proposer,

Thank you for your proposal. Our **second** vote on this proposal is **ABSTAIN**. Below is the evaluation of our [voting policy v0.3](https://docs.permanence.io/voting_policy/voting_policy_v0.3.html) on this referendum:

```
MEDIUM SPENDER
--------------
8 available members
🟢 0 • 🔴 2 • ⚪️ 3
✓ ≥50.0% required participation met
▶ Majority of all votes is abstain
⚪ ABSTAIN
```

Below is a summary of our members' comments:

> Members expressed a range of concerns and support for a Solidity interface generator tool designed for interoperable contracts on the Kusama and Polkadot Hubs. Some highlighted its potential to streamline communication between Solidity contracts and parachains, while questioning whether deploying such a tool on Polkadot might be more suitable. Several members voiced reservations about the proposal’s cost, considering the $42K ask excessive and suggesting a lower budget, while others pointed out uncertainties about scope, actual work hours, and ecosystem validation. Overall, the discussions led members to decide against a definitive positive vote, resulting in an abstention following the prescribed policy.

The full discussion can be found in our [internal voting](https://voting.opensquare.io/space/permanence/proposal/QmZLVrZHQTUK3SjvWjAR5cNap7o1XLwkcwELa8Ee8jqgK7).

Please feel free to contact us through the links below for further discussion.

Kind regards, Permanence DAO Decentralized Voices Cohort V Delegate 📅 [Book Office Hours](https://cal.com/permanencedao/office-hours) 💬 [Public Telegram](https://t.me/permanencedao) 🌐️ [Web](https://permanence.io) 🐦 [Twitter](https://twitter.com/permanencedao) 🗳️ [Delegate](https://kusama.subsquare.io/user/EicAs5s99x17qZcQzJMiBCfada9rGyEC6njfiBX3j2EPr9W/votes)

On behalf of the PBA Alumni Voting DAO -
Alumni DAO's vote is Abstain as the community could not reach a consensus. If you would like to contact the alumni to discuss your proposal please contact them on Discord https://discord.com/invite/MsqrdQpGzp

*Sol-XCM project is a typed interface generator for Solidity. With Solidity contracts deployable on Kusama Hub—and soon on Polkadot Hub—we want to enable contracts to communicate with any part of the ecosystem, and even beyond it. Interoperability is the key difference when deploying a Solidity contract on Kusama Hub compared with other ecosystems. We should highlight this as much as possible and make it easy to use.* Sol-XCM makes this possible by enabling interoperable Solidity contracts on Kusama Hub and, in the future, the Polkadot Hub.

*Full proposal:* [*https://docs.google.com/document/d/1dTAjpvBNvzg9XHeLlcC4wtmIcmnIeOTgc9MRS\_lVQyc/edit?usp=sharing*](https://docs.google.com/document/d/1dTAjpvBNvzg9XHeLlcC4wtmIcmnIeOTgc9MRS_lVQyc/edit?usp=sharing)

- Sol-XCM is a tool for Solidity contracts.
- It helps contracts talk to other parts of the ecosystem.
- Contracts can be used on Kusama Hub and soon on Polkadot Hub.
- It makes contracts work together easily.
- This is special because it lets contracts connect with many different systems.
- The main goal is to make contracts more connected.
- It focuses on making communication simple and useful.