dashboard: a Slipstream page (#84, onto main) - #85
Merged
Merged
Conversation
With SLIPSTREAM_API_URL set, the public nav gains /slipstream: the minimum submission rate and current mineable rate, how to submit, and each recent tx with where it stands -- in template, mined (ours or not), confirmed, dropped with its reason. The page reads the slipstream service's API rather than slipstream.db, so the service stays the only owner of its schema, and a service that is down costs the page one card. Admin -> Tools lists the txs still open, each with a Withdraw button. That calls removeslipstreamtx on the enforcer, which holds the txs; the service records the tx as dropped (withdrawn) on its next poll.
Slipstream txs now go to the pool's bitcoind instead of an enforcer-side pool, and Core has no RPC to take a tx back out of its mempool, so there is nothing for the button to call. The admin router and Tools page are back as they were; the public /slipstream page stays, with its intro saying what is now true: an accepted tx is broadcast, and another pool may mine it first.
dashboard: a Slipstream page
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#84 was stacked on #83's branch. It merged 11 seconds after #83, before GitHub retargeted it to
main, so it landed infeat/slipstream-serviceand never reachedmain. This PR carries it the rest of the way.The diff is exactly #84's dashboard change:
/slipstreampage. It is shown in the nav only whenSLIPSTREAM_API_URLis set, and has four parts:info.json.dashboard/lib/slipstream.jsreads the service's API, neverslipstream.db. If the service is down, the page costs one card, not the page.docker-compose.yml, plusdashboard/README.md.There is no admin withdraw action, because Core has no RPC to take a tx back out of its mempool.
Tested in #84: 4 new tests, and the full dashboard suite (193) passes.