Search results

Propulsion: was running with E_ for the last 48h. Just downloaded your "official" version from Github, and I am now on D_WhynotMe in IRC #electrum-drk

Yes. UTXOs for Darkcoin, with block headers, up to block 220640, pruned at 10k, available here - 300 MB file.

The recipe above is for the client, not the server. For the server, my pull request to your Github account is still valid - and I am currently running a server based on that version, at drk1.electrum-servers.us - on the main net.

If anyone is more versed with Github commands, then, this is the recipe: 1. Fork Electrum upstream 2. Add Vertoe darkcoin_hash library from Github 3. In bitcoin.py, add: import darkcoin_hash as darkhash HashX11 = lambda x: darkhash.getPoWHash(x) 4. In blockchain.py, modify L183...

OK. Got things working again for the client... You are correct Vertoe - it was a mess! I apologize! This is what happened: I was testing the changes on a Linux machine, but my Mac was my production unit (with my tools, DiffMerge, TextWrangler, Github, etc) - so a lot of back and forth...

Why? There are only a few MB difference in size between the 100 and 10000 pruning. I am always running 10000 on my Electrum servers (BTC, LTC, ...) - 8 GB RAM AMD Quad core 4300 with Linux - not a high end computer... Regardless of pruning size, it still takes 8 hours to generate the UTXO -...

Sorry guys, 1. It was late last night, and I forgot to include run_electrum_drk_server.py in the pull request. 2. Make sure that you put capital letter "D" on "Darkcoin_main" in your config file for the network - last line of the file (Vertoe - your latest problem) - Propulsions had is...

Excellent! If you last more than a couple of weeks, we will add you to network.py file of the client

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

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...

No problem, I had to attend a dinner tonight ... yummy Lobster Mac&Cheese!

I will maintain a server at drk1.electrum-servers.us:50002 - hit me up! ... in case the IRC channel doesn't work - I am not too experienced with this.

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

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...

I was wrong. Thanks for bringing this interesting project to our attention.

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....

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 =...

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]...

sneak peak at https://github.com/ELM4Ever/electrum-drk-server

ok. Seems that we have the fire power. Let me work on a solution...