hairtail

should I open a PR related with this issue now or later

> Request:params indicate the height to query curl --data-binary '{"jsonrpc": "2.0", "id":"documentation", "method": "getblockminer", "params": [66666] }' -H 'content-type: application/json' http://127.0.0.1:3032/ Response: { "jsonrpc": "2.0", "result": "aleo1gqa7nht8lv93ksgmfy8hnz028r776evnv5kllkcsx2ycek5ryq9suprafw", "id": "documentation" }

Since we are testnet phase, there is an easy and experiment way to do this. We can make an extra bonus for good & registered big pool miners who mine...

I'm planning to support standard JSON 2.0 compatible interface for ironfish rpc call over http. Should I open another PR here since there is a PR open for http request....

> > Refactor data struct for submitted share: > > > > 1. Miner name from which this share is submitted so that we know the last time we see...

Cool, what you have mentioned above is kind of easy way to implement auth system. If everything is ok, I will try to work on it.

Working on auth sys with [Bearer token](https://oauth.net/2/bearer-tokens/). Let me know if there's some update or anything wrong.

> wallet 2.0 shows forked status, check back when it gets released I have checked `account-performance` branch, seems that it will be in expired status for MinersFeeTransactions of forked blocks.

> Can you give the error output from the call? The stack trace would be useful here. RangeError: Maximum call stack size exceeded. That's all. No crash trace displayed.

Close as fixed.