Hive core developer meeting #26

in #core10 months ago

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 points:

Dev sync:

Listen to that one

direct rc delegations:

Work is well underway on my end, I basically talk about what I said last week there: I fixed the api problem and now am building automated test cases. It's going to take a little while

VOP for hive -> DHF conversion:

I'll do it. it's a change with little to no impact on performance. It's an issue today because if you send hive to the dhf then there is nothing that's stored in the blockchchain to tell future users how much hbd we got out. And with the rise of hbdstablizer by @smooth, for a lot

VOP for proposals creation containing the ID hive

It's an issue because if you parse the blockchain you can't get the id of a proposal after it was created unless you actively call an api call, which doesn't scale. Same it's something with little impact on performance that I'll tackle.

cli_wallet command history persistence (commands are saved when quitting and restarting the program)

Something that I will tackle sooner or later, it's mostly for power users where it's annoying to lose your progress once you close cli_wallet.

plans for hf26 ?

I figured we would throw some ideas around and talk about them, like dynamic rc costs, automated actions, NAI etc. There are a bunch of talks in there. Keep in mind nothing is final it's mostly thoughts we had on things we'd like to see for hf26. But hf26 is very far away so everything might change, or be rejected by the community.

I heavily encourage your to listen to that one, but basically there a few ideas thrown around improving hive as a core like peer to peer connectivity (block sync) and the forking logic, dynamic rcs costs (a small post should cost less rc than a big post) etc
As for some of the more "controversial"/ things that people notice changes:

Discussions about accelerated power down time for a fee (@theycallmedan talked about it in length on how we could implement this)
less than 10 votes a day (maybe 5), basically allow 200% votes.
Use NAI for assets

Then there was a bunch of questions from @arcange that I encourage you to listen to because we jump from subject to subject.

Cheers, @howo


The rewards earned on this comment will go directly to the person sharing the post on Twitter as long as they are registered with @poshtoken. Sign up at

I'm going to reblog this to listen to it later, I'm sure it's very interesting to see what direction the Blockchain is heading in.

It would be nice to get a VOP at the time of collateralized convert to indicate the amount of HBD out. This is included in the fill VOP, but that doesn't appear until 3.5 days later. During that time period there is nothing to record the change in balance from the immediately-delivered HBD.

Smts are still a thing? A lot of people really want to build on hive, but it would need a token that can be listed on exchanges. Onchain balance would be so important IMO.

HE tokens are IMO impossible to list on exchanges ( except the ETH versions of it).

SMT's question was asked at 26:35:

got a phone call :) so I had to stop after some time. I think i watch it later

@blocktrades Layer 2 Smts means we can list them on exchanges without an ETH or other smart contract versions?

It's my plan to bundle Layer2 app support into the package we deliver to exchanges, so our layer 2 smart contract system should allow for tokens to be supported on exchanges with minimal effort by the exchanges.

perfect! is there anything you need/hive can do, to help you to get it done? :)

It sounds so good, and I'm in love with Smts since years :D

I really enjoyed most of the lessons but I need more directions and instructions as a beginner

This is an interesting piece of work, the configuration is worth learning because of the converter. The changes made to the CLI wallet was awesome.
Thanks for this.