Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net - page 105. (Read 409641 times)
May 11, 2014, 11:39:44 PM
BlakeBitcoin due for release and merge mine very soon
May 11, 2014, 11:29:19 PM
Nice tease what do we call the coin between PHO an DIRAC? Ƀ the symbol formerly rejected as BTC BlicCoin?
AT and Dirac I can at least type without google search to find it
May 11, 2014, 07:35:41 PM
Updating NY2 merge server expect some down time EU3 will follow once NY2 is working on new code 
Edit:
NY2 is done its only merging BLC+PHO atm other wallets need adding
EU3 is done same as NY2 any problems let me know
Note:
for anyone running a private/solo eloipool can you please enable
# Aim to produce blocks with transaction counts that are a power of two
# This helps avoid any chance of someone abusing CVE-2012-2459 with them
# 1 = cut out feeless transactions; 2 = cut out even fee-included transactions (if possible)
POT = 2
and the Blakecoin network is as follows did not notice earlier
# Network ID for the primary blockchain
UpstreamNetworkId = b'\xF9\xBE\xB4\xD2'
Edit:
NY2 is done its only merging BLC+PHO atm other wallets need adding
EU3 is done same as NY2 any problems let me know
Note:
for anyone running a private/solo eloipool can you please enable
# Aim to produce blocks with transaction counts that are a power of two
# This helps avoid any chance of someone abusing CVE-2012-2459 with them
# 1 = cut out feeless transactions; 2 = cut out even fee-included transactions (if possible)
POT = 2
and the Blakecoin network is as follows did not notice earlier
# Network ID for the primary blockchain
UpstreamNetworkId = b'\xF9\xBE\xB4\xD2'
May 11, 2014, 10:24:23 AM
Ignatius, that looks like some very good info, thanks for sharing it. I'll definitely refer to that in the guide update.
May 11, 2014, 12:03:22 AM
Ignatius looks like a fabulous resource , well done !! I may try it out this week, at the momemt I am 'sloshing it up' in the New York merged pool !!
May 10, 2014, 11:03:59 PM
That good to know may try it out just to see it work
May 10, 2014, 09:58:51 PM
That is one drawback to merged mining. Solo or reg pool you get BLC but merged you get BLC, PHO and soon more.
So fewer solo miners as everyone moves to pool. But at least with 2 merged pools it's not all in one pool.
So fewer solo miners as everyone moves to pool. But at least with 2 merged pools it's not all in one pool.
You can solo merge mine. I believe bzyzny is writing up some mining related info, if he doesn't include the merged setup info I will pass it along for inclusion.
EDIT: Or give the info here, now:
blakecoind setup
1) Obtain a compiled blakecoind.
2) Decide on a data directory location.
3) In this directory, create blakecoin.conf text file, with the following contents:
Code:
rpcuser=MY_RPC_USERNAME
rpcpassword=MY_RPC_PASSWORD
rpcport=8772
logtimestamps=1
listen=1
gen=0
rpcallowip=127.0.0.1
server=1
daemon=1
addnode=162.243.133.80
addnode=162.243.14.130
addnode=146.185.135.24
addnode=184.171.247.23
rpcpassword=MY_RPC_PASSWORD
rpcport=8772
logtimestamps=1
listen=1
gen=0
rpcallowip=127.0.0.1
server=1
daemon=1
addnode=162.243.133.80
addnode=162.243.14.130
addnode=146.185.135.24
addnode=184.171.247.23
Obviously, change the MY_RPC_xxx to a username and password.
4) Create a newblock.sh script, with the following contents:
Code:
#!/bin/sh
killall -USR1 eloipool.py
killall -USR1 eloipool.py
Mark it executeable via "chmod 0755 newblock.sh"
5) Create a run-blakecoind.sh script, with the following contents:
Code:
#!/bin/sh
/pah/to/blakecoind \
-datadir=/path/to/data -daemon \
-blocknotify=/path/to/newblock.sh
/pah/to/blakecoind \
-datadir=/path/to/data -daemon \
-blocknotify=/path/to/newblock.sh
Mark it executeable via "chmod 0755 run-blakecoind.sh"
You must modify the (a) blakecoind path, (b) -datadir path, and (c) -blocknotify path to fit your local computer.
6) Run blakecoind via the run-blakecoind.sh script. Watch debug.log in the data directory, to make sure it started the Initial Block Download (blakecoin network sync). This might take a few minutes, to download all the blocks.
eloipool setup
1) Download eloipool dependencies, either from your Linux packager, or directly:
Python 3 http://python.org
python-bitcoinrpc https://github.com/jgarzik/python-bitcoinrpc
python-base58 https://gitorious.org/bitcoin/python-base58
midstate http://gitorious.org/midstate/midstate
2) For python-bitcoinrpc, check out an older release,
Code:
$ cd /repo/python-bitcoinrpc
$ git checkout -b solo-mining 770881c8bd9b1f92427290270b37a28751cf9df0
$ git checkout -b solo-mining 770881c8bd9b1f92427290270b37a28751cf9df0
3) Check out eloipool,
Code:
$ git clone git://github.com/BlueDragon747/eloipool_Blakecoin.git
4) Copy config.py.example to config.py, and make the following several edits,
a) change ServerName to something unique
b) increase share target if desired (note increase '0' and decrease 'f'):
Code:
-ShareTarget = 0x00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
+ShareTarget = 0x00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
+ShareTarget = 0x00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
c) DynamicTargetting = 2
d) DynamicTargetGoal = 6
e) change TrackerAddr to YOUR blakecoin address
f) comment out CoinbaserCmd,
Code:
-CoinbaserCmd = 'echo -e "1\\n$((%d / 100))\\n1579aXhdwvKZEMrAKoCZhzGuqMa8EonuXU"'
+#CoinbaserCmd = 'echo -e "1\\n$((%d / 100))\\n1579aXhdwvKZEMrAKoCZhzGuqMa8EonuXU"'
+#CoinbaserCmd = 'echo -e "1\\n$((%d / 100))\\n1579aXhdwvKZEMrAKoCZhzGuqMa8EonuXU"'
g) update TemplateSources to point to your local blakecoind RPC, including chosen username/password, and comment out the secondary source:
Code:
@@ -57,41 +57,41 @@
TemplateSources = (
{
'name': 'primary',
- 'uri': 'http://user:pass@localhost:8332',
+ 'uri': 'http://MY_RPC_USERNAME:[email protected]:8772',
'priority': 0,
'weight': 1,
},
- {
- 'name': 'secondary',
- 'uri': 'http://user:pass@localhost:18332',
- 'priority': 1,
- 'weight': 1,
- },
+# {
+# 'name': 'secondary',
+# 'uri': 'http://user:pass@localhost:18332',
+# 'priority': 1,
+# 'weight': 1,
+# },
)
TemplateSources = (
{
'name': 'primary',
- 'uri': 'http://user:pass@localhost:8332',
+ 'uri': 'http://MY_RPC_USERNAME:[email protected]:8772',
'priority': 0,
'weight': 1,
},
- {
- 'name': 'secondary',
- 'uri': 'http://user:pass@localhost:18332',
- 'priority': 1,
- 'weight': 1,
- },
+# {
+# 'name': 'secondary',
+# 'uri': 'http://user:pass@localhost:18332',
+# 'priority': 1,
+# 'weight': 1,
+# },
)
g) empty TemplateChecks (or comment out 100%),
Code:
TemplateChecks = (
)
)
h) comment out or delete BlockSubmissions
i) change log settings, and switch from testnet3 mining to mainnet:
Code:
-DelayLogForUpstream = False
+DelayLogForUpstream = True
# Bitcoin p2p server for announcing blocks found
-UpstreamBitcoindNode = ('127.0.0.1', 18333) # testnet
+UpstreamBitcoindNode = ('127.0.0.1', 8772)
# Network ID for the primary blockchain
# Other known network IDs can be found at:
# https://en.bitcoin.it/wiki/Protocol_specification#Message_structure
-UpstreamNetworkId = b'\xFA\xBF\xB5\xDA' # testnet
+UpstreamNetworkId = b'\xF9\xBE\xB4\xD2'
+DelayLogForUpstream = True
# Bitcoin p2p server for announcing blocks found
-UpstreamBitcoindNode = ('127.0.0.1', 18333) # testnet
+UpstreamBitcoindNode = ('127.0.0.1', 8772)
# Network ID for the primary blockchain
# Other known network IDs can be found at:
# https://en.bitcoin.it/wiki/Protocol_specification#Message_structure
-UpstreamNetworkId = b'\xFA\xBF\xB5\xDA' # testnet
+UpstreamNetworkId = b'\xF9\xBE\xB4\xD2'
j) update ShareLogging to reflect your desires. The simplest is to delete all the SQL-related entries, leaving only the textfile logfile. With solo mining, you don't care so much about shares. Optionally enable logging to a database here for use via an MPOS gui later.
Code:
ShareLogging = (
{
'type': 'logfile',
'filename': 'share-logfile',
'format': "{time} {Q(remoteHost)} {username} {YN(not(rejectReason))} {dash(YN(upstreamResult))} {dash(rejectReason)} {solution}\n",
},
)
{
'type': 'logfile',
'filename': 'share-logfile',
'format': "{time} {Q(remoteHost)} {username} {YN(not(rejectReason))} {dash(YN(upstreamResult))} {dash(rejectReason)} {solution}\n",
},
)
k) change log filename to something useful,
Code:
LogFile = {
- 'filename': 'filename.log',
+ 'filename': 'eloipool.log',
- 'filename': 'filename.log',
+ 'filename': 'eloipool.log',
l) Create a runit.sh script for eloipool, with the contents,
Code:
#!/bin/sh
PYTHONPATH=/path/to/python-bitcoinrpc:/path/to/python-base58:/path/to/midstate \
nohup ./eloipool.py 2>&1 >/dev/null &
PYTHONPATH=/path/to/python-bitcoinrpc:/path/to/python-base58:/path/to/midstate \
nohup ./eloipool.py 2>&1 >/dev/null &
You must change the paths to suit your local system.
m) Run eloipool with runit.sh script
n) Let's assume you are running the pool software on 192.168.1.40 IP address. Set up your miner configuration like this:
Pool X: stratum+tcp://192.168.1.40:3334
Pool X username: anyuser
Pool X password: x
The above gets you a private Blakecoin mining pool.
Credits:
BlueDragon747
kr105
lukejr
Jeff Garzik Donations / BTC tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
https://bitcointalksearch.org/topic/avalon-users-bitcoind-eloipool-configuration-158105
The pool we created above only mines Blakecoins, to merged mine BLC and PHO:
Acquire a compiled photond, create a data dir and photon.conf in the same way you did for blakecoind.
Acquire merge-mine-proxy: https://gitorious.org/bitcoin/luke-jr-bitcoin/source/8f3f29550c2ad33f5635799ba835276eaebb4a2e:contrib/merged-mine-proxy
eloipool config.py
Code:
# Secret username allowed to use setworkaux
SecretUser = "ssecreteloipool"
GotWorkURI = "http://mergedproxyuser:[email protected]:8330/"
GotWorkTarget = 0x00000000000fffffffffffffffffffffffffffffffffffffffffffffffffffff #1024
SecretUser = "ssecreteloipool"
GotWorkURI = "http://mergedproxyuser:[email protected]:8330/"
GotWorkTarget = 0x00000000000fffffffffffffffffffffffffffffffffffffffffffffffffffff #1024
photond config
Code:
rpcuser=photonrpc
rpcpassword=photonrpcpass
rpcport=9377
listen=1
gen=0
rpcallowip=127.0.0.1
port=35556
server=1
daemon=1
listen=1
addnode=162.243.101.139
addnode=72.23.74.166
addnode=62.219.234.143
addnode=78.26.209.208
addnode=162.243.101.139
addnode=77.121.61.203
addnode=107.170.123.55
addnode=218.146.3.80:3005
addnode=107.170.78.146
rpcpassword=photonrpcpass
rpcport=9377
listen=1
gen=0
rpcallowip=127.0.0.1
port=35556
server=1
daemon=1
listen=1
addnode=162.243.101.139
addnode=72.23.74.166
addnode=62.219.234.143
addnode=78.26.209.208
addnode=162.243.101.139
addnode=77.121.61.203
addnode=107.170.123.55
addnode=218.146.3.80:3005
addnode=107.170.78.146
mining proxy command
Code:
python merged-mining-proxy -w 8330 -p http://ssecreteloipool:[email protected]:8337/ -x http://photonrpc:photonrpcpass@localhost:9377/
Credits:
BlueDragon747
lukejr
tomaszsz
https://bitcointalksearch.org/topic/m.2070460
Troubleshooting and optional info by BlueDragon747:
Quote from: BlueDragon747
start blakecoin with block notify
start photon
wait for them to be in sync!
start eloi
within 3 secs start mmp
check log, wait for a share if you get a solve its working ignore errors
if you just get update aux and no solve for ages and you have decent amount of hashing or lowish gotworktarget repeat above
if you get stale merkle its fine should get a solve shortly
if you get bad merkle them it seems mmp is not connecting to eloi
In mmp I did tweak the -R rewrite to match the gotworktarget and it does run better than just leaving it out (edit at line 253 and 462 to match your gotworktarget) then just add the -R switch to you command e.g:
python merged-mine-proxy -w 8330 -p http://secretuser:[email protected]:8337/ -x http://photonrpcuser:rpcpass@localhost:9377/ -l mmp_log.txt -R >/dev/null
start photon
wait for them to be in sync!
start eloi
within 3 secs start mmp
check log, wait for a share if you get a solve its working ignore errors
if you just get update aux and no solve for ages and you have decent amount of hashing or lowish gotworktarget repeat above
if you get stale merkle its fine should get a solve shortly
if you get bad merkle them it seems mmp is not connecting to eloi
In mmp I did tweak the -R rewrite to match the gotworktarget and it does run better than just leaving it out (edit at line 253 and 462 to match your gotworktarget) then just add the -R switch to you command e.g:
python merged-mine-proxy -w 8330 -p http://secretuser:[email protected]:8337/ -x http://photonrpcuser:rpcpass@localhost:9377/ -l mmp_log.txt -R >/dev/null
You *might* be able to merge mine without eloipool, using only the blake and photon coin daemons coupled with merge-mine-proxy, but I have not tried.
EDIT/UPDATE 5-15-2014:
Moar coinz!
The launch of B+ and impending launches of Dirac and AT brings the need for config changes.
Acquire a compiled B+, create a data dir and blakebitcoin.conf in the same way you did for the other coins.
Use this copy of merge-mine-proxy: https://github.com/BlueDragon747/eloipool_Blakecoin/blob/master/merged-mine-proxy.py
blakebitcoind config
Code:
rpcuser=blakebitrpcuser
rpcpassword=blakebitrpcpass
server=1
listen=1
maxconnections=180
rpctimeout=30
rpcallowip=127.0.0.1
addnode=146.185.135.24
addnode=162.243.14.130
addnode=188.226.213.85
addnode=107.170.140.27
rpcpassword=blakebitrpcpass
server=1
listen=1
maxconnections=180
rpctimeout=30
rpcallowip=127.0.0.1
addnode=146.185.135.24
addnode=162.243.14.130
addnode=188.226.213.85
addnode=107.170.140.27
mining proxy command
Code:
python merged-mining-proxy -s 4 -w 8330 -p http://ssecreteloipool:[email protected]:8337/ -x http://photonrpc:photonrpcpass@localhost:9377/ -x http://blakebitrpcuser:blakebtrpcpass@localhost:blakebitport/
You can continue to add coins now by setting up the coin daemon, adding another -x http://user:pass@host:port/ line to the launch arguments for merge-mine-proxy, and incrementing the -s value. -s ==
May 10, 2014, 09:20:50 PM
That is one drawback to merged mining. Solo or reg pool you get BLC but merged you get BLC, PHO and soon more.
So fewer solo miners as everyone moves to pool. But at least with 2 merged pools it's not all in one pool.
So fewer solo miners as everyone moves to pool. But at least with 2 merged pools it's not all in one pool.
May 10, 2014, 09:14:09 PM
Indeed many people with a lot of hash power see the future of the Blake Coin blockchain !
There are a lot of solo miners, multiple private pools, some are far into the double digit GHs range. Unsure of exact private GHs, but your #'s look close.
or is someone solo mining with around 80x7950 worth of mining power?
There are a lot of solo miners, multiple private pools, some are far into the double digit GHs range. Unsure of exact private GHs, but your #'s look close.
May 10, 2014, 06:47:39 PM
or is someone solo mining with around 80x7950 worth of mining power?
There are a lot of solo miners, multiple private pools, some are far into the double digit GHs range. Unsure of exact private GHs, but your #'s look close.
May 10, 2014, 05:43:14 PM
name GH/s
eu1 12
eu2 0
eu3 255
ny1 57
ny2 42
suprno 2
==========
sum 366
vs.
net hashrate 550
difference: ~180GH/s
Did I forget to include a pool? Is there an error in calculations or is someone solo mining with around 80x7950 worth of mining power?
eu1 12
eu2 0
eu3 255
ny1 57
ny2 42
suprno 2
==========
sum 366
vs.
net hashrate 550
difference: ~180GH/s
Did I forget to include a pool? Is there an error in calculations or is someone solo mining with around 80x7950 worth of mining power?
May 10, 2014, 02:49:57 AM
Someone is was trying to DDoS eu3 atm
Edit:
ok banned ip block should be ok again
Edit:
ok banned ip block should be ok again
May 09, 2014, 03:27:57 PM
I think hes talking about that cs server, not the miner ;p
May 09, 2014, 02:22:30 PM
Quote
Please help ... When you connect to the server issues
Connecting to 207.210.117.83:27015 ...
STEAM validation reject
How to deal with it?
When you connect to the pool with cgminer? Which port are you using? Connecting to 207.210.117.83:27015 ...
STEAM validation reject
How to deal with it?
May 09, 2014, 12:32:45 PM
Please help ... When you connect to the server issues
Connecting to 207.210.117.83:27015 ...
STEAM validation reject
How to deal with it?
Connecting to 207.210.117.83:27015 ...
STEAM validation reject
How to deal with it?
May 08, 2014, 06:10:54 AM
oinquer, wish i could help you but i dont use windows much. however, from what i understand, cgminer 3.1.1 is considered very stable and there isnt much reason to use 3.7. if i remember right, most of the changes between those versions were for sha256d asic miners. if you really want cgminer 3.7 on windows, perhaps someone can help you with that; or you could try compiling it yourself and share it with the community also, i know someone is working on porting GUIminer to blakecoin for windows, although im not sure which version of cgminer they are using under the hood. i know perhaps thats not the answer you were looking for but hopefully it was still helpful
also, i know someone is working on porting GUIminer to blakecoin for windows, although im not sure which version of cgminer they are using under the hood. i know perhaps thats not the answer you were looking for but hopefully it was still helpful Ok, thanks i like the 3.7.2 kalroth i used for scrypt because the GUI was a little changed being easier to identify stuff.
May 08, 2014, 12:17:53 AM
I will be closing EU2 pool within a couple of days and have enabled manual payouts please withdraw your coins thanks
May 07, 2014, 07:12:32 PM
May 07, 2014, 05:56:13 PM
like it
May 07, 2014, 05:55:24 PM
hmm checking the coin and there's cgminer 3.1.1 and 3.7 but no windows compile for 3.7? anyone already did it?
if yes please give a link.
thanks.
if yes please give a link.
thanks.
cgminer 3.1.1 was most stable but it still has a lot of unused junk code in there that could be removed e.g sha-256d asic stuff, 3.7 has even more unused junk in the code and just was not as stable 24/7
so basically nothing new was added to cgminer 3.7 that benefits the Blake-256 algo, I know someone is working on a striped down version of cgminer for Blake-256 without so much junk code but its still based on the stable 3.1.1 code base
I did have a 3.7 version about compiled if I find it will post but it was some time ago now
Jump to: