create account

RE: HF20 Update: Restoring Continuity by ned

View this thread on: hive.blogpeakd.comecency.com

Viewing a response to: @bobinson/re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181001t045356458z

· @ned ·
Valuable input. Thank you.
👍  
properties (23)
authorned
permlinkre-bobinson-re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181001t054605578z
categorysteem
json_metadata{"tags":["steem"],"app":"steemit/0.1"}
created2018-10-01 05:46:06
last_update2018-10-01 05:46:06
depth9
children2
last_payout2018-10-08 05:46: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_length26
author_reputation94,449,026,656,258
root_title"HF20 Update: Restoring Continuity"
beneficiaries[]
max_accepted_payout0.000 HBD
percent_hbd10,000
post_id72,392,685
net_rshares10,054,941,349
author_curate_reward""
vote details (1)
@bobinson ·
$0.07
To add to it, I wrote the following else where: One is a suggestion and 2 is about usability aspect and a possible opportunity of STEEM


#1.

## Suggestions

Why don't everyone - community, witnesses and STEEM Inc take this opportunity to create a truly decentralized, community driven project by introducing a QA process which will be independent of the blockchain development ?

The Goals can be formulated from the witness testaments regarding HF20 written by the developers.

A DAO can be created and this can do the following but not limited to it:

- help the developers to run the TESTNET

- ensure that the code has enough test coverage

- maintain the CI-CD pipeline

- generate transactions mimicing the MAIN-NET

- publish test reports on a periodic basis

- help to bring in bug bounties

- create a code of conduct

- Attempt to join various blockchain consortiums

- work with Academicians in reasearch








  A starting point can be using something like https://gitlab.com/SBCDAO/ 


#2.



![12345.png](https://cdn.steemitimages.com/DQmQSeXsJJXGNxmSMcMruaS6uAeKe1Q9Jn7U7UbFPweAWJt/12345.png)

On this, the requirement is this "have volunteer assignments for various surveys and volunteer + their specific task on a immutable fashion". Hyperledger based private chain was the first preference because the geo-graphical region I am in has a blockchain academy run by the government and it is a partner of hyperledger + stellar. The technical volunteers wanted an open system like wikipedia and Openstreetmap so that its possible for anyone and everyone to audit the data. We managed to convince the stake holders for a public chain and due to obvious reasons STEEM blockchain was the first choice. Right now damage assessment for the homes are over and a damage assessment for the infrastructure is about to begin. The proof of volunteer assignment and task assignment is already on private STEEM chain. Now, the question is, unlike a private deployment which is controlled and tested, the public chain behaves ways like what happened this week. So, is it possible to for anyone to ensure that in the next 2 - 3 months time there will not unexpected behaviors happening ? I am well aware that you or any of the witnesses will not be able answer this question. But if the STEEM Inc has any means to contact, this could be something that can be taken up. The next opportunity could be Ushahidi rescue request platform who is interested in on a blockchain -- this also open. Since there is no way I can communicate to anyone in STEEM Inc, just sharing it here so that someone takes it up if it makes sense.
timcliff September 30, 2018 10:39 PM
@bobinson it is just as possible for a consensus upgrade on Hyperledger to experience the same issues we went through here on Steem
👍  
properties (23)
authorbobinson
permlinkre-ned-re-bobinson-re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181001t055554423z
categorysteem
json_metadata{"tags":["steem"],"users":["bobinson"],"image":["https://cdn.steemitimages.com/DQmQSeXsJJXGNxmSMcMruaS6uAeKe1Q9Jn7U7UbFPweAWJt/12345.png"],"links":["https://gitlab.com/SBCDAO/"],"app":"steemit/0.1"}
created2018-10-01 05:55:33
last_update2018-10-01 05:55:33
depth10
children0
last_payout2018-10-08 05:55:33
cashout_time1969-12-31 23:59:59
total_payout_value0.053 HBD
curator_payout_value0.017 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length2,790
author_reputation55,343,141,313,811
root_title"HF20 Update: Restoring Continuity"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id72,393,056
net_rshares36,364,901,805
author_curate_reward""
vote details (1)
@bobinson ·
@ned : followup work & status https://hackmd.io/s/ByT1BuG5m
properties (22)
authorbobinson
permlinkre-ned-re-bobinson-re-ned-re-develcuy-re-ned-re-ned-re-sapphic-re-ned-re-ats-david-re-steemitblog-hf20-update-restoring-continuity-20181003t194652869z
categorysteem
json_metadata{"tags":["steem"],"users":["ned"],"links":["https://hackmd.io/s/ByT1BuG5m"],"app":"steemit/0.1"}
created2018-10-03 19:46:54
last_update2018-10-03 19:46:54
depth10
children0
last_payout2018-10-10 19:46: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_length59
author_reputation55,343,141,313,811
root_title"HF20 Update: Restoring Continuity"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id72,567,165
net_rshares0