Skip to content

libxc: VWAP overflow fix - #3299

Merged
JoeGruffins merged 1 commit into
decred:masterfrom
martonp:orderbookOverflow
Jun 27, 2025
Merged

libxc: VWAP overflow fix#3299
JoeGruffins merged 1 commit into
decred:masterfrom
martonp:orderbookOverflow

Conversation

@martonp

@martonp martonp commented Jun 25, 2025

Copy link
Copy Markdown
Collaborator

The VWAP calculation was multiplying uint64 rates and quantities to keep track of a weighted total. This could result in a uint64 overflow. The calculation is updated to use big.Int instead.

The VWAP calculation was multiplying uint64 rates and quantities
to keep track of a weighted total. This could result in a uint64
overflow. The calculation is updated to use `big.Int` instead.
@JoeGruffins
JoeGruffins merged commit 0c77996 into decred:master Jun 27, 2025
5 checks passed
martonp added a commit to martonp/dcrdex that referenced this pull request Jul 8, 2025
The VWAP calculation was multiplying uint64 rates and quantities
to keep track of a weighted total. This could result in a uint64
overflow. The calculation is updated to use `big.Int` instead.
buck54321 pushed a commit that referenced this pull request Jul 26, 2025
The VWAP calculation was multiplying uint64 rates and quantities
to keep track of a weighted total. This could result in a uint64
overflow. The calculation is updated to use `big.Int` instead.
JoeGruffins pushed a commit to JoeGruffins/dcrdex that referenced this pull request Oct 7, 2025
The VWAP calculation was multiplying uint64 rates and quantities
to keep track of a weighted total. This could result in a uint64
overflow. The calculation is updated to use `big.Int` instead.
JoeGruffins pushed a commit to JoeGruffins/dcrdex that referenced this pull request Oct 13, 2025
The VWAP calculation was multiplying uint64 rates and quantities
to keep track of a weighted total. This could result in a uint64
overflow. The calculation is updated to use `big.Int` instead.
buck54321 pushed a commit that referenced this pull request Oct 17, 2025
The VWAP calculation was multiplying uint64 rates and quantities
to keep track of a weighted total. This could result in a uint64
overflow. The calculation is updated to use `big.Int` instead.
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.

2 participants