# Week 17 Day 3 - Daily Stand-up Minutes

### Larry
:::success
yesterday:
- Finalize Bastion contracts
- Test STG-USDC
- Debug DB issues with Rob
:::
:::info
today:
- Add Bastion to pf-core
- Launch STG-USDC
:::
:::danger
blockers: none
:::

### Bwar
:::success
yesterday:
- working on jar history database issues
:::
:::info
today:
- continue working on jar history
:::
:::danger
blockers: none
:::

### Stryker
:::success
yesterday:
- Made chain weight pie chart for dill vote page
- Worked out how to best utilize vote page real estate, decided for now that a dropwon to select chain for jar weight table is best
- combined mainnet and offchain jar weight charts into one controlled by dropdown
- Removed user vote weight charts after discussing with bwar. the page wil auto populate with your most recent vote if you've cast one and we figured that will be enough for voters to understand.
:::
:::info
today:
- Create tables with the data that's too negligible to be on the pie charts
- Add adjusted weights to jar weight chart tooltip
- Finish top mover charts on chain stats page
:::
:::danger
blockers: none
:::

### Cipio
:::success
yesterday:
- Updated Bastion USDC strategy (With Larry's help)
:::
:::info
today:
- Fix withdraws on Temple Strategy
:::
:::danger
blockers: none
:::

### Ape
:::success
yesterday:
- Add STG-USDC to pf-core
- Add aurora jars to pf-core and UI
:::
:::info
today:
- Finish adding aurora jars to pf-core and UI
:::
:::danger
blockers: none
:::

### Mard
:::success
yesterday:
- Added an extra unit test for pTokens total supply.
- Discussions and updates on the script requirements/roadmap with bwar.
- Spent some time resolving rebasing conflicts.
:::
:::info
today:
- Continue refining requirements.
- Prepare AWS scripts.
:::
:::danger
blockers:
- Ongoing fetching of the missing transactions. Can't verify the tests accuracy properly meanwhile.
:::

### Aditya
:::success
yesterday:
- Found an issue with the distribute function in gauge proxy v2 on automation tests. It is an edge case where distribute is not called for a few periods and also voting is skipped. The ideal situation is that if voting is not done for a period it should use the previous period's votes for distribution. But the logic has no way currently to find what previous period to use if voting is skipped as I assumed distribute is called every period. Did some thinking and I have almost reached the solution.
- Added more edge cases to tests.
:::
:::info
today:
- Continue with testing.
- Liquidity locking.
:::
:::danger
blockers: none
:::

###### tags: `Pickle` `dailyStandUp`