Hive core developer meeting #21

in #meeting5 months ago (edited)

2:47 - Intro(Howo)
3:34 - (Blocktrades) - changes and future planning
8:53 - RC plugin
10:40 - Usage of memory
15:33 - incoming RC delegation api feature
17:08 - json operation limit per block
21:46 - Testnet + Bug bounty
22:54 - Hive stem hackathon
26:01 - test voice on another platform like jitsi and stop paying zoom fees
26:53 - move the meeting ahead by few hours
29:18 - Soft cap hf25 or hf26
31:00 - Max curation rewards on top of author rewards
33:15 : Review Issues on gitlab

If you're listening to the whole thing, please post timestamps as a comment, the first one to do so (and correctly) will get a 100% upvote from me :)

meeting tl;dr:

Dev sync

As usual it's better to listen to this part

RC delegations

@blocktrades and team are concerned about some design decisions (operations in a non consensus plugin), after some offline discussions we realized that it was fine, we were just not aligned on semantics.

Then there are some memory concerns (a lot of new data is stored). I will be running some tests this week to build a million delegations and see the memory impact it would have on nodes, it shouldn't cost more than a extra gig of ram. So I'll be building a test to monitor this.

Also while we were discussing offline, we realized that rc delegates were non consensus meaning that it could be rolled out without a hard fork, and ultimately decided to push them to hf25.1, the reasoning being that there is no reason to risk the health of the chain making a big release when we can release hf25 and then a bit later release hf25.1 with rc delegations. I know it will come as a disapointment to some, but one of the core principles of the dev team is risk averse and if we can avoid a risk / spread it over multiple smaller releases, we will do it.

Incoming rc delegations index

Us implementing the index or not will depend on the result from the memory cost of the rc plugin, but it may have to be done via L2

Increase custom json operation limit per block

Would be a problem as we go into the middle of 2021 with a lot of applications relying on it, it's actually not a problem, as the limit is "per account per block" and not "per block".

Testnet setup + date (?) + bug bounty ?

Testnet will be setup by voluntary witnesses (most likely myself), date is still kinda undetermined, but could be as early as the end of the week, the "human" cost of organizing a bug bounty was deemed to big compared to the benefits it brings.

HiveStem hackathon on core dev things ?

We figured that it would be interesting to let people hack on hivemind, so I will be creating a guide on how to setup a dev hivemind environment so participants can participate on it if they want (things like communities, sorting algorithms etc)

Test another platform like jitsi and stop paying zoom fees

We'll need to see with @roelandp who currently pays for the account and @crimsonclad who manages the stream but we are inclined to use any platform really.

Move the meeting ahead by a few hours

There is a bit of wiggle room (1/2 hours early, an hour after), we'll run a poll with current regular participants to see what would fit them best.

soft cap in hf25 or hf26

https://gitlab.syncad.com/hive/hive/-/issues/140 we will roll out a fix on hf25, it's a very small change but an important one for hive -> hbd conversions.

from @guiltyparties:

Review of open issues on gitlab (who, when, ...). Some are 1 year old.

The possibility for authors/dapps to set a) max accepted rewards to author AND b) max accepted rewards to curator ---- both values required or set to default. Usecase: dapp wants to limit rewards for posts through it to 1$ for authors but to $10 for curators.

I think it would be possible to get close to that output via beneficiaries and max payout, I can't remember if curation rewards are before or after beneficiaries (before would make more sense) so let's say you want 1$ to the author and 10$ to curators, you can set the max reward to 20$, and a 90% beneficiary to @null, that way when it's computed you get:

50% of the reward goes to curators = 10$, out of the remaining 10$ for the author 9$ goes to @null, and 1$ goes to the author.

Something to play around with, but I think this can be done purely using the existing chain functionalities.

from @arcange:

Review of open issues on gitlab (who, when, ...). Some are 1 year old.

Some discussion regarding on who's responsibility it falls to follow up with open tickets and who should close tickets, better to listen to this part.

Then we reviewed and closed https://gitlab.syncad.com/hive/hive/-/issues/61 and https://gitlab.syncad.com/hive/hive/-/issues/14

Support what I'm doing

If you like what I'm doing, please consider voting on my new proposal:
https://peakd.com/proposals/167
hivesigner

Sort:  

2:47 - Intro(Howo)
3:34 - (Block trades) -changes and future planning
8:53 - RC plugin
10:40 - Usage of memory
15:33 - High power delegation api feature
17:08 - json operation limit per block
21:46 - Bug bounty
22:54 - Hive steam hackathon
26:01 - Test another platform like jitsi and stop paying zoom fees
26:53 - Moving meeting ahead by few hours
29:18 - Soft cap hf25 or hf26
31:00 - Max rewards
33:15 : Issues on gitlab

I quite prefer Jitsi, myself, but I'm flexible and can create a nice looking and functional meeting stream out of almost any input, so there's no worries about me. I run Zoom sandboxed pretty much solely to participate in the dev meetings. Right now I pay for the restreaming (multiple outputs from one ingest) software that I use to share the stream to multiple places out of pocket as it's not a wholly unreasonable fee, but that's not strictly necessary if we decided to livestream only to one platform. However, only one streaming location (especially something as fickle as YT) is just not very good decentralization practices, especially when we have Vimm.TV and other native solutions :)

@dtube was talking to @hellotelos because we have DSTOR (Like IPFS Torrent tech on eosio chain like steem/hive, but smart contracts... for 720P HD streaming video on chain ... yes it requires the streamers buy and stake a LOT of tokens foir the cpu and ram but thats the point! never have your Trump TV stream taken down off teh starlink

hive needs to have someone make a documentary about hive and then ask for the proposal funding after its made, and just use hive upvotes to make it.

whoerver makes a short 20 min hive doc to explain steem dan ned and justin and then hive which doenst have a real leader, i mean, our leader is just @blocktrades an anonymous website lol maybe the leader of hive now wouldbe voted in as @leofinance or @aggroed lol i wonder who would win as president

Sounds like things are pretty close to freezing and then testing. I look forward to next week to see if the code was froze and testing started.

...no reason to risk the health of the chain making a big release when we can release hf25 and then a bit later release hf25.1 with rc delegations

Very comforting to see that the health of the chain is taking priority.

Once again thank you for helping keep us informed.

Very comforting to see that the health of the chain is taking priority.

Yeah it's the number one priority, no new feature can be more important than the stability.

this isnt development, its just maintanace and the same lazy work as changing scotbot settings lol

Lets see REAL development Like I do, bringing real smartcontracts from EOSIO and telos to hive

Telos is why Appics left steem but to for hive, fgor @hellotelos

telois is willing to merge with hive you know, its not a competition

we need hive as our social media lase layer 0 !

curation should be intertwined to telos CPU stake!

Hivepower should be linked to Telos RAM !

too few peopel talk about these changes. you have to stop being so nerdy and closed, i know you guys hold these skills close to your chest but COME ON MAN... make a documentrary on Steem and hive and how important your work is!

we need to knopw what curation is! the regular people dont know! they dont know what these words meana nd you sound like wizards! But after 4 years of slow education we all understand

but you could make a really powerful documentrarty or infographic or explainer video , but we have no one professional making videos because artists always move on and make better work lol

we need to take HBD from Hivedao and have some fivver artist make videos for every update you make here

we need to PRESENt hive as smarter .. its so smart

you guys are so smart but no one knows what a Soft cap or hard fork is! But they could

you need a DOCUMENTARY on how hard hive devs do work and to explain curation, rewards, steempower hive power and why hive had to be forked and show lives of witnesses who had to deal with 30 million dollars stolen after years of hard work etc, Americans will start investing, real patriots who hate eveyrthing right now in big tech would love to see this we just need to be a lil more patriotic too... and make that documentary damnit

bro why would we make a documentary on steem about our development skills

nfts on bitshares how utterly lame lol wow

we have nfts on wax guys they have real brands and a future https://wax.atomichub.io

In order to develop Hive, I support everything that is good

The possibility for authors/dapps to set a) max accepted rewards to author AND b) max accepted rewards to curator ---- both values required or set to default. Usecase: dapp wants to limit rewards for posts through it to 1$ for authors but to $10 for curators.

50% of the reward goes to curators = 10$, out of the remaining 10$ for the author 9$ goes to @null, and 1$ goes to the author.

This should be implemented for the entire Hive universe.

Otherwise other significant changes are needed, such as ending the use all together of curation bots, which is used by those exploiting the blockchain, including some witnesses, so their actions of using dozens and sometimes hundreds of accounts are not able to be automated in a way that blends them in with other actual users.

Well feel free to go ask front ends to implement it, it's not up to the chain to do it.

..

.

So first of all, I don't see where you are coming from with this witness witch hunt, we are subject to the same rules on the chain as others.

This is not at all what was discussed in the call, he just mentioned the capacity to be added on posts if they so chose. Not a blanket change, more like a new feature if dapps want, for instance reward short content but not penalize curators.

..

..

..