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

Isolate address pool to prevent excessive address creation #191

Merged
merged 1 commit into from
Apr 19, 2016

Conversation

cjepson
Copy link
Contributor

@cjepson cjepson commented Apr 19, 2016

Automatic ticket purchases by the wallet could cause excessive usage
of the default account internal branch because the address for the
split transaction outputs was created using the exported new address
function for the wallet. The API for txToOutputs has been modified and
a new function that calls it, TxToOutputs, created. This new function
does all the locking required, so that the internal function txToOutputs
may be called by other functions in wallet that already have the
relevant locks held.

Automatic ticket purchases by the wallet could cause excessive usage
of the default account internal branch because the address for the
split transaction outputs was created using the exported new address
function for the wallet. The API for txToOutputs has been modified and
a new function that calls it, TxToOutputs, created. This new function
does all the locking required, so that the internal function txToOutputs
may be called by other functions in wallet that already have the
relevant locks held.
@alexlyp
Copy link
Member

alexlyp commented Apr 19, 2016

tACK looks good

@jcvernaleo
Copy link
Member

Looks fine to me (but only very light testing on my part).
utACK

@jcvernaleo jcvernaleo merged commit 4e689d6 into decred:master Apr 19, 2016
beansgum pushed a commit to beansgum/dcrwallet that referenced this pull request Jun 10, 2021
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.

3 participants