Delegation Report - Sik | crifferent.de

[dev0_sik]

Delegate Name: Sik | crifferent.de
Delegate ID: Moonriver and Moonbeam
Delegation Addresses:
Moonbeam: 0x10023fa70ed528e4f28915bf210f6e87b057c08e
Moonriver: 0x693aB260de2a31c1B5D7DC9cb253B87eD9b1f385

Sik Launch Collator, Treasury Councillor, Discord Mod, German Community Admin, Governance Warrior! 🫶🏻

Thanks for checking the details
I’m a DotSama native and was supporting Moonriver and Moonbeam from the get-go, collating on Moonbase Alpha testnet before Moonriver crowdloans were even a thing.
I was selected as one of the Launch-Collators on Moonriver (and later on Moonbeam) and been securing the network ever since
But I’m not just “innit for the tech” - I want to connect the people with the tech . So I became a moderator in the official Moonbeam discord and tried to help people solving their problems wherever I could.
As german is my native language, I also became admin of the german Telegram group.
I always wanted to help driving this project to success and kept up steady conversations with the core team. In late 2022 I became a Treasury Council Member, which I’m still super honoured to be part of - bringing in my technical knowledge to properly evaluate the proposals.

Last but not least I wanted to point out that I’m not only into Moonbeam and Moonriver Governance, but also got a track record being a gov Delegate on Kusama and Polkadot, serving as Councillor for HydraDX and Basilisk, or acting as Identity Registrar on several chains.

No matter what you want to talk about - you can always reach out to me

[dev0_sik]

MOONRIVER REF #65

Close XCM Channel with Litmus

[Proposal: 65] Close XCM Channel with Litmus

Abstract Our XCM monitor noticed that Litmus was no longer producing blocks. Due to this, I’m proposing closing the XCM channel between Moonriver <> Litmus. Details The proposal will call the XCM Transactor pallet with hrmpManage extrinsic with the close option to shut down the 2023 → 2106 XCM channel (and 2106 → 2023). Tested with Chopsticks with preimage hash 0x9bd482a9a1bd059a5e1c75d3c96d01e179d036c6bb779ac10c0109e7470eb4b5 [image]

My Vote: AYE

The chain is stopped and any xc-transfer would result in a loss of funds!

[dev0_sik]

MOONBEAM REF #87

Yaron Zimmermann for Treasury Committee, (Jan-June 2025)

Treasury Elections, Term January - June, 2025

Hey everyone, We’d like to announce the start of the Treasury Elections for the term January - June 2025 for the positions of Non-Foundation Treasury Council members. The current council consists of five members: • 2 Foundation Treasury Council Members • 3 Non-Foundation Treasury Council Members In May 2024, elections were held for the current Non-Foundation Council Members. The proposed process is outlined below: Responsibilities • Ensure responsible spending of treasury funds in the bes…

My Vote: AYE

Yaron has shown full dedication and professionalism in the last term and did most of the heavy-lifting

[dev0_sik]

MOONRIVER REF #66

Authorize Upgrade for Moonriver to RT3400

[Runtime] RT3400 Schedule

Upgrade Recap Here is a summary of the Runtime Upgrade 3400, including several key changes within the ecosystem. Runtime Upgrade consists of different feature sets depending on the network we’re updating. Below, you will find the detailed summary split between the destination environments: [All networks] Reduce min_gas_price by 4 Foreign assets on Moonriver and Moonbeam are now created as EVM native Gas being overestimated for PoV computation is now being refunded at the end of the transactio…

My Vote: AYE

New runtime, less gas cost, new features, more performance - I’m all in for it

[dev0_sik]

MOONRIVER REF #67

Bump XCM Safe Version to 3

[Proposal: 67] Bump XCM Safe Version to 3

Abstract Simple Proposal to bump the XCM Safe Version to 3 Details As more projects are migrating to newer versions of XCM, it is best if we set Moonriver’s XCM Safe version to 3, as it is a more modern XCM version that supports more methods. The bytes of the call can be found here. Preimage tested in chopsticks was 0x72477dd269108f83d1fb58c4c903033ac353b89d421a3ae0b14b09f267a7835a. And the result: [image]

My Vote: AYE

XCM v3 is the new standard, adopted widelym hosts more methods. LFG

[dev0_sik]

MOONRIVER REF #68

Authorize Upgrade for Moonriver to RT3401

[Runtime] RT3400 Schedule

We are administering the hotfix upgrade RT3401 to fix the treasury flow. Specifically, the runtime hotfix RT3401 would include the fix for the Treasury spending flow issue: change of the SpendOrigin on the Treasury pallet to allow either Root or more than half of the Treasury Council. The flow will work as described by Alberto but only with the spend_local extrinsic for the time being. Moonbase Alpha has already been updated. The proposal for MR is live, and we plan to put a proposal for MB ne…

My Vote: AYE

Runtime 3401 is a fix for 3400 that adresses a flaw in the treasury flow that I flagged - we need this

[dev0_sik]

MOONRIVER REF #69

Burn 100% of Transaction Fees

[Proposal: 69] Burn 100% of Transaction Fees

Abstract This Moonriver proposal is to change the proportion of transaction fees that are burned to 100% (currently, 20% of the fees are sent to the treasury). Details This proposal has been tested on Moonriver Runtime 3400 using Chopsticks and the following procedure: Made a test transfer to verify the current proportion of transaction fees that are being sent to the treasury and the user. [image] Checked the events from the transfer and confirmed that 20% of the fees are being sent to…

My Vote: AYE

This proposal seeks to burn 100% of the transaction fees imposing a deflationary force in high volume scenarios. The initial impulse came from the Gauntlet macroeconomics research and was finalized with community feedback