Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getblock on tip returns an empty string for nextblockhash #416

Closed
arnuschky opened this issue May 4, 2015 · 3 comments · Fixed by #417
Closed

getblock on tip returns an empty string for nextblockhash #416

arnuschky opened this issue May 4, 2015 · 3 comments · Fixed by #417

Comments

@arnuschky
Copy link

Not sure whether this is the intended behavior. On bitcoin core, nextblockhash is not in the dictionary.

davecgh added a commit to davecgh/btcd that referenced this issue May 4, 2015
This commit omits the nextblockhash field from the getblock RPC result
when there isn't one (i.e for currnet the tip).

Closes btcsuite#416.
davecgh added a commit to davecgh/btcd that referenced this issue May 4, 2015
This commit omits the nextblockhash field from the getblock RPC result
when there isn't one (i.e for current the tip).

Closes btcsuite#416.
@davecgh
Copy link
Member

davecgh commented May 4, 2015

Thanks.

I just pushed a PR which changes it. Realistically empty versus not present isn't a big deal (it's trivial to check for == ""), but for the sake of compatibility, I pushed the PR.

@arnuschky
Copy link
Author

Great, thanks. I wasn't sure whether there's a convention wrt to empty keys.

@arnuschky
Copy link
Author

Confirmed working here, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants