Everything EOS EOS Node Operator Round Table, 14 Sep 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Node Operator Roundtable - September 14th, 2023

Description

The Antelope Node Operator Roundtable meets every Wednesday at 14:00 UTC to share and discuss feedback to improve the Antelope protocol.

00:00 Intro
01:31 Main Net and the Goal for EOS
02:30 Early API Node Testing
13:05 Leap 5 Protocol Upgrade

The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.

// EOS Network Foundation //
https://www.eosnetwork.com
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosnetwork.com
#EOS #Web3

A

All right welcome everybody. It is Wednesday September 13th back for another node operator, Round Table, talking about the big leap 5.0 upgrade um so following up now, we're working on disabling deferred transactions uh would also love to you know. Following up on the last call, we talked on the early API testing need to get a little check in on how that's going in some of the uh documentation related to that.

A

uh Actually, before we look at mainnet status, um looks like we're all set on both jungle and kylan, we'll be running some some of our sub streams to see, if that's holds true like if there's actually no uh before seeing no deferred transactions getting through. Now that all the BPS have reported that they've turned off deferred transactions, um so stay tuned for results there, but as far as we can tell all of the BPS on both jungle and Kailyn have now disabled deferred transactions.

A

If anyone has anything they'd like to say or add besides, thank you, everybody who uh who participated there and helps poke folks who needed poking.

A

I saw you doing some poking there Michael. Thank you.

A

All right, let's move on then to mainnet, so we're uh the goal for for Eos is to have disabled by September 14th we're well on track.

A

um That's tomorrow uh in the top 21 we're just missing one I'm, sorry, two EPS that have yet to report that they've disabled different transactions. Everyone else has and we're even tracking the top standby BPS.

A

um So there we go just slow missed from the from these this group here that we don't have any any data on yet uh so we'll re-run our substream on mainnet2, once we believe everyone has been have, has it disabled and uh just to confirm that and we'll do the same on jungling, island and report back the results we see there.

A

Anything to add on maidenet.

A

All right moving right along. um Maybe we can talk a little bit about the API node testing um I, don't know if I'll want to turn it to Brian for this or, if or if there anyone who's already been playing with this. That has any feedback they want to share now, but I think there was some feedback on documentation required before we can really proceed further on the testing how's that looking right.

B

So uh Eric actually uh has executed through the test plan and and sort of had some feedback internally um I don't know Eric. Do you want to share some of your experiences there and and what changes you made based on that.

C

Yeah I mean we got some good feedback on the build instructions they weren't, um they weren't really there so I added those build instructions to the the document um I've been going through and and playing with it um checking out the in the the optimized compiler and the release chain base size I haven't gotten around to looking at the Prometheus metrics um and then also I've been trying to do some uh um like proofs of correctness, test using various sdks that we have, uh and that has not gone too well, because the proof of correctness tests like for Wharf, for example, um they were based on test data and when I try to regenerate the tests on the mainnet snapshot, it didn't work out.

C

uh So instead, I'm gonna have to do another approach where I'm putting together um test harness for beat-only transactions. You generate some load and a decent benchmarking.

C

uh If anybody else has feedback and things they want to see, improvements um lay it on me.

A

So those are those additional build. Instructions are those added here.

C

Yes, sir they're at the very bottom cool.

C

uh Build instructions there we go.

A

All right any feedback from any of our node operators. Anyone had a chance to try running through these instructions, yet.

D

No last week, I had other dumpster fires.

D

That I cuss yeah.

D

Yeah I do like the notes, still running it's on EOS, to get a benchmark of the EOS footprint but beyond.

C

D

C

uh One one of the coolest things is: if you do get a chance to do this load it up with a snapshot. You'll have to do that, because the changes in uh boost in the changes in chain base uh go. Take a look at chain base size before and after pretty cool, it gets smaller.

A

And taking a step back to the previous topic, I just noticed a comment here from Kevin. Thank you, Kevin looks like bitfinex has not disabled based on what was.

A

B

I'm not sure if it was just me.

D

um Well, it was I got it, it was for me too, all right yeah. You need to pay your internet bill.

A

Oh, my am I cutting out. Sorry, sorry, guys.

A

uh And I see a comment here from Stephen.

E

Yeah, maybe I will steer us off topic for just one second um and then I'll. Let you guys get back on task. Sorry for hijacking the call for just a second, but I did want to bring awareness to uh BPS that there are some insects up for both jungle and EOS main net as it pertains to the EOC being next release. uh We need to create a couple of new accounts and I've included the links there.

E

If anyone does have any questions around the purpose and function there, I can share some additional documentation, but the general idea is that there's one account that we're introducing for the management of ERC standard, erc20 standard tokens, and then we also are introducing an account.

E

That's kind of a proxy account that we'll use for the deposit function to EOC VM, wherein you can either send uh EOS token standard or the erc20 token standard, and it will appropriately manage that to help you bridge your various token types onto EOC VM, um so we're on 12 of 15. I, think for Jungle, the last that I looked and then um the one for mainnet I think we just got up like at.

E

Like five in the morning today um that one's less critical but the jungle, one I'm just being annoying about, because uh once we have that in place, we can deploy the latest release that we have to Jungle and we're trying to kind of get the stuff out the door, probably near the end of September or early October. However, we have it committed to a date for this product just yet. So if anyone has any questions, feel free to, let me know, and uh thanks for letting me steal the mic for just a second no.

A

Problem any questions.

A

All right um so back I think we've didn't sound like there's any feedback on this either.

A

Pause all right, any um any specific questions or asks Brian or anyone else from the enf on this topic before we move on for maybe stuff to between now and the next next call that we're looking for that hasn't already been discussed.

B

No, just you know um sort of the the same. If, if you could take a look and try to get through it and if you get stuck anywhere um reach out on Telegram uh in the Antelope node operators, Channel.

B

And um yeah we'd appreciate help doing doing this early testing. Thank folks who have already taken a look and given feedback.

C

Yeah we we had some discussions on the this is the API node so beat only so we had some discussions on configuration settings for the read-only threads on that on that forum uh and that's something I'm interested in doing is generating some load and trying to Benchmark uh number of read-only threads.

C

um You know not not slight differences between one and two threads, but really between, like 8, 16 and 32 threads, and to see what that's like it shouldn't, add a lot of memory, so we should be able to run with quite a few threads uh and I just want to make sure that that uh works out. How I think it's going to work. So that's what I'm working on next to get a recommendation together, but those read-only threads.

D

um Well, if you, if you've, got some cannons, you can fire like on the EOS. You know: mainnet data I can open up my API nodes and let you just smash them. It's a dedicated, node they're. You can just have private access to, but Point your tools at them. If that would help.

C

Is great but I I just want to do that on my Local Host first, looking for.

D

Yeah but EOS AP I know that you can smash this not out up. Yes,.

C

Okay, cool I do I, do it's about. Yes, I do uh yeah, so um we'll do I'll. Do that first and then we'll go on to the next stage and generate some load it'll be fun but uh yeah.

C

uh If anybody has any questions about, config settings uh be great to put those in the Forum too, because there's a lot there, just when I was doing some testing the other day, I had to go back to the spreadsheet, to find the config setting that I needed or uh or something to work. So thank you, Michael for putting that together.

F

Yeah, it's not just read only transactions, you know it's your table, robes as well. All runs in parallel, really cool.

D

Yeah I'd be interested to know the details of what you found you needed to go back and.

E

D

If it's just like a sanitized version of your config to see what, when you banged your head through it, what did you end up with that's how we've kind of got all these different things so yeah.

C

I was doing a get, uh was it get um get account by authorization, um Paul and I needed to turn on the? um What's that parameter for the categories and.

D

Count queries yeah, so so this just features perfect, perfect I was curious. If there were any of the other knobs you were turning but glad it helped see what I mean.

F

Yeah I have to look at it. I, don't think the the account queries is improved it all by the uh extra threads.

C

Yeah I've just test I was just testing for correctness right now. Oh yeah.

F

That that particular subset was already supported, multi-threaded um by upping the HTTP threads, uh so I, don't think it had any additional benefit with the readout links.

A

All right, Last Call on that topic.

A

Well, let's move on then uh I saw Brian. You've been updating some of the dates here and related to the.

A

um What was it here? The Highlight Reel.

B

Yeah yeah, we'll we'll have to push out sending that uh that email, um we're we're still. You know, figuring out some schedule sort of across the board for some of these things um so hope to have an update on that soon, um but yeah I, don't I, don't yet have Hyrule highlight reel ready to go this.

A

Cool anything to report uh on the instant finality integration stuff that here is tracked to be finished by September 29th. Is that looking on track from your perspective,.

B

Yeah so I think this falls into that category of of uh looking at dates across the board, I'm, confident that that date uh is not going to happen, um but I don't have an updated date for you at this time. Okay,.

A

So we'll have to uh yeah I guess: look at the the downstream dates yeah flowing from there too. Once we have a little more cool, um otherwise I don't have any. Those were the topics I had on my list to cover today. Are there any others that I'm missing that anyone would like to dive into related to the leap 5.0 upgrade or anything else? We've got plenty of time left on the agenda.

D

What on a scale of one to ten, what's the chance, I get a ship log repair tool squeezed in anytime, soon.

B

uh uh Well, I'm, not gonna, say zero, but uh I'm almost I'll accept the floating Point number you get down. Let's call it zero point, one which technically is not in the scale of one to ten, but uh it.

D

Is if you accept floating point, it's greater than zero, all right that yeah I'll work on trying to work around it, but.

A

A

Well, in that case, we can give everybody some time back um and uh yeah we'll check back in next week. uh Brian. Let me know if, if between now and next week, there's any anything on the dates side of things that we can, we can prepare to update folks on for the next call, otherwise we'll see y'all next week thanks everybody cool cheers.

E

A