1- XEP Core integration/staging tree
2- =====================================
3-
4- https://bitcoincore.org
5-
61What is XEP?
7- ----------------
2+ ============
83
9- XEP is an experimental digital currency that enables instant payments to
10- anyone, anywhere in the world. XEP uses peer-to-peer technology to operate
11- with no central authority: managing transactions and issuing money are carried
12- out collectively by the network. XEP Core is the name of open source
13- software which enables the use of this currency.
4+ The Electra Protocol has been developed with invaluable features in mind to allow merchants, customers, and casual users to incorporate Electra Protocol’s global payment
5+ system into their everyday lives. Since the beginning, Electra has kept its users at the forefront of Project decisions throughout the development process, intending to
6+ transform how the world views payments through cryptocurrency and blockchain technologies.
147
158For more information, as well as an immediately usable, binary version of
16- the XEP Core software, see https://bitcoincore.org/en/download/ , or read the
17- [ original whitepaper] ( https://bitcoincore.org/xep.pdf ) .
9+ the XEP Core software, see https://www.electraprotocol.com/ , or read the
10+ [ whitepaper] ( https://www.electraprotocol.com/whitepaper/ ) .
11+
12+ <table >
13+ <tr > <td >Ticker</td ><td >XEP</td ></tr >
14+ <tr > <td >Algorithm</td ><td >SHA-256</td ></tr >
15+ <tr > <td >Consensus</td ><td >Proof-of-Stake 3.0e</td ></tr >
16+ <tr > <td >Circulating supply</td ><td >https://explorer.electraprotocol.network/</td ></tr >
17+ <tr > <td >Block Time</td ><td >80 Seconds</td ></tr >
18+ <tr > <td >Block Size</td ><td >10 MB (Dynamic)</td ></tr >
19+ <tr > <td >Staking Reward</td ><td >3% yearly</td ></tr >
20+ <tr > <td >Transactions Per Second</td ><td >up to 1600</td ></tr >
21+ <tr > <td >Retarget</td ><td >Every Block</td ></tr >
22+ <tr > <td >Coin Maturation Time</td ><td >12 Hours & 600 confirmations</td ></tr >
23+ <tr > <td >Max Coin Age</td ><td >30 Days</td ></tr >
24+ <tr > <td >Electronic Payment</td ><td >ElectraPay</td ></tr >
25+ <tr > <td >SegWit</td ><td >Native</td ></tr >
26+ <tr > <td >Lightning Network</td ><td >Native</td ></tr >
27+ <tr > <td >Taproot</td ><td >Native</td ></tr >
28+ <tr > <td >Atomic Swap</td ><td >Yes</td ></tr >
29+ <tr > <td >Premine</td ><td >3B*</td ></tr >
30+ </table >
31+ * 1.5B the first year, then 0.5 each subsequent years. (This is the maximum amount and can be burned eventually.)
1832
1933License
2034-------
@@ -26,55 +40,5 @@ Development Process
2640-------------------
2741
2842The ` master ` branch is regularly built (see ` doc/build-*.md ` for instructions) and tested, but it is not guaranteed to be
29- completely stable. [ Tags] ( https://github.com/bitcoin/bitcoin /tags ) are created
43+ completely stable. [ Tags] ( https://github.com/ElectraProtocol/XEP-Core /tags ) are created
3044regularly from release branches to indicate new official, stable release versions of XEP Core.
31-
32- The https://github.com/xep-core/gui repository is used exclusively for the
33- development of the GUI. Its master branch is identical in all monotree
34- repositories. Release branches and tags do not exist, so please do not fork
35- that repository unless it is for development reasons.
36-
37- The contribution workflow is described in [ CONTRIBUTING.md] ( CONTRIBUTING.md )
38- and useful hints for developers can be found in [ doc/developer-notes.md] ( doc/developer-notes.md ) .
39-
40- Testing
41- -------
42-
43- Testing and code review is the bottleneck for development; we get more pull
44- requests than we can review and test on short notice. Please be patient and help out by testing
45- other people's pull requests, and remember this is a security-critical project where any mistake might cost people
46- lots of money.
47-
48- ### Automated Testing
49-
50- Developers are strongly encouraged to write [ unit tests] ( src/test/README.md ) for new code, and to
51- submit new unit tests for old code. Unit tests can be compiled and run
52- (assuming they weren't disabled in configure) with: ` make check ` . Further details on running
53- and extending unit tests can be found in [ /src/test/README.md] ( /src/test/README.md ) .
54-
55- There are also [ regression and integration tests] ( /test ) , written
56- in Python, that are run automatically on the build server.
57- These tests can be run (if the [ test dependencies] ( /test ) are installed) with: ` test/functional/test_runner.py `
58-
59- The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.
60-
61- ### Manual Quality Assurance (QA) Testing
62-
63- Changes should be tested by somebody other than the developer who wrote the
64- code. This is especially important for large or high-risk changes. It is useful
65- to add a test plan to the pull request description if testing the changes is
66- not straightforward.
67-
68- Translations
69- ------------
70-
71- Changes to translations as well as new translations can be submitted to
72- [ XEP Core's Transifex page] ( https://www.transifex.com/xep/xep/ ) .
73-
74- Translations are periodically pulled from Transifex and merged into the git repository. See the
75- [ translation process] ( doc/translation_process.md ) for details on how this works.
76-
77- ** Important** : We do not accept translation changes as GitHub pull requests because the next
78- pull from Transifex would automatically overwrite them again.
79-
80- Translators should also subscribe to the [ mailing list] ( https://groups.google.com/forum/#!forum/xep-translators ) .
0 commit comments