Hive Blockchain Developer, 3 Aug 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Hive Blockchain Core Developer Meeting

Description

The Hive blockchain is open source and community built. Core developer meeting livestreams are open for anyone to watch and provide feedback on, and are held on the first Monday of the month to allow the devs around the world who are working on the Hive blockchain to coordinate and discuss. Check this channel's upcoming events for the next scheduled meeting, or follow @hiveio on VIMM.TV for Hive powered live streams.

Hive is fast, feeless, and powers an incredible array of dapps in a social ecosystem where your wallet address unlocks access to blogging platforms, games, video sites, marketplaces, and beyond.

This meeting originally recorded:
Aug 8th - 2022

The follow up notes from this meeting:
TBA

The GitLab issue for this meeting:
TBA

Want to learn more about Hive as a decentralized blockchain solution for web 3.0?
Website: https://hive.io/
Hive Codebase: https://github.com/openhive-network/hive
Hive development community: https://peakd.com/c/hive-102930/created

A

B

Okay, well, the.

A

Whole world calls introduction. First thing is try to avoid doing things like that.

B

I mean it's nice to keep marinette busy. What happens when mainnet can be executed in the mirror and.

A

Where it is preferable, if someone tries to avoid doing things that like could cause a conflict or trend, try not to double spend it.

B

Yeah plus it's it's not part of the whole testing, so that makes sense um okay, so then, but then the marinette would be spinned. uh We would want to wait for the marinade to to be spun uh against the earliest candidate right and yeah.

A

I mean we did one just recently, but obviously we need to. We had more changes. We ran one over the weekend, even but but I think we should build a new one now uh with all the latest stuff in including the one fix I mentioned. So I'm guessing we'll need to do that, probably today or tomorrow and.

B

A

We'll we'll put that up for gandalf I'll put that up for download and let's see if gandalf just said something you need one without gaap that we have in current instance: okay, yeah, okay, so we'll uh we'll that will probably be today or tomorrow, most likely tomorrow. I would guess just given the load we got and I don't know how long does it take gandalf to to to generate a new blo, a new block log uh and maybe dumb state information, two days ish?

A

Okay, so we're probably talking, I guess most likely friday or, if not on the weekend,.

B

Okay, so that's good uh speaking of apas, the that means that um how many works works against uh the current release. Candidates going forward.

A

What works? Sorry! I didn't understand that sorry, I have mind. Oh yes, highman works against the current release. Candidate.

B

Okay and there's.

A

Actually, either one works, I mean you can do the half time mind or the other hive mind all right.

B

A

There's two different branches: the develop branch has the regular hive bond and then I forget the name of the other one, but it's got some kind of name like half compatible. Sync yeah.

B

A

B

A

Branch that contains the half one.

B

uh Do you know the timeline for merging with half or not? Inventing sorry is a half branch, uh I mean.

C

B

A

B

C

B

Is like uh will merging the uh half-based hive mind be more or less at the same time as hardcore 26? How will it be in the coming months.

A

I don't know it's I mean I would like to say that's true. Yes, but it's it's not. I mean we're probably going to keep both branches for a little bit just so that we can test test both versions independently.

A

Because there's been changes made to hide mind and then there's been changes made to you know for ha for regular for regular reasons and there's also been changes made just for half so I'm uncertain about doing. I think we'll I'd like to keep both for a little bit until we've had you know a lot just a super amount of comfort about it.

C

Actually, you do hear me.

A

Yeah, yes, I hear you, okay,.

C

Actually, I had quite that's true that we we need to have both versions of for the for some time, but I hope that that we can do this in this way that current develop height, mind will be moved to the master branch and will stay officially. This candidate, okay have compatible scenic branch built directly on top of this develop, then we can move to develop for the time when we decide to officially completely switch to the hub based version, because this version has eliminated a way to synchronize using a hypg rpc calls.

C

So that's some functionality problem which can uh be related to some some users, so api operator operators. We would like to avoid, but I hope.

A

C

A

C

A

C

There's no doubt we want.

A

Both versions so- and I think what your your proposal to just make the master the regular one and develop the new half-based one is a fine solution. Okay,.

B

Yeah, I agree: that's okay! So that's pretty good yeah! I was mostly afraid because half involves more, uh it's like a learning curve uh for node operators, and so I wanted to be sure that uh there isn't too much at once. um Even though there is like a bunch of um scripts.

A

Yeah I mean I I I mean personally, I would like to have both around at the beginning, so I I think it's it's it'd be nice to have both both available, because you know, even even on the once even publicly.

B

Yeah yeah, that makes sense um cool. So I think I read on your post that you basically were expecting uh in the next two weeks or something assuming no more issues for the release.

A

