00:26:29 <m-relay> <c​haser:monero.social> ArticMine: my understanding is that this feature has been desired for view-only wallets, and the current design doesn't allow it, however it's viable both in the FCMP+RingCT design and in Seraphis, but not a result of FCMPs per se. the monero.town poster worries that regulation may force users to give up this key, which will allow regulators too to surveil outgoing transactions. i<clipped message>
00:26:30 <m-relay> <c​haser:monero.social> s my understanding correct?
00:48:38 <m-relay> <a​rticmine:monero.social> If you mean outgoing transactions from regulated entities this is nothing more than travel rule. The regulated entity knows to whom they are sending the funds. One actually does not need a view key for this. 
00:48:39 <m-relay> <a​rticmine:monero.social> The issue is subsequent hops. If the user has given the view key of the first hop address to a VASP the user can simply transfer part of the funds to a spending wallet and spend privately from the spending wallet. 
00:48:40 <m-relay> <a​rticmine:monero.social> An aggressive regulator may try to get the view key to the spending wallet, but this opens the door further to legal pushback in the courts. This is especially the case in Europe not just the EU where BS is already under threat because of the European Convention of Human Rights.
00:51:39 <m-relay> <a​rticmine:monero.social> By the way OVK does not need a hard fork after or Seraphis FCMP. It can be implemented at the wallet level. So in practice it is a result of FCMP.
01:17:07 <m-relay> <a​rticmine:monero.social> This discussion is in my view better suited to Monero Policy
01:22:11 <m-relay> <a​rticmine:monero.social> To clarify. OVK does not need another hard fork once pre Seraphis FCMP is implemented
09:26:46 <m-relay> <j​ohn_r365:monero.social> Diego Salazar: This line in the CCS proposal, it's worded in a confusing way. Maybe it can be edited?
09:26:47 <m-relay> <j​ohn_r365:monero.social> "We aim to complete the review within 1.5 calendar (actual hours are not 1.5 months of man hours, but we have other work for other clients as well) months of the proposal being funded."
09:26:48 <m-relay> <j​ohn_r365:monero.social> Specifically the part: "actual hours are not 1.5 months of man hours"
09:28:39 <plowsof> Assumption is do not expect it to be done (date of funded += 1.5 months) because we have other on going projects and cant full time on this task 
09:32:51 <m-relay> <j​ohn_r365:monero.social> Maybe something like the below would be clearer:
09:32:52 <m-relay> <j​ohn_r365:monero.social> "Taking into account our existing project load, we aim to complete the review within 1.5 calendar months of the proposal being funded."
09:32:53 <m-relay> <j​ohn_r365:monero.social> Anyway, just my two cents, and maybe others find the wording clear as is.
23:57:53 <nioCat> Generalized Bulletproofs Security Proofs is now fully funded! https://ccs.getmonero.org/proposals/cypherstack-gbp-security-proofs.html
23:58:34 <nioCat> Rucknium Statistical Research is now fully funded! https://ccs.getmonero.org/proposals/Rucknium-Statistical-Research.html