Ryan R. Fox

I worked with @OpenLedgerApp to establish a drafting budget for this BSIP of 10 hours. It will be paid in weeks 50-51. Revisions will continue within this budget.

I agree with @pmconrad about potential security risks. In this specific case it may be mitigated by the assumption that block producing nodes should not be directly connected to the...

Assigned BSIP78 @abitmore

You are correct @abitmore I fixed the title here and updated the readme in #228 (please review)

I feel we should: - Leave this BSIP assignment as 79 - Create a new Issue for the redesign of "Short-Term Membership" to assign a new BSIP number (80) -...

I'd rather not add more status gates at this time. In case of this BSIP, we should have required the draft text be posted into this Issue discussion. Then we...

I feel this Issue needs a BSIP drafted. It will be a consensus change, so December at the earliest for release (unlikely). Next opportunity would be June. Let's get an...

Perhaps a way for current auth to sign intention to revoke legacy auths. This would make it incumbent on a new owner to perform this step as part of account...

Adding to (next) Protocol Release for further research and discussion. Not clear where the best place to discuss this will be. It seems identifying the impacted accounts is required step....

Yes, @OpenLedgerApp please do some research to identify the locked accounts. Suggesting from @oxarbitrage is to use elasticsearch plugin. Next, would be some effort to identify the accounts in a...