Skip to content
This repository has been archived by the owner on Oct 4, 2019. It is now read-only.

worker_proposal_object has too many fields #1109

Closed
afalaleev opened this issue Feb 12, 2019 · 0 comments
Closed

worker_proposal_object has too many fields #1109

afalaleev opened this issue Feb 12, 2019 · 0 comments
Assignees
Labels
Milestone

Comments

@afalaleev
Copy link
Member

        account_name_type author;
        shared_string permlink;
        worker_proposal_type type;
        worker_proposal_state state;
        account_name_type approved_techspec_author;
        shared_string approved_techspec_permlink;
        time_point_sec created;   // not required for consensus
        time_point_sec modified; // not required for consensus
        share_type net_rshares;  // not required for consensus
    };
@afalaleev afalaleev added this to the 0.21.0 milestone Feb 12, 2019
@maslenitsa93 maslenitsa93 self-assigned this Feb 14, 2019
maslenitsa93 added a commit that referenced this issue Feb 15, 2019
maslenitsa93 added a commit that referenced this issue Feb 15, 2019
maslenitsa93 added a commit that referenced this issue Feb 18, 2019
maslenitsa93 added a commit that referenced this issue Feb 18, 2019
maslenitsa93 added a commit that referenced this issue Feb 19, 2019
afalaleev pushed a commit that referenced this issue Feb 20, 2019
Move non-consensus fields from worker_proposal_object #1109
maslenitsa93 added a commit that referenced this issue Jul 24, 2019
Move non-consensus fields from worker_proposal_object #1109
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants