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 syntax to parameter referring to a block from the tip #2197

Closed
bitcartel opened this issue Mar 22, 2017 · 1 comment
Closed

Add syntax to parameter referring to a block from the tip #2197

bitcartel opened this issue Mar 22, 2017 · 1 comment
Labels
A-rpc-interface Area: RPC interface usability
Projects
Continuous Improvement

Comments

@bitcartel
Copy link
Contributor

RPC call getblock can refer to a block by height #2187.

The user might want to specify a recent block, say the 10th block before the current tip.

Devise a syntax which can be used e.g. -10 or tip-10 and see where else it can be used in the RPC interface.
@bitcartel bitcartel added A-rpc-interface Area: RPC interface usability labels Mar 22, 2017
This was referenced Mar 22, 2017
Merged
Merged
@oxarbitrage oxarbitrage mentioned this issue Dec 31, 2019
Merged
zkbot added a commit that referenced this issue Mar 5, 2020
@zkbot
Auto merge of #4280 - oxarbitrage:issue2197, r=daira
6c00a8c 
Allow negative heights in RPC calls

For issue #2197

Currently adding the feature to `getblock` and `getblockhash`. There is another candidate: `getblocksubsidy` however i want to have some review about these 2 first before repeating what could be a bad approach.
@oxarbitrage
Copy link
Contributor

Need to be closed manually as the PR was not linking the issue.

@str4d str4d closed this as completed Apr 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-rpc-interface Area: RPC interface usability
Projects
No open projects
Continuous Improvement
  
Awaiting triage
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bitcartel @str4d @oxarbitrage