The EOSIO SDK for Swift: iOS Example App is a simple application demonstrating how to integrate with EOSIO-based blockchains using EOSIO SDK for Swift. The application does two things: fetches your account token balance and pushes a transfer action.
All product and company names are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
- Xcode 10 or higher
- CocoaPods 1.5.3 or higher
- For iOS, iOS 12+
To get the example application up and running:
- Clone this repo:
git clone https://github.com/EOSIO/eosio-swift-ios-example-app.git
- At the top of
ViewController.swift, supply values for the node URL, private key(s),
quantityand anything else you wish to adjust.
- Run the app!
About the App
This app demonstrates how to:
- use the default RPC provider to query the chain for an account's token balance,
- get a new transaction from the
- create an action and add it to a transaction,
- and sign and broadcast the transaction.
To do this, we're using a few libraries and providers, in concert:
- EOSIO SDK for Swift: The core EOSIO SDK for Swift library
- Default RPC Provider: The default RPC provider implementation in the core library
- ABIEOS Serialization Provider: A pluggable serialization provider for EOSIO SDK for Swift using ABIEOS (for transaction and action conversion between JSON and binary data representations)
- Softkey Signature Provider: An example pluggable signature provider for EOSIO SDK for Swift for signing transactions using in-memory keys (not for production use)
For a more comprehensive list of available provider implementations, see EOSIO SDK for Swift - Provider Protocol Architecture.
The code in
ViewController.swift is documented with brief inline comments. For a deeper dive into EOSIO SDK for Swift, see the Usage Documentation here.
Want to help?
If you'd like to contribute to the EOSIO SDK for Swift libraries themselves, please see the contribution guidelines on those individual repos.
See LICENSE for copyright and license terms. Block.one makes its contribution on a voluntary basis as a member of the EOSIO community and is not responsible for ensuring the overall performance of the software or any related applications. We make no representation, warranty, guarantee or undertaking in respect of the software or any related documentation, whether expressed or implied, including but not limited to the warranties or merchantability, fitness for a particular purpose and noninfringement. In no event shall we be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or documentation or the use or other dealings in the software or documentation. Any test results or performance figures are indicative and will not reflect performance under all conditions. Any reference to any third party or third-party product, service or other resource is not an endorsement or recommendation by Block.one. We are not responsible, and disclaim any and all responsibility and liability, for your use of or reliance on any of these resources. Third-party resources may be updated, changed or terminated at any time, so the information here may be out of date or inaccurate.
Wallets and related components are complex software that require the highest levels of security. If incorrectly built or used, they may compromise users’ private keys and digital assets. Wallet applications and related components should undergo thorough security evaluations before being used. Only experienced developers should work with this software.