electrum

History

ThomasV 98501b17b3 rename email plugin		10 years ago
..
README	plugins readme	10 years ago
__init__.py	rename email plugin	10 years ago
audio_modem.py	transaction_dialog: allow plugins manipulate transaction sharing buttons	10 years ago
btchipwallet.py	do not base64encode signatures in requests	10 years ago
cosigner_pool.py	Split tx dialog buttons	10 years ago
email_requests.py	rename email plugin	10 years ago
exchange_rate.py	Once a user inputs a fee, retain it.	10 years ago
greenaddress_instant.py	do not base64encode signatures in requests	10 years ago
labels.py	fix trezor initialiation hook (pass window in load_wallet)	10 years ago
plot.py	make plugins available without the GUI	10 years ago
trezor.py	fix bug #1365	10 years ago
trustedcoin.py	Rename send_tx() to sign_tx()	10 years ago
virtualkeyboard.py	make plugins available without the GUI	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