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
b28b3994c7
|
4 years ago | |
|---|---|---|
| .. | ||
| audio_modem | 5 years ago | |
| bitbox02 | 4 years ago | |
| coldcard | 4 years ago | |
| cosigner_pool | 4 years ago | |
| digitalbitbox | 4 years ago | |
| email_requests | 4 years ago | |
| hw_wallet | 4 years ago | |
| keepkey | 4 years ago | |
| labels | 4 years ago | |
| ledger | 4 years ago | |
| revealer | 4 years ago | |
| safe_t | 4 years ago | |
| trezor | 4 years ago | |
| trustedcoin | 4 years ago | |
| virtualkeyboard | 6 years ago | |
| README | 7 years ago | |
| __init__.py | 7 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