EOSIO SDK for Swift is an API for integrating with EOSIO-based blockchains using the EOSIO RPC API. For a high-level introduction to our Swift and Java SDKs, check out our announcement on Medium: EOSIO™ Software Release: Native SDKs for Swift and Java.
To date, EOSIO SDK for Swift has only been tested on iOS. The goal, however, is for the core library to run anywhere Swift runs, adding other targets (macOS, watchOS, tvOS) as the library matures.
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.
- Installation
- Basic Usage
- iOS Example App
- Documentation
- Provider Protocol Architecture
- RPC: Using the Default RPC Provider
- Want to Help?
- License & Legal
- Xcode 10 or higher
- CocoaPods 1.5.3 or higher
- For iOS, iOS 11+*
*Note: ABIEOS Serialization Provider requires iOS 12+ at the moment.
To use EOSIO SDK for Swift in your app, add the following pods to your Podfile:
use_frameworks!
target "Your Target" do
pod "EosioSwift", "~> 0.2.1" # pod for this library
# Providers for EOSIO SDK for Swift
pod "EosioSwiftAbieosSerializationProvider", "~> 0.2.1" # serialization provider
pod "EosioSwiftSoftkeySignatureProvider", "~> 0.2.1" # experimental signature provider for development only
endThen run pod install. And you're all set for the Basic Usage example!
Transactions are instantiated as an EosioTransaction and must then be configured with a number of providers prior to use. (See Provider Protocol Architecture below for more information about providers.)
import EosioSwift
import EosioSwiftAbieosSerializationProvider
import EosioSwiftSoftkeySignatureProviderThen, inside a do...catch or throwing function, do the following:
let transaction = EosioTransaction()
transaction.rpcProvider = EosioRpcProvider(endpoint: URL(string: "http://localhost:8888")!)
transaction.serializationProvider = EosioAbieosSerializationProvider()
transaction.signatureProvider = try EosioSoftkeySignatureProvider(privateKeys: ["yourPrivateKey"])
/// Actions can now be added to the transaction, which can, in turn, be signed and broadcast:
let action = try EosioTransaction.Action(
account: EosioName("eosio.token"),
name: EosioName("transfer"),
authorization: [EosioTransaction.Action.Authorization(
actor: EosioName("useraaaaaaaa"),
permission: EosioName("active"))
],
data: Transfer(
from: EosioName("useraaaaaaaa"),
to: EosioName("useraaaaaaab"),
quantity: "42.0000 SYS",
memo: "")
)
transaction.add(action: action)
transaction.signAndBroadcast { (result) in
switch result {
case .failure (let error):
// Handle error.
case .success:
// Handle success.
}
}Alternatively, to avoid having to set the providers on every transaction, you can use the EosioTransactionFactory convenience class, as follows:
let rpcProvider = EosioRpcProvider(endpoint: URL(string: "http://localhost:8888")!)
let signatureProvider = try EosioSoftkeySignatureProvider(privateKeys: ["yourPrivateKey"])
let serializationProvider = EosioAbieosSerializationProvider()
let myTestnet = EosioTransactionFactory(rpcProvider: rpcProvider, signatureProvider: signatureProvider, serializationProvider: serializationProvider)
let transaction = myTestnet.newTransaction()
// add actions, sign and broadcast!
let anotherTransaction = myTestnet.newTransaction()
// add actions, sign and broadcast!
...Most EosioTransaction and RPC endpoint methods will return Promises if you ask them. Simply call the method with .promise as the first parameter and drop the callback. For example:
firstly {
transaction.signAndBroadcast(.promise)
}.done { _ in
// Handle success.
}.catch { error in
// Handle error.
}Utilities for key generation and management and other signing functionality can be found in the EOSIO SDK for Swift: Vault library.
If you'd like to see EOSIO SDK for Swift in action, check out our open source iOS Example App--a working application that fetches an account's token balance and pushes a transfer action.
Please refer to the generated code documentation at https://eosio.github.io/eosio-swift/ or by cloning this repo and opening the docs/index.html file in your browser.
The core EOSIO SDK for Swift library uses a provider-protocol-driven architecture to provide maximum flexibility in a variety of environments and use cases. EosioTransaction leverages those providers to prepare and process transactions. EOSIO SDK for Swift exposes four protocols. You, the developer, get to choose which conforming implementations to use.
The Signature Provider abstraction is arguably the most useful of all of the providers. It is responsible for a) finding out what keys are available for signing and b) requesting and obtaining transaction signatures with a subset of the available keys.
By simply switching out the signature provider on a transaction, signature requests can be routed any number of ways. Need a signature from keys in the platform's Keychain or Secure Enclave? Configure the EosioTransaction with the EOSIO SDK for Swift: Vault Signature Provider. Need signatures from a wallet on the user's device? A signature provider can do that too!
EOSIO SDK for Swift does not include a signature provider implementation; one must be installed separately. All signature providers must conform to the EosioSignatureProviderProtocol.
- Vault Signature Provider - Signature provider implementation for signing transactions using keys stored in Keychain or the device's Secure Enclave.
- Softkey Signature Provider - Example signature provider for signing transactions using K1 keys in memory. This signature provider stores keys in memory and is therefore not secure. It should only be used for development purposes. In production, we strongly recommend using a signature provider that interfaces with a secure vault, authenticator or wallet.
- Reference iOS Authenticator Signature Provider - Native iOS Apps using this signature provider are able to integrate with the EOSIO Reference iOS Authenticator App, allowing their users to sign in and approve transactions via the authenticator app.
The RPC Provider is responsible for all RPC calls to nodeos, as well as general network handling (Reachability, retry logic, etc.) While EOSIO SDK for Swift includes an RPC Provider implementation, it must still be set explicitly when creating an EosioTransaction, as it must be instantiated with an endpoint. (The default implementation suffices for most use cases.)
EosioRpcProviderProtocol- All RPC providers must conform to this protocol.EosioRpcProviderDefault Implementation - Default RPC provider implementation included in EOSIO SDK for Swift.- Nodeos RPC Reference Documentation - Nodeos RPC reference.
The Serialization Provider is responsible for ABI-driven transaction and action serialization and deserialization between JSON and binary data representations. These implementations often contain platform-sensitive C++ code and larger dependencies. For those reasons, EOSIO SDK for Swift does not include a serialization provider implementation; one must be installed separately.
EosioSerializationProviderProtocol- All serialization providers must conform to this protocol.- ABIEOS Serialization Provider Implementation - Serialization/deserialization using ABIEOS. Currently supports iOS 12+.
The ABI Provider is responsible for fetching and caching ABIs for use during serialization and deserialization. If none is explicitly set on the EosioTransaction, the default EosioAbiProvider will be used. (The default implementation suffices for most use cases.)
EosioAbiProviderProtocol- All ABI providers must conform to this protocol.EosioAbiProviderDefault Implementation - Default ABI provider implementation included in EOSIO SDK for Swift.
EOSIO Swift includes a default RPC Provider implementation (EosioRpcProvider) for communicating with EOSIO nodes using the EOSIO RPC API. Alternate RPC providers can be used assuming they conform to the minimal EosioRpcProviderProtocol. The core EOSIO SDK for Swift library depends only on the five RPC endpoints set forth in that Protocol. Other endpoints, however, are exposed in the default EosioRpcProvider.
Calls can be made to any of the available endpoints as follows:
rpcProvider.getInfo { (infoResponse) in
switch infoResponse {
case .failure(let error):
// handle the error
}
case .success(let info) {
// do stuff with the info!
print(info.chainId)
}
}Attempts are made to marshall the responses into convenient Swift structs. More deeply nested response properties may be presented as a dictionary.
Each response struct will also contain a _rawResponse property. In the event the returned struct is missing a property you were expecting from the response, inspect the _rawResponse. You will likely find it there.
Response structs for the alpha release are incomplete. Some responses will only return the _rawResponse. We aim to continue improving response marshalling. And we invite you to help us improve responses too.
Interested in contributing? That's awesome! Here are some Contribution Guidelines and the Code of Conduct.
We're always looking for ways to improve EOSIO SDK for Swift. Check out our #enhancement Issues for ways you can pitch in.
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 of 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. Any person using or offering this software in connection with providing software, goods or services to third parties shall advise such third parties of these license terms, disclaimers and exclusions of liability. Block.one, EOSIO, EOSIO Labs, EOS, the heptahedron and associated logos are trademarks of Block.one.
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.