Replies: 1 comment
-
all good and fixed. the problem was with my business logic... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi guys.
I am really having a hard time understanding this..
Let's look at this line - https://github.com/aragon/govern/blob/17552b1eecf1c79d2a9799c79ed1d2b6df9dbe76/packages/govern-core/contracts/pipelines/GovernQueue.sol#L178
So, what it does is very simple and the below line does
transferFrom
onfeeToken
.Scenario where it fails.
feeToken
for the above contract.challenge
function and it fails withbad fee pull
.Note: I am 100% sure that
feeAmount
thatgetDisputeFees
returns is 150 + 18 times 0.The way it fails is that ethers.js doesn't even open metamask to initiate transaction, it immediatelly returns an error.
Scenario Where it succeeds.
I approve 160 + 18 times 0 and then, it succeeds(transaction appears on metamask) and everything is corrct.
I wonder what really happened for the failing scenario ? this woudln't happen a month ago at all.
@ricmoo @zemse
Beta Was this translation helpful? Give feedback.
All reactions