Skip to content

Conversation

@moritzkiefer-da
Copy link
Contributor

@moritzkiefer-da moritzkiefer-da commented Jan 13, 2026

[ci]

Pull Request Checklist

Cluster Testing

  • If a cluster test is required, comment /cluster_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If a hard-migration test is required (from the latest release), comment /hdm_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.

PR Guidelines

  • Include any change that might be observable by our partners or affect their deployment in the release notes.
  • Specify fixed issues with Fixes #n, and mention issues worked on using #n
  • Include a screenshot for frontend-related PRs - see README or use your favorite screenshot tool

Merge Guidelines

  • Make the git commit message look sensible when squash-merging on GitHub (most likely: just copy your PR description).

@moritzkiefer-da moritzkiefer-da force-pushed the cocreature/no-fees branch 13 times, most recently from 70beefa to 4c95333 Compare January 20, 2026 10:09
@moritzkiefer-da moritzkiefer-da force-pushed the cocreature/no-fees branch 2 times, most recently from a30125c to cbca1ff Compare January 20, 2026 12:48
)
}

"don't collect rewards if their collection is more expensive than they reward in amulets" in {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this check does nothing now that you don't pay fees

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We may want to consider adding a check for rewards that are too small probably just some configurable amount that roughly approximates traffic cost. But that seems orthogonal to this change.

Copy link
Contributor

Choose a reason for hiding this comment

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

I guess we are lacking the protection wrt spending more traffic to collect the rewards than they are worth. That said: fine to postpone, as that goes away with the app rewards being accumulated directly by the DSO.

)
}

"don't collect rewards if their collection is more expensive than they reward in amulets" in {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We may want to consider adding a check for rewards that are too small probably just some configurable amount that roughly approximates traffic cost. But that seems orthogonal to this change.

)
}

"generate app rewards correctly" in { implicit env =>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Just doesn't make much sense to integration test this and we have daml script tests for it.

Copy link
Contributor

Choose a reason for hiding this comment

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

agreed

}
}

"generate rewards for subscriptions" in { implicit env =>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

no point in integration testing this and it's kind of pointless as a test anyway, who cares if the DSO gets an app reward coupon …

Copy link
Contributor

Choose a reason for hiding this comment

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

agreed.

@moritzkiefer-da
Copy link
Contributor Author

@meiersi-da Finally got all the tests green so should be ready for a review. Not urgent

Copy link
Contributor

@meiersi-da meiersi-da left a comment

Choose a reason for hiding this comment

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

Very nice! What a monumental effort. Thank you! Glad it also burns 2k LoCs 🔥

)
}

"don't collect rewards if their collection is more expensive than they reward in amulets" in {
Copy link
Contributor

Choose a reason for hiding this comment

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

I guess we are lacking the protection wrt spending more traffic to collect the rewards than they are worth. That said: fine to postpone, as that goes away with the app rewards being accumulated directly by the DSO.

)
}

"generate app rewards correctly" in { implicit env =>
Copy link
Contributor

Choose a reason for hiding this comment

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

agreed

}
}

"generate rewards for subscriptions" in { implicit env =>
Copy link
Contributor

Choose a reason for hiding this comment

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

agreed.

(unlockedBalance, _) <- userWalletStore.getAmuletBalanceWithHoldingFees(
round,
deductHoldingFees = deductHoldingFees,
deductHoldingFees = false,
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: any reason to not remove the parameter altogether?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

let me take a quick look how easy it is to nuke it

[ci]

Signed-off-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org>
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