Django-polaris

Update: this version will not run properly for SEP-24 deployments. Use version 1.6.2 or higher.

Update: this version will not run properly for SEP-24 deployments. Use version 1.6.2 or higher.

Features

- SEP-6,24,31: Allow source and destination accounts to differ from the SEP-10 authenticated account
- This means `Transaction.stellar_account` may not match `Transaction.to_address` or `Transaction.from_address`
- SEP-6,24: Add the `features` object to `GET /info` response bodies
- SEP-24: Update the `more_info.html` templates labels to be more user-friendly
- SEP-24: Add asterisks to require field labels
- SEP-24: Allow custom titles for the `more_info.html` and `error.html` templates

Database Migrations

- Added the `Transaction.amount_expected` column
- This column can be used to detect that the client sent an amount that differs from the amount they specified in a form or API call

Miscellaneous

- Moved all JavaScript code from Polaris' HTML templates to script files

Breaking Changes

- Downgrades `psycopg2-binary` to `<2.9`
- Django 2.2 is incompatible with pyscopg2 2.9 [1293](https://github.com/psycopg/psycopg2/issues/1293)

Bug Fixes

- SEP-24: when the TransactionForm's amount field was provided an initial value, the fee table would not be updated on page load, but is now

Bug Fixes

- Fixes the fee calculation logic for the SEP-24 UI
- This bug affected anchors that do not have a custom fee integration function.

Features

- SEP-6: Added `PATCH /transactions` endpoint and integration function.
- SEP-24: Added the ability to add a `type` field to `TransactionForm`s.
- SEP-24: Allow anchors to place transactions in `pending_anchor` after collecting KYC information.
- SEP-24: Added support for hidden fields in forms.
- SEP-24: Added `ADDITIVE_FEES_ENABLED` environment variable and setting
- SEP-12: Added `POST /customer/verification` endpoint and integration function. Also updated `GET /customer` response format to support the new `"provided_fields"` object.
- SEP-10: Update JWT's to be deterministic based on the challenge transaction provided in the request.

Database Migrations

- The `blank=True` keyword argument was added to `Asset.distribution_seed`, `Transaction.completed_at`, `Transaction.paging_token`, and `Transaction.protocol`.
- This option allows these fields to be saved without a value in forms. It also allows `None` values to be stored as `''` in database character and text fields instead of using `NULL` values.

Bug Fixes

- SEP-24: If 7 decimal places are needed to denominate an `Asset`, the `more_info.html` template would render the amounts using exponent notation. This is no longer the case.
- SEP-24: Removed `"transaction"` and `"transactions"` objects from `GET /info` response, which were not a part of the protocol.
- SEP-9: Fixed a typo in the hard-coded `photo_proof_address` field used for detecting request parameters
- SEP-6, 24, 31: `GET /info` responses no longer include `min_amount` and `max_amount` attributes if they have been updated to be different than the default values.
- Fixed transaction sequence number error for `testnet reset` subcommand, occurring when setting the home domain of a Stellar account.
- SEP-10: `POST` requests missing a `"transaction"` object no longer cause 500 responses

Dependencies

- Upgrades `stellar-sdk` to `2.13.0`, compatible with Protocol 17