• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Electrum Dark

More info...

12/02/2015-23:48:16] Starting Electrum-DRK server on localhost
[12/02/2015-23:48:17] Database version 3
[12/02/2015-23:48:17] Blockchain height 219339
[12/02/2015-23:48:17] UTXO tree root hash: 4a025e3b761de3dca93800da53b6f2de1ba8d07cd552b1c550a8b4a31885b7a4
[12/02/2015-23:48:17] Coins in database: 512147687739509
[12/02/2015-23:48:17] TCP server started on 127.0.0.1:50001
[12/02/2015-23:48:17] SSL server started on 127.0.0.1:50002
[12/02/2015-23:48:17] HTTP server started.
[12/02/2015-23:48:17] HTTPS server started.
[12/02/2015-23:48:17] Blockchain is up to date.
[12/02/2015-23:48:17] Memory pool initialized.
[12/02/2015-23:48:17] blockchain: 219339 (0.005s)
[12/02/2015-23:48:17] darkcoind is responding

https://chainz.cryptoid.info/drk/bl...079cad3b8893544959d62e68385120a6b54f378bf.htm

Above: 5121476.87739509
Chainz: 5121479.27859667
 
More info...

12/02/2015-23:48:16] Starting Electrum-DRK server on localhost
[12/02/2015-23:48:17] Database version 3
[12/02/2015-23:48:17] Blockchain height 219339
[12/02/2015-23:48:17] UTXO tree root hash: 4a025e3b761de3dca93800da53b6f2de1ba8d07cd552b1c550a8b4a31885b7a4
[12/02/2015-23:48:17] Coins in database: 512147687739509
[12/02/2015-23:48:17] TCP server started on 127.0.0.1:50001
[12/02/2015-23:48:17] SSL server started on 127.0.0.1:50002
[12/02/2015-23:48:17] HTTP server started.
[12/02/2015-23:48:17] HTTPS server started.
[12/02/2015-23:48:17] Blockchain is up to date.
[12/02/2015-23:48:17] Memory pool initialized.
[12/02/2015-23:48:17] blockchain: 219339 (0.005s)
[12/02/2015-23:48:17] darkcoind is responding

https://chainz.cryptoid.info/drk/bl...079cad3b8893544959d62e68385120a6b54f378bf.htm

Above: 5121476.87739509
Chainz: 5121479.27859667
Nice, will set up one for testnet and one for mainnet then.
 
Nice, will set up one for testnet and one for mainnet then.

If you want to run a Server, please ensure that you have the following config in your /etc/electrum-drk.conf folder:

[server]
# username for running the daemon
username = electrum-drk
password = someweirdpassword
#hostname. set it to a FQDN in order to be reached from outside
#report_host = xxx.xxxx.org
host = localhost
# ports
electrum_rpc_port = 8000
stratum_http_port = 8081
stratum_http_ssl_port = 8082
stratum_tcp_port = 50001
stratum_tcp_ssl_port = 50002
#report_host =
#report_stratum_tcp_port = 50001
#report_stratum_tcp_ssl_port = 50002
banner = Welcome to Electrum!
banner_file = /etc/electrum-drk.banner
irc = no
irc_nick = mynickname
ssl_certfile = /home/mypc/electrum/UTXO/server.crt
ssl_keyfile = /home/mypc/electrum/UTXO/server.key
logfile = /home/mypc/electrum/electrum-drk.log
#donation_address =

[leveldb]
# path to your database
path = /home/mypc/electrum/UTXO/DRK/electrum-drk-leveldb-utxo-10000
# for each address, history will be pruned if it is longer than this limit
pruning_limit = 10000

[bitcoind]
bitcoind_host = localhost
bitcoind_port = 9998
# user and password from darkcoin.conf
bitcoind_user =
bitcoind_password =

[network]
type = darkcoin_main
 
lets start focussing on testnet. will setup one too.
The server is good, but you still need the client....

... and we have to sort the IRC issue. I initially used #electrum-drk as the logging, with ED_XXX as username - but that is to be agreed with you guys. In the mean time, I set the config to NO IRC....
 
Last edited by a moderator:

Yeah that should be no prob. I can contribute at least one of such machines.

Me too, at least two heavy duty machines available. eduffield will bring in another machine for sure which i can manage.



This is me, also owning the domain electrum-drk.org
I get the feeling that this project is closer to completion than we think!

Godspeed guys, excellent job!

Be sure to ping me when you're done and it will be all over Twitter...
 
The server is working. The client is receiving and sending coins. But block_headers are not being validated by the client. We "just" have to integrate BTC, KGW, and DGW for headers validation... anyone has a shortcut to offer?

EDIT: Just saw darkcoin_subsidy on Github, from Vertoe - I will give it a try.
EDIT2: Not what I need. We could disable validating the target, the daemon at the server is already doing it... Only the block hash would be verified on the server and client side.

EDIT3: That worked! Yes! Darkcoin has a ported Electrum wallet. However, at one point in time, to increase security, it will require the addition of the target validation code.

Let's talk Bounty now! Any offers ? :)
 
Last edited by a moderator:
All ready for Propulsions to commit - both on Client and Server side - Enjoy!

The config file has a default of NO for IRC, but try it.

Let me know of any issues. On the list of servers, I should expect to see:
TaoOfSatoshi
vertoe
flare

my DRK address: Xo3JkmyJc5oUjJREGytfgM4TRnzFuaUozD
 
Uh, you beat me by 15 seconds. Good work. I will review it these days and send you huge chunks of darkcoin, we've been waiting so long for this feature, thanks! Propulsion are you around ?
 
yes there are python bindings for darkcoin subsidy and x11 available.

https://github.com/vertoe/darkcoin_hash
https://github.com/vertoe/darkcoin_subsidy

lets not talk about bounties, lets talk about donations. just add a donation address and people will gladly donate you coins. but please publish source code first, else this feels like a ransom ;-)
I used Hash - thanks a lot! But we don't need subsidy.

Darkcoin went with BTC difficulty up to block 15200, then to Kimono Gravity Well for a while, up to block 34140, then to Dark Gravity Well. That is what we need to put some suspenders over the belt....

At the moment, the proposed implementation of Electrum-DRK assumes that the darkcoind running on the Electrum-DRK-server site is checking the target and bits. Therefore, no need to check it also at the client side. But to be safe, we should check it at each end. The current implementation does check the block header hash, and the previous block hash. It is good, but would be better to check also with some additional internal info.
 
Last edited by a moderator:
I used Hash - thanks a lot! But we don't need subsidy.

Darkcoin went from BTC difficulty up to block 15200, then to Kimono Gravity Well for a while, up to block 34140, then to Dark Gravity Well. That is what we need to put the suspenders over the belt....

At the moment, the proposed implementation of Electrum-DRK assumes that the darkcoind running on the Electrum-DRK-server site is checking the target and bits. Therefore, no need to check it also at the client side. But to be safe, we should check it at each end. The current implementation does check the block header hash, and the previous block hash. It is good, but would be better to check also for some internal info.
the darkcoin subsidy is an exact copy of darkcoind's main.cpp subsidy function, just with a python wrapper, so should be not that hard to integrate.
 
the darkcoin subsidy is an exact copy of darkcoind's main.cpp subsidy function, just with a python wrapper, so should be not that hard to integrate.

The Electrum code doesn't need the subsidy - it doesn't check it. It does check for target.
 
Back
Top