electrum

History

ThomasV 83a422988e ledger: ImportError fallback		8 years ago
..
audio_modem	More cleanup of WaitingDialog	9 years ago
cosigner_pool	another cosignerpool fix	8 years ago
email_requests	Relicensing	9 years ago
greenaddress_instant	Relicensing	9 years ago
hw_wallet	call choose_device when button is clicked	8 years ago
keepkey	Remove dynamic classes in trezor compatible plugins.	8 years ago
labels	labels plugin: use get_fingerprint	9 years ago
ledger	ledger: ImportError fallback	8 years ago
trezor	trezor: fix is_xprv	8 years ago
trustedcoin	trustedcoin: remove hardcoded item	8 years ago
virtualkeyboard	finish separation between plugins and GUIs	9 years ago
README	plugins readme	10 years ago
__init__.py	Relicensing	9 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 doe