Thank you @ham and @0xd15co for the helpful input. Is there any reason this RFC thread could not be used for both adding wOUSD to the to the Eligible Collateral Universe, and for onboarding as collateral to eUSD with suggested basket weights? I am happy to update the name of the RFC. Previous basket change proposals, such as @Sawyer’s [RFC] eUSD Collateral Basket Change Proposal 5 included details on both the new asset being added as well as the proposed basket weights.
Yes a plugin has not been built yet, but as I mentioned in the RFC above, Origin engineers believe a wOUSD plugin would be quick to build, using work from the existing Origin collateral plugins. We can wait to hear from @pmckelvy before building the plugin in case there are other compatibility issues to account for or other edge cases to be aware of with the Yield Protocol architecture. I modeled the basket options above with the 2.3.1.2 10% cap in mind, so we are aligned there. A $600k allocation to OUSD is $100k more than the options I modeled above, at that amount the blended yield of eUSD would be even higher.
Regarding compliance - multiple legal opinions for OUSD exist from reputable law firms domiciled both inside and outside of the USA confirming OUSD’s status as not a security - I am happy to share them privately with parties that may need them when onboarding an asset to eUSD, such as ABC Labs, BFF, and possibly SENTZ and UGLYCASH. These documents are typically not included in public governance proposals since they are confidential legal documents.