Electrum Dark

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
What are the bandwidth requirements on a monthly bases for running an electrum server?
 

ELM4ever

Member
Feb 9, 2015
64
66
58
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).
 

ELM4ever

Member
Feb 9, 2015
64
66
58
The current blockchain headers file for DRK is 18 MB - that is the file that has to be downloaded from any Electrum-DRK-Servers to a new Electrum-DRK client when they join in.

If you want to be an Electrum-DRK-Server, the UTXOs use up about 300 MB of local disk space. Very small compared to Bitcoin...
 
Last edited by a moderator:

thelazier

Active Member
Jan 5, 2015
240
184
103
Thailand
Dash Address
Xreiza1qGJMT5BpW6BDtRJqwtcBSxGwWYN
ENCOMPASS 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!

Notes:

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.
my server : 103.13.228.168
 
  • Like
Reactions: vertoe

ELM4ever

Member
Feb 9, 2015
64
66
58
my server : 103.13.228.168
Please provide a FQDN for this IP address, or do a pull request to Encompass to add your server to lib/chains/darkcoin.py

Please also ensure that you insert your FQDN in your server config file:

report_host = xxx.xxxx.com <--- insert your FQDN here - in order to be reached from outside.
 

pbleak

Active Member
May 15, 2014
399
172
113
Would be great to see. Is DRK the only major coin without an electrum client?
 

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,891
6,719
1,283
Fire under Electrum
very cool !
 
  • Like
Reactions: moli

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Propulsion, on my screen I can't see akhavr's post because most of it is covered by a sticky google ad.

EDIT: Now that ad was removed. Thanks! :)
 
Last edited by a moderator:

DCT

Four of Ten
Jan 30, 2015
5,011
32
118
Propulsion, on my screen I can't see akhavr's post because most of it is covered by a sticky google ad.

EDIT: Now that ad was removed. Thanks! :)
Really do need a picture to see. Also please use the forum feedback forum.

I'll try to get a FQDM electrum darkcoin server running before the end of today. (my time)

Note: there is neither a daemon/wallet or an electrum client running on this server itself.
 

ELM4ever

Member
Feb 9, 2015
64
66
58
maybe flare (electrum.darkcoin.qa) or DCT (electrum.darkcointalk.org) could contribute a running electrum server too? I could add them to the PR.

ELM4ever is FQDN required?

edit, or coingun is could run one too? :)
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. "103.13.228.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.
 
Last edited by a moderator:

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
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. "103.13.228.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.
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.
 

ELM4ever

Member
Feb 9, 2015
64
66
58
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.
My server currently running is based on yours.

EDIT: I have been running on the main net for the last two weeks. The official Darkcoin daemon is the one that interfaces with the blockchain, not the electrum server... No need to use Testnet.
 
Last edited by a moderator:
  • Like
Reactions: Propulsion

ELM4ever

Member
Feb 9, 2015
64
66
58
Propulsion : Check you log file for the server, you should be able to see a DRK transaction I sent through your electrum server. "cache: invalidating X...."
 

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
ELM4ever

[04/03/2015-02:34:35] SSL 104.173.171.107:60509 1 0.4.4
[04/03/2015-02:34:53] TCP 104.173.171.107:55022 34 0.4.4
[04/03/2015-02:34:53] TCP 104.173.171.107:55023 1 0.4.4
[04/03/2015-02:34:57] TCP 104.173.171.107:55031 1 0.4.4
[04/03/2015-02:34:57] TCP 104.173.171.107:55032 1 0.4.4
[04/03/2015-02:35:07] blockchain: 229639 (0.114s)
[04/03/2015-02:35:48] blockchain: 229640 (0.026s)
[04/03/2015-02:37:28] blockchain: 229641 (0.062s)
[04/03/2015-02:38:58] blockchain: 229642 (0.316s)
[04/03/2015-02:41:58] TCP 104.173.171.107:55249 1 0.4.4
[04/03/2015-02:42:19] blockchain: 229643 (0.237s)
[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.
 
  • Like
Reactions: moli

ELM4ever

Member
Feb 9, 2015
64
66
58
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.
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.
 
  • Like
Reactions: moli

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
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.
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.
 

vertoe

Three of Nine
Mar 28, 2014
2,573
1,652
1,283
Unimatrix Zero One
My server stops working after pruning.

Code:
[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
Any idea why? txindex=1 is set. Reindexing again and see if it helps.