07:34:34 mosHST 07:34:50 sorry 20:05:27 Thinking about Seraphis and hardforks... I think anyone who wants to use tx chaining or collaborative funding cannot use it near a hardfork. Tx proofs must include protocol version numbers to prevent unwanted behavior. This means a partial tx made before a hard fork will become invalid after the hard fork. Something to keep in mind ^.^ 20:42:49 well thats a funny type of "smartcontract" 20:50:14 thankfully it's not a smartcontract, just taking advantage of design features ^.^ 21:00:36 It would only be hardforks that change tx structure or validation rules. This way you cannot sign a partial tx that gets used to make an unintended tx version. On second thought, you can get around this problem by making partial tx for both version numbers if near a hardfork boundary. 21:02:45 UkoeHB: Do you think it is currently possible for Monero to do something like BCH's Flipstarter? IIRC, last time it was discussed you were skeptical of the notion that Monero is currently capable of it. 21:08:25 Not currently, with Seraphis it is possible afaict 21:08:36 with certain variants of Seraphis* 21:21:18 Sersphis