electrum

History

Maran 327c1bafd9 Use TLS for LabelSync		10 years ago
..
README	plugins readme	10 years ago
__init__.py	header for plugins	12 years ago
audio_modem.py	new class to show buttons in LineEdit. fixes #1050	10 years ago
btchipwallet.py	revert commit 3ae2fb2e90b0296066509d1934d1c24b6333260f	10 years ago
cosigner_pool.py	fix Transaction.deserialize() to Transaction()	10 years ago
exchange_rate.py	minor fix: index	10 years ago
greenaddress_instant.py	plugins: fix buttons insertion	10 years ago
labels.py	Use TLS for LabelSync	10 years ago
openalias.py	store contacts in a separate file, shared between wallets	10 years ago
plot.py	store deserialized tx in/out in wallet file for fast computation	10 years ago
trezor.py	always_hook. fix trezor handler. fixes #1146	10 years ago
trustedcoin.py	always_hook. fix trezor handler. fixes #1146	10 years ago
virtualkeyboard.py	fix virtualkeyboard bug	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