Skip to content

Add getBestBlockId RPC method - #320

Merged
joojis merged 5 commits into
CodeChain-io:masterfrom
kakao-jun-e:release/bestblockid
Jul 5, 2018
Merged

joojis merged 5 commits into
CodeChain-io:masterfrom
kakao-jun-e:release/bestblockid

Conversation

@kakao-jun-e

Copy link
Copy Markdown
Contributor

Fixed #290

@joojis

joojis commented Jul 4, 2018

Copy link
Copy Markdown
Contributor

@redongjun Could you update the spec file along with?

https://github.com/CodeChain-io/codechain/blob/master/spec/JSON-RPC.md#chain_getbestblockid

@kakao-jun-e

kakao-jun-e commented Jul 4, 2018 •

Copy link
Copy Markdown
Contributor Author

@joojis it's OK

Could you know me why the order of field (hash and number) is reversed on a RPC response as below?

{"jsonrpc":"2.0","result":{"hash":"0x5559d68fc86a3088383bc83a8ed0b092523e578283a0260eb0cec5832a0006ea","number":0},"id":null}

@joojis

joojis commented Jul 4, 2018

Copy link
Copy Markdown
Contributor

@redongjun I was unintentional for that. You can change the order in the spec.

@kakao-jun-e
kakao-jun-e force-pushed the release/bestblockid branch from f030ef6 to 6fc2ffe Compare July 4, 2018 11:32
@joojis
joojis self-requested a review July 5, 2018 01:21
Comment thread spec/JSON-RPC.md
```

## chain_getBestBlockId
(not implemented yet) Gets the number and the hash of the best block.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is 1 more "not implemented" note in the List of Methods (line 84)

@kakao-jun-e
kakao-jun-e force-pushed the release/bestblockid branch from 64adffe to f20f841 Compare July 5, 2018 04:32

@joojis joojis left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@joojis
joojis merged commit 1a3c98c into CodeChain-io:master Jul 5, 2018
@kakao-jun-e
kakao-jun-e deleted the release/bestblockid branch July 6, 2018 00:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants