This article was first published on ARK.io | Blog - Medium
ARK’s Platform SDK — Modernization of Blockchain Network Interactions
Platform SDK makes it simple to interact with different networks. Signing, verifying, broadcasting transactions and obtaining networks specific data has been standardized to make it a breeze to integrate different blockchain networks in a matter of minutes depending on your needs.
Platform SDK is open-source and available at https://github.com/arkecosystem/platform-sdk
If you have missed the introduction post to Platform SDK give it a read here. In this blog post, we’ll go a bit more into technical detail in what the biggest challenges were when building Platform SDK and the solutions to those problems.
While we tried to come up with a standardized interface for the implementation and interactions with all kinds of different blockchain networks we ran into 3 major issues due to how those different coins worked.
The way you publicly identify wallets can differ between coins. Some coins have the concept of addresses which means your wallets will have an address, public key and private key. On the other hand, you have coins that only have a public key and private key.
This meant for some coins, people are used to using their address to interact with other people, while for another group of people it is normal to use their public key. This meant we had to come up with a standardized interface for our implementations that would provide us with the primary identifier of a wallet without exposing if it is an address or public key.
Methodology To Sign Transactions
The same way identifying wallets differs between coins the method with which data is signed also differs. With BTC, ETH or XLM, for example, it is common to use your private key to sign transactions and messages instead of using a mnemonics while with ARK we expect the user ...
To keep reading, please go to the original article at:
ARK.io | Blog - Medium