You are viewing a single comment's thread from:

RE: Some information about the Hive(previously steem) proposal system/sps/steem.dao/hive development fund/hdf

in #hive • 5 years ago

Thanks for the info. You mentioned "other priorities", can you give a quick run down of what those are please?

Sorry if these have been covered elsewhere, I've not been as up to speed with the goings on as I once was

5 years ago in #hive by
$0.51
  • Past Payouts $0.51
  • - Author $0.26
  • - Curators $0.26
1 vote
Reply 2
Sort:  
  • Trending
    • [-]
     5 years ago  

    No problems, I don't think it has been covered elsewhere except in the last dev meeting.

    Priorities are always changing a bit but something like :

    • Delay votes to prevent a future exchange takeover
    • Airdrop (or not) to excluded accounts
    • Start converting the massive amount of HIVE tokens in the sps to HBD
    • Do a security audit of the chain
    • Improve node performance so it's not as ressource hungry as before.
    • remove all notions of "steem" in the code for "hive" (trust me there are a loooot of those)

    List goes on, there are a lot of things to do, you can check them out here https://gitlab.syncad.com/hive/hive/issues

    Ultimately I don't think we'll change steem.dao for a long time, the change is purely cosmetic and it requires a LOT of work, to give you an idea here's the checklist (taken from https://gitlab.syncad.com/hive/hive/issues/25):

    • Transform this new account into a "locked" account (clear keys/ remove recovery account), see hard fork 21
    • Hard fork steem.dao funds to this new account
    • Change the STEEM_TREASURY_ACCOUNT def to the new account (needs to handle replays so it should only change at a specific hard fork ?)
    • Update all return proposals with payouts to steem.dao
    • Update all pending escrows to steem.dao
    • Update all pending payout posts with beneficiaries to steem.dao
    Loading...