List view
The current transaction API gives users full control over the construction and submission of transactions. A higher-level API would present simplified operations that facilitate the common use-cases such as account creation and payments, without requiring the client library to be concerned with transactions, operations and network submissions.
Overdue by 5 year(s)•Due by December 31, 2019•0/2 issues closedAs a convenience, users should be able to specify that some of the mechanics of transacting via Horizon are automated. Specifically: Account sequence numbers can be automatically obtained prior to transactions being attempted. Account sequence numbers can be automatically repaired in response to a bad_seq_no error Transaction posting can be automatically retried in the presence of network failures.
Overdue by 6 year(s)•Due by September 30, 2019•0/1 issues closedMeet the SDK Minimum Requirements as specified by the SDF. The SDK meets most of the proposed SDK requirements. Remaining work: * Add TradeAggregations endpoint * Add FindPaymentPaths endpoint * Complete TOML support. (Currently it is supported only to the extent required by Federation) * Update documentation to include supported protocol and Horizon versions
Overdue by 6 year(s)•Due by September 30, 2019•5/8 issues closed