0rora/0rora

Easily make, schedule, edit and respond to Stellar payments

0rora's Issues

Limit on signatures per txn

Rumour is that there is a 20 signature limit on txns. Test & adapt.

Sort payments list

Sort by any of the headers.

Change password

Logged in user must be able to change their password.

Add first-page<< & last-page >> navigation buttons

Complete the replacement of MDC with Bulma

Sidebar & login page need updating.

Retry operations that would have succeeded in failed transactions

When a transaction fails it may be due to some of the operations being invalid. In this case, the operations which would have succeeded should rejoin the queue for reprocessing. The failed operations should be marked as failed.

This issue needs some finessing. For example, a series of payments may all be OK, but fail together due to insufficient funds. In such a case, they will be retried many times with one or more being excluded each round. This is not as efficient as checking funds up-front.

Show transaction details on click

Full details of a historical transaction should expand on click (and be dismissible).

Payments from unrecognised accounts to be listed as failures

This means the op result field in DB should be expanded to include app specific states.

Do not attempt payment unless all required signatures are available.

If any signatures are missing, the payment should have a new state - TBD.

Build Docker image as release

Create user

Admin user must be able to create new users.

Destroy channel

As an admin, I want to remove the channel by closing the channel accounts and merging the balances.

Validation of CSV input

Validate CSV input. Process those rows that are OK and log anything that doesn't parse.

DB-backed local authentication.

https://github.com/pac4j/play-pac4j
https://github.com/pac4j/play-pac4j-scala-demo/tree/master/app
http://www.pac4j.org/docs/index.html

Filter payments list by account id

Sender or destination.

HTTPS for demo.0rora.com

Add source accounts

As an admin user
I want to be able to add a new source account
so that payments can be made from that account.

• Add private key via form.
• Encrypt with app secret into table
• Display added accounts (public key) in list.

Create channels

As an administrator, I want to create a set of accounts to act as channel accounts.

Give feedback to user when list navigation is delayed.

Akin to the slightly delayed toasty thing that appears when you paginate in gmail...

Link gitter chat to site & app

• in site
• in app
• update post in galactic talk
• update bio in twitter
  etc

Pagination for payments lists

Give feedback to user when CSV upload is too large.

CSV upload is too large when the form post returns 413 Request Entity Too Large.
(This can be achieved by modifying client_max_body_size 10M; in /etc/nginx/nginx.conf for example).

The Toast should indicate that the upload failed.

Use pushstate instead of # for single page navigation

https://developer.mozilla.org/en-US/docs/Web/API/History_API

Show issuer of assets

Follow well-known.toml to find the domain name of the issuer & include in payments list next to the asset code.

Update payment list contents without refresh

As payments are added to the list to be scheduled, they should appear in the list without browser refresh.

https://www.playframework.com/documentation/2.6.x/ScalaComet

Payment view counts

in the menu, the links to scheduled payments and payment history should show the counts.

if < 100: exact number
else if > < 1000: `100+`
else: `1k+`

Support federated addresses in source & destination fields.

Required enhancement to scala-stellar-sdk.

CSV upload action should present a results page.

With summary of rows imported and details of rows not imported.