You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You could expose some of that stuff potentially, eg. block headers or hashes, but nakamoto doesn't keep a full mempool and doesn't validate every tx. The wallet API could be interesting..
I'd be more interested in knowing what the use-case might be; as far as I know, the only use case for running nakamoto standalone on the desktop is for running a desktop wallet, which we have a sketch of in the wallet crate.
I'd be more interested in knowing what the use-case might be; as far as I know, the only use case for running Nakamoto standalone on the desktop is for running a desktop wallet, which we have a sketch of in the wallet crate.
There is no really use case because you need to use a BIP 157 as an external API, however I have a design on how we can track the status of our transaction, so maybe nakamoto can be the first BIP 157 node with a command line. Also, neutrino is lacking in this ecosystem
Thinking to see if we can use the wallet integration with bdk
taking the discussion from #148 (comment) to a more appropriate place
if we look at the Core RPC API, which RPCs would
nakamoto-node
be able to expose (at least from a theoretical perspective)?The text was updated successfully, but these errors were encountered: