Core developers meeting #15

in #hive4 months ago

You'll notice that the video is much better, this is all thanks to @crimsonclad,core devs meeting are now livestreamed. Be sure to tune in next time if you want to ask your questions live :)

Points touched:

Dev sync

I advise you to just listen to that part.

Why use account_id_type over account_name_type

We need to do more research on those types and decided that it wasn't critical to do those kinds of updates to the core chain now as memory usage has been reduced significantly already

Layer 1 smt + layer 2 smt ?

Why not assuming we have the resources to commit to finishing layer 1 smts, but for now no plan for layer 1, this is still quite blurry as we haven't finished evaluating which route to go to

Allow post/comment deletion with votes/active shares

We need to figure out why the steemit team added such limitation in the first place, but UX wise it's weird to be able to delete a post at 0$ and not be able at 0.01$ so why not.

Push the dev meeting by one hour

Yes. We will move the time a bit in the future to find the best time for everyone. Next meeting will be at 17 UTC (instead of 16 UTC)

Communities updates and fixes (from @asgarth)

It's a very long topic and it's better for you to listen in, but conclusion was that all of those point were "why not, will do"

Long term roadmap (at least one year) with dates

We don't want to commit to actual objectives because it's very hard to do, but for a rough idea of what's gonna be done @blocktrades just pointed to his post:

Better CoreDev Meetings reporting:

  • Summary of the points discussed + decision (ok, nok, postponed, requires gov/community feedback/vote, ...)
  • Summary of the points of the previous meeting still pending

Not much discussion there, it's great feedback from @arcange, this is what I'm doing right now ;)

Involving community devs

Lots of discussions there so I advise that you listen to it, but the idea about running a bug bounty program was discussed.

Documentation update

Definitely a must needed change, @gandalf and @howo both are thinking of hiring someone (we'll see how that goes)

Improve network security (

Better to listen in :)

Anonymous downvotes and upvotes (

It's quite hard to do anonymous things on a blockchain as it's public by nature, It's probably possible but needs quite a lot of research, we are not pursuing this for now.

Issues with Hive nodes (

We assumed it was mostly due to @anyx's node being out of date as he was the second failover node after @blocktrades, this led to some more discussion on node testing and auto failover


as a point to note, there's a bit more to be done to make this overlay look a bit more professional and the videos once uploaded to youtube will be improved a little bit further. I'm basically most focused on ensuring that these become more accessible for everyone who wants them.

I will work on having the live chat from at least and youtube integrated by next time as well, and getting 3speak running properly also.

It's cleaned up and looks much better, great work Crim!

Thank you @crimsonclad, @howo and the others for the updates!
Keep working!

Notes while listening, as per normal a lot of it was over my head.

I do like the idea of de-re-blogging a post. This would allow people to re-blog a post for visibility and then when that visibility is no longer need to un-re-blog it. (about the 0:50 minute mark)

I like the idea of being able to pin post on my own blog, would this option allow just pining my own post or would it allow me to pin other post? If pinning of other post this would be great for adding visibility to post a user would like to highlight on there blog for their followers, and an alternative to re-blogging.

Have pages for all the followers would be good, it does take time to scroll so 50 followers a page would be good.

I appreciate the responses to peoples questions, and I appreciate the response to my question/concerns.

Thank you all for the video, and post,

From the discussion I think it's your posts only. The change would mostly be a change in the order the posts are returned by the api node.

Thank you for always leaving great comments :)

Thanks, very neat format!

One other question: there were discussions about allowing proposal creators to lower (but not increase) the daily amount they ask for. I see that the work for that seems to have been completed: Was this change a part of the last hardfork? If so, does this mean proposal creators currently have the ability to reduce the amount they are asking for?

Yes ! You can also update the title and the post linked to it :)

Great meeting. Since no one seems to want to pick up the work on layer 1 SMTs at the moment, I was thinking about this possibility: For a long time we were comparing the possibilities of layer 1 SMTs vs a second layer smart contract solution for ALL SMTs, but what if there is a third option?

What if every dev who wants an SMT simply creates his own sidechain. This would allow him to implement all the smart contracts that he needs, and would remove the reliance on hive-engine.

And this would be as decentralized as hive-engine currently is, if not more, as soon as the code is open-sourced.

This would be made easy by @blocktrades work which will facilitate second layer developments on hive in the next few months.

What do you think of that? I don't know all the technical consequences of that would love a comment from you on that.

What if every dev who wants an SMT simply creates his own sidechain. This would allow him to implement all the smart contracts that he needs, and would remove the reliance on hive-engine.

This is basically solution 2 I think.
Think of ethereum, anyone can create tokens with smart contracts. The only thing that makes them interoperable are standards (ERC-20/ERC-721 etc) but in practice anyone can do whatever they want with it and create their tokens how they see fit.
So no need for multiple side chains as we can definitely have that on a single side chain.

Afaik the solution blocktrades is creating is going to be different from what hive engine is doing and will not depend on it so if you are worried about hive engine centralization, worry no more, as they will be two different system :)

Amazing. Thanks for the answer!

cosmos has a similar setup where anyone can create their own chain. As long as the layer 2's can communicate, we are good. It needs to be a seamless experience.

Thanks for the comment, had to go refresh my memory on cosmos. Building sidechains is good, but it still requires having many node operators to be decentralized. It's almost like starting a new blockchain which can be very hard.

The big selling point with Steemit's SMTs was that I could create an SMT myself without any experience, just a few clicks. I will be very bummed out if we don't get something like that. Whether layer 2 or layer 1, we need a UX like that.

Few clikcs for an SMT, no sidechains needed. Simple and efficient.

And we will probably get that experience :)

Remind me to Ardor and their blockchain as a service technology and their child chain technology. Not sure about the innerworks but it was some of the tech that also Komodo adopted for inter-chain communication as well as atomic swaps.

Definitely a must needed change, @gandalf and @howo both are thinking of hiring someone (we'll see how that goes)

Make @inertia great again.

Definitely @inertia is a good candidate for docs / dev portal improvement. I thought that he's not doing his proposals anymore because of PTSD (you can really suffer from it when you had anything to do with our APIs and docs ;-) )

Cheers, @minnowspower You Successfully Shared 0.100 WINE With @howo.
You Earned 0.100 WINE As Curation Reward.
You Utilized 3/3 Successful Calls.


WINE Current Market Price : 0.000 HIVE

Obviously monetary value was created at 0.01. A reasonable threshold. Coder intellectuals are so incompetent sometimes.

Don't tell me you guys went through all that trouble just to do a worse job. Tragic.

I know, we actually discussed this at length if you had listened to the meeting. The main question was "if the post has rewards and is deleted, is there a code limitation that prevented this because it would mess other post payout or was it just something to protect against spam (create a spam post, vote it, hide it by deleting it)"

The solution that was discussed was that in case you delete your post it would remove all rewards from that post.

Great Job! Keep up the good work.

I did notice i was able to listen live.

My one addition was that I think I recall @roadscape say he had mostly finished coding for communities that limited posting to members.

My concern is that this setting was only choose-able at community creation and not after the fact. I hope I'm wrong.

Is there some sort of more in-depth explanation of the issue between having a layer 1 solution and issue? I would like to have some kind of article explaining the challenges.

Would be great if you can add timestamps on the points so it can go to the point on the video timeline.

I'm thinking of doing that, I need to find the time to do that.

Who are the ones involved with smt on hive at the moment?

Who are the ones involved with smt on hive at the moment?