create account

Core developers meeting #15 by howo

View this thread on: hive.blogpeakd.comecency.com
· @howo ·
$28.29
Core developers meeting #15
https://www.youtube.com/watch?v=WkG7ga9gXh4

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: https://peakd.com/hive-139531/@blocktrades/roadmap-for-hive-related-work-by-blocktrades-in-the-next-6-months

## 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 (https://peakd.com/hive/@bashadow/re-howo-qm4a9r)

Better to listen in :)

## Anonymous downvotes and upvotes (https://peakd.com/hive/@mariuszkarowski/re-howo-qm4046)

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 (https://peakd.com/hive/@borislavzlatanov/re-howo-qmdaum)

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
👍  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and 258 others
properties (23)
authorhowo
permlinkcore-developers-meeting-15
categoryhive
json_metadata{"app":"peakd/2020.12.3","format":"markdown","tags":["hive","core","dev","meeting"],"users":["crimsonclad","asgarth","blocktrades","arcange","gandalf","howo","bashadow","mariuszkarowski","borislavzlatanov","anyx"],"links":["/@crimsonclad","/@asgarth","/@blocktrades","https://peakd.com/hive-139531/@blocktrades/roadmap-for-hive-related-work-by-blocktrades-in-the-next-6-months","/@arcange","/@gandalf","/@howo","https://peakd.com/hive/@bashadow/re-howo-qm4a9r","https://peakd.com/hive/@mariuszkarowski/re-howo-qm4046","https://peakd.com/hive/@borislavzlatanov/re-howo-qmdaum"]}
created2021-01-05 17:31:57
last_update2021-01-05 17:31:57
depth0
children27
last_payout2021-01-12 17:31:57
cashout_time1969-12-31 23:59:59
total_payout_value16.556 HBD
curator_payout_value11.738 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length2,932
author_reputation515,737,941,459,006
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,232,392
net_rshares143,463,334,138,575
author_curate_reward""
vote details (322)
@bashadow ·
$1.85
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)

(0:55)
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.

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

(1:21)
I appreciate the responses to peoples questions, and I appreciate the response to my question/concerns.

Thank you all for the video, and post,  



