chaincase-app
Connect Full Node UI
https://github.com/chaincase-app/Chaincase/issues/215 Drafting this PR so we can have a discussion on the open qs
Open Questions
- Where to persist node address provided by the user. A natural candidate is the config file
- After we collect the node address we can create a new CoreNode object and configure a new block provider. How can we re-register the wallet manager services to include the new block provider? Perhaps there is an alternate way to re-config the block provider during run-time?
follow the wasabi implementation
Where to persist node address provided by the user. A natural candidate is the config file
Config.MainNetBitcoinP2pEndPoint
After we collect the node address we can create a new CoreNode object and configure a new block provider. How can we re-register the wallet manager services to include the new block provider? Perhaps there is an alternate way to re-config the block provider during run-time?
Related to https://github.com/chaincase-app/Chaincase/pull/178 which allows for options to change at runtime. An MVP/PoC that only connects to config available at start is ok to me
can we delete the connect button and auto try to connect on either page open or boot or when the endpoint changes? fine to show loading animation to show action is happening
Current UI
I
I added a separate input field for port. Not sure if I want to keep it
some inspiration. I don't see a need for the toggle, nor a save button, but I think providing feedback by way of "connected" is best practice
Designs look dope. Let me see what I can do.
does it connect? we don't support signet or liquid yet.
I'll remove those ports. It connects to my local node. What are the chaincase P2P tor hidden services (test and main net)?
