
**Summary:**
Proposal to open a bi-directional channel between Shiden Network and GMorDIE. The primary use cases will be allow our community of builders to propose different proofs of concepts, ideate and implement novel builds between both chains.

**Technical details:**
The procedure for opening the channels is as follows:

- Shiden proposes to open the Shiden to GMorDIE HRMP channel
- Wait until the proposal on Step 1 gets approved & enacted.
- GMorDIE accepts the Shiden to GMorDIE HRMP channel, requests opening of the GMorDIE to Shiden HRMP channel and adds SDN to its asset registry.
- Wait until the proposal on Step 3 gets approved & enacted.
- Shiden proposes to accept GMorDIE to Shiden HRMP channel.
- Wait for another session on Kusama for the change to be effective.
- These extrinsics need to be called with the parachain’s sovereign account as the origin. To achieve this, on the GMorDIE side we will use polkadot-xcm pallet to send XCM message to the relay chain, by executing the following extrinsic from the parachain.

As a prerequisite, the parachain’s sovereign account must contain at least 10 KSM to be locked as collateral (5 for each channel direction), plus some KSM to pay for XCM execution fees.

Proposal: Open HRMP channel between Shiden Network and GMorDIE

This proposal aims to incorporate Astar's **"Unstoppable Community Grants"** program into Shiden and allow for the community to make proposals for these new type of grants that involve dApp staking. 

**Context:** The Shiden Network, as the canary network for Astar Network, is still integral for the continued experimentation, development and innovation that can happen in the ecosystem. Shiden offers a unique environment where developers can gather and work together to create new uses cases and proof of concepts that may bring value to the not just Astar, but the whole of Kusama and Polkadot.

In order to promote these builds to happen and mature, we need a better incentive model to attract teams, and/or at least reward the builders that currently are shipping products. This is where Unstoppable Community Grants can help. The community has access to the Shiden Treasury that is relatively unused. 

- For an overview of the Unstoppable Community Grants and how it works, please see the following presentation: [UCG: Overview](https://docs.google.com/presentation/d/1HH8651zROJjE3cXFCGCsP3-dXwMR2TvoclYT0WkuF5E/edit?usp=sharing)

- The structure of each proposal can follow the already created "Steps": [UCG: Steps](https://docs.google.com/document/d/1AddQUrHE6M6llEdaIYKNlV8QC-pffWdPX7gfNcNC6xw/edit?usp=sharing)

*If proposal is accepted, the Shiden council, and together with the Shiden community, will help create guidelines and adapt the UCG in a matter that sustains the treasury, and allocates grants to truly innovative projects.*

*Suggestions and changes to the above posted resources can be made by the council to better suit ShidenDAO and its community of builders.*

✅ **A "YES" vote signals to the ShidenDAO that the UCG program be incorporated.**
⛔ **A "NO" vote signals to the ShidenDAO to reject the UCG program incorporation.**

Incorporate the Unstoppable Community Grants program with ShidenDAO

More information about the proposal can be found here: https://forum.astar.network/t/open-hrmp-channel-between-shiden-network-picasso/4619

Proposal: Open HRMP channel between Shiden Network and Picasso

GM Shiden Friends,

I am GuiGou, Astar Tech Ambassador, and I am glad to write this proposal for the Lucky dApp Staking program on Shiden.

About Lucky:

Lucky is a dApp built on top of dApp Staking in Astar Network. If the user stakes on the Lucky dApp, he will still receive the rewards from the dApp Staking, and furthermore, he will have a chance to win extra rewards. It's a no-loss lottery!

The dApp is built with several ink! smart contracts, a subquery indexer, and off-chain workers (scheduled jobs). We plan to replace the scheduled jobs with phat contracts to improve decentralization and demonstrate the interoperability between ink! smart contracts (Shiden/Astar) and ink! phat contracts (Khala/Phala). 
Next, we will add extra features.

The dApp is already live in Shibuya.

Website: 
https://lucky.substrate.fi/

Docs: 
https://polkaverse.com/11201/introducing-the-d-app-lucky-37998

Twitter: 
https://twitter.com/LuckyDapp

Github for the contracts: 
https://github.com/GuiGou12358/lucky-contracts

Github for the indexer: 
https://github.com/GuiGou12358/lucky-subql

Github for the workers: 
https://github.com/GuiGou12358/lucky-workers

Github for the UI: 
https://github.com/arnobase/lucky-ui-1-fork


The Team:
 GuiGou: Tech Ambassador for Astar and Ambassador for Phala and Unique
 Arno: Ambassador for Polkadot, Phala, Acala and Talisman Sentinel

Discussion can be found here:
https://forum.astar.network/t/shiden-lucky-dapp-staking-program/4604

Many Thanks

Shiden - Lucky dApp Staking program

TL;DR
We propose to open HRMP communication between Shiden Network and Quartz. This will require actions on both chains.

More information: https://forum.astar.network/t/open-hrmp-channel-between-shiden-network-and-quartz-network/4586/1

Proposal: Open HRMP channel between Shiden Network and Quartz Network

This proposal aims to refund Shiden collators who were mistakenly slashed during the Kusama “dispute” incident.
During this time, a lot of Shiden blocks were rejected by Kusama validators while the collators could do nothing to fix it.
Details of the incident here: https://github.com/paritytech/polkadot/issues/6862

**Period**: 10/03/2023 06:30 UTC to 10/03/2023 22:00 UTC

**Number of slashes**: 12
Event ID	Block	Block Timestamp	Collator
3551700-47	3551700	2023-03-10 14:09:56	Z4X3SJ61EYa7Nbt5PUwkdyhnFkMk63eX57qQKMSSwn4YFUN
3551700-43	3551700	2023-03-10 14:09:56	WdvwQ5z2FNEbFCB782sj4TmTRoAJpB6Zt3oaXw2KJ1UqyvQ
3551700-39	3551700	2023-03-10 14:09:56	WizRzDHCKrUEX17gGxux6nHHTJgWovBopLDx7geRvmqSvt8
3551700-35	3551700	2023-03-10 14:09:56	aqJNUQpx2fSEQrUGEPsVBGgDKtRwto2i2ZTqMfSAQFaJ7DG
3551700-31	3551700	2023-03-10 14:09:56	Zedo1qEx2Rez7TrGQB3ZpUA1pREx6Fh5baHtBEPNYp7db1p
3551700-27	3551700	2023-03-10 14:09:56	XDPR9sZPVx3K23PGUtwJ8tKePCVuSdEBmTyBkjEkRA3z8qr
3551700-23	3551700	2023-03-10 14:09:56	Yyj1cKmeN2zf6nEHvqiuJ93SrHYaBgs3ZP4he5enGRtyv4V
3551700-19	3551700	2023-03-10 14:09:56	WPhsn7TRWQx9LSqDyFU6oT6wEbvtBy5g7VE3kTiyBSbmZW1
3551700-15	3551700	2023-03-10 14:09:56	apaNTC8x1KW5gCb8qetAS1swbvDSukoUJKzfyKy4UGnWYPY
3551700-11	3551700	2023-03-10 14:09:56	YV8jKMcihuMM1cpfAV2qd8JpPG2dxr24pCHauj5NbrEY2YA
3551700-7	3551700	2023-03-10 14:09:56	W8PzksJcA1Ag82GNvuxT6Ejp4KXqQexNXqysJyuxSvHSmH9
3551700-3	3551700	2023-03-10 14:09:56	XoY6Qh7bpmhe8h3h5aR1GbQA3ee7Aj7zKsCxBhR2RC8JULE

**Amount slashed per collator**: 320 SDN
**Total amount**: 3840 SDN



 Proposal: refund slashed collators during relay chain incident

# Description

We propose to open a bi-directional channel between Shiden Network and Bit.Country Pioneer. The primary use cases will be:

1. $SDN can be transferred to Bit.Country Pioneer and used as a payment method in the NFT marketplace on Bit.Country Pioneer and Bit.Country Pioneer Metaverse.
2. $NEER can be transferred to Shiden to be used in the ecosystem of Shiden Network and the protocols build on top of the network.

Please feel free to comment and discuss here: https://forum.astar.network/t/open-hrmp-channel-between-shiden-network-and-bit-country-pioneer/4391

Open HRMP Channel Between Shiden Network and Bit.Country Pioneer

**Description**

We propose to open a bi-directional channel between Shiden Network and Basilisk. The primary use cases will be:

- Transfer $SDN to the Basilisk Snek Swap to be permissionlessly paired and traded with any other listed asset.
- Allow Shiden ecosystem projects to leverage Basilisk LBP for future token distribution.

Please feel free to comment and discuss here: https://forum.astar.network/t/open-hrmp-channel-between-shiden-network-and-basilisk/4330

Open HRMP Channel Between Shiden Network and Basilisk

**Proposal**: list [Web3alert.io](https://web3alert.io/start) to Shiden dApp staking
Hi, Shiden network community!
We are the Web3alert team and would like to apply for the Shiden dApp Staking listing.
We’ve successfully applied for Astar dApp staking and now apply for Shiden.

Presentation of our project and discussion can be found here:
[https://forum.astar.network/t/web3alert-io-shiden-dapp-staking-application/4303](https://forum.astar.network/t/web3alert-io-shiden-dapp-staking-application/4303)

List Web3alert.io to Shiden dApp staking

We propose to open a bi-directional channel between Shiden Network and Genshiro. The primary use cases will be:
To transfer Shiden’s native token (SDN) and Shiden’s ecosystem assets to Genshiro to integrate with Genshiro’s suite of DeFi products.

Please feel free to comment and discuss here: https://forum.astar.network/t/open-hrmp-channel-between-shiden-network-and-genshiro/3778

Open HRMP Channel Between Shiden Network and Genshiro

Proposal #1

Burn 100% of the transaction fee: the current burn mechanism burns 20% of the transactions, and the rest goes to the collator that produced the block. We want to increase the 20% to 100% so that all transaction fees will be burned in the network.

Discussion: https://forum.astar.network/t/shiden-burn-proposal-and-buyback-initiative/4123/

Burn proposal #1: burn 100% of transaction fee

Proposal #2:

Burn unclaimed rewards from delisted dApps from dApp Staking: as noticed, many more proposals pop up to delist inactive dApps from Shiden dApp staking. This proposal will burn all the rewards not claimed by the dApp after being delisted.

Discussion: https://forum.astar.network/t/shiden-burn-proposal-and-buyback-initiative/4123

Burn proposal #2: burn unclaimed rewards from delisted dApps

Proposal #3:

Burn 10% of treasury at the end of each quarter: a part of the block rewards currently goes to the treasury. This proposal is to burn each quarter 10% of the treasury wallet. We also would like to motivate our ShidenDAO community to create a great way to use our treasury in the next phase.

Discussion: https://forum.astar.network/t/shiden-burn-proposal-and-buyback-initiative/4123

Burn proposal #3: burn 10% of treasury at the end of each quarter

This proposal seeks to delist standard protocol from the dappstore.
I purposed it in astar forum and now submit to community for vote.

Feel free to read proposal and discussion here: [https://forum.astar.network/t/proposal-delist-standard-protocol-from-dappstaking-shiden/4111](url)

Proposal to Delist Standard protocol dApp

I am writing to propose to delist Emiswap from Shiden dApp staking. These are my findings:

1. No liquidity. 
2. They are pausing their development due to market conditions. This is against our culture. Bull or bear, we have to build.
3. 212 eras of unclaimed rewards. It seems that they have forgotten. 

Therefore, when they come back being active to develop and increase the liquidity, we can vote to list them again.

Discussion can be found here:
https://forum.astar.network/t/proposal-to-delist-emiswap/4112/1

 Proposal To Delist Emiswap from dApp Staking

### Description ###
**Proposal**: Delist Decus from dApp staking

This proposal seeks to delist Decus from the dApp store on Shiden Network. The justification for the delisting are the following reasons:

**Inactive or Changed Twitter - Inactive Community Building - Project does not exist**

- No respect of the Decus roadmap for Shiden. Decus has not deployed its smart-contracts or integrated its Bitcoin wrapper solution on Shiden in over a year.
- No Github activity since November 2021.
- Decus has not been active on Twitter 1 since January 2022. The same is true for Discord.
- The Decus team hasn’t touched their dApp Staking developer rewards for 380 days. 3,053 SDNs are on the developer’s account according to the subscan.
- According to Decus Official Account on Telegram, the project is on “hiatus”.

Discussion can be found here:
https://forum.astar.network/t/proposal-delist-decus-from-dapp-staking-shiden-dapp/4083

Delist Decus from Shiden's dApp Staking


**Proposal:** Delist Deep Waifu from dApp staking

The dApp **"Deep Waifu"** should be delisted for the following reasons:

1. Website [https://deepwaifu.ai/](url) doesn’t work, specifically the intention of the dApp is not functioning.
2. Their previous twitter account changed to [https://twitter.com/ChronoLogicETH](url). Possibly meaning they have left the project.
3. Cannot find the project, nor a related community, anywhere else.


**Discussion can be found here:**
[https://forum.astar.network/t/proposal-delist-deep-waifu-from-dapp-staking-shiden-dapp/4072?u=0xramz](url)

Delist Deep Waifu from dApp staking

**TL;DR**
We propose to open HRMP communication between Shiden Network and Crab Network. This will require actions on both chains.

**Summary**
We propose to open a bi-directional channel between Shiden Network and Crab Network. The primary use cases will be:

1. To support Crab Network’s light-client cross-chain messaging protocol (LCMP) via XCM-LCMP rounter. Shiden ecosystem devs will be able to use LCMP to communicate with Ethereum, BNB Chain, etc. on Shiden Network.
2. $CRAB can be transferred to Shiden to be used in the ecosystem of Shiden Network and the protocols build on top of the network.

**Proposal**
There is no on-chain proposal. The proposal created in this forum acts as an official proposal between Crab Network and Shiden Network.

**Technical details (WIP)**
The procedure for opening the channels is as follows:

1. Crab Network initializes a proposal to open Crab Network to the Shiden Network HRMP channel via the Astar forum.
2. Wait until the proposal on step 1 gets approved & enacted.
3. Onboard your testnet on the Rococo relay chain and exchange public endpoints and parachain-ids.
4. Wait until onboarding was successful on testnet.
5. Shiden Network proposes to accept the Crab Network to Shiden Network HRMP channel and open a Shiden Network to Crab Network HRMP channel via [Astar MuliSig Governance Batch call].
6. Wait until the proposal on step 5 gets approved & enacted.
7. Crab Network accepts the Shiden Network to Crab Network HRMP channel.
8. Wait for another session on Kusama/or/Polkadot for the change to be effective.

These extrinsics need to be called with the parachain’s sovereign account as the origin. To achieve this, on the Crab Network side we will use polkadot-xcm pallet to send XCM message to the relay chain, by executing the following extrinsic from the parachain. Shiden Network should make an open request call and an accept request call with its pallet.

As a prerequisite, the parachain’s sovereign account must contain at least 10 KSM to be locked as collateral (5 for each channel direction), plus some KSM to pay for XCM execution fees.

**Discussion**
https://forum.astar.network/t/open-hrmp-channel-between-shiden-network-and-crab-network/4043

Open HRMP Channel Between Shiden Network and Crab Network

# TL;DR

We propose to open HRMP communication between Shiden Network and Bifrost Kusama. This will require actions on both chains.

# Summary

We propose to open a bi-directional channel between Shiden Network and Bifrost Kusama. The primary use cases will be:

1. To prepare for opening HRMP channel between Astar Network and Bifrost on Polkadot so that the $vDOT, liquid staking DOT tokens, can be transferred to Astar to be used in the ecosystem of Astar Network and the protocols built on top of the network.
2. $vKSM, liquid staking KSM tokens, can be transferred to Shiden to be used in the ecosystem of Shiden Network and the protocols built on top of the network.
3. $KSM tokens on Shiden can be transferred to Bifrost Kusama and used in Kusama validator staking while receiving the liquid tokens
4. Build liquid staking solution for Shiden dApp Staking

# Proposal

There is no on-chain proposal. The proposal created in this forum acts as an official proposal between Bifrost Kusama and Shiden Network.

# Technical details (WIP)

The procedure for opening the channels is as follows:

1. Bifrost Kusama initializes a proposal to open Bifrost Kusama to the Shiden Network HRMP channel via the Astar forum.
2. Wait until the proposal on step 1 gets approved & enacted.
3. Onboard your testnet on the Rococo relay chain and exchange public endpoints and parachain-ids.
4. Wait until onboarding was successful on testnet.
5. Shiden Network proposes to accept the Bifrost Kusama to Shiden Network HRMP channel and open a Shiden Network to Bifrost Kusama HRMP channel via [Astar MuliSig Governance Batch call].
6. Wait until the proposal on step 5 gets approved & enacted.
7. Bifrost Kusama accepts the Shiden Network to Bifrost Kusama HRMP channel.
8. Wait for another session on Kusama/or/Polkadot for the change to be effective.

These extrinsics need to be called with the parachain’s sovereign account as the origin. To achieve this, on the Bifrost Kusama side we will use polkadot-xcm pallet to send XCM message to the relay chain, by executing the following extrinsic from the parachain. Shiden Network should make an open request call and an accept request call with its pallet.

As a prerequisite, the parachain’s sovereign account must contain at least 10 KSM to be locked as collateral (5 for each channel direction), plus some KSM to pay for XCM execution fees.

# Discussion
https://forum.astar.network/t/open-hrmp-channel-between-shiden-network-and-bifrost-kusama/4030

Open HRMP Channel Between Shiden Network and Bifrost Kusama

**Proposal**: Delist Stake Technologies
Stake Technologies, (aka Astar Foundation) the company behind the network, has been part of our dApp staking mechanism from day 1. As mentioned during our launch event, we as ShidenDAO will delist them from dApp staking.

Discussion can be found here:
https://forum.astar.network/t/delist-stake-technologies-from-dapp-staking/3971/

Delist Stake Technologies from dApp staking

**TL;DR**
We propose to open HRMP communication between Shiden Network and Sakura Network. This will require actions on both chains.

**Summary**
We propose to open a bi-directional channel between Shiden Network and Sakura Network. The primary use cases will be:

1. To prepare for opening HRMP channel between Astar Network and Clover Network on Polkadot so that the $80M FDV worth of $CLV tokens can be transferred to Astar to be used in the ecosystem of Astar Network and the protocols built on top of the network.
2. $SKU can be transferred to Shiden to be used in the ecosystem of Shiden Network and the protocols built on top of the network.

**Proposal**
There is no on-chain proposal. The proposal created in this forum acts as an official proposal between Sakura Network and Shiden Network.

**Technical details (WIP)**
The procedure for opening the channels is as follows:

1. Sakura Network initializes a proposal to open Sakura Network to the Shiden Network HRMP channel via the Astar forum.
2. Wait until the proposal on step 1 gets approved & enacted.
3. Onboard your testnet on the Rococo relay chain and exchange public endpoints and parachain-ids.
4. Wait until onboarding was successful on testnet.
5. Shiden Network proposes to accept the Sakura Network to Shiden Network HRMP channel and open a Shiden Network to Sakura Network HRMP channel via [Astar MuliSig Governance Batch call].
6. Wait until the proposal on step 5 gets approved & enacted.
7. Sakura Network accepts the Shiden Network to Sakura Network HRMP channel.
8. Wait for another session on Kusama/or/Polkadot for the change to be effective.

These extrinsics need to be called with the parachain’s sovereign account as the origin. To achieve this, on the Sakura Network side we will use polkadot-xcm pallet to send XCM message to the relay chain, by executing the following extrinsic from the parachain. Shiden Network should make an open request call and an accept request call with its pallet.

As a prerequisite, the parachain’s sovereign account must contain at least 10 KSM to be locked as collateral (5 for each channel direction), plus some KSM to pay for XCM execution fees.

**Discussion**
https://forum.astar.network/t/open-hrmp-channel-between-shiden-network-and-sakura-network/3959

Open HRMP Channel Between Shiden Network and Sakura Network

**Description**
**TL;DR**

We propose to open HRMP communication between Shiden Network and Crust Shadow. This will require actions on both chains.

**Summary**

We propose to open a bi-directional channel between Shiden Network and Crust Shadow. The primary use cases will be:

1. To enable IPFS-based decentralized storage solutions for devs in the Shiden ecosystem (e.g. directly place storage orders on Crust's decentralized storage network by calling smart contracts on Shiden).
2. After reserve_transfer is enabled, users will be able to use their assets on top of Shiden Network to pay for decentralized storage orders on Crust Network's IPFS nodes.
3. $CRU can be transferred to Shiden to be used in the ecosystem of Shiden Network and the protocols build on top of the network.

**Proposal**

There is no on-chain proposal. The proposal created in this forum acts as an official proposal between Crust Shadow and Shiden Network.

**Technical details (WIP)**

The procedure for opening the channels is as follows:

1. Crusr Shadow initializes a proposal to open Crust Shadow to the Shiden Network HRMP channel via the Astar forum.
2. Wait until the proposal on step 1 gets approved & enacted.
3. Onboard your testnet on the Rococo relay chain and exchange public endpoints and parachain-ids.
4. Wait until onboarding was successful on testnet.
5. Shiden Network proposes to accept the Crust Shadow to Shiden Network HRMP channel and open a Shiden Network to Crust Shadow HRMP channel via [Astar MuliSig Governance Batch call].
6. Wait until the proposal on step 5 gets approved & enacted.
7. Crust Shadow accepts the Shiden Network to Crust Shadow HRMP channel.
8. Wait for another session on Kusama/or/Polkadot for the change to be effective.

These extrinsics need to be called with the parachain’s sovereign account as the origin. To achieve this, on the Crust Shadow side we will use polkadot-xcm pallet to send XCM message to the relay chain, by executing the following extrinsic from the parachain. Shiden Network should make an open request call and an accept request call with its pallet.

As a prerequisite, the parachain’s sovereign account must contain at least 10 KSM to be locked as collateral (5 for each channel direction), plus some KSM to pay for XCM execution fees.

**Discussion**
https://forum.astar.network/t/open-hrmp-channel-between-shiden-network-and-crust-shadow/3958

Proposal: Open HRMP Channel Between Shiden Network and Crust Shadow

**TL;DR**
We propose to **open HRMP channel** between **Shiden Network** and **Khala Network**.

**Summary**
We propose to open a bi-directional channel between Shiden Network and Khala Network. The primary use cases will be:

To enable cross-parachain routing and support transferring Shiden’s ecosystem assets to Ethereum via SubBridge.
$PHA can be transferred to Shiden to be used in the ecosystem of Shiden Network and the protocols build on top of the network.
When Khala Network’s Fat Contract comes to live, developers in Shiden’s ecosystem will be able to build use cases with Fat Contract which allows sending HTTP requests from smart contracts. Developers will be able to utilize fat contract and XCM to build TEE-based price feed oracle, social data oracle, etc. for Shiden’s ecosystem.
To transfer Shiden’s ecosystem assets to Khala Network so they can be privatized and transferred confidentially and anonymously.

**Technical details (WIP)**
The procedure for opening the channels is as follows:

1. Khala Network initializes a proposal to open Khala Network to the Shiden Network HRMP channel via the Astar forum.
2. Wait until the proposal on step 1 gets approved & enacted.
3. Onboard your testnet on the Rococo relay chain and exchange public endpoints and parachain-ids.
4. Wait until onboarding was successful on testnet.
5. Shiden Network proposes to accept the Khala Network to Shiden Network HRMP channel and open a Shiden Network to Khala Network HRMP channel via [Astar MuliSig Governance Batch call].
6. Wait until the proposal on step 5 gets approved & enacted.
7. Khala Network accepts the Shiden Network to Khala Network HRMP channel.
8. Wait for another session on Kusama/or/Polkadot for the change to be effective.

These extrinsics need to be called with the parachain’s sovereign account as the origin. To achieve this, on the Khala Network side we will use polkadot-xcm pallet to send XCM message to the relay chain, by executing the following extrinsic from the parachain. Shiden Network should make an open request call and an accept request call with its pallet.

As a prerequisite, the parachain’s sovereign account must contain at least 10 KSM to be locked as collateral (5 for each channel direction), plus some KSM to pay for XCM execution fees.

**Discussion**
https://forum.astar.network/t/open-hrmp-channel-between-shiden-network-and-khala-network/3950

Open HRMP Channel Between Shiden Network and Sakura Network

Proposal: Open HRMP Channel Between Shiden Network and Crust Shadow

Proposal: Open HRMP Channel Between Shiden Network and Khala Network