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

Omniwallet issues affecting Omniwallet REST client #140

Open
msgilligan opened this issue Jun 1, 2017 · 0 comments
Open

Omniwallet issues affecting Omniwallet REST client #140

msgilligan opened this issue Jun 1, 2017 · 0 comments
Assignees

Comments

@msgilligan
Copy link
Member

msgilligan commented Jun 1, 2017

This is a tracking issue for Omniwallet issues that will resolve issues in the Omniwallet REST client. This issues are listed in "priority to OmniJ" order:

  1. Address-balance rate-limit issue: Multiple address-balance request returns zero BTC balances due to rate limit omniwallet#1507
  2. Include reserved amount in /v2/address/addr query: address-balance request should return 'reserved' balances omniwallet#1511
  3. Watch-only backup/export of Omniwallet addresses: Add watch-only backup/export of wallet addresses omniwallet#1287
  4. Distinguish Divisible from Indivisible property type in address-balances: Distinguish divisible vs. indivisible values with numeric formatting. omniwallet#1235
  5. Ability to query block hash along with block height: API /v1/system/revision.json should return block hash of recent block omniwallet#1504
  6. Linkable URL on Omniwallet for showing an address-balance: GET URL for Omniwallet balance check omniwallet#1288
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants