01:05:07 <Nacho[m]> how do I verify without reversing it
12:00:53 <plowsof11> monerodocs maintainer (qertoip) is willing to add co-maintainers with full commit rights https://github.com/monero-project/monero-site/issues/1754#issuecomment-1596062593
13:02:24 <DanrdarkIsnotthe> I vote ofrn
14:37:01 <nioc> ofrn is our #1 support guy
14:37:09 <nioc> I vote Dan
14:37:55 <nioc> I imagine that I am still talking into the void 
14:39:47 <naphtha[m]> i vote yeat
14:50:12 <merope> nioc: if you talk into the void enough, the void will talk back
17:12:57 <r4v3r23[m]> kayabanervedo full membership proofs do anything to solve the 10-block lock "problem"?
19:54:06 <xmrack[m]> r4v3r23: I think so since zcash has full membership proofs and, if I remember correctly, no unlock time requirements. Maybe I’m making an ignorant assumption though 
20:09:14 <Rucknium[m]> r4v3r23: Better to ask in #monero-research-lab:monero.social . I am 40% of this (not very sure): You probably cannot confirm a child tx in the same block that a parent tx is in since the merkle tree that contains that parent tx is not yet in the blockchain. In most (all?) UTXO currencies, you can chain many tx in a single block.
20:11:35 <Rucknium[m]> (More 40% sure): If a block whose merkle tree you reference for constructing the "shielded" tx is re-orged out of the blockchain, then you have to re-submit the tx (the tx is invalid). The problem with the decoy model + re-orgs is that the real spend can be potentially revealed (or guessed) when re-orged decoys are invalid but your real spend is still valid.
20:14:18 <boog900[m]> Here: https://www.youtube.com/live/m-qWvfhABrY?feature=share 
20:14:18 <boog900[m]> At 37 mins he say it doesn't go away