<d​imalinux:monero.social> That's a little harsh. Right in my pull request (submitted 5 days early) I wrote:

<d​imalinux:monero.social> > The starting point for all the code under u256 was crypto-bigint 0.5.5 with some ideas borrowed from newer releases. Almost all the code was modified, as my version is only for 256-bit ints. If you want me to do anything special for attribution, let me know.

<d​imalinux:monero.social> The `crypto-bigint` ('off-the-shelf') library, which was already being used for the vast majority of the math, is dual licensed under Apache and MIT. There was no hiding where the code came from and I wanted to know if the judges wanted me to add attribution somewhere specific in the code.

<r​ottenwheel:unredacted.org> been meaning to ask this. I vaguely remember someone bringing it up months ago. wonder if it's cuprate guys? will have to fish for it.

<s​yntheticbird:monero.social> thats gonna be hard the @MoenroResearchL isn't a month old

<s​yntheticbird:monero.social> thats gonna be hard the @MoneroResearchL account isn't a month old

<r​ucknium:monero.social> ppopth, developer of EthShadow, contacted me. He said:

<r​ucknium:monero.social> > The main problem I had when I tried to develop EthShadow is that some essential syscalls were not implemented by Shadow yet, so I had to implement them myself. If Monero uses some unsupported syscalls and they are essential, you probably need to implement them in Shadow. If they are not essential, you can omit them and Shadow will just emit an error and the application will like<clipped message

<r​ucknium:monero.social> ly treat them as no-ops.

<r​ucknium:monero.social> >However, I think the point here is that Shadow is currently maintained by a few developers, so they don't have enough resources to support all the syscalls. When more people contribute to Shadow, I think we don't have to worry about the issues I mentioned anymore.

<r​ucknium:monero.social> He shared this video presentation about EthShadow: youtube.com/watch?v=g-VE038cW1M

<r​ucknium:monero.social> He said his current workload would prevent him from trying to create a Monero-Shadow implementation.

<r​ucknium:monero.social> gingeropolous: ^

<r​ottenwheel:unredacted.org> I'll prove you wrong whenever I get back on desktop, kitty.

<s​yntheticbird:monero.social> I'll eat you alive whenever I grow up, rouepourrite

<d​iego:cypherstack.com> hi guiz, so there's been yet another error in regards to payments towards me for our recent MRL work, this time in MRLs favor, not mine

<d​iego:cypherstack.com> it seems I was actually paid 70 XMR on April 8th, and I guess luigi just forgot to tell me as I don't have correspondence with him about it.

<d​iego:cypherstack.com> ccs.getmonero.org/proposals/fcmp++-research.html

<d​iego:cypherstack.com> but the payout is there and it is indeed after I asked for payment on the CCS git comments, so it matches

<d​iego:cypherstack.com> seeing as how I just got paid 175 XMR, that means I now owe 70 XMR back to the MRL fund

<d​iego:cypherstack.com> I will await jberman, kayabanerve, or luigi1111 to tell me where to send

was there another error?

<d​iego:cypherstack.com> the error is that I was overpaid because I didn't realize I was partially paid already

please pay $100k fine to me

<d​iego:cypherstack.com> send me 100 and I'll send you double back

address?

monero-project/meta #935#issuecomment-1867257410 contains ccs2 wallet details

also also I'm confused

<d​iego:cypherstack.com> Let me break down the timeline as I recall it.

<d​iego:cypherstack.com> I say I will do the work for 175 XMR and start doing the work. March?

<d​iego:cypherstack.com> Somewhere along the line I get confused and think the work is 70 XMR

<k​ayabanerve:matrix.org> Can we request a pause on all CCS payments to Cypher Stack until Diego, Luigi, myself, Rucknium, and likely sgp_: who also kept track of this are in sync, assuming such a pause doesn't exceed next Wednesday?

<d​iego:cypherstack.com> we complete the work and I ask for payout here: repo.getmonero.org/monero-project/c…als/-/merge_requests/449#note_29312

<k​ayabanerve:matrix.org> Not to be a dick who disenfranchises Cypher Stack. Because it sounds like there's a cumulative error here and yes, we have to sit down and sort it out. Waiting for Diego to continue writing up the schedule.

<d​iego:cypherstack.com> I ask for 70 XMR. It seems it's paid out April 8th. I don't really have correspondence between luigi and me about it being paid out or my poking him to do it besides that request on the CCS comments

<d​iego:cypherstack.com> Because I'm not informed of the payout and don't check my wallets day after day, it goes unnoticed by me.

<d​iego:cypherstack.com> Kayaba asks me in a personal conversation to actually not get the payout because one of two things needs to happen:

<d​iego:cypherstack.com> 1. He has some comments on the initial deliverable. We need to fix those before payout. OR

<d​iego:cypherstack.com> 2. Because we're already at that point working on a technical note that we actually give thumbs up (which would later be rescinded because of the divisors debacle), we complete that and that technical note + the initial deliverable would be sufficient for payout

