-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix: audit gas refund logic #24
Draft
fadeev
wants to merge
36
commits into
main
Choose a base branch
from
audit-gas-refund-logic
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
36 commits
Select commit
Hold shift + click to select a range
560abc1
upgradeable wip
fadeev 9cbb94d
wip
fadeev 6b8e43c
wip
fadeev 76b927b
wip
fadeev 76ecec6
wip
fadeev 7b75695
NFT works
fadeev e56a27b
yarn lock
fadeev 3299510
Remove initialize task
fadeev c10a0c4
token contract now upgradeable
fadeev 2703523
solidity version
fadeev 2d20568
remove comment
fadeev 510ad53
gitignore
fadeev 41115ea
feat: use ZETA for gas when sending from ZetaChain (#10)
fadeev 9ca161f
rename ft contracts
fadeev a3f58ba
FT: pay with ZETA when transferring tokens from ZetaChain
fadeev 62732a3
fix: gas refund logic
fadeev ebaccbe
remove unused error
fadeev fd3d640
Merge branch 'main' into upgradeable
fadeev 9ed7830
Merge branch 'upgradeable' into audit-gas-refund-logic
fadeev fcab2fa
fix: remove fallback functions (#26)
fadeev 76b5c25
fix: added setGasLimit (#25)
fadeev 326c16b
burnable init
fadeev b5767bb
ZeroMsgValue
fadeev dcae400
nft: TokenTransfer event
fadeev a2fd412
mint: throw errors if token not found
fadeev 1d52473
UniversalTokenEvents
fadeev 9d9834e
Universal Events
fadeev f62a780
fix mint task
fadeev f61fb4f
token: fix mint
fadeev 3b9a093
fix: validate token URI (#29)
fadeev 0b208f1
fix: address validation (#28)
fadeev 565a6fe
rename tasks
fadeev 99d2b08
token: rename tasks
fadeev ae1b1d8
rename
fadeev 5dbab72
fix: make contracts pausable (#27)
fadeev d4583b3
Merge branch 'upgradeable' into audit-gas-refund-logic
fadeev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -17,3 +17,5 @@ cache_forge | |
access_token | ||
|
||
localnet.json | ||
|
||
.openzeppelin |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
// SPDX-License-Identifier: MIT | ||
pragma solidity 0.8.26; | ||
|
||
import "../evm/UniversalNFT.sol"; | ||
|
||
contract EVMUniversalNFT is UniversalNFT {} |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
// SPDX-License-Identifier: MIT | ||
pragma solidity ^0.8.26; | ||
|
||
import "../zetachain/UniversalNFT.sol"; | ||
|
||
contract ZetaChainUniversalNFT is UniversalNFT {} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i am not sure i understand this, so for example if we refund to smart contract, and it fails, lets say smart contract doesn't have receiver function by mistake - we let tx succeed even though funds are not transfered, do we then transfer funds manually?
it doesn't look like a security issue to me, would be nice to add exploit scenario to issue for better understanding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now tokens just remain in the contract. I suppose we can implement a recover function so that the owner can recover these tokens.
@0xM3R