 Show Posts
|
|
Pages: [1] 2 »
|
Anyone else having low ETH hashrate on ETHOS? I'm getting around 9 mhs per AMD card, s/b 22-27. Both Claymore and ETHMiner have the same issue, so I'm wondering if there is a settings fix....
Yesterday's new Epoch made 4 of my 5 3GB 1060s drop to about 8 mhs (from 18) using nanominer (only miner that still works for 3gb cards afaik). |
|
|
|
|
Oh no!
Epoch 239 has arrived and my 3GB GTX 1060s stopped working: CUDA error - cannot allocate big buffer for DAG.
|
|
|
|
|
Feature request for EthMan: A way to acknowledge alarms and have the beeping stop without having to shutdown the app and restart once the miner(s) are fixed.
Thanks.
|
|
|
|
Thanks for the link. You'd think they would link it from the Multipool status page for convenience.  |
|
|
|
|
Their Multipool has only found ORPHAN blocks for the last 24 hours.
|
|
|
|
According to https://ghash.io/MULTI, all blocks found in the last 24 hours have been ORPHAN (mining DOGE, SXC, and a bit of WDC). Is it broken? Any reason to continue using it if all it finds are ORPHANS that don't payout? |
|
|
|
|
I encountered a compilation problem on one of my two Debian boxes. Somewhere, the problem box has something the other one doesn't that is causing a conflict with libboost and uint64_t. All the normal dependencies are identical (compiler and other libraries).
The compile was failing on rpcmining.cpp and the fix was to replace all occurrences of int64_t with boost::int64_t and uint64_t with boost::uint64_t. The change does not break compilation on the other box that didn't have problem, so it may be worthwhile to make this change permanent? In fact, it appears all other uses of int64_t is actually boost::int64_t (grep int64_t *cpp |grep -v boost).
This isn't specific to Eccoin -- searching for the compile error lead to the suggested fix from the bitcoin mailing list, and other people encountering the problem with other coins as well. I have not been able to determine what is causing the conflict though.
|
|
|
|
What's up with these 0.25 MNC block rewards? I can't find any mention of them in the docs or any of the MNC threads I can find, but I'm seeing a lot of them and have even found a couple of the blocks - <snip>
2014-04-03 16:15:38.616496 New work for worker! Difficulty: 0.000354 Share difficulty: 0.007324 Total block value: 0.250000 MNC including 0 transactions
2014-04-03 16:15:44.764758 New work for worker! Difficulty: 0.000335 Share difficulty: 0.007324 Total block value: 0.250000 MNC including 0 transactions
rob@Bishop:~/p2pool-master/data/mincoin$
The block rewards are 2 MNC (plus any transaction fees that get included). What version of p2pool are you running? My guess is the SUBSIDY_FUNC in bitcoin/networks.py is incorrect. If there really were block worth less than 2 MNC, you would be able to find them with any blockexplorer. |
|
|
|
Good find! And no need to cut-n-paste the others and they're already linked as Previous Block. |
|
|
|
The nefarious stratum server on 190.97.164.179:3333 is no longer answering. It was not running standard stratum server pool -- normally the client sends data first (like HTTP) but this server was sending mining.notify immediately (more like SMTP). The mining.notify includes the hash of the previous block, but it's endianess is opposite of what any block explorer expects, but someone with more patience than myself should be able to find what coin it was mining. These are a few hashes I collected: 67272dab30992028ef77ee8d027a52a1e95582234e11ea9052a11626181c2ad4 --> 181c2ad452a116264e11ea90e9558223027a52a1ef77ee8d3099202867272dab
a5ed793ec7847f3b1904c3194d6bcec6977dc97b354a9f91c5c8985fb6344bb9 --> b6344bb9c5c8985f354a9f91977dc97b4d6bcec61904c319c7847f3ba5ed793e
21cf02e69c9a41875ee6ea26dae7e9a1a993b2dc37b1fe0f829ae5172451612a --> 2451612a829ae51737b1fe0fa993b2dcdae7e9a15ee6ea269c9a418721cf02e6
d0f67fec0722ba7f4ed0e10703a9afcbc86564316187944426906b5267345f62 --> 67345f6226906b5261879444c865643103a9afcb4ed0e1070722ba7fd0f67fec
430719e64f1653d0adb10b79ecb0a6bbcc8bfca77ab18713e123c66c03274404 --> 03274404e123c66c7ab18713cc8bfca7ecb0a6bbadb10b794f1653d0430719e6
First column is the hash from the mining.notify, second is the same swabbed around. |
|
|
|
Of the 10 million MNC available how many coins have been mined so far? Can someone pls tell me. thx.
1,666,148 according to http://mincoin.io, just below the download links. |
|
|
|
400+ blocks and counting... only 0.5% fee! Network difficulty is < 3!!!
|
|
|
|
I have some questions about PoS... I've read about it and understand the general concept, but I think an example with real numbers would very useful.
So can someone describe what will happen for someone holding 100000 ECCoin? If I have 100k today, will it start paying PoS interest in 42 days or is it from the time PoW ends? Is there a minimum amount required?
Thanks! No minimum required. 25% is the annual rate, so 100K you hold 42 days, will generate approximately 100000 * 0.25 * 42 / 365 = 2876 ECCs. And then you hold 102876 ECCs, hold another 42 days will generated you 102876 * 0.25 * 42 / 365 = 2959 ECCs, and so on and so forth. This helps but also confuses me more at the same time... You make it seem like interest payouts (aka PoS rewards) are only paid out every 42 days, but isn't it 42 days of holding? The example shows that after 84 days, I'd have 102876 ECC, but aren't there any rewards paid on days 43 to 83 on the 100k stake? So on the first day of PoS rewards, 2876 ECC are earned from holding 100k as shown, and wouldn't the same be earned the on day 2 of PoS? Then after 42 days of holding the first 2876 PoS reward, it starts earning PoS reward as well? I guess what he said is that you hold 100K for 42 days, then you will get 2876 ECCs in pos blocks, then you have 102876 ECCs now, holding them another 42 days will generate another 2959 ECCs for you. Pos is exactly like interests, and the 2nd time you like get the compound interest, your 2nd interest is based on 102876 that's why you get more 2nd time. I've just found the answer I was looking for here: http://bitcoin.stackexchange.com/questions/20007/how-does-proof-of-stake-mining-workI initially thought the PoS payout was like daily compound interest from the banking world but it is 42-day compound interest. It's the detail about coin-age being reset to zero upon PoS payout that I wasn't aware of. |
|
|
|
I have some questions about PoS... I've read about it and understand the general concept, but I think an example with real numbers would very useful.
So can someone describe what will happen for someone holding 100000 ECCoin? If I have 100k today, will it start paying PoS interest in 42 days or is it from the time PoW ends? Is there a minimum amount required?
Thanks! No minimum required. 25% is the annual rate, so 100K you hold 42 days, will generate approximately 100000 * 0.25 * 42 / 365 = 2876 ECCs. And then you hold 102876 ECCs, hold another 42 days will generated you 102876 * 0.25 * 42 / 365 = 2959 ECCs, and so on and so forth. This helps but also confuses me more at the same time... You make it seem like interest payouts (aka PoS rewards) are only paid out every 42 days, but isn't it 42 days of holding? The example shows that after 84 days, I'd have 102876 ECC, but aren't there any rewards paid on days 43 to 83 on the 100k stake? So on the first day of PoS rewards, 2876 ECC are earned from holding 100k as shown, and wouldn't the same be earned the on day 2 of PoS? Then after 42 days of holding the first 2876 PoS reward, it starts earning PoS reward as well? |
|
|
|
|
I have some questions about PoS... I've read about it and understand the general concept, but I think an example with real numbers would very useful.
So can someone describe what will happen for someone holding 100000 ECCoin? If I have 100k today, will it start paying PoS interest in 42 days or is it from the time PoW ends? Is there a minimum amount required?
Thanks!
|
|
|
|
I temporarily removed p2pools from OP. and donated you some ECCs.
Thank-you very much! And congratulations on passing the over 2 billion mined mark  If anyone is wondering about generating a vanity address for themselves, simply use the command-line option -X 33 for the ECC coin type. |
|
|
|
I've just spent all afternoon and a better part of my evening trying to get a P2Pool node running for ECCoin because I really wanted one of the 200k bounties... but I have come to the conclusion that it was a big waste of time  Since ECCoin is based off Peercoin, it will need the yet-to-be-released changes that will allow p2pool to work with these coins. There is currently a protocol incompatibility. Weekly Update #75
There will be a change with the release plan of peercoin. I have decided to include a minor protocol change for future p2pool support so the release will become a mandatory upgrade release. There will be at least 4 weeks or more upgrade window provided to users. The previously planned v0.3.1 will become the v0.4.0 release, and the previous v0.4 development would become the v0.5 development.
Weekly Update #80
Peercoin v0.4 is going through final round of validation. Release candidate will be announced in a few days once all tests complete and build starts. The upgrade schedule will be fixed before release candidate according to what I described last week.
Oh well... at least I have my ECC vanity address: ESnowLehcXPQoGFBCgS8ZHzCfHXW3VUk48 |
|
|
|
Great service! BTW, you shouldn't claim payments are faster with Coinbase when they are actually much much longer to confirm. If the rig owner only sees Rented - Waiting payment... without the Waiting 1 confirmation... that the renter sees, no wonder some are annoyed at alleged deadbeat renters! |
|
|
|
Please join: The first 24 hours of operation have past without any major issue. Blocks have been found, coins have been earned, payouts have gone through. |
|
|
|
Excellent, thanks for the report. Btw, were you compiling natively on the pi or were you using a crosscompiler? Thanks!
Native on the pi. $ clang -v
Debian clang version 3.0-6.2 (tags/RELEASE_30/final) (based on LLVM 3.0)
Target: arm-unknown-linux-gnueabihf
Thread model: posix
I read something about changes in the arm processors which is why the CFLAGS with explicit CPU version are needed. |
|
|
|
|
