lightninglabs / lightninglabs/pool

rpc: add node tier information to matched orders in BatchSnapshot

Open
#203 0 comments 0 reactions 0 assignees View on GitHub
batch rpc
Dominant language
Go
Stars
259
Forks
51
PR merge metrics
No merged PRs in 30d

Description

By exposing these values, traders can start to get a better idea of the cost gap between a t0 vs t1 channel as defined now.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the RPC definition and implementation for BatchSnapshot, then trace how matched orders are assembled. Identify the existing node-related values available for each matched order and confirm the intended t0 and t1 tier representation. Done means the BatchSnapshot response exposes node tier information for matched orders and the relevant RPC behavior is covered by tests, if present.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.