Steve Degosserie

@xgreenx Thanks for your feedback ! I was unaware of your implementation. This is just a simple, incomplete example. My motivation was to show a more advanced chain extension example...

@NukeManDan yep !

To make the lib more portable, it could make sense to drop .Net Core target, and only target .Net Standard v2.1.

I've stumbled on the issue that the Signer requires the 512-bit secret key, while most other libs and tools expose & use the 256-bit (aka MiniSecretKey) one. I've asked the...

Why not use the `sr25519-dotnet` lib ?

@darkfriend77 I just pushed some code over here : https://github.com/stiiifff/substrate-enterprise-sample-app/blob/de46e463335eb9fab22f32970e78da57bbeeb2f8/Parity.Substrate.EnterpriseSample/Services/AccountService.cs#L16 I can generate a mnemonic with the `dotnetstandard-bip39` nuget, derive entropy & seed from the mnemonic, then create a keypair...

@darkfriend77 I opened a PR https://github.com/gautamdhameja/sr25519-dotnet/pull/1. Please try with one of the native lib, I've built them from the latest master branch of the C bindings (https://github.com/Warchant/sr25519-crust) which is compatible...

> @stiiifff I used your branch PR (https://github.com/stiiifff/sr25519-dotnet/tree/netstd-2_1) branch and now it doesn't verify any of the signatures ... **sr25519-crust seems to be on 0.85** ?? As mentioned in the...

@darkfriend77 OK, I found an issue in the sr25519-dotnet lib: https://github.com/gautamdhameja/sr25519-dotnet/blob/259d403cee7d08b7da764246c49bcbbf1e9af9c4/sr25519-dotnet.lib/SR25519.cs#L119. If you pass a string with chars that are not valid UTF8 characters, this is gonna mess the whole...

@NukeManDan @joepetrowski gentle nudge on this one. Without it, the parachain template does not provide a sane default XCM config for new parachain projects.