<d​iego:cypherstack.com> and since doing 1 would be wasted work when we were already doing 2, I decided to delay asking for payout

<d​iego:cypherstack.com> not realizing that:

<d​iego:cypherstack.com> 1. I'd already been paid out without my knowledge

<d​iego:cypherstack.com> 2. Completing this technical note would not be fast or easy and would ultimately result in SLVer Bullet :P

<d​iego:cypherstack.com> Which brings us to a couple weeks ago when someone corrected my stupid error and 70 XMR was rightly corrected to 175 XMR

<d​iego:cypherstack.com> Which brings us to a few days ago where I was actually paid out 175 XMR

<d​iego:cypherstack.com> which brings us to yesterday when ofrnxmr contacts me and says according to his spreadsheet I was already paid 70 XMR, and I check and it's true

ok thanks for confirming, i forgot to tell diego payment was sent, we can leave it at that. return to CCS2 wallet primary address (linked above in luigis github comment), safest. OR return to the exact research fund address inside ccs2 wallet - which can be found @ ccs.getmonero.org/index.php/projects

<k​ayabanerve:matrix.org> I'd say private, not personal, but yes. I did ask we delay completion until either we reconcile on the existing draft document OR we supersede the existing draft document (as done by Silver Bullet) which was externally organized by CS in a generous contribution to the Monero community.

<d​iego:cypherstack.com> long story short, I owe MRL 70 XMR

<k​ayabanerve:matrix.org> Diego Salazar: I don't think you do immediately.

<d​iego:cypherstack.com> ah yes, private is a better word. Sorry.

<k​ayabanerve:matrix.org> I believe you billed distinctly 70 and 175.

<k​ayabanerve:matrix.org> Brandon did two separate divisor reviews.

<d​iego:cypherstack.com> at this point it's so jumbled in my head and I can't find evidence of this

<k​ayabanerve:matrix.org> When you asked for 175 correcting 70, I flagged that to circle back on as I don't think you asked 70 when owed 175 and need a 105 diff. I thought you were owed 70 and later owed 175.

<k​ayabanerve:matrix.org> One on sums of points, then one on the complete concept, which was "recommended or not", and such a jumble.

<k​ayabanerve:matrix.org> I *immediately* thought the first was 70, the second 175, and would now have to check MRL logs.

<d​iego:cypherstack.com> interesting yeah

<d​iego:cypherstack.com> repo.getmonero.org/monero-project/c…als/-/merge_requests/449#note_29312

<d​iego:cypherstack.com> and this initial 70 XMR request links to the sum of points document

<k​ayabanerve:matrix.org> But if you were recently paid 175, not +105, I think *off the top of my head*, you're square. Not owing 70 back.

<k​ayabanerve:matrix.org> That do say "sums of points" in the title.

<k​ayabanerve:matrix.org> I don't believe the complete review which was a "do not recommend" was ever published.

<d​iego:cypherstack.com> I see. This all seems accurate to me, and was what I initially thought, but couldn't find the conversation.

<k​ayabanerve:matrix.org> I believe I asked, before payout and before publication, of the 'draft' (it was your submission, it was eligible for publication, I'm only calling it a draft as it wasn't published and I had feedback which was unaddressed) for you to hold off on both.

<k​ayabanerve:matrix.org> So if you quoted 70 for that document, which was published with link attached, that all makes sense to me.

<k​ayabanerve:matrix.org> If you've now been sent 175, and have a quote for 175 for what became the externally-sponsored SB project, I immediately believe we're all square.

<k​ayabanerve:matrix.org> (And I did check the link you cited. It was a quote for 175)

<k​ayabanerve:matrix.org> The only question would be in how we contracted review for 175, you didn't publish an immediate response nor claim payment, then after leaving a NACK, self-organized Silver Bullet which you're now submitting as the deliverable.

<k​ayabanerve:matrix.org> Obviously, I have no issue there :)

<k​ayabanerve:matrix.org> When I'm home, I can check my gists (which are unlisted, so I can't simply view from my public profile) for the quotes I've written up and provide greater confirmation of this.

<d​iego:cypherstack.com> right. Our "deliverable" as it were was going to that MRL meeting and saying we can't recommend, but we've already begun work on fixing it, funded by PUP

<k​ayabanerve:matrix.org> But I *think* it's square and we should all hold off on sending money anywhere.

<k​ayabanerve:matrix.org> But DW, if you're concerned, I'll take 245 XMR from you and hold onto it.

<k​ayabanerve:matrix.org> Until I spend it.

<k​ayabanerve:matrix.org> But I'll take it :)

<d​iego:cypherstack.com> deal

<k​ayabanerve:matrix.org> Verbal agreement, everyone saw ^

<d​iego:cypherstack.com> oh no I seem to have lost my keys. Will get back to you on sending the 245

<g​ingeropolous:monero.social> Rucknium: , thanks. I've encountered that syscal thing as well.