0 replies, 195 views, 0 likes
Uspatange is actively seeking the historical address of the
UiPoolDataProvider contract to find user reserve data, but is facing difficulties. This highlights both a proactive problem-solving approach and potential issues with documentation or guidance within the community.
This discussion revolves around Uspatange's quest to find historical holding patterns for users, particularly the reserves they had in collateral/debts. They are planning to utilize the
UiPoolDataProvider on an archive node. However, they are encountering difficulties in locating the historical address of the
UiPoolDataProvider contract. The current contract, known as
UiPoolDataProviderV2V3, is located at the address
[0x00...4e1a](https://etherscan.io/address/0x00e50fab64ebb37b87df06aa46b8b35d5f1a4e1a). There is a possibility of older contracts such as
UiPoolDataProviderV2. Uspatange has also examined the
getAddress function of
LendingPoolAddressProvider but is uncertain about the id to use when invoking this function1.
The community's reaction to this issue is not included in the provided summaries. Therefore, it is not possible to provide an accurate representation of their response.
The positive aspect of this discussion is the proactive approach taken by Uspatange. They are actively seeking solutions and exploring different avenues to find the historical address of the
UiPoolDataProvider contract. This shows a high level of engagement and problem-solving initiative within the community.
The negative aspect of this situation is the difficulty faced by Uspatange in finding the historical address of the
UiPoolDataProvider contract. This could indicate a lack of clear documentation or guidance within the community, which could potentially hinder the progress of other members facing similar issues.
Posted a month ago
Last reply a month ago
Summary updated a month ago
Last updated 03/12 08:00