Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PARTNER-329] SEP-6/24: Add new user_action_required_by transaction field #1484

Merged
merged 4 commits into from
May 8, 2024

Conversation

Ifropc
Copy link
Contributor

@Ifropc Ifropc commented May 8, 2024

Add optional user_action_required_by field. This field should be used to show the time anchors gives for the user to make an action before transaction will automatically expire or be refunded. In certain statuses, such as pending_user_transfer_start or incomplete, anchor waits for the user before advancing transaction to the next status. Using new user_action_required_by field, anchor indicates the deadline of the action to take place. Anchor should specify the action waited on using message or more_info_url. user_action_required_by should only be set for the statuses that will lead to anchor automatically setting transaction to the next status (such as expired/refunded) once the deadline is reached, and should be not set (or set to null) in all other cases.

Also added missed on_hold field to SEP-6 transaction

@Ifropc Ifropc requested review from CassioMG and JakeUrban May 8, 2024 00:12
Copy link
Contributor

@CassioMG CassioMG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great UX improvement

Copy link
Contributor

@JakeUrban JakeUrban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks pretty good, just looking to see some more context added to the field description

ecosystem/sep-0006.md Outdated Show resolved Hide resolved
@Ifropc Ifropc changed the title [PARTNER-329] SEP-6/24: Add new action_required_by transaction field [PARTNER-329] SEP-6/24: Add new user_action_required_by transaction field May 8, 2024
@Ifropc Ifropc enabled auto-merge (squash) May 8, 2024 21:20
@Ifropc Ifropc requested a review from JakeUrban May 8, 2024 21:20
@Ifropc Ifropc merged commit ade0bf7 into master May 8, 2024
3 checks passed
@Ifropc Ifropc deleted the PARTNER-329-anctio-required-by branch May 8, 2024 22:29
Ifropc added a commit to stellar/anchor-platform that referenced this pull request May 17, 2024
### Description

- Add new field `user_action_required_by` to SEP-6/24/31 transactions
and related DB entries.
- Added configuration option for SEP-6 and SEP-24 to set initial value
on transaction creation.
- Added support for related RPC requests to update this field.
- Added ability to query platform transactions sorted by
`user_action_required_by` field

### Context

Implements stellar/stellar-protocol#1484

### Testing

- `./gradlew test`
- New test cases covering all new features

### Documentation

https://stellarorg.atlassian.net/browse/ANCHOR-688
https://stellarorg.atlassian.net/browse/ANCHOR-704

### Known limitations

N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants