Skip to content

Feat/remove rebasing erc20 #61

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 16 commits into from
Dec 20, 2024
Merged

Feat/remove rebasing erc20 #61

merged 16 commits into from
Dec 20, 2024

Conversation

@apexearth
Copy link
Collaborator

@apexearth apexearth commented Dec 14, 2024

  • also contains block rate changes
  • attempting to gain a higher level of consistency between deploys
  • validation on StrategyBalance was failing due to some entities not existing
    • those are created using block frequency updates, so there must still be some inconsistency there :(

@apexearth
use static block rates for polling
6e25abd
@apexearth
delete erc20-rebasing and create the entities on the otoken processor…
3a8e65a 
…s instead

- erc20-rebasing got too complicated due to all the nuance needed for tracking otokens
- while we used to track other rebasing tokens - we no longer do, so it doesn't make sense to keep it
@apexearth
uncomment validate code
c4e2f9c
@apexearth
fix strategy balances on base
154ecdd
@apexearth
Add start/head timestamps to processing status so we can better measu…
17a3cb5 
…re processing speeds
@apexearth
process arbitrum woeth using the event tracker
9006fbf
@apexearth
better organization/perf for validation logic
6b0e0e2
@apexearth
perf work
8d7786b 
- extend context with `blocksWithContent` and `frequencyBlocks` to reduce overall iterations
- print extra stats & debug info
- modify blockFrequencyUpdater to allow for parallel execution
- fix ousd wotoken `from`
- attack performance in several places
@apexearth
moderate changes to otoken processing for performance
7b253bf 
- some shuffling of function positions - not quite as much changed as the line count suggests
- risks to mention are the parallel processing of things and how we no longer `getLatestOTokenObject` but instead `getOTokenObject(block)`
  - seems more intelligent - if it works right
@apexearth
- transactionally it doesn't make sense to process these async
c7c97e4 
- Instead, let's get all the RPC data needed ahead of time
@apexearth
ensure exchange rates async ahead of time in otoken processor
6ed840f 
get status for arb
@apexearth
add script to log processing times
cf64f1e
@apexearth
fix getOTokenObject
0a91063
@apexearth
clean up logging
cb65c17
@apexearth
update processing times
3eaa0a4
@apexearth
update entities.json
48a8eb9
@apexearth apexearth merged commit 48a8eb9 into main Dec 20, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@apexearth