isthmus: could be a flag to identify txs

Hmm, if that’s the case, it’s working…

I hope they aren’t doing anything where obfuscating the flow of funds is important, because the unique flag makes tracing long chains trivial (probably the change outputs).

I’ve been looking around for open source libraries with this behavior, searching for monero-derived code that sets or verifies an unlock time of 3, but so far I’ve found nothing.

are we still looking at removing that option?

ofrnxmr[m]: it is not implemented in the current seraphis protocol

Hi. I was doing some research into Ringct and I was unable to find records of chats around it in the monero/meta github repo. The earliest chat that mentions ringct is here: monero-project/meta #58 and there are no logs. My main question is, was ringct deployed before bulletproofs were agreed upon as a solution to the rangeproof size problem? I imagine there was some great discussions around this issue

and any insights would be greatly appreciated.

Yes, there used to be a less efficient range proof used in RingCT transactions before bulletproofs

It used Borromean proofs, from gmaxwell originally IIRC.

That makes a lot of sense. Thanks for the lead!

I believe this is the paper for the original RingCT specification: eprint.iacr.org/2015/1098.pdf

If you have not looked at the git logs, I would do so. Pointers are likely to be found there.

jeffro256: moneromooo I will look at the logs, thanks for the quick response.

DGoon[m]: You may also find some information in old developer meeting logs, they were posted to getmonero.org in the past

👍️