Powered by Transit API: Now Supporting Native Ledger Signing
The Transit API is a community-owned standard API layer that makes it easy for signature providers and dApps to connect on the EOS blockchain.
If the Transit API is new to you, please see the original announcement here.
Many developers in the EOS community have embraced the Transit API because it provides a great degree of flexibility and freedom when it comes to supporting the best signature providers in the space. We thank them for their support. It takes a community to create a standard.
We are pleased to announce that Transit API now has native Ledger support. Native Ledger support means no additional wallet software is required to use your Ledger to interface with a dApp.
One Line of Code
If you are already a developer using the Transit API then, depending on your implementation it’s as easy as adding one line of code like the example below.
walContext.addWalletProvider(ledger({ pathIndexList: [ 0, 1, 2, 35 ] }));
More signature provider plugins coming!
Stay tuned for an announcement regarding the completion of a Lynx plugin for the Transit API. If you have questions or wish to contribute then visit the telegram group here.
