You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
ThomasV 641968fcf8 Wizard: do not ask seed type, default to segwit 5 years ago
..
audio_modem integrate PSBT support natively. WIP 6 years ago
bitbox02 hw plugins: log exception at import time (but only if interesting) 5 years ago
coldcard hw plugins: log exception at import time (but only if interesting) 5 years ago
cosigner_pool plugins: remove 'on_new_window' hook 5 years ago
digitalbitbox hardware devices: run all device communication on dedicated thread (#6561) 5 years ago
email_requests qt: rm some usages of get_parent_main_window 5 years ago
hw_wallet ledger: fix enumerating ledger devices with new bitcoin app (1.5.1) 5 years ago
keepkey transaction: change Transaction.is_segwit_input(txin) to txin.is_segwit() 5 years ago
labels plugins/labels: better error message when using imported wallets 5 years ago
ledger hw plugins: log exception at import time (but only if interesting) 5 years ago
revealer qt: rm some usages of get_parent_main_window 5 years ago
safe_t qt: move window.get{Open,Save}FileName to util 5 years ago
trezor hw plugins: log exception at import time (but only if interesting) 5 years ago
trustedcoin Wizard: do not ask seed type, default to segwit 5 years ago
virtualkeyboard no more "import *" 7 years ago
README file reorganization with top-level module 8 years ago
__init__.py file reorganization with top-level module 8 years ago

README

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.