Why was the 'getinfo' command removed? #11671

issue ilsawa opened this issue on November 12, 2017
  1. ilsawa commented at 5:15 PM on November 12, 2017: none

    It seems some bright spark has decided that getinfo command is not needed in new versions of the daemons, and removed it. Now you need one command to see the amount of blocks, another one to see the amount of connections, and one more to see the balance. But now there are: getblockchaininfo getmempoolinfo gettxoutsetinfo getmemoryinfo ("mode") getmininginfo getaddednodeinfo ( "node" ) getnetworkinfo getpeerinfo getwalletinfo which individually do not provide general information. Thank you developers. Remove this command in your own wallets. But take getinfo back to me, leave the possibility to compile with this command.

    I do not understand the meaning of your innovation if it deprives the user of convenience.

  2. ghost commented at 9:35 PM on November 12, 2017: none

    Write a SH script that runs the "get*info" commands and formats the results however you like.

    At some point there was talk about including something like that in bitcoin-cli, but I'm not sure what happened to it.

  3. luke-jr commented at 9:36 PM on November 12, 2017: member

    bitcoin-cli -getinfo will be in 0.16. You can get it early in Knots.

  4. fanquake commented at 7:34 AM on November 13, 2017: member

    Duplicate of #11382. See discussion in #8780 and #10871.

  5. fanquake closed this on Nov 13, 2017

  6. Crypto2 commented at 2:07 AM on December 25, 2017: none

    tbh it should be left in just for reasons of compatibility with other coins so providers don't have to write extra code when supporting multiple Bitcoin-based coins. Even though it isn't a position Bitcoin may want being the 1st it kind of sets a core amount of basic functions that all Bitcoin RPC-compatible coins should have and getinfo is a major one of of those. Plus it isn't a large function and making 1 RPC call instead of 2-3 is always preferred.

  7. kangasbros commented at 12:25 PM on January 31, 2018: none

    I think also that getinfo should be preserved. It can be a parent call which collects the information using the new calls. There is lots of code around using this command and removing it probably requires lots of (IMO unnecessary) work.

  8. jnewbery commented at 2:31 PM on January 31, 2018: member

    @kangasbros, you've already made your opinion known in #11382 . This has been discussed multiple times in multiple venues.

    Fundamentally, getinfo requires information from multiple subsystems. The implementation is messy, and the locks all over the place make it difficult and expensive to maintain. Keeping it would mean we can't do refactors to clean up wallet and rpc code, burdening the project with long-term technical debt.

    Bitcoin Core is an open source project. You are completely free to fork the code and do the work necessary to maintain this code. Complaining that other people aren't doing that work for you achieves nothing.

    EDIT: I suggest we lock this issue. No new substantive arguments are being made to revert the change.

  9. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-13 18:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me