Yeah, I think that's the general plan. Oh there's, there's not a date yet set, but yeah yeah. I mean I'm going to tag the release candidate in the next couple days.

B

Yeah, okay, cool uh in terms of libraries, the the night changes are in right.

A

Oh sorry, what is that.

B

Then the number uh the new way to describe assets uh with numbers instead of uh oh.

A

Yes, in a uh yes, yes and that yeah, yes, that's that code is all in.

B

Okay, cool uh and the libraries I assume are compatible with it uh because I don't believe there is in library wise since we didn't add that many new operations.

A

Are you if the libraries are still consistent or yeah we'll have problems, uh it's something that needs to be tested for sure, and this is so the library guys absolutely need to get the new version and test to see if they encounter any problems, just like the apps of course themselves need to. But I mean that's, you testing with the apps will be primarily exercising the libraries. I think.

B

Yeah I mean, I don't think, there's anything wrong. I mean I thought you think about it. Yeah.

A

I don't, I don't necessarily expect any problem, but it's you know, that's what we're running. That's what we need to do: the mirror net testing for yeah.

B

A

Api changes, I mean it's very, it's very easy to introduce a subtle api change. We already we've seen a few we had to we had we had the issue with the get get. I think it was a get block api. You know it was the get block api or get account history api.

A

I can't remember one of the two, which was we're getting a slightly different format between the legacy format of json and the other one on one of the calls so and then so these these some of these some of the changes with all the apis. You got it's it's really.

A

We have to be very we've got a lot of tests for them, but there's just so many api calls to support in so many ways they can be called that we definitely want to do a thorough testing by the apps who may be using them in unusual ways, and no there could be one app that uses an api that no one else uses or uses in a way that no one else uses.

A

So I really encourage anybody's got an app to do to do their testing. Do they're testing themselves with their app against the new version.

B

Yeah sounds good um okay, so that kind of segues into my last thing. So if so, to summarize long story short, uh you know in the few next days a marinette will be spun the wait, but then can we deploy witnesses on the mirror nets? Oh, I guess.

A

You can yes yeah the way the way the mirror net works is uh we could just anybody we could. Basically, you can use your. I think. If I recall you could just use your own keys to do it, but um gandalf could correct me and I think what we're doing right now is we run with like on the mirror net. We have like a skeleton key and that skeleton key allows us to be any witness.

B

Can outfit making drugs in in the class.

A

B

um No I'm like explaining for the people who are listening on the as like a podcast, um okay, great so, okay, so that means uh in the coming days testnet is coming up. uh I mean what mirrornet uh most uh app devs will be able to test against it, uh spin up new nodes and see and get familiar with the code itself and yeah report to uh buy a post or whatever on on gitlab. Maybe if they find anything, and we should be good to go, you think.

B

There was more or less of an faq in the end. For for me, um do you guys have any other uh questions.

C

I just have questions regarding the ubuntu version: uh should we stay with uh 2004, or can we go to 2204.

A

uh It's gandalf's gonna say, but I I don't necessarily agree with him.

A

I I think, you're fine to use whichever one you want. um I I mostly am using 22 most a lot of other devs are using 20, uh but I've been testing, I would say 90 percent of the time on 22.. So.

B

And we can compile on 22.

A

C

A

That's when I test, I mean I compile, build and run there, so I do everything on the same system.

C

B

It's okay for me,.

B

Okay, okay, questions.

B

uh Looks like that's it. Okay, awesome uh in that case we'll! uh Well, I guess we'll we'll see each other on chain uh for the testing very soon.

A

Yeah, I guess the primary thing is: everybody should be getting ready to to test their stuff, so allocate some time for testing of apps and we'll, like, I said I'll I'll, make an announcement in the mattermost core dev channel when there's a when we tag a release. But, honestly, if you want to do some preliminary testing, you could go ahead with the develop and the problems we've. We like, I said we know of two problems, one only on shutdown and the other one is the other one.

A

We have a fixed board, but it's not been merged and yet.

B

A

Okay, great so mike, I guess what that means is that the fix we're likely to make probably would allow you to continue if you build with an old one.

B

No okay, that makes sense.

B

Yeah any last comments, questions.

A

Yeah, I guess in gandalf, said: please don't use it on the main net. That's.

B

A

On the main net yeah.

B

A

Yes, uh at least as a producer as a block producer, it's fun to use it. You can hook up to the main net and you can test on the main net. I mean just don't use it as your your block producer.

B

Yeah very very good uh should ask okay have a great day. Everyone goodbye.

A

Okay, so okay, crimson clad, said she's gonna contact the dab.

C

A

Witnesses to be sure that they're aware of what's going on okay, thanks guys I'll see ya.

C