Loss of CDT to the SSV token upgrade contract

Dear All, this proposal is about an honest mistake that was made during the process of a token upgrade of CDT to SSV. CDT tokens were sent to the SSV token upgrade contract with a “Transfer” function instead of “Convert” function, thus making those CDT tokens lost in the contract without the issuance of new SSV tokens back to the sender’s address as should have been. The transaction was made a few days ago, and can be seen below: TXID: 0x3841d711a66009acca799717bb537f76589b2db4e8c8ed2e5e7808399a89c6be

Proposal Details

The proposal is basically to allow the SSV DAO committee to issue back to the sender’s address (0x697302628be3dd222da2c817b405c561ac25fdea) the appropriate amount according to the original CDT → SSV token upgrade process. According to the above mentioned transaction, a total of 214,691 CDT tokens were transferred to the SSV contract, which applies for 2,146.91 SSV tokens (1:100)

So a total of 2,146.91 SSV tokens should be issued to the address 0x697302628be3dd222da2c817b405c561ac25fdea

Reason for

Since this was a complete honest mistake by the owner of the address (me basically) I believe this is the right thing to do. supporting of this proposal would be highly appreciated.

Reason Against

From tokenomic perspective this will inflate the amount of ssv tokens BUT it should have been like this anyway if the swap was to be performed properly.

Mechanics

DAO m.sig committee to issue the appropriate amount of SSV tokens to the following address 0x697302628be3dd222da2c817b405c561ac25fdea as described above (following a successful vote)

Note: Since there is also the Fundamental Labs refund request proposal going on, it would be probablly easier and more convienient for the committee to execute both proposals (following a successful vote ofc)