Allocate DAO Royalties to Exploit Reimbursements (Created By Temp)

Proposal to reimburse those who lost NFTs in the hack of GB discord on May 8th, 2022 using roughly 2.5 months of the DAO's royalty income.

Roughly 57eth worth of NFTs were stolen as a result of the phishing link, across 22 wallets.

At our current 10% royalties, and an average of around 5eth weekly coming in from them, it would take roughly 2.5 months for the victims to be fully reimbursed from the royalties.

The funds will be distributed once 50% and 100% of the reimbursement funds are raised.

For transparency, and to remain unbiased, I will state the community concerns for and against this proposal:

Pros:

• Victims will get reimbursed for their losses, which could keep them as a community member.
• Community will get positive publicity for supporting it's holders (and even those who were not holders, but still affected)

Cons:

• Community will get negative publicity for reimbursing those who did not take the proper individual security measures.
• Having a halted DAO for months will turn away investors.
• Reimbursement puts a target on Gray Boys for more scams.
• Community members are not encouraged to practice personal security.

Affected wallets: 0x040635e5fd80b59b0501613a17fa0055fa464143 0x097beda03815a1a86dfdb0414e4a933deb5c55a7 0x12270ad9cc99f9014f44766acc3ed781ef2ac416 0x1de597caf08d335902774d3cd0412eaee12afcb6 0x3037588feadedb42d5608e00fe3fa6249544ac4c 0x30525393cef7e513fc8712e0de097b4a7e4d8920 0x36c87acd0618b7e19cb3db71f39c381c87e4ee93 0x39a34314bde4a59a96657714085abf01004ffbd2 0x5f4d8f9a0fba855349d3c69f23701d25675be714 0x8b17d2f9ad49c1e8c92137abdc2c33efacd780dc 0x8efc8dadddebb16aba836a6c7bc50181b87f50da 0x9fc181b94d47de12219d4d9e8d71f0fcd3e13f2b 0xab4fac64b627cb87749e4814270f31fd707c6be7 0xab820546586cf0ebc7931449998132edc2e480f1 0xbfaa40816c707967ae0a7c0d10c3e72eba7bd3b4 0xc0352e3c8b8c0249caf4ad9ff07c903617822e4a 0xd7d6f5ef71d3d82f710f3bba3f478af747677792 0xdde700727c8f79c00014eb60d38634bb263fe99e 0xebec918d4bb22dc75221d865e645added4e72a8a 0xeee23b04ae90243f7abcb15bcb914387d73895b9 0xf470849e6a054a941ad7aac5ac8a7dbfdf190c6c