[RFC] PTBR 18: PoolTogether <> G9 Software Inc

[sliponit]

@Brendan

In mid-December, the Optimism launch was discovered to have an issue that wasn’t caught by either of the two audits or the beta launch. The Aave vaults were severely limiting how much users could deposit, so the protocol was unable to scale. This bug made it through many rounds of checks; and it shows how no audit is a silver bullet. It proved that the beta was a good idea, though it didn’t catch the issue. We do the best we can.

I do not think G9 did the best they could here.

• In october 2024, I sent your way some alternative private auditor. I think they did a quote for a live audit in front of an audience from a well known auditor community. This for a lot less than what was spent on public audit competitions from code4arena. These discussions are private, but I believe you chose not to pursue because it was “too late” at the time.
• I also suggested One last audit. Now we are many commits later, notably introducing at last WETH instead of POOL as prize token. Two more public audit competitions happened, one with sherlock still pending results.

I hope more audits are gonna be done on the (many) core contracts of v5 and that G9 does not consider that the current immunefy bounty program is sufficient.

@Brendan

We are going to deploy to Ethereum in the next few weeks, which means that we’ve delivered on everything with the notable exception of the buyback and burn.

@Brendan

PoolTogether is live on Optimism, Base, Arbitrum, and will be deployed to Ethereum by the end of Q2. Each deployment can be permissionlessly extended by anyone.

Unclear, in the next few weeks or by the end of Q2?

As is, I am voting against this proposal.

Side question: Is voting still possible on mainnet only?