🐞 Gas Error when Submitting Inflation & BUIDL Balance not showing

Describe the bug

Two bugs shown in image above.

1. BUIDL balance does not show on the DFO screen, reads as a balance of 0, when the account has BUIDL.

2. I get an error when trying to query the inflation function. It reads an error about gas.

Expected behavior

To show balance

and

To allow me to query and submit inflation without gas error.

complete the following information):**

MetaMask

Reward

4. ETH Wallet:

0x58aa4075099bd491a49f3a21807f37f275ad2e3f

[alet89]

2. "I get an error when trying to query the inflation function. It reads an error about gas."

That's normal because the fair inflation function is set to be callable every 100800 blocks. Last fair inflation event was done at the block 10211296, so you can query the function from the block 10312096 https://etherscan.io/block/countdown/10312096. Metamask reply with the gas error, because it's a general error and they set this error by default to some advanced errors.

1. "BUIDL balance does not show on the DFO screen, reads as a balance of 0, when the account has BUIDL."

🤔 This is strange have you signed your wallet to Metamask? Because I'm trying to reproduce your behavior, but It works fine for me... Can you share more detailed info...

My BUIDL is now showing. However when I switch between an account in the same Meta Mask it stays stuck on the balance of the account that is loaded when going to the DFOhub.

Not sure how I got the 0 balance to show the first time.

Edit: I think how I got the 0 balance was by accepting the permission from DFOhub, then went to DFO dapp. The second time it showed since I relogged with the permission being accepted, so it registered the balance.

To replicated a new account without permissions, then go to DFOhub and it will show 0 balance for account, till relogged?

[vasapower]

@NovedNav To know at any time when to submit the next Fair Inflation operation by yourself, you can switch to the State tab of DFOhub and have a look at the value of the 'lastSwapBlock' variable and add the value of the 'swapBlockLimit' variable. You will obtain the next block deadline @alet89 was talking about.

[alet89]

Thanks for the bug report, it's not a risky bug, we have scheduled to fix that during the Uniswap integration release

Bug Report Reward done: https://etherscan.io/tx/0x930db14d80a70b2f8e75658755ff7dc61d4d0688a634accee421ca3d34ccbcea