@bumi, @hueso: I resolved the question about token number resolution. It has to be WEI for ERC20 and wallet display, but we use integers as uint32 for all other kredits amounts internally. Ready for review/merge!
@bumi, @hueso: I resolved the question about token number resolution. It has to be WEI for ERC20 and wallet display, but we use integers as `uint32` for all other kredits amounts internally. Ready for review/merge!
hueso
approved these changes 2022-08-29 20:10:01 +00:00
raucao
merged commit fd012d5359 into feature/export-import2022-08-30 08:53:55 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
closes #184
@bumi, @hueso: I resolved the question about token number resolution. It has to be WEI for ERC20 and wallet display, but we use integers as
uint32for all other kredits amounts internally. Ready for review/merge!@@ -149,0 +164,4 @@uint32 amountWithdrawable = confirmedKredits - c.kreditsWithdrawn;require (amountWithdrawable > 0, "No kredits available");c.kreditsWithdrawn += amountWithdrawable;wondering if we should add an
assert(c.kreditsWithdrawn <= confirmedKredits)?That's just the same as the line above, where
confirmedKredits - c.kreditsWithdrawnis required to be> 0, no?