create account

Core dev meeting #42 by howo

View this thread on: hive.blog |  peakd.com |  ecency.com
core · @howo · (edited)
$202.64
Core dev meeting #42
![social_hive_light.jpg](https://files.peakd.com/file/peakd-hive/howo/23wN2RDCNPLiYdw6WJdTT7vXKrdkPN9WGeQg69m15z27Bqj1yDiYS5bo2Dwn4DGHByM2C.jpg)

Hello,

I'm really sorry about the lack of video, we had recording problems, and couldn’t record the meeting.

Instead I wrote some notes to give you an idea of what was discussed, I'm sorry this is incomplete and we'll switch to @gtg's video solution next so that those issues won't happen again.

## Developers sync: 

On my end I mostly spent time updating my hivemind pull requests following the hardfork changes and supporting RC delegation questions (many heart attacks of people telling me it doesn’t work when in fact it’s something they did wrong).

Then I started working on implementing a feature request by @brianoflondon for recurrent transfers: https://gitlab.syncad.com/hive/hive/-/issues/382 

On @blocktrades side (this is somewhat of a non-exhaustive list and will probably be in greater details in a post of his own):

There was some cleanup work following hard fork 26/27, doing some performance analysis on nodes, to see how things have changed.

Then they pushed a bunch of small changes:

- Fixed a problem with shutdowns that could happen sometimes when you did ctrl + c on a node.

- Fixes and improvements to the block statistics 

- Added more RC statistics in the form of daily report, with a new API about it (this will happen in hf 27.1)

- New api calls for updated witness scheduling

- CLI wallet side, fixed a longstanding bug to allow controlling it from websockets.

- Updated our cryptography lib to increase performance (tests ongoing but so far the initial testing shows a 40% increase !)

- New block log utility to help manage compressed block logs:

   - Comparing compressed block logs to output a checksum even though they were compressed using different methods
   - Truncating a compressed block log (previously you had to uncompress, truncate, then re-compress) 

-  Improved get_block_range by forcing it to use http to improve performance due to a websocket issue. The current suspect is that websockets is doing compression which causes slowdowns 


## Adding a VOP to record successful RC delegation

We talked a bunch about the potential use cases and  potential edge cases and issues.

The main discussion revolved around the fact that it’s hard to track if an RC delegation got executed or not (and what was executed). But after some back and forth, we concluded that since the node rejects incorrect transactions, it made sense to let the custom json denote of the change.

Hive version 1.27.1: 

We want to ship version 1.27.1 very soon:tm: (aka in a few weeks) to provide improvements to HAF and hivemind. We’ll try to slot in a change to RC delegations to include an RC minimum to prevent spam and improve dev experience.

We’ll try to include at the bug that @engrave brought up: https://gitlab.syncad.com/hive/hive/-/issues/338  

There's then a lot of discussions between @arcange and @blocktrades on his specific HAF setup that I don't think are really worth talking about.
👍  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and 504 others
👎  , ,
properties (23)
authorhowo
permlinkcore-dev-meeting-42
categorycore
json_metadata{"app":"peakd/2022.10.3","format":"markdown","tags":["core","dev","meeting"],"users":["gtg","brianoflondon","blocktrades","engrave","arcange"],"image":["https://files.peakd.com/file/peakd-hive/howo/23wN2RDCNPLiYdw6WJdTT7vXKrdkPN9WGeQg69m15z27Bqj1yDiYS5bo2Dwn4DGHByM2C.jpg"]}
created2022-11-07 22:42:42
last_update2022-11-09 16:30:18
depth0
children21
last_payout2022-11-14 22:42:42
cashout_time1969-12-31 23:59:59
total_payout_value101.364 HBD
curator_payout_value101.280 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length3,082
author_reputation511,962,302,102,641
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,152,323
net_rshares465,747,940,601,716
author_curate_reward""
vote details (571)
@antisocialist · 
I was asking to add who sold and who bought as a 3rd line below the price and bought/sold on the right, but they said the api didn't provide that data and that it was a core issue.
Can you help with this?

https://beta.hivehub.dev/market/limit

![image.png](https://files.peakd.com/file/peakd-hive/antisocialist/23tRxJZhyx2Ze2fQJowRtUN6z1wdbTkiBRcEz2MMZzFQyJMYbZvyLtZQm7XBsQucgb5GZ.png)


![image.png](https://files.peakd.com/file/peakd-hive/antisocialist/Eo1wpgrKBFdBcxnuUT9GJrzGuUxiv8iXJzRsYQRFSZ5jhZ7k8sc6aDHXbcpzP1bdgTP.png)
properties (22)
authorantisocialist
permlinkre-howo-rlpjt6
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.11.1"}
created2022-11-21 17:12:42
last_update2022-11-21 17:12:42
depth1
children0
last_payout2022-11-28 17:12: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_length529
author_reputation273,683,974,280,829
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,509,736
net_rshares0
@arcange · 
Who is @arcage? Were none of his questions worthy of interest?
I find it unfortunate that you limit the content of your meeting report according to your personal opinion.
👍  
properties (23)
authorarcange
permlinkre-howo-rl1pbk
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-08 20:09:24
last_update2022-11-08 20:09:24
depth1
children1
last_payout2022-11-15 20:09: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_length170
author_reputation1,146,606,639,109,506
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,175,988
net_rshares1,927,847,106
author_curate_reward""
vote details (1)
@howo · 
> Who is @arcage? 
Fixed thanks :p

> Were none of his questions worthy of interest?

Sorry, given that they were highly specific to your use cases (like the conversation on your HAF setup) it was hard to follow and take notes on it so I couldn't include it. But feel free to write something as a reply to this comment, I'll gladly edit the post to include them.
properties (22)
authorhowo
permlinkre-arcange-rl39t9
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.11.1"}
created2022-11-09 16:29:33
last_update2022-11-09 16:29:33
depth2
children0
last_payout2022-11-16 16:29: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_length362
author_reputation511,962,302,102,641
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,198,672
net_rshares0
@brianoflondon ·
Thank you for your support before, will you support now?
Thank you so much for your support of my @v4vapp proposals in the past, my previous one expired this week.

I'd be really happy if you would continue supporting my work by voting on this proposal for the next 6 months:

- [Proposal 244 on PeakD](https://peakd.com/me/proposals/244)
- [Proposal 244 with Hivesigner](https://hivesigner.com/sign/update-proposal-votes?proposal_ids=%5B244%5D&approve=true)
- [Proposal 244 on Ecency](https://ecency.com/proposals/244)

Additionally you can also help this work with a [vote for Brianoflondon's Witness using KeyChain or HiveSigner](https://vote.hive.uno/@brianoflondon)

If you have used [v4v.app](https://v4v.app/) I'd really like to hear your feedback, and if you haven't I'd be happy to hear why or whether there are other things you want it to do.
properties (22)
authorbrianoflondon
permlinkre-core-dev-meeting-42-20221213t124018z
categorycore
json_metadata"{"app": "v4vapp"}"
created2022-12-13 12:40:18
last_update2022-12-13 12:40:18
depth1
children0
last_payout2022-12-20 12:40:18
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_length795
author_reputation760,188,324,097,883
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id119,080,188
net_rshares0
@cal02 · 
Hola amigo, gracias por tú voto y por visitarnos ❤️
properties (22)
authorcal02
permlinkrmnm6y
categorycore
json_metadata{"app":"hiveblog/0.1"}
created2022-12-10 02:42:36
last_update2022-12-10 02:42:36
depth1
children0
last_payout2022-12-17 02:42:36
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_length51
author_reputation13,554,613,243,080
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,992,301
net_rshares0
@deepresearch · 
Nice to see an update! RC delgation seems to be working fine for me, however RC cost for account creation token apparently is the same as pre-hardfork. Does it work as intended?
👍  
properties (23)
authordeepresearch
permlinkre-howo-2022118t7355611z
categorycore
json_metadata{"tags":["core","dev","meeting"],"app":"ecency/3.0.34-mobile","format":"markdown+html"}
created2022-11-08 06:35:03
last_update2022-11-08 06:35:03
depth1
children2
last_payout2022-11-15 06:35:03
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_length177
author_reputation163,080,111,191,269
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,159,683
net_rshares41,025,630,250
author_curate_reward""
vote details (1)
@andablackwidow ·
$0.08
Eh, I kept looking for the source of the rumor about the increase in RC cost of account tokens, but have not found it...

Yes, working as intended. The parameters that govern account token pool are set directly by witnesses. That was enough reason to make sure other RC changes don't affect it. Besides account tokens are already outrageously expensive and they swing in price by 30% on daily basis (due to pool being almost dry all the time). Not much room to make them even more costly IMHO.

> New account tokens - no change (by design).

Refer to [this article](https://hive.blog/hive-139531/@andablackwidow/are-customjson-going-to-be) for comprehensive description of all RC changes.
👍  
properties (23)
authorandablackwidow
permlinkre-deepresearch-2022119t13941978z
categorycore
json_metadata{"tags":["core","dev","meeting"],"app":"ecency/3.0.28-surfer","format":"markdown+html"}
created2022-11-09 00:39:36
last_update2022-11-09 00:39:36
depth2
children0
last_payout2022-11-16 00:39:36
cashout_time1969-12-31 23:59:59
total_payout_value0.038 HBD
curator_payout_value0.039 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length688
author_reputation84,494,108,783,084
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,181,857
net_rshares181,890,153,120
author_curate_reward""
vote details (1)
@howo · 
I'm not sure if this was changed with the various transaction adjustments, @blocktrades do you know ?
properties (22)
authorhowo
permlinkre-deepresearch-rl1lyw
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-08 18:56:54
last_update2022-11-08 18:56:54
depth2
children0
last_payout2022-11-15 18:56: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_length102
author_reputation511,962,302,102,641
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,174,373
net_rshares0
@engrave ·
$0.14
Thanks, I believe it's worth fixing this long-standing bug with market history API. We have an API to serve OCHLV data to create candlestick charts for the internal market and we can't use it because it's broken. It would be great to see such data together with market depth chart.
👍  , , , , , , , , , , , ,
properties (23)
authorengrave
permlinkre-howo-rl02bc
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-07 22:55:09
last_update2022-11-07 22:55:09
depth1
children0
last_payout2022-11-14 22:55:09
cashout_time1969-12-31 23:59:59
total_payout_value0.070 HBD
curator_payout_value0.069 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length281
author_reputation318,719,797,600,724
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,152,543
net_rshares328,644,240,812
author_curate_reward""
vote details (13)
@getron · 
Hi @howo , want to ask you, what is going on with the ExxP project? It seems like it is dead, almost 2 years no update at all???

Do you plan to update and to maintain this project? Or what is happening there?

Because, the plugin is not working almost at all, and there are many errors and conflicts with most other things in WP.

Can you please give us an update on this?

I would like to see this project updated, because, it works great and it has great potential to be one of the best there.
👍  ,
properties (23)
authorgetron
permlinkre-howo-rl0250
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-07 22:51:00
last_update2022-11-07 22:51:00
depth1
children0
last_payout2022-11-14 22:51:00
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_length496
author_reputation507,066,527,013
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,152,466
net_rshares0
author_curate_reward""
vote details (2)
@katirayo · 
You are forgiven, it is not really your fault.

>Hello,

I'm really sorry about the lack of video, we had recording problems, and couldn’t record the meeting.


This is a good evolve, there will definitely be an extension.
properties (22)
authorkatirayo
permlinkre-howo-rl1qgk
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-08 20:34:15
last_update2022-11-08 20:34:15
depth1
children0
last_payout2022-11-15 20:34:15
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_length222
author_reputation19,476,347,900,657
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,176,582
net_rshares0
@manniman · 
![untitled.gif](https://media.tenor.com/8rLfeTackEQAAAAC/check-bubbly.gif)
👍  , , , , ,
properties (23)
authormanniman
permlinkre-howo-rl01v0
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-07 22:45:00
last_update2022-11-07 22:45:00
depth1
children0
last_payout2022-11-14 22:45:00
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_length74
author_reputation77,790,724,868,389
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,152,366
net_rshares0
author_curate_reward""
vote details (6)
@nonameslefttouse ·
$0.27
Today I'd like to suggest both HP and RC delegations expire after x amount of time by default.  

There are several instances of active accounts benefiting from inactive account delegations from years ago.  *Not cool.*

Same thing will happen with RC.  *Not cool.*

That's only one problem I see.

Your thoughts?  Anyone else care to chime in?
👍  , , , ,
properties (23)
authornonameslefttouse
permlinkre-howo-rl0hml
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-08 04:25:33
last_update2022-11-08 04:25:33
depth1
children7
last_payout2022-11-15 04:25:33
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_length347
author_reputation593,361,688,458,528
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,157,956
net_rshares632,601,954,405
author_curate_reward""
vote details (5)
@andablackwidow ·
$0.17
From the technical standpoint something that stays up potentially forever is worse than something with definite lifetime (because the former can build up over time). That supports the idea of expiration.

From usability point of view I can see potential problem. Now you can set two accounts - one as cold storage, second as active. You set your active as proxy for cold storage, you delegate all HP from cold to active and you are good to go, never to have to touch the cold storage (well, until renewal of proxy setting once a year).

Back to technical side. It would require additional index on delegation objects, so it is not only pluses in that field.
I think we'd need to see what is average effective lifetime of delegation (with and without weighting it by its power) - maybe it is not such big of a problem after all?
👍  
properties (23)
authorandablackwidow
permlinkre-nonameslefttouse-2022119t1279415z
categorycore
json_metadata{"tags":["core"],"app":"ecency/3.0.28-surfer","format":"markdown+html"}
created2022-11-09 00:27:06
last_update2022-11-09 00:27:06
depth2
children1
last_payout2022-11-16 00:27:06
cashout_time1969-12-31 23:59:59
total_payout_value0.082 HBD
curator_payout_value0.083 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length827
author_reputation84,494,108,783,084
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,181,672
net_rshares387,526,714,503
author_curate_reward""
vote details (1)
@nonameslefttouse · (edited)
At this point, I just wanted to throw the idea out there and see what people think.  Certainly don't want to burden anyone or suggest bogging performance.  

I see your potential problem and would counter it by delegating *renewal rights* from cold to active.  *Easier said than done.  I know...* 

And I'm not really looking at it like it's a major issue, I just know it could turn into one.  There are little pockets everywhere; seemingly forgotten delegations.  And even being small I view as a problem because that just adds to the total of wasted resources.  Similar to *shrinkage*, in a sense. Especially problematic in the long run, and *if* price goes up.

Handing out RC, set it and forget it.  Incentive to powerup; set that and forget that too.  Not a fan of the free ride.

Any single one of these little 'projects' springing up asking for delegation could stop paying out whenever they feel like it.  Meanwhile inactive account doesn't notice for two years, passes away, or loses keys.  That little project becomes a parasite, forever.  *Ill-gotten gains.*

Again, I don't want to convince anyone it's a problem that needs an immediate solution.  Just something not worth ignoring completely.  Unfortunately I don't know a damn thing about what's under the hood of the blockchain.  I just drive the damn thing and want it to be running efficiently.
properties (22)
authornonameslefttouse
permlinkre-andablackwidow-rl23qo
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-09 01:20:48
last_update2022-11-09 02:06:03
depth3
children0
last_payout2022-11-16 01:20:48
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_length1,362
author_reputation593,361,688,458,528
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,182,540
net_rshares0
@antisocialist · 
Second.
properties (22)
authorantisocialist
permlinkre-nonameslefttouse-rl0mi9
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-08 06:10:57
last_update2022-11-08 06:10:57
depth2
children0
last_payout2022-11-15 06:10: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_length7
author_reputation273,683,974,280,829
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,159,352
net_rshares0
@dalz ·
$0.17
Well the same was done for witness vote to expire if account is not active for kore than one year... so this will be an extension of it
👍  
properties (23)
authordalz
permlinkrl0sgd
categorycore
json_metadata{"app":"hiveblog/0.1"}
created2022-11-08 08:19:24
last_update2022-11-08 08:19:24
depth2
children1
last_payout2022-11-15 08:19:24
cashout_time1969-12-31 23:59:59
total_payout_value0.084 HBD
curator_payout_value0.084 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length135
author_reputation1,914,512,155,548,263
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,161,164
net_rshares400,729,593,439
author_curate_reward""
vote details (1)
@nonameslefttouse · (edited)
Yes.  That's how I imagined it.  Wouldn't be hard to renew delegations before the time expires if needed, especially if the frontend somehow highlights which ones need attention.  Just requires user input, like voting for witnesses.
 
Plugs up all the leaks.
👍  
properties (23)
authornonameslefttouse
permlinkre-dalz-rl0ufo
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-08 09:02:12
last_update2022-11-08 09:08:54
depth3
children0
last_payout2022-11-15 09:02: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_length260
author_reputation593,361,688,458,528
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,161,821
net_rshares40,922,201,845
author_curate_reward""
vote details (1)
@howo ·
$0.17
Hmmm, while I see the use case, we don't like to add time-based event too much because they cause load on the chain. This would be something could be automated through an L2 (for RC, HP requires an active key which is no go).

As for the HP I'm like, why is it a problem ? People are free to do what they wish with their stake, if they wish to delegate then go MIA well it's their choice. It was bad for governance votes because it directly affects things like witness rankings or proposals but for delegations it has a lower impact (if you want to mention people self voting and such, I'd say abuse can be countered with free downvotes or by various initiatives)
👍  
properties (23)
authorhowo
permlinkre-nonameslefttouse-rl1lxh
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-08 18:56:09
last_update2022-11-08 18:56:09
depth2
children1
last_payout2022-11-15 18:56:09
cashout_time1969-12-31 23:59:59
total_payout_value0.085 HBD
curator_payout_value0.086 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length664
author_reputation511,962,302,102,641
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,174,359
net_rshares401,771,856,329
author_curate_reward""
vote details (1)
@nonameslefttouse · (edited)
I hear you.  People are most certainly free to make choices.  Until they die or lose their keys.  And sure, one could simply downvote.  *That always goes well...*

I appreciate your thoughts on this matter.  

Keep up the good work.  It's appreciated.
properties (22)
authornonameslefttouse
permlinkre-howo-rl1n5a
categorycore
json_metadata{"tags":["core"],"app":"peakd/2022.10.3"}
created2022-11-08 19:22:21
last_update2022-11-08 19:30:18
depth3
children0
last_payout2022-11-15 19:22: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_length253
author_reputation593,361,688,458,528
root_title"Core dev meeting #42"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id118,174,932
net_rshares0
@poshtoken · (edited)
https://twitter.com/1429415246129729538/status/1589784880137003008
https://twitter.com/1459494815968620548/status/1589978677567434752
https://twitter.com/742876529756110848/status/1590042479818342401
<sub> The rewards earned on this comment will go directly to the people( @michupa, @steemadi, @wilsonthe ) sharing the post on Twitter as long as they are registered with @poshtoken. Sign up at https://hiveposh.com.</sub>
properties (22)
authorposhtoken
permlinkre-howo-core-dev-meeting-4220229
categorycore
json_metadata"{"app":"Poshtoken 0.0.1","payoutToUser":["michupa","steemadi","wilsonthe"]}"
created2022-11-08 01:02:39
last_update2022-11-08 18:06:51
depth1
children0
last_payout2022-11-15 01:02: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_length422
author_reputation5,243,139,134,373,049
root_title"Core dev meeting #42"
beneficiaries
0.
accountreward.app
weight10,000
max_accepted_payout1,000,000.000 HBD
percent_hbd0
post_id118,154,697
net_rshares0
Help/Feedback