# TBR-Q1-2023 - PT Inc Client Team
| | |
| --------- | ---------- |
| Team Name | **PT Inc. Client Team** |
| Quarter and Year | **Q1 2023** |
| Payout Address | **0x3927E0642C432A934a4EAA64C79bC8a1D8ac5Fb7** |
| Total USD Value Requested | **$45,136.31 USD** |
# Purpose
The PoolTogether Inc. Client team is responsible for providing client support for the protocol. This includes maintaining and expanding the flagship consumer interface at app.pooltogether.com and developing additional dapps on tools.pooltogether.com and vote.pooltogether.com. The Client team is also building tooling for developers to easily build on top of the protocol with things like tutorials, SDKs and APIs.
# Goals
1. **Explore PoolTogether Ecosystem**
Exploring the PoolTogether ecosystem is too difficult and needs to be reworked. An updated version of the current landing page at <https://tools.pooltogether.com> will be designed and developed to highlight the possibilities of the protocol, existing interfaces and tools for the protocol and ways to build on top of the protocol.
**Deliverable:** A redesigned Protocol Ecosystem landing page.
2. **Protocol Landing Page**
An updated landing page for the protocol with more of a "protocol focus" and less of a "product focus". We want to highlight governance, protocol features and the DAO more and focus less on the singular interface located at <https://app.pooltogether.com>. Some examples of "protocol focused" landing pages are: Liquity, Lido, Uniswap and Aave.
**Deliverable:** A redesigned Protocol landing page.
3. **PoolTogether V4 App Maintenance & Bugs**
While it's fully functional there's always optimizations, upgrades and inevitable bugs. We will continue to maintain and improve the existing interface.
4. **Hiring**
The client team is looking to hire 1 full time engineer to help work across the stack on the various interfaces and infrastructure used by the client team and external developers. As Dylan transitions to the protocol team we will need more front end developer bandwith to help with the upcoming goals.
**Stretch Goals**
5. **PoolTogether Hyperstructure Interface Alpha**
In conjunction with the protocol team the client team will provide a new interface for the next version of the protocol. As of now, the new interface will be more of an admin interface and less of a consumer app. We will be prioritizing functionality and simplicity for of development over user experience (it'll still be pretty though).
**Deliverable:** No guaranteed deliverable. Depends on external factors.
6. **PoolTogether Hyperstructure Tools Alpha**
With the new protocol design several mini apps (tools) will be required to interact with specific pieces of the protocol. The client team will provide intuitive interfaces for each mechanism. An example from last quarter that will be expanded upon is the [liquidator](https://tools.pooltogether.com/liquidator) (NOTE: set the app to developer mode to access.)
**Deliverable:** No guaranteed deliverable. Depends on external factors.
8. **PoolTogether Hyperstructure SDK Alpha**
A Typescript SDK will be developed alongside the interface. This SDK will provide a simple way for developers to build on top of the protocol without needing to know the low level details of the protocol. Some priorities are: simplicity and customizability. Tutorials and documentation will be provided similar to the existing `v4-client-js`.
**Deliverable:** No guaranteed deliverable. Depends on external factors.
# Budget
## Requested Amount
| Amount | Token |
| ----- | ----- |
| 67,083.56 | POOL |
## Budget Breakdown
### Team Members
| Role | Yearly USD Compensation | Commitment Percentage | Quarterly USDC | Quarterly POOL | Contributor | Contributor Discord |
| ---- | ---- | ---- | ---- | ---- | ---- | ---- |
| Senior Designer | $145,000 | 100% | 0 (covered by PT Inc.) | 16,811 | Alex | alxx#6155 |
| Software Engineer | $202,000 | 100% | 0 (covered by PT Inc.) | 24,618.14 | Dylan DesRosier | dylandesrosier#6262 |
| Junior Software Engineer | $100,000 | 100% | 0 (covered by PT Inc.) | 6,502.32 | Noah Cukiert | Ncookie#1619 |
| Senior Software Engineer | $250,000 | 100% | 0 (covered by PT Inc.) | 37,156.10 | **Open Role** | |
The maximum POOL salary for the open position is being requested (see the [compensation formula spreadsheet](https://docs.google.com/spreadsheets/d/1zkgljshTWmJke85LZqtlZYxmb6aZLoFQxeWx5q7mEPI/edit#gid=0))) to keep the door open for high quality candidates. If we do not hire this quarter, we will roll the tokens over to next quarter. If we decide we don’t need to fill the role, we will return the tokens. If we hire they will likely be below the max, so we will return or roll over the remaining tokens.
### Team Expenses
Additional expenses are currently being covered by PT Inc.
# Retrospective
## Q4 2022 Goals
1. **Core App Redesign**
The interface found at <https://app.pooltogether.com> was overhauled, all code is available on [GitHub](https://github.com/pooltogether/v4-ui).
2. **V5 App Alpha**
An alpha version was [built](https://github.com/pooltogether/v4-ui/pull/68) but has been halted. There is more work being done designing the protocol and the UI comes second. Alongside the core app alpha some additional mini apps (tools) were required. A liquidator implementation is available [here](https://tools.pooltogether.com/liquidator).
3. **V5 JS SDK**
An alpha version was [built](https://github.com/pooltogether/v4-client-js/tree/new-tokenomics-alpha) but has been halted. There is more work being done designing the protocol and the JS SDK comes second.
4. **V3 App Deprecation**
The [v3 interface](https://v3.pooltogether.com) was deprecated. Support for all features from the v3 site are available on <https://app.pooltogether.com> and <https://tools.pooltogether.com>.
5. **Hiring**
One engineering position was filled, another engineering position is still open. We also hired a Senior Designer earlier than anticipated so we've redirected the unfilled positions POOL to them.
## Budget Surplus
**18,004 POOL**
- 25,373.03 - 7,369 POOL
These tokens are from the unfilled Software Engineer position will be rolled over this quarter and subtracted from the total requested amount as the position is still open. However, due to hiring a Senior Designer that wasn't initially planned for Q4 we've repurposed these funds to handle their POOL allocation. The rate used is the same as what is being requested in this document and was pro-rated to their start date for the quarter.
# Appendix
## Token Pricing
| Token | USD |
| ---- | ---- |
| USDC | $1 |
| POOL | $0.6728370667 |
# TBR-Q4-2022 - PT Inc. Client Team
| | |
| --------- | ---------- |
| Team Name | **PT Inc. Client Team** |
| Quarter and Year | **Q4 2022** |
| Payout Address | **0x3927E0642C432A934a4EAA64C79bC8a1D8ac5Fb7** |
| Total USD Value Requested | **$45,939 USD** |
# Purpose
The PoolTogether Inc. Client team is responsible for providing client support for the protocol. This includes maintaining and expanding the flagship consumer interface at app.pooltogether.com and developing additional dapps on tools.pooltogether.com and vote.pooltogether.com. The Client team is also building tooling for developers to easily build on top of the protocol with things like tutorials, SDKs and APIs.
# Goals
1. **Core App Redesign**
The interface found at app.pooltogether.com is in need of an update. The app started as a prototype and grew into the production app. The team has paid a Designer for a complete redesign and will be implementing this. The goal of the redesign is to be more approachable for new comers while maintaining the same (and more) level of details. Along with that, the redesign sets up the application for expanding to many more prize pools (deposit tokens, yield sources)
**Deliverable:** Deploy redesigned app in Q4
2. **V5 App Alpha**
The client team has been developing an Alpha version of the app for the proposed V5 of PoolTogether. This will allow the community to have a more tangible way of testing the proposed changes. The team is working closely with the Protocol team to ensure a smooth transition from V4 to V5 in the future.
**Deliverable:** Deploy alpha app in Q4
3. **V5 JS SDK**
Alongside the alpha app, the client team will release alpha versions of @pooltogether/v4-client-js for interacting with the V5 protocol.
**Deliverable:** Deploy V5 JS SDK
4. **V3 App Deprecation**
Unfortunately the existing V3 app is expensive and difficult to maintain. To prepare for shutting down that UI we need alternative UIs for users to: withdraw & claim rewards.
**Deliverable:** Deprecate V3 app
**Deliverable:** Deploy V3 mini apps
5. **Hiring**
The PoolTogether client team is looking to hire 1 full time engineer to help work across the stack on the various interfaces and infrastructure used by the client team and external developers.
**Deliverable:** Hire a full time engineer
# Budget
## Requested Amount
| Amount | Token |
| ----- | ----- |
| 46,624.47 | POOL |
## Budget Breakdown
### Team Members
| Role | Yearly USD Compensation | Commitment Percentage | Quarterly USDC | Quarterly POOL | Contributor | Contributor Discord |
| ---- | ---- | ---- | ---- | ---- | ---- | ---- |
| Software Engineer | $202,000 | 100% | 0 (covered by PT Inc.) | 16,811.16 | Dylan DesRosier | dylandesrosier#6262 |
| Junior Software Engineer | $100,000 | 100% | 0 (covered by PT Inc.) | 4,440.28 | Noah Cukiert | Ncookie#1619 |
| Software Engineer | $250,000 | 100% | 0 (covered by PT Inc.) | 25,373.03 | **Open Role** | |
The maximum POOL salary for the open position is being requested ( see the [compensation formula spreadsheet](https://docs.google.com/spreadsheets/d/1zkgljshTWmJke85LZqtlZYxmb6aZLoFQxeWx5q7mEPI/edit#gid=0))) to keep the door open for high quality candidates. If we do not hire this quarter, we will roll the tokens over to next quarter. If we decide we don’t need to fill the role, we will return the tokens. If we hire they will likely be below the max, so we will return or roll over the remaining tokens.
### Team Expenses
Additional expenses are currently being covered by PT Inc.
# Appendix
## Token Pricing
| Token | USD |
| ---- | ---- |
| USDC | $1 |
| POOL | 0.985298 |
# PTIP-15: Part 2 - Deposit POOL
## Simple Summary
This proposal is to continue POOL distribution to governance managed prize pools at a reduced rate. If not passed, POOL distribution will completely stop on May 26th.
## Motivation
The initial POOL distribution period has been quite successful in
* Generating ~$200,000 in weekly prizes
* Growing AUM to ~$230 million
* Growing reserves by $75,000 - $150,000 weekly (depending on interest rates)
However, since this POOL distribution was set before the POOL token was issued. It has never been optimized using the real world data we now have. The initial POOL distribution was outlined here and was designed to [distribute 5% of the total supply over 14 weeks](https://medium.com/pooltogether/introducing-pool-23b09f36db48).
This proposal continues POOL distribution at a substantially reduced rate. The goal of this proposal is to optimize POOL distribution to generate the largest prizes and getting POOL into the hands of long term aligned community members.
## Specification
- Extend POOL distribution for 14 more weeks at the following rates
- Reduce USDC POOL distribution from 2,295 per day to 1,400
- Reduce Dai POOL distribution from 2,295 per day to 700
- Reduce COMP distribution from 255 per day to 50
- Reduce UNI distribution from 255 per day to 50
- Increase LP reward distribution from 300 to 500 POOL per day
Overall, these changes reduce total daily POOL distribution by 49%. Maintaining these rates fo 14 weeks will distribute a total of 274,400 POOL. It should be communicated that we expect POOL distribution to continue after those 14 weeks but there may be modifications to it.
### Rationale
There are many variables involved in setting POOL distribution rates so it's impossible to fully know what the impact will be. However, a few over-arching ideas guided our thinking.
- POOL distribution had to be slowed for the simple reason that it began with a VERY fast distribution rate. The initial distribution rate was optimized for getting as much POOL as possible into the hands of the community (5% of total supply over 14 weeks).
* The yield rates on assets are highly varied. Targeting high yield assets with POOL distribution leads to larger prizes and faster reserve growth. Targeting low yield assets helps grow AUM but doesn’t contribute significantly to prizes.
* POOL distribution is equal across similar asset types (stable coins both get the same rate) this fragments prizes and prevents the growth of really large headline prizes ($1 million per week).
With these high level ideas we landed on the following parameters
- A total 49% reduction in POOL distributed per day
- The largest cuts 80% were to the non-stablecoin prize pools which have the lowest APRs and therefore smallest prizes
- USDC receives the highest allocation of 1,400 POOL (2x that of Dai) this creates a clear favorite pool that can be the primary entry point to new depositors and also provide the highest headline prize.
- An increase in LP incentives to POOL / ETH holders of 200 POOL (500 per day instead of 300 per day) which should incentive healthier liquidity for POOL
You can [see the details of the changes along with other variables here](https://docs.google.com/spreadsheets/d/149njhQ1gA9kVOLLLzGvUhoTL3NVtzIf-fDHXnPuUhmw/edit#gid=784369451).
It's worth noting a few things this proposal does not do.
- The proposal does not re-allocate any POOL specifically to incentive sponsorship over deposits. This has been a popular idea as a way to have less whales win prizes but it was deemed too big of a change to implement right now alongside the other changes.
- This proposal does not change pool reserve rates. It was decided it was best to address this separately.
### Technical Specification
This proposal exceeds the current 10 transaction limit of proposals, so it will be split into two parts:
Part 1: Reduce Drip Rates
Part 2: Deposit more POOL
## Status
This was discussed at length [in a previous thread](https://gov.pooltogether.com/t/1-million-weekly-prizes-pool-distribution/1055). Due to time constraints on the initial distribution ending this should be submitted for on-chain voting in ~36 hours.