Releases: kinecosystem/kin-android
v2.1.2
v2.1.1
v2.1.0
2.0.0
1.0.1
- contains a couple bug fixes from 1.0.0 to enforce account creation is only performed when the address for an account provided is not found.
1.0.0 RC1
This release cleans up several things now that the migration to Solana has been completed and items to improve the developer and user experience have been identified and developed as per the Technical Roadmap post here https://kin.org/technical-roadmap-through-migration-completion/.
Removed
- all stellar code outside of the KeyPair class & .stellarBase32Encode() stringify key functions for posterity & debugging
- base-compat has been shaved down to only backup & restore UI which now directly sits upon
:base
Added
- Associated Account support (https://spl.solana.com/associated-token-account)
- Token Account Merging on
KinAccountContext
initialization if necessary - Supports creating a token account on send if the destination does not yet have a kin token account
- sign + submit have been broken up into 2 rpc calls to agora so that TransactionHash is always present (non-zero) and can be used to fetch transaction status in the case it does not respond
...and more.
Additional release notes & documentation around 1.0.0 coming soon ™️
Milestone 4 - Kin on Solana Release
Release Notes
-
Public Interface Changes
-
AccountSpec addition as an option in sendPayments (used by payInvoice & sendPayment - defaults to Preferred)
-
Exact: Use the EXACT account address specified and only that. Fail otherwise.
-
Preferred: PREFER to use the account address I specify, but if that does not exist, resolve the tokenAccounts for this account and use the first one.
-
-
Functional Changes
-
Addition of v4 agora gRPC apis to submit Kin transactions to the Solana blockchain
-
V4 agora apis can use resolved token accounts according to the source or destination AccountSpec: see AccountSpec definitions in Public Interface Changes above
-
Addition of KinServiceWrapper to upgrade from v3->v4 agora apis to facilitate the Solana migration based on the response of getMinimumBlockchainVersion rpc
-
Both base and base-compat have the ability to migrate to Kin on Solana
-
Base-compat continues to use text based memos
-
Base continues to use KinBinaryMemo memos
-
The Demo app now defaults to having the migration process on with .testMigration()
-
-
Solana Migration Notes:
-
You have the ability to test out solana migration by setting
-
.testMigration() on KinEnvironment instances in base or setting KinClient.testMigration() before creating any KinClient instances.
-
.setMinApiVersion() on KinEnvironment instances in base allows developers to force which api version the KinService should use either 3 for stellar or 4 for solana.
-
It is not required to set this as we default to 3 until migration day to solana.
-
KinLogger now outputs [V3] or [V4] on request & response pair print outs to the system log. You can tell that your traffic is on solana if you’re seeing V4 traffic.
-
See AccountSpec changes above
-
KinService.testService is now updated with an airdrop RPC for Solana which replaces FriendBot that you can use to fund your account with more test Kin
-
Read here for more information about the migration.
-
Milestone 2 Release
- support for Agora KinEnvironment (optional in base, configured by default in base-compat)
- invoice support
- spend library
- design library
- design-showcase apps
- updated demo app