Tags: bkontur/runtimes
Tags
Update rust and use stable for benches (polkadot-fellows#574) <!-- Remember that you can run `/merge` to enable auto-merge in the PR --> <!-- Remember to modify the changelog. If you don't need to modify it, you can check the following box. Instead, if you have already modified it, simply delete the following line. --> - [x] Does not require a CHANGELOG entry We are trying to get the command bot working. However, right now it is timing out when trying to build the runtimes plus the omni bencher after 6 hours. This should not take 6 hours ;) So, one guess is that maybe the nightly is doing something that takes quite long to build. We want to try the stable compiler and see if that fixes the issue. --------- Co-authored-by: GitHub Action <action@github.com>
Lower Parachain and Data Deposits to Encourage Experimentation on Kus… …ama (polkadot-fellows#501) Chaos is a ladder, this PR proposes bringing the rungs a tad bit closer to make it easier to climb. In other words, this PR aims to lower the barriers for experimentation and innovation within the Polkadot ecosystem. We're reducing both the `ParaDeposit` and `DataDepositPerByte` to encourage more developers and projects to deploy and test their ideas on Kusama. The changes: - Reduced ParaDeposit from 40 UNITS to 4 UNITS - Lowered DataDepositPerByte from 1 CENT to 0.1 CENTS These adjustments will make it more accessible for teams to register a blockchain and get started. I think that making things accessible starts with making them affordable, this aims to do just that. This aligns with Kusama's role as a canary network, where we can push the boundaries of what's possible. While we're lowering the initial costs, it's worth noting that this change **doesn't implement an adaptive fee structure** that would increase costs if too much code is registered too quickly. Such a mechanism could be considered for future implementations, potentially as a Polkadot-ready solution. Kusama is the playground for radical innovation. With these lowered deposits, we're inviting chaos – controlled chaos that drives progress. Expect the unexpected, and let's see what comes out the other end. :)
Explain approval rights (polkadot-fellows#42) This also adds a tutorial on how to add the github name to the on-chain identity. --------- Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com> Co-authored-by: Przemek Rzad <roopert7@gmail.com> Co-authored-by: André Silva <andrerfosilva@gmail.com>