👍  , ,
properties (23)
authorbashadow
permlinkre-howo-qmh8ux
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-05 19:59:18
last_update2021-01-05 19:59:18
depth1
children1
last_payout2021-01-12 19:59:18
cashout_time1969-12-31 23:59:59
total_payout_value0.926 HBD
curator_payout_value0.926 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length875
author_reputation100,388,692,638,882
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,234,122
net_rshares10,034,178,395,914
author_curate_reward""
vote details (3)
@howo ·
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 :) 
properties (22)
authorhowo
permlinkre-bashadow-qmhr8y
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-06 02:36:33
last_update2021-01-06 02:36:33
depth2
children0
last_payout2021-01-13 02:36:33
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length188
author_reputation515,737,941,459,006
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,239,578
net_rshares0
@borislavzlatanov ·
$1.71
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: https://gitlab.syncad.com/hive/hive/-/issues/39  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?
👍  ,
properties (23)
authorborislavzlatanov
permlinkre-howo-qmh6wg
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-05 19:17:03
last_update2021-01-05 19:17:03
depth1
children1
last_payout2021-01-12 19:17:03
cashout_time1969-12-31 23:59:59
total_payout_value0.856 HBD
curator_payout_value0.857 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length423
author_reputation23,556,498,017,463
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,233,700
net_rshares9,393,846,232,719
author_curate_reward""
vote details (2)
@howo ·
Yes ! You can also update the title and the post linked to it :)
👍  
properties (23)
authorhowo
permlinkre-borislavzlatanov-qmhr65
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-06 02:34:54
last_update2021-01-06 02:34:54
depth2
children0
last_payout2021-01-13 02:34:54
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length64
author_reputation515,737,941,459,006
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,239,564
net_rshares144,827,536,456
author_curate_reward""
vote details (1)
@btcmillennial · (edited)
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.
properties (22)
authorbtcmillennial
permlinkqmhvz2
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-06 04:18:39
last_update2021-01-06 04:30:09
depth1
children2
last_payout2021-01-13 04:18:39
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length205
author_reputation12,319,059,273,546
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,240,487
net_rshares0
@howo · (edited)
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. 
properties (22)
authorhowo
permlinkre-btcmillennial-qmik8w
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-06 13:02:57
last_update2021-01-06 13:07:57
depth2
children1
last_payout2021-01-13 13:02:57
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length450
author_reputation515,737,941,459,006
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,245,505
net_rshares0
@btcmillennial ·
Great Job! Keep up the good work.
properties (22)
authorbtcmillennial
permlinkqmildb
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-06 13:27:12
last_update2021-01-06 13:27:12
depth3
children0
last_payout2021-01-13 13:27:12
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length33
author_reputation12,319,059,273,546
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,245,831
net_rshares0
@crimsonclad ·
$11.59
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 vimm.tv and youtube integrated by next time as well, and getting 3speak running properly also.
👍  , , , , , , , , , ,
properties (23)
authorcrimsonclad
permlinkqmh394
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-05 17:58:18
last_update2021-01-05 17:58:18
depth1
children2
last_payout2021-01-12 17:58:18
cashout_time1969-12-31 23:59:59
total_payout_value5.794 HBD
curator_payout_value5.794 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length426
author_reputation323,763,088,722,311
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,232,725
net_rshares52,399,461,706,828
author_curate_reward""
vote details (11)
@resiliencia ·
Thank you @crimsonclad, @howo and the others for the updates!
Keep working! 
properties (22)
authorresiliencia
permlinkre-crimsonclad-qmhaew
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-05 20:32:57
last_update2021-01-05 20:32:57
depth2
children0
last_payout2021-01-12 20:32:57
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length76
author_reputation439,416,110,152,638
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,234,568
net_rshares0
@theycallmedan ·
It's cleaned up and looks much better, great work Crim!
properties (22)
authortheycallmedan
permlinkqmh4no
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-05 18:28:39
last_update2021-01-05 18:28:39
depth2
children0
last_payout2021-01-12 18:28:39
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length55
author_reputation1,254,058,380,138,691
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,233,118
net_rshares0
@enforcer48 ·
$0.27
> Definitely a must needed change, @gandalf and @howo both are thinking of hiring someone (we'll see how that goes)

Make @inertia great again.
👍  , ,
👎  ,
properties (23)
authorenforcer48
permlinkre-howo-qmhebg
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-05 21:57:18
last_update2021-01-05 21:57:18
depth1
children1
last_payout2021-01-12 21:57:18
cashout_time1969-12-31 23:59:59
total_payout_value0.136 HBD
curator_payout_value0.136 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length143
author_reputation426,238,777,098,689
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,235,724
net_rshares1,959,044,360,407
author_curate_reward""
vote details (5)
@gtg ·
$0.28
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 ;-) )
👍  
properties (23)
authorgtg
permlinkqmim5l
categoryhive
json_metadata{"users":["inertia"],"app":"hiveblog/0.1"}
created2021-01-06 13:44:09
last_update2021-01-06 13:44:09
depth2
children0
last_payout2021-01-13 13:44:09
cashout_time1969-12-31 23:59:59
total_payout_value0.138 HBD
curator_payout_value0.138 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length230
author_reputation461,864,997,189,447
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,246,049
net_rshares2,025,911,530,657
author_curate_reward""
vote details (1)
@jarvie ·
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. 
properties (22)
authorjarvie
permlinkre-howo-qmj6u3
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2021.01.1"}
created2021-01-06 21:10:51
last_update2021-01-06 21:10:51
depth1
children0
last_payout2021-01-13 21:10:51
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length296
author_reputation388,491,264,112,133
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,252,109
net_rshares0
@jza ·
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.
properties (22)
authorjza
permlinkqn5gbj
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-18 21:42:57
last_update2021-01-18 21:42:57
depth1
children0
last_payout2021-01-25 21:42:57
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length174
author_reputation38,038,019,310,991
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,437,577
net_rshares0
@jza ·
Would be great if you can add timestamps on the points so it can go to the point on the video timeline.
properties (22)
authorjza
permlinkqn5grt
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-18 21:52:42
last_update2021-01-18 21:52:42
depth1
children1
last_payout2021-01-25 21:52:42
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length103
author_reputation38,038,019,310,991
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,437,715
net_rshares0
@howo ·
I'm thinking of doing that, I need to find the time to do that.
👍  
properties (23)
authorhowo
permlinkre-jza-qn8xca
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2021.01.3"}
created2021-01-20 18:43:21
last_update2021-01-20 18:43:21
depth2
children0
last_payout2021-01-27 18:43:21
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length63
author_reputation515,737,941,459,006
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,472,700
net_rshares8,340,829,228
author_curate_reward""
vote details (1)
@jza ·
Who are the ones involved with smt on hive at the moment?
properties (22)
authorjza
permlinkqn8ont
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-20 15:35:54
last_update2021-01-20 15:35:54
depth1
children0
last_payout2021-01-27 15:35:54
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length57
author_reputation38,038,019,310,991
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,470,221
net_rshares0
@jza ·
Who are the ones involved with smt on hive at the moment?
properties (22)
authorjza
permlinkqn8oo7
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-20 15:36:09
last_update2021-01-20 15:36:09
depth1
children0
last_payout2021-01-27 15:36:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length57
author_reputation38,038,019,310,991
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,470,223
net_rshares0
@marki99 ·
$0.41
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. 


