new RPC method for querying with bid & sequence #270

New issue

Closed

opened 2019-05-08 17:29:49 +02:00 by BrannonKing · 1 comment

BrannonKing commented

2019-05-08 17:29:49 +02:00

(Migrated from github.com)

Allow querying on name, where it will return the winning bid for that claim name.
Allow querying on name and claim_id or partial claim_id.
Allow querying on name and sequence number (creation order).
Allow querying on name and bid number (according to current bid order).
Include an option to not return the value/metadata field.

Can it support a partial name if there is only one hit for that name? Maybe, but this isn't critical. Can it support no name or a partial name if the claim_id is given in full? Sure.

We need a new RPC method that supports more robust querying of the claim trie. This will eventually replace getclaimsforname, and it will need a corresponding "proof" RPC method that returns the merkle tree for the queried data. Requirements: 1. Allow querying on name, where it will return the winning bid for that claim name. 2. Allow querying on name and claim_id or partial claim_id. 3. Allow querying on name and sequence number (creation order). 4. Allow querying on name and bid number (according to current bid order). 5. Include an option to not return the value/metadata field. Can it support a partial name if there is only one hit for that name? Maybe, but this isn't critical. Can it support no name or a partial name if the claim_id is given in full? Sure.

lyoshenka commented

2019-05-21 22:29:52 +02:00

(Migrated from github.com)

sdk ended up taking this over

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#270

No description provided.