4 ms·

Yeah, they probably should abstract and write it down at this point. 20 years is a long prototype :). Moving to C is not a bad idea at all. It would shake ou

Yeah, they probably should abstract and write it down at this point. 20 years is a long prototype :). Moving to C is not a bad idea at all. It would shake out those issues. The RFC bit is more to get it so you can rip it apart and do the thing in any language. I have done a few of these sorts of things over the years. It is very easy to tie yourself to a particular language library without realizing it. Sometimes just writing down what bits go back and forth and responsibility helps shake out those oddities. If I were doing it I would probably start with a port with something like C just so I could understand what is really needed and what is cruft. Then doc it into the RFC format as I went along.

synctext 6y ago
Hopefully you still see this late reaction by IPv8/Tribler team. There is now Kotlin code, Android Trustchain app and expired IETF draft. On top of the pretentiously named IPv8 overlay, we now have tamper-proof accounting and trust function operational. Took a mere 20 years of my life:-) [1] https://github.com/Tribler/kotlin-ipv8/ https://github.com/Tribler/kotlin-ipv8/ [2] https://github.com/Tribler/trustchain-superapp https://github.com/Tribler/trustchain-superapp [3] https://tools.ietf.org/id/draft-pouwelse-trustchain-01.html https://tools.ietf.org/id/draft-pouwelse-trustchain-01.html [4] https://dicg2020.github.io/papers/devos.pdf https://dicg2020.github.io/papers/devos.pdf