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