Jonathan Washburn

Results 11 issues of Jonathan Washburn

### Preliminary Checks - [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues - [X] This issue is not a question, feature...

bug
triage
itn3

### Preliminary Checks - [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues - [X] This issue is not a question, feature...

bug
triage

### Preliminary Checks - [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues - [X] This issue is not a question, feature...

bug
triage

Fixes #138 Moves configuration up to index so it's easier to see how/where things are happening. Removes dangling fee factory that was never implemented. Creates new PayoutCalculator factory. Provides new...

The current calculator is over complicated vs. what is needed once supercharged awards are gone. If processing on Fork 1, use a new calculator that does not include supercharged rewards.

Currently staking-ledger-utils co-mingles .burnSupercharged with MF/O1/Investors addresses. We should have a complete separation of (private) local configuration data vs.public (MF/O1 controlled) lists.

### Preliminary Checks - [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues - [X] This issue is not a question, feature...

bug
triage

### Preliminary Checks - [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues - [X] This issue is not a question, feature...

bug
triage

Block 1582 from the O1 precomputed storage on GCS is invalid, or there is a bug in the block loader: ``` Apr 03 00:33:25 nym3 bash[2806445]: Downloading devnet-1582-3NLZQcjScyXEhitHToSb31RbAWQ3AqJRLxqLxNAo17YmTLYteGyk.json block Apr...

status-needs-repro
bug
impacts users
needs repro
community-major-bug

I don't think this warrants an RFC; if it does, please close, and I can resubmit with an RFC and proposed solution. Maybe I'm doing it wrong - and if...