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.
 
 
 
 
SomberNight 1cfac928f9
trustedcoin: longer timeout for server signing
7 years ago
..
audio_modem no more "import *" 7 years ago
coldcard bip32: refactor whole module. clean-up. 7 years ago
cosigner_pool bip32: refactor whole module. clean-up. 7 years ago
digitalbitbox bip32: refactor whole module. clean-up. 7 years ago
email_requests no more "import *" 7 years ago
greenaddress_instant fix greenaddress plugin: follow-up 75f6ab9133 7 years ago
hw_wallet move opcodes to bitcoin.py 7 years ago
keepkey keepkey: support v6.0.0+ firmwares (webusb) 7 years ago
labels labels: don't dump trace if failed to connect to server 7 years ago
ledger ledger: suppress error message if user cancels tx signing 7 years ago
revealer no more "import *" 7 years ago
safe_t Merge pull request #5118 from SomberNight/trezor_init_20190213 7 years ago
trezor Merge pull request #5118 from SomberNight/trezor_init_20190213 7 years ago
trustedcoin trustedcoin: longer timeout for server signing 7 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.