create account

HF21 Recommendation: Raising Custom JSON Limit by steemitblog

View this thread on: hive.blogpeakd.comecency.com
· @steemitblog ·
HF21 Recommendation: Raising Custom JSON Limit
![Custom JSON.jpg](https://cdn.steemitimages.com/DQmQWeX9oHm3Bgjfq843yB996GpYjwrCWR2L4BMDAoczcZi/Custom%20JSON.jpg)

Hello Steemians, we would like to open up public discussion of another minor addition to HF21: removing the limit to the number of custom JSON operations that can be included in a block by a single account. 

<h1>For App Developers</h1>

Many Steem developers have informed us that this limit is adversely impacting the user experience in their applications. We want to do everything we can to make sure that Steem is the best blockchain protocol for powering web applications with amazing user experiences, which is why we believe it is worth discussing this change. 

We have attempted to keep private discussions of this change to a minimum and a final decision has not been made. We would like all discussions on this topic to occur in the comments section of this post, or in follow up posts where appropriate.  This way Steem users can gain as much insight into the change, and the reasons for supporting or opposing it, as possible. 

<h1>Why Limit Custom JSON ops?</h1>

When this limit was created Steem only had bandwidth to rate-limit transactions. The big cost of custom JSON is an undo state for the plugins that process custom JSON. Because the Resource Credit is more sophisticated than the original bandwidth system, it more accurately captures that cost, and is therefore much more effective at rate limiting excessive use of custom JSON ops. This makes the limit antiquated. 

<h1>DOS?</h1>

The DOS attack that led to the introduction of this limit did not impact the reliability of the Steem Blockchain. All witnesses continued to produce blocks without interruption, but it did result in an outage on Steemit.com. There is still the opportunity for the operation to be sent in a burst which could result in a short hiccup for nodes processing custom JSON. 

<h1>Increase to 5</h1>
After weighing the pros and cons of such a change, we would recommend increasing the limit to 5 custom JSON ops per block. This will greatly increase flexibility for DAPP developers while continuing to ensure the stability of said DAPPs. This would enable us to re-evaluate the change prior to the SMT hardfork and decide to either relax the limit further, remove it entirely, or keep it where it is based on usage by DAPP developers. 

<h1>Feedback</h1>

We have done our best to ensure that private discussions of this change were kept to a minimum, and that no final decisions on this change were made. We invite those who support this change, and those who do not, to voice their opinions in the comments to this post. The goal is to give Steem users one place where they can come to learn about this change, understand the various sides, and voice their support or lack thereof.

_The Steemit Team_
πŸ‘  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and 77 others
properties (23)
authorsteemitblog
permlinkhf21-recommendation-raising-custom-json-limit
categoryhf21
json_metadata{"tags":["hf21","hardfork","customjson"],"image":["https://cdn.steemitimages.com/DQmQWeX9oHm3Bgjfq843yB996GpYjwrCWR2L4BMDAoczcZi/Custom%20JSON.jpg"],"app":"steemit/0.1","format":"markdown"}
created2019-07-02 22:01:54
last_update2019-07-02 22:01:54
depth0
children59
last_payout2019-07-09 22:01: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_length2,822
author_reputation332,472,558,821,177
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout0.000 HBD
percent_hbd10,000
post_id87,695,130
net_rshares13,273,414,958,333
author_curate_reward""
vote details (141)
@abitcoinskeptic ·
Just do this and SPS, then seriously consider cancelling the other changes.

Posted using [Partiko Android](https://partiko.app/referral/abitcoinskeptic)
properties (22)
authorabitcoinskeptic
permlinkabitcoinskeptic-re-steemitblog-hf21-recommendation-raising-custom-json-limit-20190702t234158421z
categoryhf21
json_metadata{"app":"partiko","client":"android"}
created2019-07-02 23:42:00
last_update2019-07-02 23:42:00
depth1
children2
last_payout2019-07-09 23:42: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_length153
author_reputation335,387,091,612,941
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,699,152
net_rshares0
@jarvie · (edited)
There's a lot of changes ... which ones. The change from 15 minutes to 1 minute?
They're coming out with a lot of small but solid updates each day. 
properties (22)
authorjarvie
permlinkre-abitcoinskeptic-abitcoinskeptic-re-steemitblog-hf21-recommendation-raising-custom-json-limit-20190702t235250307z
categoryhf21
json_metadata{"tags":["hf21"],"app":"steempeak/1.13.5"}
created2019-07-02 23:52:54
last_update2019-07-02 23:53:36
depth2
children1
last_payout2019-07-09 23:52: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_length148
author_reputation388,491,264,112,133
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,699,581
net_rshares0
@abitcoinskeptic ·
2e12 reward curve concerns me the most. The rest are simple on their own but combined effects are confusing.

Posted using [Partiko Android](https://partiko.app/referral/abitcoinskeptic)
properties (22)
authorabitcoinskeptic
permlinkabitcoinskeptic-re-jarvie-re-abitcoinskeptic-abitcoinskeptic-re-steemitblog-hf21-recommendation-raising-custom-json-limit-20190702t235441258z
categoryhf21
json_metadata{"app":"partiko","client":"android"}
created2019-07-02 23:54:42
last_update2019-07-02 23:54:42
depth3
children0
last_payout2019-07-09 23:54: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_length186
author_reputation335,387,091,612,941
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,699,667
net_rshares0
@aggroed ·
$1.40
This change is super important to steem-engine and steemmonsters so that user actions never conflict and stop something from happening.  It gets more important as new apps and automation are added.
πŸ‘  , , , , , , , , , ,
properties (23)
authoraggroed
permlinkpu1djm
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-02 22:38:09
last_update2019-07-02 22:38:09
depth1
children9
last_payout2019-07-09 22:38:09
cashout_time1969-12-31 23:59:59
total_payout_value1.050 HBD
curator_payout_value0.348 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length197
author_reputation1,343,345,274,857,310
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,696,511
net_rshares2,757,722,399,652
author_curate_reward""
vote details (11)
@peakmonsters ·
$0.31
We also would be greatly benefited as well!

Also making the necesary node/jussi changes to allow more than 2000 characters would be amazing as well that way we would decrease number of json transactions on a daily basis.
πŸ‘  ,
properties (23)
authorpeakmonsters
permlinkre-aggroed-pu1djm-20190702t235144429z
categoryhf21
json_metadata{"tags":["hf21"],"app":"steempeak/1.13.5"}
created2019-07-02 23:51:45
last_update2019-07-02 23:51:45
depth2
children0
last_payout2019-07-09 23:51:45
cashout_time1969-12-31 23:59:59
total_payout_value0.234 HBD
curator_payout_value0.077 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length221
author_reputation90,081,627,193,998
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,699,530
net_rshares616,636,668,255
author_curate_reward""
vote details (2)
@rishi556 ·
$0.12
What happens if USER A with 20 token X sends 20 to USER B and USER C in the same block? Who gets prioritized?
πŸ‘  ,
properties (23)
authorrishi556
permlinkpu1mbz
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 01:48:00
last_update2019-07-03 01:48:00
depth2
children7
last_payout2019-07-10 01:48:00
cashout_time1969-12-31 23:59:59
total_payout_value0.092 HBD
curator_payout_value0.030 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length109
author_reputation132,754,869,222,673
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,704,216
net_rshares245,263,488,646
author_curate_reward""
vote details (2)
@andrarchy ·
Really interesting question. My guess is that asset transfers would be limited to one per block. Maybe there are a sub-type of transactions that are easier to bundle. E.g. if you and I play a game that ends in the transfer of an asset, then maybe all of our moves within the game can be bundled into a single block, while the asset transfer operation is included in its own block.
properties (22)
authorandrarchy
permlinkpu2efi
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 11:54:54
last_update2019-07-03 11:54:54
depth3
children2
last_payout2019-07-10 11:54: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_length380
author_reputation230,168,201,522,782
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,726,486
net_rshares0
@smitop ·
The transaction that gets included in the block earlier by the witness producing the block.
properties (22)
authorsmitop
permlinkre-rishi556-pu1mbz-20190703t114906044z
categoryhf21
json_metadata{"tags":["hf21"],"app":"steempeak/1.13.5"}
created2019-07-03 11:49:12
last_update2019-07-03 11:49:12
depth3
children0
last_payout2019-07-10 11:49: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_length91
author_reputation1,622,694,571,233
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,726,217
net_rshares0
@wehmoen · (edited)
 
properties (22)
authorwehmoen
permlinkre-rishi556-pu1mbz-20190703t181605299z
categoryhf21
json_metadata{}
created2019-07-03 18:16:06
last_update2020-06-03 06:22:36
depth3
children2
last_payout2019-07-10 18:16: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_length1
author_reputation86,504,380,503,125
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,744,626
net_rshares0
@anyx ·
$0.77
I don't object at all to this change, but I wanted to caution those using custom_json's for derived consensus data, that this may change how you interpret ordering. 
You can no longer do async/parallel application of transactions within a block as the account would not be guaranteed unique. 
In other words, right now one can shortcut ordering as blocks are clearly totally ordered. With this change, one needs to pay attention to the order of transactions within a block to ensure deterministic application across observers.
πŸ‘  , , , , ,
properties (23)
authoranyx
permlinkpu1iai
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 00:20:45
last_update2019-07-03 00:20:45
depth1
children1
last_payout2019-07-10 00:20:45
cashout_time1969-12-31 23:59:59
total_payout_value0.580 HBD
curator_payout_value0.192 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length526
author_reputation98,676,136,100,181
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,700,449
net_rshares1,526,988,029,122
author_curate_reward""
vote details (6)
@smooth ·
Good point but I'm pretty sure this limit was implemented in 'non-enforced soft fork' and can't be fully relied upon for any security purpose anyway. If anyone is doing that they are currently vulnerable.
properties (22)
authorsmooth
permlinkpu1nqq
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 02:18:27
last_update2019-07-03 02:18:27
depth2
children0
last_payout2019-07-10 02:18: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_length204
author_reputation253,602,537,834,068
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,705,671
net_rshares0
@beggars ·
Yes, please. This is an essential changed. However, five operations per block seems a little small (although, 5 is better than nothing is 10 isn't agreeable). I would preferably prefer to see this increased to ten. Specifically, this would benefit Steem Engine greatly as well as the airdrop bot that I have created which gets around this limitation.

Furthermore, can we please increase the limit of 2000 characters for a custom JSON operation for Jussi backed nodes? I would ideally like to see this increased to 10000 characters to make life a little easier from a development perspective.
properties (22)
authorbeggars
permlinkpuaq8b
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-07 23:50:36
last_update2019-07-07 23:50:36
depth1
children0
last_payout2019-07-14 23:50: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_length592
author_reputation75,322,612,974,570
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,966,079
net_rshares0
@blocktrades ·
$0.03
I'm in favor of this change, seems low risk, and beneficial to dapps.
πŸ‘  ,
properties (23)
authorblocktrades
permlinkpu1ffa
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-02 23:18:45
last_update2019-07-02 23:18:45
depth1
children0
last_payout2019-07-09 23:18:45
cashout_time1969-12-31 23:59:59
total_payout_value0.026 HBD
curator_payout_value0.008 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length69
author_reputation1,285,246,393,380,149
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,698,197
net_rshares69,801,085,871
author_curate_reward""
vote details (2)
@booster ·
$6.17
You have our support for more custom json!
You have our support for more custom json!
You have our support for more custom json!
You have our support for more custom json!
You have our support for more custom json!
You have our support for more custom json!

Sincerely Team Booster
πŸ‘  , ,
properties (23)
authorbooster
permlinkpu31sl
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 20:19:33
last_update2019-07-03 20:19:33
depth1
children0
last_payout2019-07-10 20:19:33
cashout_time1969-12-31 23:59:59
total_payout_value6.145 HBD
curator_payout_value0.026 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length281
author_reputation68,767,115,776,562
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd0
post_id87,750,291
net_rshares16,212,765,761,527
author_curate_reward""
vote details (3)
@bronkong ·
Bring it on and make STEEM ready for the rise of Dapps.
properties (22)
authorbronkong
permlinkpu3zyw
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-04 08:37:45
last_update2019-07-04 08:37:45
depth1
children0
last_payout2019-07-11 08:37: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_length55
author_reputation119,065,477,740,690
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,772,605
net_rshares0
@cervantes ·
We fully agree with this change and will install a fork containinig it.
πŸ‘  
properties (23)
authorcervantes
permlinkpu1k1b
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 00:58:24
last_update2019-07-03 00:58:24
depth1
children0
last_payout2019-07-10 00:58: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_length71
author_reputation840,203,117,254,877
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,702,003
net_rshares263,100,674
author_curate_reward""
vote details (1)
@chekohler ·
$0.03
That's great news, I think steemit should focus on making the chain more developer-friendly, we've seen what community devs can achieve and it's important for attracting new business and giving dapps room to grow
πŸ‘  
properties (23)
authorchekohler
permlinkre-steemitblog-hf21-recommendation-raising-custom-json-limit-20190703t064921080z
categoryhf21
json_metadata{"tags":["hf21"],"app":"steempeak/1.13.5"}
created2019-07-03 06:49:21
last_update2019-07-03 06:49:21
depth1
children0
last_payout2019-07-10 06:49:21
cashout_time1969-12-31 23:59:59
total_payout_value0.021 HBD
curator_payout_value0.007 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length212
author_reputation524,332,427,393,665
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,716,768
net_rshares57,613,192,425
author_curate_reward""
vote details (1)
@drakos ·
$0.03
https://i.stack.imgur.com/MNeE7.jpg
πŸ‘  
properties (23)
authordrakos
permlinkpu1dk3
categoryhf21
json_metadata{"tags":["hf21"],"image":["https://i.stack.imgur.com/MNeE7.jpg"],"app":"steemit/0.1"}
created2019-07-02 22:38:30
last_update2019-07-02 22:38:30
depth1
children0
last_payout2019-07-09 22:38:30
cashout_time1969-12-31 23:59:59
total_payout_value0.020 HBD
curator_payout_value0.006 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length35
author_reputation112,280,226,665,329
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,696,525
net_rshares56,461,299,973
author_curate_reward""
vote details (1)
@elbrava ·
Nice, an intelligent exchange of ideas and opinions under a Steemitblog. Gotta love that. No idea what you are talking about exactly, but I don't mind. Much better than the usual hate/sarcasm mix. 

Posted using [Partiko iOS](https://partiko.app/referral/elbrava)
properties (22)
authorelbrava
permlinkelbrava-re-steemitblog-hf21-recommendation-raising-custom-json-limit-20190703t093326020z
categoryhf21
json_metadata{"app":"partiko","client":"ios"}
created2019-07-03 09:33:27
last_update2019-07-03 09:33:27
depth1
children2
last_payout2019-07-10 09:33: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_length263
author_reputation6,548,533,456,556
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,721,728
net_rshares0
@andrarchy · (edited)
Great right?! So I can explain a little bit if you're interested. Custom JSON ops are essentially a way of storing code on the blockchain so that developers can make apps more decentralized and transparent but at very low cost (free even). This enables something we refer to as "Soft Consensus" which I like to describe as "trust through validation" rather than "trust through decentralized computation." The idea behind protocols like EOS and Ethereum is that in order for users to trust apps, the computations powering those apps must be performed by the blockchain itself. Steem's approach is different. We say that, yes, there are SOME computations users want done by the blockchain like  those relating to token transfers, token vests, voting actions, the storing of speech (i.e. content), and a few others. But that's it. Developers can't ask Steem to "calculate Pi to 1,000,000 decimal points." 

Bounding the amount of computational work Steem can be asked to do enables the efficiency which allows for many of the special features of Steem like free transactions. This creates a unique opportunity for developers, in that they can decentralize the mechanics of their app without incurring the costs that come from having that code processed by the blockchain. Granted, this is something that you can do on practically any blockchain. The problem is that this would be extremely expensive to do with any other blockchain, therefore if you were going to store your code on Ethereum you might as well have it computed by Ethereum as well. 

Soft Consensus only really makes sense on Steem because of the speed and fee-less nature of it. By hosting the code to your app on Steem you accomplish two things: 1. you enable your code to be audited by developers who can then validate that you are executing the on-chain code faithfully, and 2. you open your code to 3rd party developers. For example, because the market for SteemMonster exists in Soft Consensus, as far as Steem is concerned, there is no such thing as SteemMonsters, just a bunch of meaningless custom JSON ops. But inside those custom JSON ops is all the code powering their market, which 3rd parties can use to build their own apps. So now anyone can build their own market for SteemMonsters cards, which is how PeakMonsters.com exists. 

It is my thesis that of all the code needed to power a given app, 99% of that code does not need to be decentralized at all. Of the code that need to be decentralized (i.e. on a blockchain), 99% of *that* code (the 1%) only needs to be in soft consensus where it can be *audited*. Only the remainder (1% of 1%) needs to be on-chain *and executed* on-chain. I believe that what we try to do with Steem is to look at that .01% of code that is *super critical* for decentralized applications, and add those to Steem. This enables Steem to perform those Smart Contracts exceptionally well, at an unrivaled low cost. 

Hope that helps!
πŸ‘  ,
properties (23)
authorandrarchy
permlinkpu2fwz
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 12:27:00
last_update2019-07-03 15:07:27
depth2
children1
last_payout2019-07-10 12:27: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_length2,939
author_reputation230,168,201,522,782
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,727,944
net_rshares36,472,507,435
author_curate_reward""
vote details (2)
@hobo.media ·
I respect your right to feel that way, however, the key value add of Bitcoin and all blockchains is *asset possession*. Your argument for soft consensus is actually the same argument Peter Schiff makes for why he thinks Bitcoin has no value. 

Schiff argues that gold is better than bitcoins in every way. This is because to him the soft consensus of validation that he owns the gold is enough. 

This is in contrast to the "Not Your Keys, Not Your Bitcoin" argument. The argument for Bitcoin's value is that possession is crucial. Stocks, bonds, and commodities like gold and silver are not ever in your possesion even when you have a note that verifies that it belongs to you. Corporations still have many ways to get out of giving you the asset and/or the value of that asset. 

The whole case being made by Bitcoiners and Etherians is that if you do not have full possession of your asset it isn't really yours. This becomes evidentally so in international business dealing wherein your ability to punish overseas businesses for misbehavior below the $20,000 range becomes quite difficult and rarely worthwhile. 

Soft consensus is merely evidence of right to something. The problem with that is at the highest levels we see that *evidence* to a right is not enough. When Germany wanted to repatriate their gold the US Reserve bank indicated that it would take 7 years. That's ridiculous, if it was there it should not have taken so long. Clearly, possession is essential at all levels. 

Now, if you need validation for a fairly non-valuable item then it is fine. No body cares about a receipt for a donut, but its good for it to be censorship-resistant in case someone claims that you walked out without paying. Soft consensus is great for accounting purposes, but for storing valuables like NFTs its not such a great thing. 

Here's a perfect example of how *validation* is not enough. When MagicDice did their exit-scam, there was a mountain of evidence that MagicDice owed its players tokens/dividends. The Steem blockchain has transaction details full of validation of those players rights. Still, they got jack all. 

Why is validation of ownership rights on the Steem blockchain not enough for the victims of MagicDice? Because if its *not your keys, its not your bitcoin*... Possession is everything.
properties (22)
authorhobo.media
permlinkpuuwb9
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-18 21:14:03
last_update2019-07-18 21:14:03
depth3
children0
last_payout2019-07-25 21:14: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_length2,313
author_reputation21,121,859,045,871
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id88,463,654
net_rshares0
@emrebeyler ·
Looks like a good change. A big win for the user experience with almost zero bad impact on the blockchain. I support this change as a backup witness.
πŸ‘  
properties (23)
authoremrebeyler
permlinkpu319t
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 20:08:18
last_update2019-07-03 20:08:18
depth1
children0
last_payout2019-07-10 20:08: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_length149
author_reputation448,535,049,068,622
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,749,830
net_rshares4,461,399,666
author_curate_reward""
vote details (1)
@ew-and-patterns ·
$1.16
If there is a quick way to limit it again in case of emergency, I am okay with removing the limit completely.
πŸ‘  , , , , , ,
properties (23)
authorew-and-patterns
permlinkpu2w6u
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 18:18:33
last_update2019-07-03 18:18:33
depth1
children0
last_payout2019-07-10 18:18:33
cashout_time1969-12-31 23:59:59
total_payout_value0.880 HBD
curator_payout_value0.280 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length109
author_reputation138,703,829,387,626
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,744,749
net_rshares2,325,224,385,466
author_curate_reward""
vote details (7)
@freebornangel ·
This [new steem](https://steemit.com/busy/@whatsup/new-steem-it-s-not-like-old-steem) is much better than the old steem.
Ya'll have managed to find a second change that we can agree on.
That's a start.

If it makes nextcolony load faster, even better.
properties (22)
authorfreebornangel
permlinkpu1kfl
categoryhf21
json_metadata{"tags":["hf21"],"links":["https://steemit.com/busy/@whatsup/new-steem-it-s-not-like-old-steem"],"app":"steemit/0.1"}
created2019-07-03 01:07:09
last_update2019-07-03 01:07:09
depth1
children0
last_payout2019-07-10 01:07: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_length251
author_reputation171,005,551,503,977
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,702,478
net_rshares0
@guiltyparties ·
$0.84
I fully agree with the limit increase, the flexibility/speed it will give apps is crucial. The onus on adjusting to the change is on the app devs. 

There's also no need for it to be a witness parameter.  If there's a reason to adjust it upwards or downwards in the future, that adjustment is unlikely to be critical enough to alone warrant a HF and will be part of the next logical HF regardless.
πŸ‘  
properties (23)
authorguiltyparties
permlinkpu1ude
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 04:39:45
last_update2019-07-03 04:39:45
depth1
children0
last_payout2019-07-10 04:39:45
cashout_time1969-12-31 23:59:59
total_payout_value0.702 HBD
curator_payout_value0.138 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length397
author_reputation261,203,126,670,124
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,711,528
net_rshares1,846,431,388,994
author_curate_reward""
vote details (1)
@holger80 ·
$0.20
Allowing more than 1 custom_json and rasing the size limit will be a great improvement for all steem bases apps. I support these changes.

Posted using [Partiko Android](https://partiko.app/referral/holger80)
πŸ‘  , ,
properties (23)
authorholger80
permlinkholger80-re-steemitblog-hf21-recommendation-raising-custom-json-limit-20190704t090600613z
categoryhf21
json_metadata{"app":"partiko","client":"android"}
created2019-07-04 09:06:00
last_update2019-07-04 09:06:00
depth1
children0
last_payout2019-07-11 09:06:00
cashout_time1969-12-31 23:59:59
total_payout_value0.148 HBD
curator_payout_value0.048 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length208
author_reputation358,857,509,568,825
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,773,644
net_rshares397,881,791,559
author_curate_reward""
vote details (3)
@immanuel94 · (edited)
This change is amazing! That's exactly what I needed. :)
properties (22)
authorimmanuel94
permlinkpu2bo3
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 10:55:15
last_update2019-07-03 10:55:54
depth1
children0
last_payout2019-07-10 10:55: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_length56
author_reputation212,637,383,853,137
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd0
post_id87,723,951
net_rshares0
@isnochys ·
$0.04
I wonder, what else will be added to HF21?
Is there a plan?
Are you making this up on the go?
Do you have a release manager?

Not that any testing is needed, I guess?

HF AZ-5
πŸ‘  
properties (23)
authorisnochys
permlinkpu1rm6
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 03:42:06
last_update2019-07-03 03:42:06
depth1
children1
last_payout2019-07-10 03:42:06
cashout_time1969-12-31 23:59:59
total_payout_value0.028 HBD
curator_payout_value0.009 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length175
author_reputation47,917,144,909,021
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,709,510
net_rshares77,019,211,136
author_curate_reward""
vote details (1)
@andrarchy · (edited)
We make these determinations on a case-by-case basis, provide our recommendations, and solicit feedback from the community as well as the Witnesses. If the community wants something, and their Witnesses want something, we will do our best to oblige them especially if the changes are minor, low risk, and will not delay the hardfork.
properties (22)
authorandrarchy
permlinkpu2enp
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 11:59:48
last_update2019-07-03 12:00:30
depth2
children0
last_payout2019-07-10 11:59: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_length333
author_reputation230,168,201,522,782
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,726,687
net_rshares0
@jarunik ·
Would be beneficial for nextcolony to allow more game commands in one block.
properties (22)
authorjarunik
permlinkpu40o5
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-04 08:52:54
last_update2019-07-04 08:52:54
depth1
children0
last_payout2019-07-11 08:52: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_length76
author_reputation16,657,654,981,962
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,773,182
net_rshares0
@jarvie ·
Love this one! Good job communicating each day btw. 
It'd be good to remind people about the timing of the proposed Hard Fork... keep it in their minds when this may happen and give them a reason to interact sooner than later.
properties (22)
authorjarvie
permlinkre-steemitblog-hf21-recommendation-raising-custom-json-limit-20190702t235502855z
categoryhf21
json_metadata{"tags":["hf21"],"app":"steempeak/1.13.5"}
created2019-07-02 23:55:06
last_update2019-07-02 23:55:06
depth1
children0
last_payout2019-07-09 23:55: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_length226
author_reputation388,491,264,112,133
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,699,690
net_rshares0
@jaydih · (edited)
I support the idea of gradual change. Stability is one of the top priorities.
properties (22)
authorjaydih
permlinkpu1ih4
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 00:24:42
last_update2019-07-03 00:25:00
depth1
children0
last_payout2019-07-10 00:24: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_length77
author_reputation160,272,694,389,766
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,700,605
net_rshares0
@john371911 ·
I'm for it.
πŸ‘Ž  
properties (23)
authorjohn371911
permlinkpu1h3h
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-02 23:54:57
last_update2019-07-02 23:54:57
depth1
children0
last_payout2019-07-09 23:54: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_length11
author_reputation62,738,849,761,030
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,699,685
net_rshares-37,299,980,624
author_curate_reward""
vote details (1)
@jondoe ·
$1.03
These are all great ideas, no just scrap that silly EIP. Everything else you are doing is good for the price of steem, that is likely going to hurt it, it likely already has.
πŸ‘  , ,
properties (23)
authorjondoe
permlinkpu2u6n
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 17:35:09
last_update2019-07-03 17:35:09
depth1
children0
last_payout2019-07-10 17:35:09
cashout_time1969-12-31 23:59:59
total_payout_value0.774 HBD
curator_payout_value0.257 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length174
author_reputation484,533,716,905,550
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,742,913
net_rshares2,046,532,714,665
author_curate_reward""
vote details (3)
@josephsavage ·
$0.27
Are there serious downsides to having it be a witness-configured limit instead of a hard-coded limit?
πŸ‘  , , , ,
properties (23)
authorjosephsavage
permlinkre-steemitblog-hf21-recommendation-raising-custom-json-limit-20190702t222614252z
categoryhf21
json_metadata{"tags":["hf21"],"app":"steempeak/1.13.5"}
created2019-07-02 22:26:15
last_update2019-07-02 22:26:15
depth1
children6
last_payout2019-07-09 22:26:15
cashout_time1969-12-31 23:59:59
total_payout_value0.204 HBD
curator_payout_value0.064 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length101
author_reputation40,260,007,396,591
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,696,057
net_rshares536,044,765,197
author_curate_reward""
vote details (5)
@inertia ·
Letting witnesses configure it gives us flexibility so that if we want to adjust it later, we don't need a hardfork or replay.

A possible downside is that a witness decides to ignore the other witnesses and ends up bricking accounts.  But I think that's a risk with almost any op, not just custom_json.  A witness doing that has to modify steemd and explicitly attack the community, which is grounds for unapproving such a witness.
πŸ‘  
properties (23)
authorinertia
permlinkpu1dal
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-02 22:32:48
last_update2019-07-02 22:32:48
depth2
children3
last_payout2019-07-09 22:32: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_length432
author_reputation346,568,901,399,561
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,696,312
net_rshares1,807,346,783
author_curate_reward""
vote details (1)
@smooth ·
You can't unapprove a backup.
properties (22)
authorsmooth
permlinkpu1nsq
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 02:19:39
last_update2019-07-03 02:19:39
depth3
children2
last_payout2019-07-10 02:19: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_length29
author_reputation253,602,537,834,068
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,705,729
net_rshares0
@vandeberg ·
It is currently implemented entirely via soft consensus (plugins). The biggest downside currently would be developer time to reimplement the system to use witness voted limits.
πŸ‘  
properties (23)
authorvandeberg
permlinkpu1dao
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-02 22:32:48
last_update2019-07-02 22:32:48
depth2
children1
last_payout2019-07-09 22:32: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_length176
author_reputation31,759,426,110,944
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd0
post_id87,696,313
net_rshares1,770,237,419
author_curate_reward""
vote details (1)
@arcange ·
I think having generic "witness-configured parameter" logic added to the Steem blockchain would really be a plus. Once done, you will not have to reinvent the wheel.

I see many use case, on top of the custom_json limit, that would benefit being implemented as a witness-configured parameter.
properties (22)
authorarcange
permlinkre-vandeberg-pu1dao-20190704t132122074z
categoryhf21
json_metadata{"tags":["hf21"],"app":"steempeak/1.13.5"}
created2019-07-04 13:21:21
last_update2019-07-04 13:21:21
depth3
children0
last_payout2019-07-11 13:21: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_length292
author_reputation1,146,622,708,341,708
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,783,575
net_rshares0
@knircky ·
$2.55
I would like to remove this limit as much as possible. We have been having to built big work arounds because of this limit.

Make app developers have proper amount of SP but limits per block make everything clunky and complex.
πŸ‘  , , , , , , , , ,
properties (23)
authorknircky
permlinkpu1j9b
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 00:41:36
last_update2019-07-03 00:41:36
depth1
children5
last_payout2019-07-10 00:41:36
cashout_time1969-12-31 23:59:59
total_payout_value1.930 HBD
curator_payout_value0.618 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length226
author_reputation212,905,587,244,262
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,701,235
net_rshares5,080,276,764,666
author_curate_reward""
vote details (10)
@wehmoen · (edited)
$0.96
 
πŸ‘  ,
properties (23)
authorwehmoen
permlinkre-knircky-pu1j9b-20190703t044041556z
categoryhf21
json_metadata{}
created2019-07-03 04:40:42
last_update2020-06-03 06:20:12
depth2
children4
last_payout2019-07-10 04:40:42
cashout_time1969-12-31 23:59:59
total_payout_value0.802 HBD
curator_payout_value0.156 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1
author_reputation86,504,380,503,125
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,711,567
net_rshares2,109,909,682,708
author_curate_reward""
vote details (2)
@ew-and-patterns ·
$1.14
How much do you estimate 3speak would need to run smoothly? 10? 20?

If a limit of 5 is not enough for 3speak, how will this ever be enough for future DAPPs that we can't even dream about yet?
πŸ‘  , , , ,
properties (23)
authorew-and-patterns
permlinkpu2t22
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 17:10:51
last_update2019-07-03 17:10:51
depth3
children1
last_payout2019-07-10 17:10:51
cashout_time1969-12-31 23:59:59
total_payout_value0.862 HBD
curator_payout_value0.274 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length192
author_reputation138,703,829,387,626
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,741,753
net_rshares2,275,809,279,027
author_curate_reward""
vote details (5)
@raycoms ·
As a workaround you could create a number of accounts and split RC over them to create this.
properties (22)
authorraycoms
permlinkpu2l1l
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-03 14:17:45
last_update2019-07-03 14:17:45
depth3
children1
last_payout2019-07-10 14:17: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_length92
author_reputation115,046,969,395,583
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,733,491
net_rshares0
@lidtrompet ·
Effectively limitations reduce discussions and there are discussions that deserve a good debate because of the level of interest they have.

One of the questions they ask me is: why are the discussions so limited?


Efectivamente las limitaciones disminuyen las discusiones y hay discusiones que bien merecen un buen debate por el nivel de interΓ©s que poseen.

Una de las preguntas que me hago es: ΒΏpor quΓ© son tan limitadas las discusiones?
properties (22)
authorlidtrompet
permlinkpu6gty
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-05 16:38:57
last_update2019-07-05 16:38:57
depth1
children0
last_payout2019-07-12 16:38: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_length441
author_reputation40,453,099,419
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,848,401
net_rshares0
@nextcolony ·
$0.05
This is a great opportunity to improve the user experience of NextColony. 
We're supporting this change.
πŸ‘  
properties (23)
authornextcolony
permlinkpu3y71
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-04 07:59:24
last_update2019-07-04 07:59:24
depth1
children0
last_payout2019-07-11 07:59:24
cashout_time1969-12-31 23:59:59
total_payout_value0.038 HBD
curator_payout_value0.012 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length104
author_reputation126,503,747,539,708
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,771,454
net_rshares104,078,520,443
author_curate_reward""
vote details (1)
@oliverschmid ·
Yes! We urgently need this change.
properties (22)
authoroliverschmid
permlinkpu40d0
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-04 08:46:12
last_update2019-07-04 08:46:12
depth1
children0
last_payout2019-07-11 08:46: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_length34
author_reputation108,456,372,075,578
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,772,957
net_rshares0
@rondras ·
$0.05
This would a great improvement for all DApp developers. The current system is great compared to other blockchains, but this would help to lift the user experience closer to  the level on non blockchain apps.
πŸ‘  
properties (23)
authorrondras
permlinkpu3ym3
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-04 08:08:27
last_update2019-07-04 08:08:27
depth1
children0
last_payout2019-07-11 08:08:27
cashout_time1969-12-31 23:59:59
total_payout_value0.038 HBD
curator_payout_value0.012 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length207
author_reputation18,390,194,709,037
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,771,718
net_rshares101,997,497,225
author_curate_reward""
vote details (1)
@satren ·
I prefer the change to 5.
πŸ‘  
properties (23)
authorsatren
permlinkpu8p9w
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-06 21:34:45
last_update2019-07-06 21:34:45
depth1
children0
last_payout2019-07-13 21:34: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_length25
author_reputation463,263,569,897,351
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,909,526
net_rshares418,211,793
author_curate_reward""
vote details (1)
@therealwolf ·
Iβ€˜m in favor of increasing the limit to 5. I don’t think this needs to be a witness parameter right now. Maybe in the future, but for now there are bigger fish to fry.
properties (22)
authortherealwolf
permlinktherealwolf-re-steemitblog-hf21-recommendation-raising-custom-json-limit-20190702t224449708z
categoryhf21
json_metadata{"app":"partiko","client":"ios"}
created2019-07-02 22:44:51
last_update2019-07-02 22:44:51
depth1
children0
last_payout2019-07-09 22:44: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_length167
author_reputation581,693,011,827,252
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,696,779
net_rshares0
@theycallmedan ·
$0.97
I approve this change, because as you mentioned, it will increase flexibility for DAPP developers.
πŸ‘  , , , , ,
properties (23)
authortheycallmedan
permlinkpu1ci7
categoryhf21
json_metadata{"tags":["hf21"],"app":"steemit/0.1"}
created2019-07-02 22:15:45
last_update2019-07-02 22:15:45
depth1
children0
last_payout2019-07-09 22:15:45
cashout_time1969-12-31 23:59:59
total_payout_value0.738 HBD
curator_payout_value0.229 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length98
author_reputation1,254,058,380,138,691
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd0
post_id87,695,690
net_rshares1,935,810,043,033
author_curate_reward""
vote details (6)
@tts ·
To listen to the audio version of this article click on the play image.
[![](https://s18.postimg.org/51o0kpijd/play200x46.png)](http://ec2-52-72-169-104.compute-1.amazonaws.com/steemitblog__hf21-recommendation-raising-custom-json-limit.mp3)
Brought to you by [@tts](https://steemit.com/tts/@tts/introduction). If you find it useful please consider upvoting this reply.
properties (22)
authortts
permlinkre-hf21-recommendation-raising-custom-json-limit-20190702t222226
categoryhf21
json_metadata""
created2019-07-02 22:22:27
last_update2019-07-02 22:22:27
depth1
children0
last_payout2019-07-09 22:22: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_length368
author_reputation-4,535,154,553,995
root_title"HF21 Recommendation: Raising Custom JSON Limit"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,695,928
net_rshares0