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

add live apy to home #90

Merged
merged 9 commits into from
Aug 23, 2021
Merged

add live apy to home #90

merged 9 commits into from
Aug 23, 2021

Conversation

vmaark
Copy link
Contributor

@vmaark vmaark commented Aug 16, 2021

No description provided.

@vercel
Copy link

vercel bot commented Aug 16, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/tenderize/tender-app/3K97PqJLNY2e1Sw25PATF7gRxRxC
✅ Preview: https://tender-app-git-mv-graph-data-apy-tenderize.vercel.app

@kyriediculous
Copy link
Member

Looks good at first glance, will do some manual testing on this when the contracts are redeployed

@kyriediculous
Copy link
Member

rebased this on top of master to redeploy the preview with the latest contract addresses

@kyriediculous
Copy link
Member

Looks like I still have to refresh before the rewards show the correct amount.

To reproduce:

Request 100 LPT from faucet
Approve 100 LPT for stake
Deposit 100 LPT
See Stake is 100 LPT ✅
See Rewards is 100 LPT 🔴
Refresh
Rewards is now 0 LPT

@kyriediculous
Copy link
Member

kyriediculous commented Aug 21, 2021

I Believe one potential solution is to refetch the subgraph query until data.tenderizerStake gets updates with the deposit amount and only re-render the component (or at least the specific infocard) when that is the case.

@vmaark
Copy link
Contributor Author

vmaark commented Aug 23, 2021

fixing rewards updating issue in a separate PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants