LBRY-Vault/electrum/plugins
Marko Bencun b9b08b768f
plugins/bitbox02: fix min version check
Inform the user that they need to upgrade if their firmware version is
out of date.

The previous `check_device_firmware_version()` was dead code, and the
bb02 function called inside also does not exist.
2020-06-03 15:36:15 +02:00
..
audio_modem integrate PSBT support natively. WIP 2019-11-04 22:24:36 +01:00
bitbox02 plugins/bitbox02: fix min version check 2020-06-03 15:36:15 +02:00
coldcard coldcard: log exception traceback in create_client 2020-05-13 18:11:53 +02:00
cosigner_pool plugins: fix labels plugin FIXME re "just enabled plugin" 2020-05-25 17:31:13 +02:00
digitalbitbox hww hidapi usage: try to mitigate some thread-safety issues 2020-04-17 19:53:39 +02:00
email_requests change many str(e) to repr(e) as some exceptions were cryptic 2019-07-17 20:12:52 +02:00
hw_wallet hww: stop keystore.thread when closing wallet 2020-04-17 19:53:42 +02:00
keepkey hww: fix HardwareClientBase not having reference to plugin 2020-04-17 19:53:35 +02:00
labels plugins: fix labels plugin FIXME re "just enabled plugin" 2020-05-25 17:31:13 +02:00
ledger hww hidapi usage: try to mitigate some thread-safety issues 2020-04-17 19:53:39 +02:00
revealer logging: basics 2019-05-02 15:19:03 +02:00
safe_t hww: fix HardwareClientBase not having reference to plugin 2020-04-17 19:53:35 +02:00
trezor hww: fix HardwareClientBase not having reference to plugin 2020-04-17 19:53:35 +02:00
trustedcoin trustedcoin: (trivial) add a stub method in plugin base class 2020-05-29 20:51:52 +02:00
virtualkeyboard no more "import *" 2019-02-11 20:21:24 +01:00
__init__.py file reorganization with top-level module 2018-07-13 14:01:37 +02:00
README file reorganization with top-level module 2018-07-13 14:01:37 +02:00

Plugin rules:

 * The plugin system of Electrum is designed to allow the development
   of new features without increasing the core code of Electrum.

 * Electrum is written in pure python. if you want to add a feature
   that requires non-python libraries, then it must be submitted as a
   plugin. If the feature you want to add requires communication with
   a remote server (not an Electrum server), then it should be a
   plugin as well. If the feature you want to add introduces new
   dependencies in the code, then it should probably be a plugin.

 * We expect plugin developers to maintain their plugin code. However,
   once a plugin is merged in Electrum, we will have to maintain it
   too, because changes in the Electrum code often require updates in
   the plugin code. Therefore, plugins have to be easy to maintain. If
   we believe that a plugin will create too much maintenance work in
   the future, it will be rejected.

 * Plugins should be compatible with Electrum's conventions. If your
   plugin does not fit with Electrum's architecture, or if we believe
   that it will create too much maintenance work, it will not be
   accepted. In particular, do not duplicate existing Electrum code in
   your plugin.

 * We may decide to remove a plugin after it has been merged in
   Electrum. For this reason, a plugin must be easily removable,
   without putting at risk the user's bitcoins. If we feel that a
   plugin cannot be removed without threatening users who rely on it,
   we will not merge it.