Closed dennis00010011b closed 6 years ago
This is weird, I've beeing trying to reproduce the bug (with the code in branch 2.0
and with the code from PR #1065), and no luck, everything seems to work fine today :confused:
@dennis00010011b Can you confirm this?
I'm using Ropsten.
The crowdsales addresses:
2.0
: 0xb04a586a5d36b2811f32a116d345ac9b5a81d922
PR #1065
: 0xbf4a10b84686d0c493bfbc49fe41b8da89edc074
@fernandomg Hm.. I can't reproduce with 2.0: 0xb04a586a5d36b2811f32a116d345ac9b5a81d922
But it still reproducible with 2.0: 0xce4c704c3af8f359929ed09d3fe3739913d5e263
@fernandomg
Cause of this issue is that I used supply
=100 but some whitelisted addresses have maxCap
> 100 . That's why maxContribution
field less than maxCap
for some addresses . For avoid such cases we need the validation of whitelisted addresses : minCap
should be less than supply
@dennis00010011b really good catch! thanks!
To fix this issue, allow a whitelisted account's maxCap
to be not greater than the tier's supply
Steps:
3 .Finish deployment
Expected result:
Actual result:
If you are reporting a problem with Token Wizard, please include the following information:
Which network did you use? (Mainnet, Kovan, Rinkeby, etc.)
Ropsten
If you were able to create it, what is the URL of your crowdsale?
proxyID 0xce4c704c3af8f359929ed09d3fe3739913d5e263
Do you have screenshots showing the problem?
Do you see errors in the dev console? If yes, please include a screenshot
No