 Show Posts
|
|
Pages: « 1 2 3 4 [5] 6 »
|
It supports JSON RPC protocol, connect to boolberry.extremepool.org:1111 if you really need pool. I am trying to connect to extremepool but... seems I lack something simpleminer.exe --pool-addr=boolberry.extremepool.org:5555 --login BBR_Address --pass x --mining-threads 1
2014-Jul-21 12:27:49.606545 Connecting boolberry.extremepool.org:5555....
2014-Jul-21 12:27:49.824945 Connected boolberry.extremepool.org:5555 OK
2014-Jul-21 12:28:09.855380 Failed to invoke http request to /json_rpc
2014-Jul-21 12:28:09.855380 Failed to invoke login boolberry.extremepool.org:555
5, disconnect and sleep.... Also, any idea how to mine from different machine to same wallet? Will i need to have blockchain on that machine too :S |
|
|
|
I have a running wallet on a long fork but all recent transactions are marked with a question mark. Does it mean all these blocks were deleted from the database and we cannot get them back? No, I had another computer that was not fully synced yet when the reorganization happened and cut it off. And all block upto block 43685 was left was there.
|
|
|
|
How the data was lost? Had the wallet deleted recent blocks immediately as the fork occurred? The issue was not the block propagation at all (if that even is an issue). The issue was with the checkpoint node being off-line and hitching onto an incorrect fork, where then it forced all other nodes to go to that fork since it is the checkpoint node. That incorrect fork was not caused by block propagation delays either, it was caused by the creation of PoS blocks. Since it has been off-line, the staked coins on it accumulated coinage. When the node came back on-line, it created a few PoS blocks immediately, before it synced up, causing a fork. Since it was the checkpoint node, the network was forced to that chain.
Up to block 43685 was all I could salvage.
|
|
|
|
I synced from the 76.127.202.17 and now on 43710 block, getblockhash 35587 is correct. We was on 44449 block before the fork! You can see it on http://www.blockexperts.com/slm right now. Everything was fine till that height. Now last 15-20 hours are lost. I think it's not right. Don't you have data to restore? If you are back at block 35587 or so, there was a fork in the blockchain. The upcoming update will have the hard checkpoints for that fork.
You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"
To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155
|
|
|
|
Here is simple calculation what to expect with solo mining: Current difficulty from http://boolberry.com/state.html - 200GH It means you need 200*1024 seconds to find a block with 1Mhs mining power (280X). There are 86400 seconds in a day so expect to find a block on average every 200000/86000 = 2 days 8 hours. It will take 4 days 16 hours for a 500khs card (6870, 750Ti) and so on. Don't be afraid to mine few days without any result. I've implemented low difficulty shares (like you do with a pool) so you can check everything works as expected. If you get efficiency about 100% the calculation above is correct. Anyway you cannot get anything for sure with random process like mining. So don't blame me if you get nothing in a week.  |
|
|
|
Use command line parameter. Moreover read my previous message on multi GPU configurations. I'm so new with BBR and I try to SOLO with this Boolberry OpenCL miner. Does this seem to be OK with my 750Tis? It seems like only miner0 is working, other 5 cards are not. |
|
|
|
I used 14.4 and 14.6. there's error while mining, it says fatal error, and then the hashrate decrease,what's the version of you video card driver for test? i'm using 13.12 for AMD 280X
|
|
|
|
Set thread_delay in miner_conf.json to 2000 (2 seconds) or even more. It could help in multi GPU configurations. Moreover you can run 3 miners independently. Copy you data directory for each instance, set device_index in miner_conf.json in copied directories to 1 and 2 and run 3 instances boolbd --data-dir <datadir1> --start-mining=<address> --mining-threads=1
boolbd --data-dir <datadir2> --start-mining=<address> --mining-threads=1
boolbd --data-dir <datadir3> --start-mining=<address> --mining-threads=1
Moreover it makes sense to reboot before changing anything. Stupid question.
If I am running the qt wallet and solo mining. Does the blocks go to the qt wallet or doe I still need to run the simple wallet to get the blocks?
EDIT:
I have a 280x, 270x, and 270.
I put in the threads for 3 but only gpu 0 (280x) runs.
I get for the other 2 "cl invalid value, platform value must be between 0 & 4294967295"
I also get that on my 750ti's
|
|
|
|
It works on NVidia but AWS g2.2 gets only 365 khs on GPU + 200 khs on CPU . It's not enough even for spot Linux instances right now.
Is this officially mean AWS mining is profitable again?!!?
It's OpenCL. God only knows if it'll even work with Nvidia. Besides, AWS mining has always been profitable... you just need to know some stuff. |
|
|
|
Yes, I've done simpleminer version first just to find out all the pools to be unreliable for real mining so I've done boolbd version. Anyway simpleminer works just fine if you find fast and reliable JSON RPC pool.
Oh ok, so this is optimized for solo mining only at the moment then?
|
|
|
|
You should run boolbd.exe to solo mine. It's exactly the same as with original miner. My version just uses GPUs instead of CPU cores. boolbd --start-mining=<address> --mining-threads=1 (or 2,3 if you have many GPUs). It should synchronize the blockchain before mining starts so wait if you run boolbd.exe first time. If you loaded the blockchain with original boolbd this miner will use it. Look at the output for lines like: hr: 510698, efficiency: 185% (shares 2/2, blocks 0/0) Open source Boolberry OpenCL miner https://github.com/mbkuperman/boolberry-opencl.gitRead README.md for details and build instructions. Windows x64 executables: https://github.com/mbkuperman/boolberry-opencl/releases/download/v1.0/BoolberryOCL-20140719.zip2% developer donation (you can change or disable it in the configuration file) Solo version: boolbd.exe (best performance/reliability) Pool (JSON RPC) version: simpleminer.exe (please, use solo version if you can!) Personally, I think it doesn't make any sense to use pools while the block value is about $7. Just give enough time to the solo miner. Tested on AMD GPUs only! Expected performance: 6870, R270x - 500-600 khs 6970, R280X - 900-1000 khs OpenCL code is available under the terms of the GNU Public License version 3. Author: Mikhail Kuperman ( mbk.git@gmail.com) BBR donation address: 1EmWGnwhydr3S2vRWQbbefh1hgDKgMjdMGe43ZgdPhdARhNBRkUMuD4YzLA2nyYG8tg2HKCCBg4aDam JKypRQWW1Ca2kSV8 BTC donation address: 1Lns6UjL3sw77DJ5z1EKJZy6SnqriqvVGK Boolberry daemon OpenCL configuration
OpenCL miner supports ordinary mining parameters:
--start-mining=[address]
--mining-threads=[n], n - number of GPUs to use
Run the daemon once to create miner_conf.json in the data directory.
Keys to tune the miner: "platform_index" - use OpenCL platform (if you have manym, default 0)
"device_index" - use OpenCL devices from (if you have many, default from 0)
"difficulty" - virtual share difficulty for statistics
"donation_percent_opencl" - OpenCL developer donation, default value - 2%
"kernel" - OpenCL kernel file name
"kernel_type" - kernel type: 0 - all-in-one, 1 - multiple step version (wild_keccak-multi.cl)
"thread_delay" - delay in ms between thread startups
"work_size" - OpenCL work size (smaller values make the computer more responsive) So, it's "--start-mining" instead of "--pool-address" for the miner? If certain options like kernel_type, work_size, etc aren't put it, will it go to a default setting? So, there's no stratum for it yet? I'm mining with it, but what shows the stats of the hashrate? |
|
|
|
You should run boolbd.exe to solo mine. It's exactly the same as with original miner. My versions just uses GPUs instead of CPU cores. boolbd --start-mining=<address> --mining-threads=1 (or 2,3 if you have many GPUs). It should synchronize the blockchain before mining starts so wait if you run boolbd.exe first time. If you loaded the blockchain with original boolbd this miner will use it. I'm not sure how you solo mine BBR with GPU as every error message when starting simpleminer.exe is "Failed to parse arguements: the option --login is required but missing." Why is this a necessity, and what does the login pertain to?
|
|
|
|
Yes. what does that mean "expected performance" ? Is this numbers you obtained with your cards ? |
|
|
|
OK. I've just commented the line that caused the exception and updated the release. Now it exits fine. Sure, i'm looking at sources... btw: you also could check executables on https://www.virustotal.com/ to be sure if there are no malware. Today I merged last commits (about a week) from your master branch and now my boolbd.exe gives an exception upon exit (last log record - [SRV_MAIN]Node stopped). It was OK before that. Do you have a clue what commit could cause it? Have no idea..., hard to say without additional info, can you point the place where does it crushes ? Just run it under gdb or visual studio to catch... Also, sometime clean/full rebuild helps. |
|
|
|
Sure, i'm looking at sources... btw: you also could check executables on https://www.virustotal.com/ to be sure if there are no malware. Today I merged last commits (about a week) from your master branch and now my boolbd.exe gives an exception upon exit (last log record - [SRV_MAIN]Node stopped). It was OK before that. Do you have a clue what commit could cause it? |
|
|
|
Open source Boolberry OpenCL miner https://github.com/mbkuperman/boolberry-opencl.gitRead README.md for details and build instructions. Windows x64 executables: https://github.com/mbkuperman/boolberry-opencl/releases/download/v1.0/BoolberryOCL-20140719.zip2% developer donation (you can change or disable it in the configuration file) Solo version: boolbd.exe (best performance/reliability) Pool (JSON RPC) version: simpleminer.exe (please, use solo version if you can!) Personally, I think it doesn't make any sense to use pools while the block value is about $7. Just give enough time to the solo miner. Tested on AMD GPUs only! Expected performance: 6870, R270x - 500-600 khs 6970, R280X - 900-1000 khs OpenCL code is available under the terms of the GNU Public License version 3. Author: Mikhail Kuperman ( mbk.git@gmail.com) BBR donation address: 1EmWGnwhydr3S2vRWQbbefh1hgDKgMjdMGe43ZgdPhdARhNBRkUMuD4YzLA2nyYG8tg2HKCCBg4aDam JKypRQWW1Ca2kSV8 BTC donation address: 1Lns6UjL3sw77DJ5z1EKJZy6SnqriqvVGK |
|
|
|
Open source Boolberry OpenCL minerhttps://github.com/mbkuperman/boolberry-opencl.gitRead README.md for details and build instructions. Windows x64 executables: https://github.com/mbkuperman/boolberry-opencl/releases/download/v1.0/BoolberryOCL-20140719.zip2% developer donation (you can change or disable it in the configuration file) Solo version: boolbd.exe (best performance/reliability) Pool (JSON RPC) version: simpleminer.exe (please, use solo version if you can!) Personally, I think it doesn't make any sense to use pools while the block value is about $7. Just give enough time to the solo miner. Tested on AMD GPUs only! Expected performance: 6870, R270x - 500-600 khs 6970, R280X - 900-1000 khs OpenCL code is available under the terms of the GNU Public License version 3. Author: Mikhail Kuperman ( mbk.git@gmail.com) BBR donation address: 1EmWGnwhydr3S2vRWQbbefh1hgDKgMjdMGe43ZgdPhdARhNBRkUMuD4YzLA2nyYG8tg2HKCCBg4aDam JKypRQWW1Ca2kSV8 BTC donation address: 1Lns6UjL3sw77DJ5z1EKJZy6SnqriqvVGK
|
|
|
|
|
DEV, you should check the POS algorithm - it overloads the CPU as primer said before (I was forced to transfer all coins to other wallet to fix it) and distorts a sensible POW/POB algorithm. At the same time it's half cents per block doesn't make any sense for miners - I just closed the wallet with all my coins.
|
|
|
|
DEV, please, look at POB blocks algorithm. Something's definitely wrong. I could post some numbers later if you need. Looks like SlimCoinAfterBurner() is called a lot rarely lately. Just 30 calls out of 200 blocks. About 6 calls an hour. It's a lot less it was before. POS blocks could distort it somehow. It was different before them. Everything else looks fine.
Out of those 200 blocks, how many were PoW. The SlimCoinAfterBurner() is only called every time a new PoW block is found, thus PoB blocks can only be found after PoW blocks, not PoS blocks. I guess it's the number of POW blocks - 30 out of 200. Could POS blocks distort the algorithm? They pop up very often. A lot more often then POB blocks for similar share of coins. At the same time POW difficulty is pretty high for a coin without exchange. Could the algorithm try to adjust difficulty for POW+POS blocks together? |
|
|
|
|
DEV, please, look at POB blocks algorithm. Something's definitely wrong. I could post some numbers later if you need. Looks like SlimCoinAfterBurner() is called a lot rarely lately. Just 30 calls out of 200 blocks. About 6 calls an hour. It's a lot less it was before. POS blocks could distort it somehow. It was different before them. Everything else looks fine.
|
|
|
|
|
