What version are you using?

What did you do?

curl -v -H "Accept: text/event-stream" "https://horizon.stellar.org/accounts/GAFNBDOZBFUKHB4ZY5ANC

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
All the files in src/ are using TS while the files in test are not. For consistency we should be using TS too in tests files, it will also let us dog food on our types.

A nice side effect of this is that we can start using modules in tests, that way we don't have to define in glo

Lets say price of foocoin is 0.1. If user tries to buy foocoin at 0.801, don't let them.

This is for market taking only. If they are trying to sell foocoin at 0.0001, thats fine because they are making and not taking any orders.

In classes like Address, its unclear what properties such as balances flags or most other fields actually contain. For example I'm not sure if balances is an array or a dict, and im not sure what properties the values inside of it contain. It's also unclear if inflation_destination is a public key string or an Address type.

Documentation should clarify what the shapes and types of all

When dealing with amounts in stellar, you're dealing with them as a string. This can lead to difficulty checking equality (or comparison). There are many wrong was to do this such as
Float(str1) == Float(str2)
BigDecimal(str1).equals(BigDecimal(str2))
Other creatively wrong ways

It seems the right way is to use

public static boolean equalAmounts(String amount1, String amount2)

Create a view for setting the app password. Show it if there is no app password set yet (and feature flag for now!) right after the T&Cs screen.

Nice to have: Ask user about whether to enable biometric authentication in a second step if biometric auth is available. If so, perform biometric auth and update app launch auth policy.

• overview of what this is
• how it install this
• where is the DB kept?
• how do you set the config?
• How do you connect horizon to this?

Currently balances are shown for all created trustlines but there is no mention if one of them is unauthorized.

There is an issue open to add the authorize state in the account endpoint in horizon: stellar/go#159

stellar/laboratory#363 (comment):

state is a term of art in React, so I avoid using that as the name. It might have been clearer to name this prop 'signatureCheckState' or something.

Produce generated documentation with up-to-date export schemas and man pages.

The server must be reloaded when the public/private keys are modified. This prevents the need of an external mechanism/script to reload the server when we update keys, for example when using Let's Encrypt.