- Aug 6, 2014
What are the bandwidth requirements on a monthly bases for running an electrum server?
For Darkcoin - at the moment almost nil. You need to run a darkcoind (daemon), to keep track of all darkcoin transactions, and then an Electrum-DRK server, which listens to Electrum clients (1 so far).What are the bandwidth requirements on a monthly bases for running an electrum server?
my server : 184.108.40.206ENCOMPASS devs, the guys behind the new Multi-coins Electrum wallet client, have successfully tested the Darkcoin implementation add-on, and are about to release their update.
Encompass have taken the Electrum 2.0 code and made generic the parts of the Electrum code that is generic to all coins - then they added specific libraries where the unique details of each coins is listed - the result, less than an 1 hour of work to port a new coin to Electrum - a great approach to Electrum! Therefore, a coin that wants to be added to Electrum only needs a few changes in the code to be included into the Encompass wallet (but coin dev have to provide Electrum-Servers for their coin).
The Darkcoin Encompass client NEEDS additional Electrum-drk servers to function. So far, I have provided a Darkcoin main-net server for the last two weeks, based on this github repo - which works really well. However, we need more than one Electrum server, for security reasons.
Please provide me with your URL, so that I can include it in the /lib/chains/darkcoin.py spec file of Darkcoin Encompass, on the next commit (this week).
If you want to provide a pull request by yourself, be my guest, by inserting your Electrum-DRK server URL into the darkcoin.py file available at /github.com/ELM4Ever/encompass, and submit it to /github.com/mazaclub/encompass main repo.
Trying to have a personalized Electrum Client for Darkcoin, will not work, in my opinion, let's join the Encompass revolution! I personally tried to adapt the Electrum client to Darkcoin, and there are too many files to update. Encompass found the right way to do it!
1. Currently, Multisig and Trezor support are "disabled" on Encompass - more tests are required by devs.
2. Darkcoin PoW is not checked at the client side of Encompass - the Darkcoin "ever changing" specific PoW algorithms have not been ported to Phyton yet. However, all Electrum-DRK servers, connected to a darkcoind daemon is checking PoW. Suspenders over a belt are always better, but until Darkcoin devs provide a Python implementation of the DRK PoW, it will have to do for now.
3. With Encompass, one seed creates addresses for ALL supported multi-coins. Therefore, if you loose your seed, you loose all the coins associated with that seed. Just be aware. However, the convenience to switch from one coin to the other, within the same wallet makes so much sense. I would not keep $100k in this kind of wallet, but would well likely do something less - ... until Trezor support is activated!
THIS IS A CALL FOR NEW (and dedicated) main-net Electrum-DRK SERVERS. The Encompass (Darkcoin) client will be available after the commit this week.
PS: Without the "darkcoin_hash" python library from vertoe, this would have never been possible.
Please provide a FQDN for this IP address, or do a pull request to Encompass to add your server to lib/chains/darkcoin.pymy server : 220.127.116.11
Really do need a picture to see. Also please use the forum feedback forum.
So we are using Encompass as the client and which repository as the electrum-drk-server itself?
"not yet" - ELM4ever said it needs more testing. but if it does we should stick to encompass, as it seems actively maintained.So we are using Encompass as the client and which repository as the electrum-drk-server itself?
Also, I was under the impression Encompass didn't support Trezor.
FQDN is always better, but not mandatory.
Which repository are we going to use for the server? The one under my github account or another?FQDN is always better, but not mandatory.
However, it is mandatory that people running a server to use IRC in their server config file (irc = yes), and that they also define the report_host variable to match their FQDN or external IP address. Otherwise, your server will not get listed in the clients. "18.104.22.168" is currently is this situation, he (she) is running a server, it is up, but it is not listed in the encompass clients because not in IRC.
My server currently running is based on yours.Which repository are we going to use for the server? The one under my github account or another?
I'll knock this out right now.
That's the one! Congratulations! You are an official Electrum-DRK server! And you show up in the client list of available servers.ELM4ever
[04/03/2015-02:46:57] sent tx: 5a233ed0f7063f25836cbdc349e58287f65e4d34b10ddee9$
[04/03/2015-02:46:59] cache: invalidating Xppn8RSZ4ffYMXu1rL5EZucBaHNDeis2u3
[04/03/2015-02:46:59] cache: invalidating XouAQGK2GGeiSE6Xa2sgPhmTRsPLyxZAyw
[04/03/2015-02:47:19] blockchain: 229644 (0.229s)
[04/03/2015-02:47:29] cache: invalidating XouAQGK2GGeiSE6Xa2sgPhmTRsPLyxZAyw
[04/03/2015-02:47:29] cache: invalidating Xppn8RSZ4ffYMXu1rL5EZucBaHNDeis2u3
[04/03/2015-02:47:29] blockchain: 229645 (0.071s)
It's all there; looks good.
Heh, I doubt that server can handle 10k, I'll give it a go though. It'll be back in the list once it's finished the database.That's the one! Congratulations! You are an official Electrum-DRK server! And you show up in the client list of available servers.
Now the next step is for you to upgrade to 10k pruning... instead of 1k.
Also try Encompass 0.4.4 for your client.
[04/03/2015-08:36:14] Starting Electrum-DRK server on localhost [04/03/2015-08:36:16] Database version 3 [04/03/2015-08:36:16] Blockchain height 209517 [04/03/2015-08:36:16] UTXO tree root hash: 6b96a0cb2565e13d82a28ae56411bad910a1d2922d40e068f7c3e5d7fd346176 [04/03/2015-08:36:16] Coins in database: 507314432375985 [04/03/2015-08:36:16] catching up missing headers: 209510 209517 [04/03/2015-08:36:16] TCP server started on 127.0.0.1:50001 [04/03/2015-08:36:16] SSL server started on 127.0.0.1:50002 [04/03/2015-08:36:16] HTTP server started. [04/03/2015-08:36:16] HTTPS server started. [04/03/2015-08:36:16] Stopping Stratum [04/03/2015-08:36:16] Error: make sure you run darkcoind with txindex=1; use -reindex if needed. [04/03/2015-08:36:16] blockchain reorg 209517 00000000000ac9c11b397217f305237975a0a8b68a8b2b7373b2b2ed6ef4f208 000000000001d1a5a8bac1691b7b5c442dabf3bc18f83363f42ab4a212618024 [04/03/2015-08:36:16] no undo info for 209517 [04/03/2015-08:36:17] Closing database... [04/03/2015-08:36:17] Database is closed [04/03/2015-08:36:17] Electrum-DRK Server stopped