https://github.com/stellar/java-stellar-anchor-dev/blob/main/src/main/java/org/stellar/anchor/sep24/Sep24Service.java#L73
https://github.com/stellar/java-stellar-anchor-dev/blob/main/src/main/java/org/stellar/anchor/sep24/Sep24Service.java#L170

Refer to https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#request for how to process asset_issuer correctly.

What problem does your feature solve?

Since the fields used in payment-* implementations may not relate 100% 1:1 with the PaymentsService interface, we should have go-to documentation where devs can go to look for examples.

What would you like to see?

A javadoc or a *.md file where users can quickly understand how to use the payments sdk.

What alternatives are there?

❓

This is the description of the issue

What problem does your feature solve?

When a call to the Circle API returns an unexpected response body with an ok status code, it's treated as a successful API call.

What would you like to see?

Unexpected response bodies should be detected and handled as an internal error.

What alternatives are there?

N/A

Cc @JakeUrban

• Implement ping() method.
• Implement getDistributionAccountAddress() method.
• Implement getAccount(String accountId) method.
• Implement createAccount(String accountId) method.
• #40
  • Payment history for CircleWallet->CircleWallet transfers.
  • Payment history for CircleWallet->Stellar transfers.
  • Payment history for Stellar->CircleWallet transfers.
  • Payment history for CircleWallet->BankWire transfers.
  • #87
  • Pagination
• Implement sendPayment(Account sourceAccount, Account destinationAccount, String currencyName, BigDecimal amount) method.
  • #3
  • #21
• #57
  • Instructions to receive CircleWallet<-CircleWallet deposits.
  • Instructions to receive CircleWallet<-Stellar deposits.
  • Instructions to receive CircleWallet<-BankWire deposits.
    • #86
• Polishes
  • #2
  • #26
  • #27
  • #84
  • #88
• #65

Implement writing of Events to a queue (Kafka/SQS) in the anchor platform
Implement reading of Events from a queue (Kafka/SQS) in the anchor reference server
Deploy single instance Kafka in SDF K8s env for the anchor platform to utilize

• #157
• #155
• #160
• #193
• #167
• #169
• #173
• #175

GanttStart: 2022-02-22
GanttDue: 2022-03-12

stellar-anchor-platform will be on Gradle. We should convert Maven to Gradle build.

example-spring-webflux subproject will be an example code for anchor who choose to use anchor-sdk with Spring WebFlux implementation

From @marcelosalloum :
FYI: assertThrows will return an instance of the thrown exception that you could use to verify the exception values, like in:

val thrown = assertThrows<HttpException> { request.block() }
assertEquals(HttpException(400, "Request body contains unprocessable entity.", "2"), thrown)
Also, assertEquals only works if the Exception implements the .equals(Object) method, which can be generated by @lombok.Data.

@lijamie98 would like to review all assertThrows in the tests.

https://github.com/stellar/java-stellar-anchor-sdk/blob/preview/src/main/java/org/stellar/anchor/sep24/Sep24Service.java#L394

Original discussion thread: https://stellarfoundation.slack.com/archives/CHVFR99UJ/p1643305002018700

• #89
• Add a swagger documentation for the endpoints
• Add API tests
• TODO: add further sub-tasks?

Core Module, Reference Server Implementation and Callbacks
GanttStart: 2022-03-14
GanttDue: 2022-04-15

Scaffold Spring application with the following features.

1. Spring application
2. Enable property configuration read from application.properties
3. Stubbed sep-12 controller
4. Stubbed sep-12 service layer
5. Stubbed sep-12 DTOs (request and response)
6. JPA access
7. SQLite driver

As an Anchor Engineering developer, I want to implement SEP-38 protocol core module such that the SEP-38 Anchor Tests: anchor-tests.stellar.org passes when run against the anchor platform service.
GanttStart: 2022-03-14
GanttDue: 2022-04-01

Tasks:

• #74
• #75
• #76
• #77
• #78
• #79
• #81
• #80
• #135
• #137
• #116

What

Based on this thread we should conclude about validating sender and receiver accounts prior to making a payment.

Why

We need to define if we want the SDK to take the responsibility of failing fast or if we prefer to send the results to the caller.

Cc @JakeUrban

Add the jitpack badge to show the latest version available on jitpack.io
Add the Github workflow CI badge to show the latest status of GH CI.

Design the interfaces the core module will use to initiate Callback API and Event API requests for the Anchor Platform.

example-spring-mvc subproject will be an example code for anchor who choose to use anchor-sdk with Spring MVC implementation.

What problem does your feature solve?

The Account class is used in two contexts:

• the id (and idTag) attributes be used as an identifier
• the Account's data (balances & capabilities) is needed for processing

The payment service package does not communicate whether Account objects used throughout the package's API contract require or will contain the account's data.

This means that users of the package, and the package's other methods, must commonly check for whether or not this data is present and load it if necessary.

To make this situation easier, we should do the following:

• Ensure methods using Account objects always have documentation on whether the account's data will be present
• Provide helper methods that load this data when necessary

What would you like to see?

Added Account.loadBalances() and Account.loadCapabilities() methods.

There also must be a way to indicate that this data has not been loaded. One way to do this is to make Account.balances and Account.capabilities nullable. However, because some types of accounts can have no balances, using this as a condition of whether or not data has been loaded will not suffice.

as an anchor platform developer I would like a common interface and management library for configure management using different config sources. This should initially support file based configuration.

As an Anchor Engineering developer, I want to implement SEP12 protocol core module for clients to upload KYC (or other) information to anchors integrating with the Anchor Platform.
GanttStart: 2022-02-22
GanttDue: 2022-03-12

example-micronaut subproject will be an example code for anchor who choose to use anchor-sdk with Micronaut implementation

The MGI StellarAdapterService was based on git submodule source code integration. We will need to convert their project to integrate with the anchor-sdk.

As an Anchor Engineer I want to access database through a shared platform module.

1. Create Sep-31 endpoints in platform.
2. Implement Sep-31 service in core.
3. Define anchor integration interface without implementation.

Anchor Platform API (Anchor to Platform)
GanttStart: 2022-03-14
GanttDue: 2022-04-04

Create the anchor platform configuration management interface so development of modules can begin using without configuration management backend implementations.

Implement the Java classes necessary to represent the schemas for the APIs mentioned in the title.

These classes will belong to its own subproject so they can be reused by anchors who must implement the other side of the given API. @lijamie98 will create the subproject.

Apply Google Java Format at git commit.
https://github.com/google/google-java-format

jitpack.io now works with stellar as the groupId. We need to research if it works with org.stellar as the groupId.

Currently, the JWT is only validated against the signature. The Sep10TokenFilter should validate more values in the JWT.

1. CLIENT_DOMAIN should match if it exists.
2. TransactionId should exist.
3. The issuer should match host_url.