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.

Sign up for GitHub

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

Jump to bottom

Add Shelley tip query command #933

Merged
merged 2 commits into from May 11, 2020
Merged

Add Shelley tip query command #933

merged 2 commits into from May 11, 2020

Conversation

intricate
Copy link
Contributor

No description provided.

@intricate intricate self-assigned this May 11, 2020
@erikd
Copy link
Contributor

erikd commented May 11, 2020

This command needs a --network-magic parameter for non-mainnet.

@erikd
Copy link
Contributor

erikd commented May 11, 2020

bors r+

@iohk-bors
Copy link
Contributor

iohk-bors bot commented May 11, 2020

Build succeeded

@iohk-bors iohk-bors bot merged commit fe49b1f into master May 11, 2020
@iohk-bors iohk-bors bot deleted the intricate/tip-query-api branch May 11, 2020 09:28
@intricate
Copy link
Contributor Author

This command needs a --network-magic parameter for non-mainnet.

The command does accept a --network-magic parameter:

| QueryTip Network

@erikd
Copy link
Contributor

erikd commented May 12, 2020 •
edited

Choosing the network has been sorted out.

Usage: cardano-cli shelley query tip (--mainnet | --testnet-magic INT)
  Get the node's current tip (slot no, hash, block no)

Available options:
  --mainnet                Use the mainnet magic id.
  --testnet-magic INT      Specify a testnet magic id.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@erikd erikd erikd approved these changes

@dcoutts dcoutts Awaiting requested review from dcoutts

@Jimbo4350 Jimbo4350 Awaiting requested review from Jimbo4350

Assignees

@intricate intricate

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@intricate @erikd