-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Refundable Crowdsale #877
Comments
Thanks for the detailed report @cwhinfrey! We will look into it. |
4 tasks
Since the suggested change breaks the API (yes we should have done this before 2.0), @nventuro suggested to create a new one that is |
ninjacrypto
added a commit
to ninjacrypto/openzeppelin-solidity
that referenced
this issue
Aug 24, 2023
…met (#1452) This attack was reported in OpenZeppelin/openzeppelin-contracts#877
ninjacrypto
added a commit
to ninjacrypto/openzeppelin-solidity
that referenced
this issue
Aug 24, 2023
…met (#1452) This attack was reported in OpenZeppelin/openzeppelin-contracts#877 (cherry picked from commit 80458ebc72f1c7c9695416edbe26690f72e406a0)
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
🎉 Description
The current implementation of RefundableCrowdsale refunds the original purchaser if the
goal
is not met. However, tokens can be transferred instantly. This opens up refundable crowdsales that do not meet their goal to the following attack:This could be prevented by pausing token transfers until the goal is reached or until the crowdsale is finalized.
It is also possible that refunds could be given as tokens are returned but it would greatly complicate the crowdsale when presale allocations and bonuses are involved.
🐛 This is a bug report.
The text was updated successfully, but these errors were encountered: