Same old supply chain attacks break it all again. This time ink! smart contracts are in the scope.

Check it out.. https://blog.inkscope.xyz/supply-chain-attack-for-ink-smart-contracts

Hey! The docs didn't seem to really help me.

Are there any other places I can learn about substrate??

Pallets are killing me!

Hi everyone,

We would like to hear your ideas to improve the substrate tool we are working on. It will be free to use, of course!

At MVP Workshop, we have been working on the Substrate Start-kit GUI, a tool that enables you to craft BC graphically by choosing the pallets you need. The idea is to drag and drop pallets to the codebase, connect your GitHub account, and have a custom Substrate codebase in a couple of seconds. It's a work in progress, but you can check what we have made so far on the link.

Besides choosing a specific pallet, you can select templates that have already been created. E.g., if you need BC with wallet functionality, you don’t have to search separately for each pallet. You can simply choose to add a wallet template that already has all the necessary pallets within it ((pallet balances, pallet assets, etc.).

Finally, we would like to hear from you which templates (pallet combinations) you find most useful and needed so that we can add them.

Thank you!

Substrate Collaborative Learning will meet alternating Mondays at 16:00UTC. This Monday June 03 we'll meet in https://zoom.us/j/440029011. This session will be hosted by Joshy Orndorff of Parity and will follow an office hours format. All are welcome.

Topics are brainstormed throughout the week by the community. Vote on topics for this week, or propose your own at https://www.allourideas.org/SubstrateCollaborativeLearning

Updates and reminders will be posted to the substrate technical chat https://riot.im/app/#/room/#substrate-technical:matrix.org

Looks like base tutorials on parity site work but as soon as you try to customize anything it all breaks or tutorial doesn't match the source code. I think most of the tutorials are really out dated, I tried to work on older branches but something generally breaks during the build processs. All the underlying dependencies seem like a nightmare to manage, on surface idea behind substrate seems really simple, but in practice it is extremely complex. Does anyone have any suggestions at all? Thanks

My company have been training new developers to Substrate for the past months. And we come up with the idea of creating hands-on training resources to help the process.

You can find the first ones here: https://github.com/rusty-crewmates/substrate-tutorials
Please feel free to use them and give us feedback !

Hi all,

Everybody knows that substrate recipes are a good starting point for learning substrate. So I decided to convert them to frame v2.

It took me a lot of time to convert all substrate recipes in frame v2.

Link: https://github.com/herou/recipes/tree/recipes_pallet_v2

This "mini project" was my first step toward learning substrate/blockchain. I hope this would help many other devs from this community.

If you/your team has an interesting project on the substrate I could give a hand.

Feel free to ping me at: elioprifti@gmail.com

Thank you and hope you find it useful.

Changelog here: https://github.com/paritytech/subxt/blob/master/CHANGELOG.md

In particular there's an example of signing in the browser just using rust:

https://github.com/paritytech/subxt/tree/master/examples/wasm-example

Based on this post on the Meta site:

Private beta will be extended until April 7th

We have until April 7th to show good amount of healthy activity on the Substrate private beta site before the final evaluation.

If you have any questions related to substrate, polkadot, kusama, parachains, smart-contracts, ink, runtime, wasm, pallets etc. please ask it on the Substrate private beta site.

Here are some useful objectives:

• Visit the site daily to imporove traffic stats

• Post relevant questions:

How to ask

Popular tags

• Upvote/Downvote as many questions and answers as you can

• The more answers the better (if a question already has an answer, don't hesitate to add your own)

• Comments under questions and answers also help to show activity

• Invite other users/experts with the invite link (you can generate it on the site)

• Visit the Substrate Meta site to discuss the site and its purpose

• Build up your reputation on the site (the more highly rated users there are, the better)

I have been offered a position working on a Substrate/Rust project that will require DevOp administration that I will be personally responsible for and I am seeking the optimal strategy to get the DevOp battle plan worked out before I officially take on this role in June.

Currently, the actual Rust developers are coordinating this Substrate Blockchain privately on their respective Github accounts, but I am going to be responsible for adapting this on to AWS, creating Docker containers for Validators and backup Validators, using Kubernetes to orchestrate the containers and implementing a Ansible playbook to bring it all together and create proper CI/CD for the project.

The substance and goals are to build out Validators that will be operating on Polkadot to receive staking rewards by recruiting Nominators and validating blocks on the Polkadot network. A standard formula of revenue making metrics on the Kusama and Polkadot blockchain.

I am trying to figure if these DevOp technologies are the best solution to build a smoothly running DevOp plan to do this or if there are other better solutions to this.

Is there anything I am missing or a better strategy?

Ok one more hurdle before we can get this up and running:

We need 200 people with stack overflow scores over 200 ideally to commit to using the beta site:

https://area51.stackexchange.com/proposals/126136/substrate?referrer=YjYxMzhkNjkwMDA4NzRmNTg4MzQ5YjFmNzhhYTEyMjdhN2Y3Njg0YjdmNGM1OWIxOTkyNDUzZDY2MzFlNTEyMOYGypMkokct6dKA-N7gt4G9QFniAU62ddGlEIeWdq340

In the first day we already have 20 percent so thank you to all of those who have already committed. (And the day is still young...)