Nuke 🌄

Sure!! @muddlebee I would say we have you update things here, but really they should land upstream in substrate itself, so please open a PR here, and @ me but...

He @Manuelandro @kamikazebr - any word on progress here? :grin:

cool @tarrball ! :grin: .... maybe a PR here? I think we could maintain an alt branch of this with your support that is pure TS... or with the maintainers...

much like the README has: `[](https://github.com/paritytech/parity-signer/releases/)` Although github is not always an indication that an apk is available, so might confuse some users.

In addition / alternatively, this can live on stackoverflow. https://stackoverflow.com/questions/65348505/runtime-building-string-not-found-in-this-scope I would appreciate some help in answering this properly in this issue before posting an answer there 🙏🏼

Right, best practice for _large items_ should be done with off-chain storage and mapped hashes (IPFS CIDs) stored. But many starting out will run into this kind of error, experimenting....

Integration tests is what you are after here, right? Related request: https://stackoverflow.com/questions/66884974/how-do-you-write-a-system-test-for-your-runtime This is something I think would be super valuable in general to have on the devhub - as...

Related? https://github.com/paritytech/substrate/discussions/8370 If this lands in substrate, types for the API at least will be much more transparent and automatically generated. 🧙🏼

Hi, I have few question regarding gossip. I try to use sc_network_gossip::GossipEngine. I hope this is the right way to go. Do we get the messages sent to us using...

we are in the middle of setting this up, I would say master is the one to use found (the ui to select) here : https://docs.substrate.io/rustdocs