have downloaded like 30 min ago and still results in same problem. and have it set as your url to download from re downloaded just now and still making no difference.
So does the -P option spit out anything useful? |
|
|
|
|
FYI, about the scratchpad being too old, you can run your miner with -P to see the scratchpad being too old messages!
|
|
|
|
The scratchpad has always been a painful piece of work, I don't know how many times I've had to re download it. It just keeps getting bigger n' bigger, there have been times I've had to stop mining because of download restrictions of my ISP. If 1blockologist is going to take over development,it would be a good place to start and sort this out. It is so painful to have to re download scratchpad after a reboot because you've had to do some update that requires a reboot, or suffered from a power failure. Cheers Jon  I wish the scratchpad can be generated in gpu memory like that genoil ethminer or claymore ethminer. is it possible dev mbk ? No, it's created as part of the result of finding a block, and isn't just appended, but parts get changed every block. It would take a fundamental change to the way the hashing works to do that. |
|
|
|
is it currently under DDOS ? Why does BBR mining come under DDOS? Its not even that valuable at the moment. Why is someone even doing this? It is probably mined by small group with FPGAs, and they are responsible for DDoS attacks. As someone said earlier this is private coin... can't we make it more expensive for them to do this, more machines to DDOS? The network has rate has more than doubled since my announcement and subsequent price increase, so keep up the public fight Are there code upgrades that could/will make setting up and maintaining mining pools easier? clintar2 mentioned there seems to be memory leak in the miner, I wonder if other communities encountered this, or if it could be a unique problem with the wild keccak algorithm I did? I don't remember saying that. Maybe you are referring to my old post about the experimental keepalive version of my miner that was having issues? that's fixed up in the repos now. |
|
|
|
Thanks, it's working now  There was only a small complaint about missing bignum.node upon startup, but that was an easy thing to fix with "npm install bignum". Hello, i had same problem at first it needed async, then bignum, I sort this out, but now I'm not able to install multihashing at all. I tried nodejs v0.1, 4, 6, 7, different versions of npm, but any of those won't work. Can you help me with that? cheers nodejs 7 already out? man people weren't exaggerating about the 6 months life cycle of javascript frameworks I found some pre-release somewhere it probably failed with some message about a library missing. probably have to install boost libs. i think the package was libboost1.55-all-dev |
|
|
|
I'm getting this message in my private pool : 2016-09-13 12:29:54 Error with transfer RPC request to wallet daemon {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}
2016-09-13 12:29:54 Payments failed to send to [{"amount":10100000000000,"address":"1BHN*******************************m"},{"amount":97000000000000,"address":"1Eyo******************************B"},{"amount":100000000000,"address":"1AxQ******************************k"}] with paymentid:
2016-09-13 12:29:54 Error with transfer RPC request to wallet daemon {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}
2016-09-13 12:29:54 Could not retrieve wallet balance i cant make automatic payments to workers  my daemon and simplewallet starts with: ./boolbd --rpc-bind-ip my_ip_address --rpc-bind-port 10102 ./simplewallet --wallet-file x --password "password" --daemon-address my_ip_address:10102 --rpc-bind-port 10103 anyone can help me? Try to add |
|
|
|
EVERY POOL IS DOWN!!!
Yeah, sorry. DDOS. Provider null routed me because of it. |
|
|
|
Is it still possible to realistic solo mine or is the difficulty too high? If it is worth it to solo mine how do you do it? Through the gui wallet or through a separate app? Would love some help on trying to get started
Solo mine is fine. Just need the daemon with opencl https://github.com/mbkuperman/boolberry-opencl Or you could try setting up my pool code locally. If anyone is going to connect to my pool, I suggest the keepalive version of the miners. It just has a heartbeat so miner doesn't timeout between share submissions and have to reconnect. git clone -b keepalive https://github.com/clintar/cpuminer-multi-opencl.gi for amd or git clone -b keepalive https://github.com/clintar/bbr-cudaminer.git and if you are fancy and have IPV6, you can try connecting like so ./minerd -o stratum+tcp://[2600:3c03::f03c:91ff:febb:7e66]:5555 -u @clintar -p x -k http://[2600:3c03::f03c:91ff:febb:7e66]/scratchpad.bin I don't know why, but just because you can. |
|
|
|
Ok, got a pool going. http://50.116.52.225 no domain registered even, and haven't even hit a block yet with my hashrate. Throw a miner on it if you like! |
|
|
|
anybody got it working with Cuda in Windows?
I don't think it can compile in windows. Did you try to use the opencl version? |
|
|
|
Should I put a pool up again?
Please do  Today I got desperate enough to try and set up a local pool, but it's not working out. There's always a problem installing the multi-hashing module, which seems to be a common issue. My patience is running out with these new fangled modular systems -- I miss the days when I was developing miners from scratch As BBR is gaining new traction, one can hope that more pools will spring up. It would signify a healthy ecosystem -- the current situation is looking too fragile for a long term investment. Please use my pool code. Modules are updated to use newer versions of node. https://github.com/clintar/cryptonote-universal-pool.git |
|
|
|
|
Should I put a pool up again?
|
|
|
|
are there any more Cryptonote coins apoart from XMR and BBR  BCN (Bytecoin), DSH (Dash), XDN (Darknote) Dash is not Cryptonote (it has another method of anonimization). Other Cryptonotes : Aeon, Bytecoin, Digitalnote. and apparentely, we now have a monero classic... https://bitcointalk.org/index.php?topic=1600638.0Who would like to crowd fund a Boolberry (Not So) Classic [BBC]? |
|
|
|
Is there a specification for Eth Stratum v2? Currently my SGMiner port only works with getwork, and it does NOT work well at low diff.
Try DonkeyPool - min diff is 1.5 Bill and fluctuates so all miners share submit average is equal to the average ETH blocktime. That's what stratum is suppose to do, right? There are now (3) stratum options (thanks to NiceHash). They each have differing opinions on how to deliver getWork from the wallet without polling a websocket. DonkeyPool supports the Coinotron spec, which makes the most sense. Why use a proxy? all miners now support some type of stratum. DonkeyPool still has getWork support, but only until June 30. Then it's all stratum(ish) support. DonkeyPool getwork string would be address: / workername / hashrate integer value eg www.donkeypool.com/0xaaaadddreeesss/worker/10No, Stratum is a lot better, which is why I'd rather SGMiner use it than getwork. But fucking NiceHash had to reinvent the wheel (again) - are there actual specs for any of these stratum versions? Specifically 2 and 3? I don't even know about a V3. The way I understand it, there's the dwarfpool one, then coinotron's based off the bitcoin/slush protocol, and now nicehash. I don't know about version numbers except nicehash adjusted the coinotron one to allow for their needs, so if coinotron's was V1, I guess nicehash is V2. This was the info nicehash gave http://forum.ethereum.org/discussion/7369/dagger-hashimoto-added-to-nicehash. Other info I found was from https://github.com/Coinotron/eth-stratum-mining-proxy/commit/065bf6423a310a590029cf2f2395c7f1e21467af for the original coinotron stuff. For the dwarfpool stuff, I read through the code https://github.com/sammy007/open-ethereum-pool but that's probably not the easiest to pick through. Wish someone put out a full spec. |
|
|
|
I'll see if I can do a chunky 1.0.8 or perhaps even 1.1 with 3 or 4 x 512MB chunks. I like making old stuff work Cool, and thanks for the other stratum protocol support. That's awesome! |
|
|
|
1.1.7 is out. Adds support for pools using eth-proxy-style stratum. Main reason to support it is because of the upcoming choice between soft-fork or not. Supporting more pools will allow users to choose between more pools that choose the path they support, without having to change to a different mining client. Removed flags: -SV (replaced by -SC) -ES (superseded by -SP) Added flags -SC [n] Where n is 1 (async, default) or 2 (sync) stratum client. async uses a bit more CPU but has working --work-timeout, wheras sync client doesn't have that (yet). -SP [n] Where n is 0 (stratum, default), 1 (eth-proxy) or 2 (nicehash). Stratum protocol to use. -SE [e] Where e is email address. Used by eth-proxy. In some pools (like nano) you can also add it to the worker name using /. Example dwarfpool: ethminer.exe -U -S eth-eu.dwarfpool.com:8008 -SP 1 -O 0xeb9310b185455f863f526dab3d245809f6854b4d.worker -SE genoil@hotmail.comhttps://github.com/Genoil/cpp-ethereum/tree/110/releasesYes it could still have bugs, tested major pools (dwarf, f2, nano) with success, but something may have slipped through. Thanks for testing! Using your chunky V1.0.7. The only version which works with my two ancient HD 6950. Slow and inconsistent but it works. Thank you.  Cool, thx . How big is the DAG these days? This chunky 1.0.7 was really just a sketch to test chunking, if I remember well, it should break after the DAG hits 1.5GB. Also, it is possible to make it faster by using bigger chunks. But that's not configurable in 1.0.7-chunky... How would I be able to build the equivalent for linux? |
|
|
|
Hey, Claymore. I've got some code that implements coinotron stratum protocol I added to open-ethereum-pool and have been testing my pool code with your miner. When I set -esm 2, on every new job I get ETH: Outdated share found - skip I assume this is because my pool has very low diff, so it hits a share before work gets changed, but it only happens in that mode, so just wondering if I am doing something wrong or if that's harmless. |
|
|
|
Thanks, I didn't encounter that during my own tests.
The same code appears in the EthStratumClientV2.cpp file, too, but I don't think the problem showed in there, but my memory might be backwards on that. |
|
|
|
1.1.5 is out. Adds support for nicehash stratum (add -ES flag), as well as a third option to load DAGs. This is only supported on CUDA for the time being. It allows you to generate the DAG on 1 GPU and then distribute it via system RAM to the other GPUs. Usage: -L single <n>, where <n> is the GPU ID. As I don't have a dev system with multiple OpenCL GPU's on the same platform, I can't currently port this to OpenCL.
This work has all been done by nicehash themselves, thank you!
It kind of paves the way for supporting more stratum variants, so -ES wil probably change into -SM <s> in an upcoming release.
Using the miner WITHOUT -ES gives ℹ 13:24:25|openclminer0 Solution found; Submitting to blah ...
✘ 13:24:25|openclminer0 Exception thrown in Worker thread: basic_string::substr which is caused by the string minernonce = solution.nonce.hex().substr(m_extraNonceHexSize, 16 - m_extraNonceHexSize); in libstratum/EthStratumClient.cpp I just put that code behind the if (!m_ethereumStratum) block like so string minernonce;
if (!m_ethereumStratum)
cnote << " Nonce:" << "0x" + solution.nonce.hex();
else
minernonce = solution.nonce.hex().substr(m_extraNonceHexSize, 16 - m_extraNonceHexSize); to get it to work, fyi. |
|
|
|
|
Ok, going to let eth.cncoin.farm stay at 0% until end of month. 1% after that. We'll see if there is any interest. Pool never hit a block the entire time at 1%, so never even had a fee, really.
|
|
|
|
|
Show Posts
