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.

Sign up for GitHub

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

Jump to bottom

About the maximum time for aggregate bonded transactions. #969

Open
bootarou opened this issue Mar 17, 2024 · 1 comment
Open

About the maximum time for aggregate bonded transactions. #969

bootarou opened this issue Mar 17, 2024 · 1 comment
Assignees
@Jaguar0625
Labels
catapult Related to the C client, catapult. Status: WIP This issue or PR is a work in progress. Type: Bug Not the ladybug kind, but the software gremlin kind.

Comments

@bootarou
Copy link

I don't think it's practical to set the AggregateBond duration to a maximum of 48 hours.
I think need 10 days. Japan's Specified Commercial Transactions Law provides for an eight-day cancellation period.
@bootarou bootarou added catapult Related to the C client, catapult. Status: WIP This issue or PR is a work in progress. Type: Bug Not the ladybug kind, but the software gremlin kind. labels Mar 17, 2024
@trestoJP
Copy link

If possible, I thought that versatility would be expanded if the aggregate bonded period could be selected or set arbitrarily, and the amount of XYM locked by HashLockTransaction would increase depending on the length.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Jaguar0625 Jaguar0625

Labels
catapult Related to the C client, catapult. Status: WIP This issue or PR is a work in progress. Type: Bug Not the ladybug kind, but the software gremlin kind.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Jaguar0625 @gimre-xymcity @bootarou @Wayonb @trestoJP @0x6861746366574