👍  
properties (23)
authormarki99
permlinkre-howo-qmh3vt
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-05 18:11:54
last_update2021-01-05 18:11:54
depth1
children6
last_payout2021-01-12 18:11:54
cashout_time1969-12-31 23:59:59
total_payout_value0.204 HBD
curator_payout_value0.205 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length846
author_reputation11,400,723,818,181
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,232,919
net_rshares2,756,300,488,021
author_curate_reward""
vote details (1)
@howo ·
> 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 :)  
👍  
properties (23)
authorhowo
permlinkre-marki99-qmhrir
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-06 02:42:27
last_update2021-01-06 02:42:27
depth2
children1
last_payout2021-01-13 02:42:27
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length803
author_reputation515,737,941,459,006
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,239,639
net_rshares2,886,194,286
author_curate_reward""
vote details (1)
@marki99 ·
Amazing. Thanks for the answer!
properties (22)
authormarki99
permlinkre-howo-qmi0vx
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-06 06:04:45
last_update2021-01-06 06:04:45
depth3
children0
last_payout2021-01-13 06:04:45
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length31
author_reputation11,400,723,818,181
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,241,723
net_rshares0
@theycallmedan ·
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.
👍  
properties (23)
authortheycallmedan
permlinkqmh4ri
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-05 18:30:57
last_update2021-01-05 18:30:57
depth2
children3
last_payout2021-01-12 18:30:57
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length160
author_reputation1,254,058,380,138,691
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,233,150
net_rshares2,863,497,510
author_curate_reward""
vote details (1)
@jza ·
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.
properties (22)
authorjza
permlinkqn5gk6
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-18 21:48:06
last_update2021-01-18 21:48:06
depth3
children0
last_payout2021-01-25 21:48:06
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length235
author_reputation38,038,019,310,991
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,437,659
net_rshares0
@marki99 · (edited)
$0.30
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. 
👍  , , ,
properties (23)
authormarki99
permlinkre-theycallmedan-qmhevj
categoryhive
json_metadata{"tags":["hive"],"app":"peakd/2020.12.3"}
created2021-01-05 22:09:21
last_update2021-01-06 00:01:18
depth3
children1
last_payout2021-01-12 22:09:21
cashout_time1969-12-31 23:59:59
total_payout_value0.152 HBD
curator_payout_value0.152 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length538
author_reputation11,400,723,818,181
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,235,878
net_rshares2,165,407,863,676
author_curate_reward""
vote details (4)
@minnowspower ·
!wine
properties (22)
authorminnowspower
permlinkqmhscn
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2021-01-06 03:00:24
last_update2021-01-06 03:00:24
depth1
children1
last_payout2021-01-13 03:00:24
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length5
author_reputation2,668,591,933,105
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,239,819
net_rshares0
@wine.bot ·
<center>
<sup>Cheers, @minnowspower You Successfully Shared <b>0.100 WINE</b> With @howo.</sup>
<sup>You Earned <b>0.100 WINE</b> As Curation Reward.</sup>
<sup>You Utilized <b>3/3</b> Successful Calls.</sup>

<img src="https://files.peakd.com/file/peakd-hive/hiveupme/U5hr4v6K-Wine2Greeting.png" alt="wine-greeting">

---
<sup>[WINE Current Market Price](https://hive-engine.com/?p=market&t=TESTO) : <b>0.000 HIVE</b></sup>
</center>
properties (22)
authorwine.bot
permlink20210106t030042500z
categoryhive
json_metadata{"tags":["wine","wineyard"],"app":"tan-bot/1.1","format":"markdown"}
created2021-01-06 03:00:42
last_update2021-01-06 03:00:42
depth2
children0
last_payout2021-01-13 03:00:42
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length435
author_reputation8,889,474,969,673
root_title"Core developers meeting #15"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id101,239,822
net_rshares0