Skip to content
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

Recover assets from vault in Aragon #70

Open
daviddavo opened this issue Mar 30, 2022 · 6 comments
Open

Recover assets from vault in Aragon #70

daviddavo opened this issue Mar 30, 2022 · 6 comments
Labels
cache-scripts help wanted Extra attention is needed

Comments

@daviddavo
Copy link
Member

daviddavo commented Mar 30, 2022

Our current method to recover assets is to get the balance of the DAO address. There are some platforms, like Aragon, that store assets in another app and not the core, thus, having a different address where the balance is stored.

@daviddavo daviddavo added the bug Something isn't working label Mar 30, 2022
@daviddavo
Copy link
Member Author

It seems that this problem occurs because we pass a too high value to millify. (That value being 7.4e68. I don't know if it is possible to have that much money, so I think we have an error at some point in the cache_scripts. This fix will be going as v8.2.1 and directly in the master branch

@daviddavo
Copy link
Member Author

daviddavo commented Mar 31, 2022

There is a DAO with an incredible amount of ROC, which, according to CryptoCompare has a value of 0.0005074 ETH (even If it has not been used in 3 years).

This is the recovery vault with addr 0x0, aka a burn address...

I think we should keep a list of "burn addresses" to delete from our dataframes. Or should we keep this info? @javiag

@javiag
Copy link
Contributor

javiag commented Mar 31, 2022

It sounds very reasonable.

My main concern is how do we know that the address is a "burn address". Is there a curated list somewhere? Can users declare that an address is a burn address?

In addition, I'd like you to document carefully the process in the code, but also to explain it in the documentation (I don't know if in the about page, because it is too technical).

@daviddavo
Copy link
Member Author

Update: The problem seems to be that there are a lot of DAOs with the recoveryAddress set to 0x0. An example of that would be MyBit. If you go to MyBit on dao-analyzer, it doesn't display anything (it fails). Because it has the 0x0 vault address, it tries to display the 7.4e68 value, and it fails... Furthermore, the "Tokens without fiat equivalence" thing is incorrect.

I don't quite understand how Aragon DAOs finances go... Currently, we are using the recoveryAddress, but there are some daos which don't have a recoveryAddress, but have the finance application so they have some value stored. Others have the tokens stored in the agent...

Here are the installed apps for MyBit

In the meantime, I think setting the vault address from 0x0 to NaN should suffice.

@daviddavo daviddavo added the help wanted Extra attention is needed label Apr 1, 2022
@daviddavo
Copy link
Member Author

We should at least put a disclaimer because the assets are only on the recovery vault

@daviddavo
Copy link
Member Author

This is a "feature" of all DAO platforms (even though in Aragon is the problem is more prominent because of "apps"). Perhaps we should still put a disclaimer, or even add a "caption" to every graph explaining it a bit. But that would be another issue...

@daviddavo daviddavo changed the title Fix assets graph for Aragon Recover assets from vault in Aragon Sep 6, 2023
@daviddavo daviddavo added cache-scripts and removed bug Something isn't working labels Sep 6, 2023
@daviddavo daviddavo moved this to Waiting in DAO Analyzer Kanban May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cache-scripts help wanted Extra attention is needed
Projects
Status: Waiting
Development

No branches or pull requests

2 participants