Skip to content
Permalink
Browse files

Merge pull request #200 from EOSIO/develop

Merging recent README updates into Master
  • Loading branch information...
brandonfancher committed Jun 3, 2019
2 parents f96355d + e8b3c80 commit 0cca337048af410ec43d8d78ee109e98afe3b7fc
@@ -160,6 +160,7 @@ EOSIO SDK for Swift _does not include_ a signature provider implementation; one
* [Vault Signature Provider](https://github.com/EOSIO/eosio-swift-vault-signature-provider) - Signature provider implementation for signing transactions using keys stored in Keychain or the device's Secure Enclave.
* [Softkey Signature Provider](https://github.com/EOSIO/eosio-swift-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](https://github.com/EOSIO/eosio-swift-reference-ios-authenticator-signature-provider) - Native iOS Apps using this signature provider are able to integrate with the [EOSIO Reference iOS Authenticator App](https://github.com/EOSIO/eosio-reference-ios-authenticator-app), allowing their users to sign in and approve transactions via the authenticator app.
### RPC Provider Protocol
@@ -415,7 +415,7 @@ <h1 id='eosio-sdk-for-swift-img-src-https-img-shields-io-badge-eosio-alpha-blue-
<a href="https://swift.org"><img src="https://img.shields.io/badge/Language-Swift_4.2-orange.svg" alt="Swift 4.2"></a>
<img src="https://img.shields.io/badge/Deployment%20Target-iOS%2011-blue.svg" alt=""></p>

<p>EOSIO SDK for Swift is an API for integrating with EOSIO-based blockchains using the <a href="https://developers.eos.io/eosio-nodeos/reference">EOSIO RPC API</a>.</p>
<p>EOSIO SDK for Swift is an API for integrating with EOSIO-based blockchains using the <a href="https://developers.eos.io/eosio-nodeos/reference">EOSIO RPC API</a>. For a high-level introduction to our Swift and Java SDKs, check out our announcement on Medium: <a href="https://medium.com/eosio/eosio-software-release-native-sdks-for-swift-and-java-e6086ddd37b8">EOSIO™ Software Release: Native SDKs for Swift and Java</a>.</p>

<p>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.</p>

@@ -555,6 +555,7 @@ <h3 id='signature-provider-protocol' class='heading'>Signature Provider Protocol
<ul>
<li><a href="https://github.com/EOSIO/eosio-swift-vault-signature-provider">Vault Signature Provider</a> - Signature provider implementation for signing transactions using keys stored in Keychain or the device&rsquo;s Secure Enclave.</li>
<li><a href="https://github.com/EOSIO/eosio-swift-softkey-signature-provider">Softkey Signature Provider</a> - Example signature provider for signing transactions using K1 keys in memory. <em>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.</em></li>
<li><a href="https://github.com/EOSIO/eosio-swift-reference-ios-authenticator-signature-provider">Reference iOS Authenticator Signature Provider</a> - Native iOS Apps using this signature provider are able to integrate with the <a href="https://github.com/EOSIO/eosio-reference-ios-authenticator-app">EOSIO Reference iOS Authenticator App</a>, allowing their users to sign in and approve transactions via the authenticator app.</li>
</ul>
<h3 id='rpc-provider-protocol' class='heading'>RPC Provider Protocol</h3>

@@ -613,7 +614,7 @@ <h2 id='license' class='heading'>License</h2>
<p><a href="https://github.com/EOSIO/eosio-swift/blob/master/LICENSE">MIT</a></p>
<h2 id='important' class='heading'>Important</h2>

<p>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.</p>
<p>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.</p>

<p>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.</p>

BIN +245 Bytes (100%) docs/docsets/EosioSwift.tgz
Binary file not shown.
@@ -415,7 +415,7 @@ <h1 id='eosio-sdk-for-swift-img-src-https-img-shields-io-badge-eosio-alpha-blue-
<a href="https://swift.org"><img src="https://img.shields.io/badge/Language-Swift_4.2-orange.svg" alt="Swift 4.2"></a>
<img src="https://img.shields.io/badge/Deployment%20Target-iOS%2011-blue.svg" alt=""></p>

<p>EOSIO SDK for Swift is an API for integrating with EOSIO-based blockchains using the <a href="https://developers.eos.io/eosio-nodeos/reference">EOSIO RPC API</a>.</p>
<p>EOSIO SDK for Swift is an API for integrating with EOSIO-based blockchains using the <a href="https://developers.eos.io/eosio-nodeos/reference">EOSIO RPC API</a>. For a high-level introduction to our Swift and Java SDKs, check out our announcement on Medium: <a href="https://medium.com/eosio/eosio-software-release-native-sdks-for-swift-and-java-e6086ddd37b8">EOSIO™ Software Release: Native SDKs for Swift and Java</a>.</p>

<p>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.</p>

@@ -555,6 +555,7 @@ <h3 id='signature-provider-protocol' class='heading'>Signature Provider Protocol
<ul>
<li><a href="https://github.com/EOSIO/eosio-swift-vault-signature-provider">Vault Signature Provider</a> - Signature provider implementation for signing transactions using keys stored in Keychain or the device&rsquo;s Secure Enclave.</li>
<li><a href="https://github.com/EOSIO/eosio-swift-softkey-signature-provider">Softkey Signature Provider</a> - Example signature provider for signing transactions using K1 keys in memory. <em>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.</em></li>
<li><a href="https://github.com/EOSIO/eosio-swift-reference-ios-authenticator-signature-provider">Reference iOS Authenticator Signature Provider</a> - Native iOS Apps using this signature provider are able to integrate with the <a href="https://github.com/EOSIO/eosio-reference-ios-authenticator-app">EOSIO Reference iOS Authenticator App</a>, allowing their users to sign in and approve transactions via the authenticator app.</li>
</ul>
<h3 id='rpc-provider-protocol' class='heading'>RPC Provider Protocol</h3>

@@ -613,7 +614,7 @@ <h2 id='license' class='heading'>License</h2>
<p><a href="https://github.com/EOSIO/eosio-swift/blob/master/LICENSE">MIT</a></p>
<h2 id='important' class='heading'>Important</h2>

<p>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.</p>
<p>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.</p>

<p>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.</p>

0 comments on commit 0cca337

Please sign in to comment.
You can’t perform that action at this time.