Add tidext in real world usage

[lemarier]

Signed-off-by: David Lemarier david@lemarier.ca

[cla-bot-2021]

User @lemarier, please sign the CLA here.

[jsdw]

Dumb question maybe, but could you point me to the usage of subxt in that project; I can't find anything offhand (https://github.com/iotaledger/stronghold.rs/search?q=subxt)?

[lemarier]

Dumb question maybe, but could you point me to the usage of subxt in that project; I can't find anything offhand (https://github.com/iotaledger/stronghold.rs/search?q=subxt)?

Hey @jsdw , this is not a dumb question!
Maybe I should remove the Stronghold link to prevent confusion? (let me know if you want me to proceed)

This is the Stronghold signer integration:
https://github.com/tidelabs/tidext/blob/dev/tidext/src/keyring/stronghold.rs

The documentation is available here as well;
https://tidelabs.github.io/tidext/

Hope this help

[niklasad1]

@jsdw note that tidext is a fork of subxt that's probably why you didn't found it ^^

[jsdw]

Aha, thanks guys, confusion cleared up :)

(I would be curious to know why you forked Subxt though! Was it missing some crucial features?)

[niklasad1]

Should be sufficient to add Stronghold here, I think tidext will cause confusion.

I guess you need some tweaks to subxt, perhaps you are using some other polkadot/substrate tags or what it's the reason behind the fork?

[lemarier]

Hey guys, thanks for review!

The main reason is that we need to have substrate locked to the same version that our chain and our primitives as they are shared between different services.

Once we stabilize everything, we should be good to use the same substrate version that subxt use and delete the fork.

There is no missing features in subxt, we had some previously but you guys fixed them all!

PS; I removed the Stronghold link to prevent any confusion

Thanks again!