cumulative payment units #937

hopeyen · 2024-11-26T22:05:46Z

Why are these changes needed?

Keep it consistent with the contracts

I've made sure the tests are passing. Note that there might be a few flaky tests, in that case, please comment that they are not relevant.
I've checked the new test coverage and the coverage percentage didn't drop.
Testing Strategy
- Unit tests
- Integration tests
- This PR is not tested :(

hopeyen added 17 commits November 25, 2024 17:09

temp: add v1 back

826533e

feat: disperser api v2 payment

a71ff3a

fix: precise uint64->big.Int conversion

f50af66

fix: rm v1 payment api, add paymentState to v2

1652b30

refactor: undo client side changes, focus on server

2bb6358

fix: lint

5199bef

fix: use existing signaturemethod

0894fa7

feat: add payment request validation and tests

04e19c5

fix: tests

3e86339

fix: rebase

ea7f331

refactor: rm log

8ea4f03

refactor: protobuf comments and rename

8dc8bc0

refactor: constants and comments

6edca72

refactor: dynamodb store query fn for BinRecords

f43ec36

refactor: move payments into validateDispersalRequest

f015c38

refactor: generate new proto file

a9a6f79

fix: dynamodb cumulative payment read as *big.Int

1c6c1da

hopeyen mentioned this pull request Nov 26, 2024

[v2] disperser server payments api #902

Merged

5 tasks

Base automatically changed from hope/v2-payments to master December 2, 2024 22:43