New PRs for upstreaming seraphis: #9196 (crypto utils), #9197 (hash functions), #9198 (blake2b)

<t​widtwo:matrix.org> I just finished research into implementing drivechain on monero this is the link to the research if you want to check it out.

<t​widtwo:matrix.org> github.com/BrandyJSon/drivechain-xm…20of%20drivechain%20to%20monero.pdf

Twidtwo is this incompatible with the recent relay rule for reducing the size of tx extra?

<t​widtwo:matrix.org> Missed that change. Luckily 465 bytes is enough for each message except for the 2BYTE_BUNLDE_ACK in the case there are more then 215 active sidechains and one of them has more then 256 proposed bundles. I apologize for the oversight.

Kayabanerve ^ tx extra still allows.for 456 bytes of "scripting space"?

<t​widtwo:matrix.org> This is the thread I was basing my answer off of monero-project/monero #8733

<t​widtwo:matrix.org> 456 bytes is assuming the transaction has 16 outputs. 1060 bytes is the the technical max length of tx extra that will get relayed.

<k​ayabanerve:matrix.org> plowsof: Data space. Monero doesn't execute any of it.

<k​ayabanerve:matrix.org> If you define an off-chain protocol for it, that doesn't make Monero have scripting. That makes you using Monero for data transport for your script engine.

<k​ayabanerve:matrix.org> This proposal would add scripting to TX extra.

<k​ayabanerve:matrix.org> I find Drivechains as a whole a flawed idea. I don't support adding this level of scripting to TX extra. Any scripting added should be enough all future applications can be built be recursive instantiations of the fundamental script. This absolutely fails to do that.

<k​ayabanerve:matrix.org> I'm also not convinced of some of the discussions in this paper (under "Further Research").

<k​ayabanerve:matrix.org> The techniques monero-project/research-lab #116 culminates in would offer soundness guarantees, not require nodes run additional other nodes, and have full privacy across the SC pool (if added with a dedicated pool which didn't supersede the entire flow, as proposed). That fixes the miner voting concerns, reduces computational load if dome correctly, doesn<clipped message>

<k​ayabanerve:matrix.org> 't require miners vote on which apps to validate, and doesn't lose privacy when discussing which sidechain/app was interacted with.