Skip to content

Releases: jillesvangurp/stellar-kotlin-client

First release from jillesvangurp/stellar-kotlin-client

24 Jan 12:25
Compare
Choose a tag to compare

This is the first release after moving the code from the old Inbot repository.

  • The project has been renamed to stellar-kotlin-client
  • updated a lot of the dependencies and use the latest java client for Stellar
  • Some minimal tweaks to address compatibility issues with the new version of the java client & gradle issues

Update java stellar & other deps

24 Jan 11:47
Compare
Choose a tag to compare
Pre-release

DON'T USE; I messed up the maven publish config in this one

Upgrade to java sdk 0.9.0

18 Jul 11:13
Compare
Choose a tag to compare

Upgrade dependency and fix some api breakage.

  • On the Kotlin side there are no API compatibility breaking changes and things should work as they used to; with the exception of the java specific things that changed in the Java sdk.
  • io.inbot.kotlinstellar.KotlinStellarWrapper.trades() now takes an optional publicKey parameter that defaults to account.accountId if you don't specify it.

Upgrade to java sdk 0.8.0

01 Jul 09:47
Compare
Choose a tag to compare
  • use java sdk 0.8.0
  • fix network handling now that the java sdk no longer uses global variables for that
  • update other dependencies as well

Upgrade to java sdk 0.7.0

17 May 11:01
Compare
Choose a tag to compare
  • latest java sdk
  • fix deprecation issues
  • AccountResponse.pagingToken seems to have disappeared, so commenting that out for now.

Fix Npe

26 Mar 13:11
Compare
Choose a tag to compare
v0.9.5

fix npe

fix retry on timeout by using correct sequence nr

25 Mar 13:34
Compare
Choose a tag to compare

Sequence number was mismatching because building a transaction increments it client side. Since it was not changed server side, safe to retry.

fix exception on retry

20 Mar 09:07
Compare
Choose a tag to compare

Now simply gives up with another exception. TODO, we need a more robust retry strategy.

Java sdk 0.6.0 and improved transaction retry

27 Feb 16:44
Compare
Choose a tag to compare
  • update dependencies
  • improve transaction retries and error logging around that

Depend on latest stellar sdk, no more forks

23 Jan 13:20
Compare
Choose a tag to compare

Beta release.

The stellar kotlin wrapper, exposes the full power of the Java SDK and adds convenience, sane defaults that you can override, and safety. The Java SDK offers you all the primitives you need for interacting with stellar but it can be a bit boilerplate heavy and using it in a responsible way requires yet more boiler plate.

At this point the library should be usable for production code. We plan to keep the API stable but may still need to do small changes.

So, go and use it. Give us feedback. File issues. Or just let us know what you think.

Changes

This release updates dependencies and not much else

  • java-stellar-sdk 0.4.1, with our PR merged (thanks @bartek) . This means no more jersey dependencies.
  • All other dependencies have been updated as well
  • there are no functional changes in this release.

Development Status

  • We have been using version of this library at inbot for several months without issues. Hundreds of stellar transactions have been processed.
  • We have are currently juggling many projects and I've done less work on this lately than I hoped. However, we continue to intend to support this and build this out.
  • We have support for most but not all operation types in Stellar. You can still use those but it may need more boiler plate. Support here simply means that a convenient method is available in the wrapper. You can still benefit from this library by using the extension methods for doing transactions with retries, error handling, etc. taken care off.
  • cliste remains awesome but needs more work and will likely move to its own repository as soon as I can find the time to do that.
    • it needs support for remaining things in the sdk not covered yet
    • I'd like to make the output more consistent and disable info logging
    • I'd like to introduce json output to facilitate scripted usage