electrum

History

ThomasV 45007a27e4 plugins readme		10 years ago
..
README	plugins readme	10 years ago
__init__.py	header for plugins	12 years ago
audio_modem.py	audio_modem: update plugin to work with latest version.	10 years ago
btchipwallet.py	fix: add wallet types only if available	10 years ago
coinbase_buyback.py	remove appdata_dir and data_dir	10 years ago
cosigner_pool.py	fix: start listener after testing if available	10 years ago
exchange_rate.py	set self.wallet to None in plugin constructor	10 years ago
greenaddress_instant.py	don't duplicate code	10 years ago
labels.py	Make all LabelSync calls async.	10 years ago
openalias.py	Merge pull request #1042 from openalias/master	10 years ago
plot.py	do not self-enable plot plugin	10 years ago
trezor.py	Merge pull request #1029 from m0mchil/transport_close	10 years ago
trustedcoin.py	trustedcoin plugin: fix is_billing	10 years ago
virtualkeyboard.py	init plugins before gui. register wallet types in plugin constructor	10 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