You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an idea following on from launching the development version of Loot DAO and @jdville03 's note that we won't be able to currently display a balance amount in the token badge for an "external" ERC20 token, i.e. not tracked and managed via the DAO's ERC20 token Extension contract.
Is it possible for us to make the token badge component display the balance of an ERC20 token from the actual contract, which is not tracked by our Tribute ERC20 token Extension?
Maybe adding a render prop to render the result of a hook's (or no hook) function call to balanceOf? Or by perhaps making another similar hook/component to the one currently use?
We could add some kind of config to conditionally render the correct stuff, maybe via env var, to keep the code more generic. E.g. env var as stringified JSON SOME_UI_TOKEN_CONFIG="{"type": "external", "symbol": "AGLD"}" , or separate the env vars data.
This is an idea following on from launching the development version of Loot DAO and @jdville03 's note that we won't be able to currently display a balance amount in the token badge for an "external" ERC20 token, i.e. not tracked and managed via the DAO's ERC20 token Extension contract.
Is it possible for us to make the token badge component display the balance of an ERC20 token from the actual contract, which is not tracked by our Tribute ERC20 token Extension?
Maybe adding a render prop to render the result of a hook's (or no hook) function call to
balanceOf
? Or by perhaps making another similar hook/component to the one currently use?We could add some kind of config to conditionally render the correct stuff, maybe via env var, to keep the code more generic. E.g. env var as stringified JSON
SOME_UI_TOKEN_CONFIG="{"type": "external", "symbol": "AGLD"}"
, or separate the env vars data.cc: @jdville03 @sophiacodes
The text was updated successfully, but these errors were encountered: