[PRFC] Victim Repayment Plan

It’s a nice start! Maybe a bit too premature to have it as a PIP that could be executed, given negotiations may still be ongoing.

I would like to see a larger initial amount converted into ETH and distributed to the victims. Also, I’m not sure on the benefits of using weekly emissions as a form of repayment? How much does the constant sell pressure it would create on the prisma token concern you?

However, I think what we want from the repayment plan depends a lot on how much (if any) can be recovered from the hacker.

1 Like

Hi guys,

I previously shared my thoughts briefly in discord.

It’s a strong case that no tokenized recompensation plans were effective past the LEO/bitfinex centralised one, especially this is the case for DeFi protocols. BZx also tokenized losses & people determined that it would be unlikely that those losses would be repaid in any reasonable amount of time and they ended up facing a class action lawsuit.

DeFi examples:

BZx with p125 token -

Harvest.finance with grain token

Beanstalk and their token

This model has empirically shown to never amount to even coming close to repaying the victims, I strongly believe making a debt token sounds good in theory but works out less than optimally in practice especially for victims.

We should focus on doing whats possible and dispersing currently existing assets rather than anticipated future assets and revenue in the form of debt.

The top 5-6 whales excluded the sum of total losses in ETH are ~3 Million USD.

There are a total of 25 users affected, there is a case to be made to pay back each user up to 100k USD of funds and do a debt token for the remainder, this would make MOST users affected whole immediately, these amounts could be edited but the treasury should be able to handle it.

Barring the exception of the funds being returned by the hacker maybe we could discuss the above in either this thread or a new one if you prefer I make a new proposal.

Thank you,

Bt8

4 Likes

I like the idea. Prefer this proposal over original.

Downside is that it discourages whales from getting involved in future. If only my first $X is “protected” I’m heavily disincentized from putting more in.

I understand, I believe this incident to be an isolated scenario so I just wanted to propose something that made most users whole with what is possible.

interesting proposal and good points by @bt8

the risks of defi are numerous and one does not invest and assume a +100% APY is anywhere close to risk free.

i do not support crippling the protocol to make everyone whole if that means the protocol dies a slow death. I lost $$$ on a hack in the past (xtoken) and no big surprise the repayment plan didn’t work there either and the project is dead.

the underlying questions for me are- if we vote to enact this proposal, does more or less capital find its way to the protocol? will the additional debt overhang significantly hinder growth of the protocol to the point where the victims are happy but the protocol can no longer compete in the market?

i only want the protocol to survive and thrive …

1 Like

Hi Riptide,

The DeFi risks are indeed numerous, although in our case there was no +100% APY, it turns out users who overcollaterized (tried to play their positions safer) were among the most affected, and users with less collateral backing lost less in this hack.

I do not wish to see the protocol crippled either, it is in no ones interest to have that! I believe a plan that goes along the lines of my proposal would require a breakdown of what could render most users whole meanwhile allowing the team to have enough treasury left to cover ample runway. Only they would be able to tell us an approximate figure of what that would be and what they need.

I think from there a proposal can begin to form that tries to rely less on future debt.

2 Likes

Just want to point out that the treasury belongs to the DAO. This whole proposal and forum etc exists so that the DAO can determine what happens.

2 Likes

TLDR - debt token to help the victims, pros it can repay without significantly affecting the protocol, cons it is a gamble and historically hasn’t worked for similarly affected hacked communities. 25 wallets in total effected, estimated 20 of these wallets were a sum of 3 million loss. Alternative idea that is being embraced is to make the smaller wallets disproportionately affected whole, suggested amount cap of $15k for first epoch payment per affected wallet from converting mkUSD into Eth equivalent (not a bad idea with Eth price down right now 1 Eth = 1 Eth from a hack perspective). This would make approx 40-50% of the hacked victims (might be under estimated) whole, leaving the remaining victims/debt to be addressed with the above recommended debt token.
I personally have 3 wstEth lost in the hack, and this constitutes half of my entire (small) portfolio at the moment. 50% loss of portfolio disporrtionately affects me vs a $20 million wallet that lost $1 million is the idea behind this argument. My vote is for the cap payment idea of $15k max per affected wallet for first round, make the small wallets whole, get the rest in the debt token.

Here’s a table of actually losses and immediate repayment thresholds.

Given Prisma Fee receiver holds 1.7mm mkUSD, we can repay somewhere between 25-50 ETH without touching the prisma.

I suggest somewhere in the 25 ETH range, which would, make 4 people whole, another few accounts with minimal losses, and leave 600k mkUSD and all the existing prisma left for treasury.

Addresses Before After Change wStETH Conversion Rate Loss (in ETH) Repay up to 100 ETH Repay up to 50 ETH Repay up to 25 ETH
0x56A201b872B50bBdEe0021ed4D1bb36359D291ED 1745.08 463.18 -1281.9 1.1648 -1,493.157 -100.00 -50.00 -25.00
0xcbfdffd7a2819a47fcd07dfa8bcb8a5deacc9ea8 824.6 192.12 -632.48 1.1648 -736.713 -100.00 -50.00 -25.00
0xc487370895f6e8f5b62d99bf1472c95a94073379 377.2 95.6 -281.6 1.1648 -328.008 -100.00 -50.00 -25.00
0x9fceded3a0c838d1e73e88dde466f197df379f70 356.28 102.12 -254.16 1.1648 -296.046 -100.00 -50.00 -25.00
0x1b72bac3772050fdcaf468cce7e20deb3cb02d89 166.41 47.49 -118.92 1.1648 -138.518 -100.00 -50.00 -25.00
0x3b15cec2d922ab0ef74688bcc1056461049f89cb 107.18 18.89 -88.29 1.1648 -102.840 -100.00 -50.00 -25.00
0x16f570e93fdbc3a4865b7740deb052ee94d87e15 113.6 32.4 -81.2 1.1648 -94.582 -94.58 -50.00 -25.00
0x4a3fced7c536e39ca5292a024ee66c9b45b257ec 87.93 19.85 -68.08 1.1648 -79.300 -79.30 -50.00 -25.00
0xf8d1c9ab49219f7acf7b1d84705e5aea3b8ce0aa 70.3 17.85 -52.45 1.1648 -61.094 -61.09 -50.00 -25.00
0xf9ca66ef84c773fab422562ab41b1ee8d4397418 47.3 15.48 -31.82 1.1648 -37.064 -37.06 -37.06 -25.00
0xc47fae56f3702737b69ed615950c01217ec5c7c8 40 11.69 -28.31 1.1648 -32.975 -32.98 -32.98 -25.00
0x774bb9306df1cd921eb842b1388c78f75e6ef79f 172.18 149.36 -22.82 1.1648 -26.581 -26.58 -26.58 -25.00
0x19562df3e7fd2ae7af4e6bd288b04c2c90405212 31.22 9.15 -22.07 1.1648 -25.707 -25.71 -25.71 -25.00
0x1b004189e64d5b2f71d5be554470e6c49e10123b 21.74 5.98 -15.76 1.1648 -18.357 -18.36 -18.36 -18.36
0x3b82ee6c15b212ed69d5795bcd957e136eaa4bff 13.02 3.45 -9.57 1.1648 -11.147 -11.15 -11.15 -11.15
0x14b30b46ec4fa1a993806bd5dda4195c5a82353e 4.22 1.21 -3.01 1.1648 -3.506 -3.51 -3.51 -3.51
0x409c6c5ec5c479673f4c09fb80d0f182fcff643e 3.8 0.93 -2.87 1.1648 -3.343 -3.34 -3.34 -3.34
0x409c6c5ec5c479673f4c09fb80d0f182fcff643e 0.93 0.99 0.06 1.1648 0.000
0x3b82ee6c15b212ed69d5795bcd957e136eaa4bff 3.45 3.52 0.07 1.1648 0.000
0x409c6c5ec5c479673f4c09fb80d0f182fcff643e 0.99 1.06 0.07 1.1648 0.000
0x19562df3e7fd2ae7af4e6bd288b04c2c90405212 9.23 9.3 0.07 1.1648 0.000
0x3b15cec2d922ab0ef74688bcc1056461049f89cb 18.89 18.97 0.08 1.1648 0.000
0xf8d1c9ab49219f7acf7b1d84705e5aea3b8ce0aa 17.85 17.93 0.08 1.1648 0.000
0x19562df3e7fd2ae7af4e6bd288b04c2c90405212 9.15 9.23 0.08 1.1648 0.000
0xc47fae56f3702737b69ed615950c01217ec5c7c8 11.69 11.78 0.09 1.1648 0.000
Total in ETH -3,488.937 -993.66 -608.68 -361.35
Total in USD -10,815,705 -3,080,333 -1,886,910 -1,120,196
2 Likes

The table is a nice visual

Apart from the fee receiver (0xfdCE0267803C6a0D209D3721d2f01Fd618e9CBF8), are there any other addresses controlled by the DAO containing cryptoassets?

2 Likes

Just a note: If you take that much mkUSD and dump it for ETH, doesn’t it significantly drain the liquidity and hurt the peg? It’s something to consider.

We need to be really careful about that. Sure, you can say that you are going to do that in batches, but then the liquidity may run out, or we will have a lot of redemissions.

This needs to be considered. I like the plan with fixed reimbursement more, but we need to be careful with the numbers.

2 Likes

Should be easily resolvable by heavily bribing mkusd/ETH or mkusd/USDC pools for a few weeks. Probably USDC better because it attracts more TVL per unit emission and USDC/ETH trades with minimal slippage.

We easily got 1mm in mkusd/usdc TVL with 4.4% of voting power this epoch. Get it to 15-20% and we’ll easily have enough to swap with minimal slippage (perhaps even positive slippage if people without mkusd start trying to farm it with USDC)

Here is my proposal.

  1. We heavily incentivize mkUSD-USDC for a week or two to build TVL.
  2. We swap 1.1mm mkUSD to ETH, and distribute up to 25ETH per affected account. This repays smaller accounts (6 out of 17 accounts are almost fully repaid) and gets leaves 600k mkUSD in treasury and all the Prisma.
  3. The remainder lost gets the debt token airdropped according to Tommy’s instructions.

Hi guys, I made a new proposal based off the ideas discussed here by Tommy + Maximumpain and tried to make a simpler repayment plan

Made the change to PRFC since we haven’t moved to snapshot voting yet

This is not material too the plan, but IT IS material to the calculations. Hopefully the Prisma team does not rely exclusively on a forum post because some of the numbers aren’t accurate. No offense to the person who took the effort of creating the table, but here are a couple of corrections that the team should make (or even better do the math from on-chain).

Wallet 0x409c6c5ec5c479673f4c09fb80d0f182fcff643e is listed 3 times (I’m guessing hackers moved tokens more than once), but the actual difference should be in the rance of 2.81 ETH (3.8 before hack, 0.99 after).
Same for wallet 0x3b82ee6c15b212ed69d5795bcd957e136eaa4bff, who lost 9.5 ETH (from 13.02 to 3.52).
Wallet 0xf8d1c9ab49219f7acf7b1d84705e5aea3b8ce0aa lost about 52.37 ETH (from 70.3 to 17.93).

Team do your part and review both the estimated losses and what needs to returned.

I took the numbers from the post mortum table.

I didn’t check for duplicates. Any “gains” I just floored to zero. Apologies

Nothing to apologize and thank you for doing the work in the first place.

I checked 3 wallets that were in more than 1 hack, but not all the numbers for everyone.

Does someone have the exact numbers for each hack (past the two decimals) and we can do a more precise calculation? I’m happy to “run the numbers” if someone can provide the raw information

Borrower Total Collat Diff Total Debt Diff Attack Count
0x56A201…D291ED -1281.897208 1497.972891 1
0xcbfDfF…Cc9eA8 -632.473987 738.390919 1
0xC48737…073379 -281.597436 467.522591 1
0x9FceDE…379f70 -254.157990 485.751974 1
0x1B72Ba…B02d89 -118.919959 333.078670 1
0x3B15CE…9f89CB -88.211928 506.108512 2
0x16F570…d87E15 -81.199696 290.796637 1
0x4A3Fce…b257eC -68.080547 255.540779 1
0xf8D1C9…8Ce0aa -52.374561 500.112200 2
0xf9Ca66…397418 -31.825258 243.375708 1
0xc47faE…c5C7C8 -28.218348 465.725472 2
0x774bB9…6Ef79F -22.816279 618.585189 2
0x19562D…405212 -21.923910 677.456522 3
0x1b0041…10123B -15.755664 216.745824 1
0x3B82eE…AA4bfF -9.498108 419.520585 2
0x14B30b…82353e -3.006842 203.385971 1
0x409C6c…ff643e -2.749010 608.315612 3
Totals -2994.706731 8528.386055 26

source

1 Like

Hi VictimsBFF + Wavey,

Just a small note to add to your table your calculations seem correct although they should be denominated in WSTETH and not ETH, so technically the ETH value lost is higher.