RPC: Implement getnettotals #84
Labels
Comments
gsalgado
pushed a commit
to gsalgado/btcd
that referenced
this issue
Jul 29, 2014
This commit is the result of several big changes being made to the wallet. In particular, the "handshake" (initial sync to the chain server) was quite racy and required proper synchronization. To make fixing this race easier, several other changes were made to the internal wallet data structures and much of the RPC server ended up being rewritten. First, all account support has been removed. The previous Account struct has been replaced with a Wallet structure, which includes a keystore for saving keys, and a txstore for storing relevant transactions. This decision has been made since it is the opinion of myself and other developers that bitcoind accounts are fundamentally broken (as accounts implemented by bitcoind support both arbitrary address groupings as well as moving balances between accounts -- these are fundamentally incompatible features), and since a BIP0032 keystore is soon planned to be implemented (at which point, "accounts" can return as HD extended keys). With the keystore handling the grouping of related keys, there is no reason have many different Account structs, and the AccountManager has been removed as well. All RPC handlers that take an account option will only work with "" (the default account) or "*" if the RPC allows specifying all accounts. Second, much of the RPC server has been cleaned up. The global variables for the RPC server and chain server client have been moved to part of the rpcServer struct, and the handlers for each RPC method that are looked up change depending on which components have been set. Passthrough requests are also no longer handled specially, but when the chain server is set, a handler to perform the passthrough will be returned if the method is not otherwise a wallet RPC. The notification system for websocket clients has also been rewritten so wallet components can send notifications through channels, rather than requiring direct access to the RPC server itself, or worse still, sending directly to a websocket client's send channel. In the future, this will enable proper registration of notifications, rather than unsolicited broadcasts to every connected websocket client (see issue btcsuite#84). Finally, and the main reason why much of this cleanup was necessary, the races during intial sync with the chain server have been fixed. Previously, when the 'Handshake' was run, a rescan would occur which would perform modifications to Account data structures as notifications were received. Synchronization was provided with a single binary semaphore which serialized all access to wallet and account data. However, the Handshake itself was not able to run with this lock (or else notifications would block), and many data races would occur as both notifications were being handled. If GOMAXPROCS was ever increased beyond 1, btcwallet would always immediately crash due to invalid addresses caused by the data races on startup. To fix this, the single lock for all wallet access has been replaced with mutexes for both the keystore and txstore. Handling of btcd notifications and client requests may now occur simultaneously. GOMAXPROCS has also been set to the number of logical CPUs at the beginning of main, since with the data races fixed, there's no reason to prevent the extra parallelism gained by increasing it. Closes btcsuite#78. Closes btcsuite#101. Closes btcsuite#110.
gsalgado
pushed a commit
to gsalgado/btcd
that referenced
this issue
Jul 29, 2014
If a websocket client was already connected and the wallet and/or chain server is loaded into the rpc server (enabling the handlers specific to those components), the btcdconnected notifications were not being sent, and this could break clients that expected the notification. I'm not happy with this change, but since this is how notifications are currently done (unsolicited), and to not break compatibility yet, I'm adding these back in for now. Eventually, this notification will require explicit registration before it is received by a client. See issue btcsuite#84. Closes btcsuite#115.
davecgh
added a commit
to davecgh/btcd
that referenced
this issue
Aug 16, 2017
This makes vet happy by manually copying the notification state fields during the deep copy instead of copying the entire struct which contains an embedded mutex.
kcalvinalvin
added a commit
to kcalvinalvin/btcd
that referenced
this issue
Nov 29, 2024
…reexo-lib main: update utreexo library
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per the title, the getnettotals RPC method is needed. Now that the peers track this information.
The text was updated successfully, but these errors were encountered: