Everything EOS EOS Node Operator Round Table, 21 Sep 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Node Operator Roundtable - September 21st, 2023

Description

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

0:00 Intro
0:20 Disable deferred transactions on EOS
3:48 API Node Testing for Leap 5.0.0
7:57 EOSIO Contract
10:04 Pomelo Season 7

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's September 20th back for another note operator, Round Table, talking about the leap 5.0 upgrade um following up on where we were last week, uh looks like actually so we we uh on the Deferred transaction side of things, as you know, we're uh disabling them, we've already disabled them on Jungle in kailan and we're in the process of disabling them. On EOS and I can confirm.

A

um We both received verbal confirmation from all the BPS that they've disabled deferred transactions and we've run our substream and the substream has confirmed there are no deferred transactions now getting executed on the EOS Network. So now, officially deferred transactions are disabled, So yeah! Thank you. Everybody for participating. Getting your your configurations, updated poking folks, all that stuff much appreciated.

A

B

Spencers to the to the pokers you're, very good at it.

A

It's a little. It's amazing, a little poking goes a long way yep.

A

um So yes, thank you. um Anyone have anything to add on that topic.

C

Yeah I also saw some upgrades to uh uh leap four, zero, four as well so got some upgrades as well right.

D

All right, I would just say that we should keep an eye on RAM usage uh and see if it um starts going up significantly. We may have to take some action.

B

And just uh be explicit, the reason that theoretically could happen is because of deferred transactions being submitted, but not executed right. Okay, yes,.

A

Anticipate like an increase in attempts to submit deferred transactions since they're not going through or that's just no.

D

A

Of them not being executed, yes,.

D

Because they're not being executed, they're building up and so we'll want to keep an eye on that. If that uh precedes a significant increase in Ram, we may want to take some action to clear those out.

A

Okay and I have not heard any Rumblings from anybody impacted negatively from the absence of deferred transactions. I don't know: if uh do we have anyone from EO support on the line, uh looks like Dario's here, I, don't know if, if you've heard anything or have anything to report on that side of things.

E

No all good from our worst idea, cool other than the ram increase on the contracts. That's the first one that came back.

D

Yeah is there a uh a martyr for that I was looking at the US Nation stats page. Is there one for RAM usage.

A

Matthew, do we have a RAM usage on the stats.

E

We have an internal one, I, don't know if there's a public one.

A

Okay, we'll keep an eye out on it, and maybe we can share our reporting periodically.

A

A

All right anything else on that topic.

A

All right, let's move on then to early API node testing for leap, don't have much and here um any news on this front, any anyone having made progress in testing running into anything any questions, any blockers or anything from the enf side to add or request.

E

I haven't made much progress on internal testing, but I do know we saw over on Telos.

E

They were smashing snot out of one of their nodes, doing a get Block with like thousands of threads and ultimately crashed the node due to open file restrictions, but uh was discussed, uh try doing the same abuse on a 5.0 node, so I shipped them full logs for test net and mainnet on Telos to spin up a 5-0 and see if it does any different I, don't know if it'll have time to gather all the benchmarks, but you'll have two different ones that he's smashing on the read-only threads, so that may and it's it's heavier blocks right.

E

You know, I mean it's not just empty test snap plots so that might produce some interesting information.

D

Yeah we improved handling of running out of pile, handles um I, believe that Supply got oh I, don't believe X and forty dollar, and so yeah I'll be very interested. Is that.

E

In the pre-release 5.0 that we would be running okay, so that API test version.

A

Anything else on API node testing.

D

Yeah I mean I, haven't spun that up yet.

A

Okay, well, this may be a short one today and Brian anything from your side or Eric to.

B

Add you know on this I'll just say like we did make some updates to this uh to this document. um So if folks do give it another look when they have a chance, um you know has been updated. uh So some of the some of the concerns from previous conversations been addressed um or I'm, not concerns, confusion, I, guess, right, um uh I, don't believe, there's anything else to add. At this point, I.

E

Will put on the list just spin up and paste?

E

Thank you. Where are we at in General on that timeline plan? Or maybe that's the next piece you follow up with I know, deferred transactions and retesting were big but when's. The next I don't know.

B

All right so so next up would be um a release candidate one um or at this point we've kind of done. You know the that pretty work of you know around deferred transactions, and so next up is actually having a release that people can. uh You know.

E

Yeah jungle, so all the jungle BPS will be waiting on an rc1 or something of that equivalent to the next major Milestone sounds like right.

A

In the meantime, yeah test in our early API and keep an eye on that Ram all right last call for topics New or Old or anything to add on any of the existing topics.

F

And maybe I'll just continue with my question: there's nothing else on the agenda now. I did look it up now on that, but we're talking it's in the USA of mantrack.cpp and it looks like the link key- is a temple of the requirement, the account code and tie, so it doesn't take into you. It will Factor any the permission need so so, in other words like when it searches for that link, if basically you're sending a leak out with the c with the scene account code and type, and that will just replace the existing one.

F

So in effect, doing like an online versus creating a new one, which kind of is limiting, or at least the application we're doing, because we want users to be able to like a browser, creates a permission that allows them to do certain things that allows a browsing sign on their behalf. But this way I can have them. Do it see on their phone and on on their desktop here, I can kind of explain. More I was just wondering if there's any potential other way to allow that kind of behavior.

D

um I would say: I mean our egg. Is our link off expert uh he's done some of the kind of crazy things in the past with setting up some some permission, so um yeah I would ask him.

D

You know posted on the developers Channel as well. He monitors that so I mean either way. um Okay,.

F

I'll do that. Thank you.

A

A

I'll just do a Shameless plug pomelo season, 7 applications open today, so if you're, uh if you're participating, get those applications in and otherwise look forward to donations in one week from today,.

E

I'll say: thanks to Kevin, we helped squeeze out a hot fix but fixes some problems with nodes. So he's just an awesome man to to squeeze in some State history fixes because I'm still breaking them on the rag.

A

Awesome all right well, thank you, everybody! Thank you, Kevin. Thank you. Everybody else and have an awesome day, cheers.

F

Everyone take care.