Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add tidext in real world usage #508

Merged
merged 2 commits into from
Apr 14, 2022
Merged

Add tidext in real world usage #508

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dfffdcf
Add `tidext` in real world usage
lemarier Apr 8, 2022
d1db924
remove `Stronghold` link
lemarier Apr 11, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,7 @@ Please add your project to this list via a PR.
- [phala-pherry](https://github.com/Phala-Network/phala-blockchain/tree/master/standalone/pherry) The relayer between Phala blockchain and the off-chain Secure workers.
- [crunch](https://github.com/turboflakes/crunch) CLI to claim staking rewards in batch every Era or X hours for substrate-based chains.
- [interbtc-clients](https://github.com/interlay/interbtc-clients) Client implementations for the interBTC parachain; notably the Vault / Relayer and Oracle.
- [tidext](https://github.com/tidelabs/tidext) Tidechain client with [Stronghold](https://github.com/iotaledger/stronghold.rs) signer.
Copy link
Member

@niklasad1 niklasad1 Apr 11, 2022 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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!


**Alternatives**

Expand Down