<k​ayabanerve:matrix.org> FYI I will explicitly and publicly opt-out of being a judge, as I already have, yet with the additional comment I may enter (publicly or anonymously) as a contestant in the above proposed contest.

<k​ayabanerve:matrix.org> Apparently some people started suggesting the prize pool to be over 100k

<k​ayabanerve:matrix.org> I'll work for 1.2m USD a year

<k​ayabanerve:matrix.org> (at least, I'll work for a month at such a rate, if time allows and the topic is sufficiently interesting)

<j​d8zjsnww0a:matrix.org> Onion nodes?

<k​ayabanerve:matrix.org> I'll also note I won't merge unsafe code/code known to be vartime/have a variable memory access pattern/etc into my libs, and if the contest does allow C code for some bump of performance, some other org will have to take over maintenance of the FCMP++ libraries if they want to realize that performance. I believe I'm allowed to decline to maintain/offer such code and I don't want <clipped message

<k​ayabanerve:matrix.org> such code to win the contest, only to cause drama when I don't accept it into my tree. I'll be clear now my tree is my tree, and if my opinions sufficiently diverge from the Monero community (as they may here re: unsafe code), it is the Monero community's responsibility to define and maintain their own tree. Hopefully this statement avoids any potential drama over source tree mana<clipped message

<k​ayabanerve:matrix.org> gement and merge policy.

<k​ayabanerve:matrix.org> Monero doesn't follow my tree FWIW, Monero follows a specific git commit which is currently a git commit in my tree. Same as RandomX. If Monero ever wanted a RandomX change while tevador isn't around/willing, we'd need a monero-project/randomx and to update where the git submodule points.

<a​ntilt:we2.ee> ... adds a dependency. if you look for mesh routing: reticulum

<a​ntilt:we2.ee> ... adds a dependency. if you look for mesh routing, reticulum :

<a​ntilt:we2.ee> media.ccc.de/v/38c3-reticulum-unstoppable-networks-for-the-people#t=3