|
minerjoen
|
 |
November 08, 2015, 11:30:53 AM
Last edit: November 08, 2015, 02:16:54 PM by minerjoen |
|
How to mine this coin? Can you explain clearly?
The most simple way using 611-Qt is pressing: Help -> Debug windows -> Console running this command at the line >: setgenerate true $NUMBER-OF-THREADS i.e. if you like to run four threads of CPU mining: setgenerate true 4 You can disable mining running: setgenerate false Of course you can use any other mining source by connecting it to the tcp port 8661 of your 611d or 611-Qt installation. 611 (SixEleven) should also support MergedMining with Bitcoin. It would be great if anyone could check if this feature works or not and share the result with us. Hey i am wondering how to mine. This because i support cpu only coins. When u look at the examples about how to mine, its by using the console. That's good because that would mean u must use ur CPU. But in a other post i read about sha256 what means u can also use ur asic bitcoin miners? Anyway i use at cpu coins mostly: setgenerate true -1 (-1 he takes all the cores u have), only at cryptonight coins i use 4 cores instead of 8 (beter performance when using 50% of ur CPU and lower power consumption) How is that with this coin? Edit: i download the wallet from the website and its 100% synced. It didnt get stuck on some point, so that's good. Also this coin looks good so i want to give it a try with a test computer. (but i want a answer on my question above) I am mining for like 30 minutes now, but still 0 rewards. Is this because i only use 1 cpu ( i got a I7 2600 in my test system, 4 cores with hyperthreading (8cores in console)) My hashrate conform the console (using set generate true -1 what means 8 cores): 12:33:29  gethashespersec12:33:29  4836363Can u give me some info about how long to wait, or is this to low for mining? Edit 2: now i use 4 cores instead of 8 cores and my hash rate is: 12:56:56  gethashespersec 12:56:56  5077770So more speed when using 50% of cores ( that's great ) Edit 3: The coins are comming in, but many orphans ( using the cpu with setgenerate true -4 (50% from my total cores)) |
Bitcoin: 1GPjrqoWGQfqyCEYnPhbA3nWN9dmMwFHRE
Elementrem: 0xF4789b95826C4474B3E7C780Fd90f639b51C4B6c
|
|
|
|
|
|
|
|
|
|
|
|
Bitcoin mining is now a specialized and very risky industry, just like gold mining. Amateur miners are unlikely to make much money, and may even lose money. Bitcoin is much more than just mining, though!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
p3yot33at3r
|
|
November 08, 2015, 11:51:48 AM |
|
611 (SixEleven) should also support MergedMining with Bitcoin. It would be great if anyone could check if this feature works or not and share the result with us.
I tried - it doesn't work: All stale blocks when merge mining.......  This was using p2pool, port 8330, rpcport 8331. AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 000000000b47cb1c0918f199fe679ddb9849ac99c732ca957bec3d2e1b51c369
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale
BitcoinMiner:
AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 000000001484053cf81fd262cb0ef3079c721e6f36325d96f509838d3a19b5a3
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale
BitcoinMiner:
AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 000000001c7bd9c4a9ae4559ef5fa9917b624799f5a9ca937a624d3793541b82
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale
BitcoinMiner:
AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 0000000012458a6af15c226fd6358d088ea8bc57612ac9c0acb90a7327808ace
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale
BitcoinMiner:
AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 000000001f93fb5782563a84103da967593a78de5cecb3703b2f7c8476f73fb0
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale |
|
|
|
|
|
docker
|
|
November 08, 2015, 11:58:26 AM |
|
mates which cpu is best to mine 611 I got a 4510u?
|
|
|
|
|
|
minerjoen
|
|
November 08, 2015, 12:00:14 PM |
|
mates which cpu is best to mine 611 I got a 4510u?
I think a xeon cpu with 16-32 cores  An i7 4510u is that a laptop cpu or what? I see on the intel site it got 2 cores with hyperthreading what makes it visual to 4 cores. I guess its a laptop CPU. Laptop cpu's sucks somehow to mine coins. My i7 2600 ( desktop ) got 4 cores with hyperthreading to 8 cores. |
Bitcoin: 1GPjrqoWGQfqyCEYnPhbA3nWN9dmMwFHRE
Elementrem: 0xF4789b95826C4474B3E7C780Fd90f639b51C4B6c
|
|
|
|
PatrickMacH (OP)
|
 |
November 08, 2015, 12:50:40 PM |
|
611 (SixEleven) should also support MergedMining with Bitcoin. It would be great if anyone could check if this feature works or not and share the result with us.
I tried - it doesn't work: All stale blocks when merge mining....... This was using p2pool, port 8330, rpcport 8331. [...]
BitcoinMiner:
AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 000000001484053cf81fd262cb0ef3079c721e6f36325d96f509838d3a19b5a3
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale //// debug print
printf("BitcoinMiner:\n");
printf("proof-of-work found \n hash: %s \ntarget: %s\n", hash.GetHex().c_str(), hashTarget.GetHex().c_str());
}
pblock->print();
printf("%s ", DateTimeStrFormat("%x %H:%M", GetTime()).c_str());
printf("generated %s\n", FormatMoney(pblock->vtx[0].vout[0].nValue).c_str());
// Found a solution
CRITICAL_BLOCK(cs_main)
{
if (pblock->hashPrevBlock != hashBestChain)
return error("BitcoinMiner : generated block is stale"); Are you sure this is a bug? For me it seems to be a feature of P2Pool: https://en.bitcoin.it/wiki/P2Pool#StalesThe generated hash of merged mining does not match the hash of the previous 611 block. The difficulty of P2Pool is probably less that the target in order to get a P2Pool block generated every 30 seconds. Can you try to run the pool against 611 (SixEleven) for a longer period? |
|
|
|
|
p3yot33at3r
|
|
November 08, 2015, 01:10:39 PM
Last edit: November 08, 2015, 01:31:57 PM by p3yot33at3r |
|
I ran it for nearly an hour in case it was a diff adjustment issue, but it didn't change - my logs are completely full of the above stale block logs. My console readout was a constant: merged block submital result:false expected:true My conf file: server=1
daemon=1
rpcuser=my_user_name
rpcpassword=my_user_password
rpcport=8331
port=8330
rpcallowip=127.0.0.1
rpcallow=192.168.1.1
listen=1 More info: 2015-11-08 13:29:57.866379 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.866866 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.867552 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.868084 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.868623 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.869125 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.869629 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.870185 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.870684 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.871184 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.871861 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.872397 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.898732 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.004717 Merged block submittal result: True
2015-11-08 13:30:00.005360 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.006046 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.006493 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.007185 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.007816 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.008388 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.008963 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.009389 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.029207 Got new merged mining work!
2015-11-08 13:30:00.032948 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.033474 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.034137 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.034623 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.035099 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.035582 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.036206 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.036677 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.037301 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.038146 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.038799 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.039364 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.039876 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.040347 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.040822 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.043035 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.044597 > Merged block submittal result: False Expected: True |
|
|
|
|
|
sssergy
|
|
November 08, 2015, 03:09:48 PM |
|
beta 2 working
|
|
|
|
|
|
p3yot33at3r
|
|
November 08, 2015, 03:34:44 PM |
|
beta 2 working
With merge mining? |
|
|
|
|
|
minerjoen
|
|
November 08, 2015, 05:16:24 PM |
|
mining working well here ( just normall, not merge, just by using the console  , get some orphans but thats it ) How many coins are u guys making in like 1 hour? |
Bitcoin: 1GPjrqoWGQfqyCEYnPhbA3nWN9dmMwFHRE
Elementrem: 0xF4789b95826C4474B3E7C780Fd90f639b51C4B6c
|
|
|
|
PatrickMacH (OP)
|
 |
November 08, 2015, 11:19:04 PM
Last edit: November 09, 2015, 01:42:47 AM by PatrickMacH |
|
mining working well here ( just normall, not merge, just by using the console , get some orphans but thats it ) How many coins are u guys making in like 1 hour? Too good to be true - beta4 has been revoken due to the "Las Vegas" bug  https://github.com/fflo/sixeleven/releases/tag/v6.1.1-b4 describes how to step back to 611-beta2 until "Las Vegas" has been resolved. Heavy setback to block #21085  |
|
|
|
notsofast
Legendary
 Offline
Activity: 1517
Merit: 1042
@notsofast
|
|
November 09, 2015, 02:30:26 AM |
|
mining working well here ( just normall, not merge, just by using the console , get some orphans but thats it ) How many coins are u guys making in like 1 hour? Too good to be true - beta4 has been revoken due to the "Las Vegas" bug https://github.com/fflo/sixeleven/releases/tag/v6.1.1-b4 describes how to step back to 611-beta2 until "Las Vegas" has been resolved. Heavy setback to block #21085 aaaand stuck there once again. |
twitter.com/notsofast
|
|
|
|
minerjoen
|
|
November 09, 2015, 04:29:53 AM |
|
mining working well here ( just normall, not merge, just by using the console , get some orphans but thats it ) How many coins are u guys making in like 1 hour? Too good to be true - beta4 has been revoken due to the "Las Vegas" bug https://github.com/fflo/sixeleven/releases/tag/v6.1.1-b4 describes how to step back to 611-beta2 until "Las Vegas" has been resolved. Heavy setback to block #21085 Ah But where to download that beta2 version? This because also on the website u see beta4 and nothing about beta2. |
Bitcoin: 1GPjrqoWGQfqyCEYnPhbA3nWN9dmMwFHRE
Elementrem: 0xF4789b95826C4474B3E7C780Fd90f639b51C4B6c
|
|
|
wildduck
Legendary
Offline
Activity: 966
Merit: 1001
|
|
November 09, 2015, 07:23:12 AM |
|
My wallet is runing perfectly  Curently at block 89772 |
|
|
|
|
notsofast
Legendary
Offline
Activity: 1517
Merit: 1042
@notsofast
|
|
November 09, 2015, 11:55:12 AM |
|
My wallet is runing perfectly Curently at block 89772 Are you still on the beta4 fork with the las vegas bug? Because there was essentially a rollback to the point at which the blockchain originally got stuck, during the reversion to beta2. |
twitter.com/notsofast
|
|
|
|
minerjoen
|
|
November 09, 2015, 12:46:19 PM |
|
My wallet is runing perfectly Curently at block 89772 Are you still on the beta4 fork with the las vegas bug? Because there was essentially a rollback to the point at which the blockchain originally got stuck, during the reversion to beta2. First: How to check wich version i have? When i go in my wallet is say:version 0.6.11 When i go to the link above from github i only see the beta4 to download, when i go to the website i can only download the beta4. I dont know wich version i have atm... But it looks like mining is working etc, but if all this coins are gone because i'm at the wrong blockchain or something(what means i am mining for nothing) i want to know that asap. Edit: i just re-opend the wallet, i got coins but it dont start syncing ( is that the beta4 bug?) |
Bitcoin: 1GPjrqoWGQfqyCEYnPhbA3nWN9dmMwFHRE
Elementrem: 0xF4789b95826C4474B3E7C780Fd90f639b51C4B6c
|
|
|
cliffmadsen
Member
Offline
Activity: 109
Merit: 10
DigiByte
|
|
November 09, 2015, 03:09:16 PM
Last edit: November 09, 2015, 03:23:54 PM by cliffmadsen |
|
My wallet is runing perfectly Curently at block 89772 Are you still on the beta4 fork with the las vegas bug? Because there was essentially a rollback to the point at which the blockchain originally got stuck, during the reversion to beta2. First: How to check wich version i have? When i go in my wallet is say:version 0.6.11 When i go to the link above from github i only see the beta4 to download, when i go to the website i can only download the beta4. I dont know wich version i have atm... But it looks like mining is working etc, but if all this coins are gone because i'm at the wrong blockchain or something(what means i am mining for nothing) i want to know that asap. Edit: i just re-opend the wallet, i got coins but it dont start syncing ( is that the beta4 bug?) |
|
|
|
|
|
minerjoen
|
|
November 09, 2015, 07:01:12 PM |
|
My wallet is runing perfectly Curently at block 89772 Are you still on the beta4 fork with the las vegas bug? Because there was essentially a rollback to the point at which the blockchain originally got stuck, during the reversion to beta2. First: How to check wich version i have? When i go in my wallet is say:version 0.6.11 When i go to the link above from github i only see the beta4 to download, when i go to the website i can only download the beta4. I dont know wich version i have atm... But it looks like mining is working etc, but if all this coins are gone because i'm at the wrong blockchain or something(what means i am mining for nothing) i want to know that asap. Edit: i just re-opend the wallet, i got coins but it dont start syncing ( is that the beta4 bug?) here is that beta2 version anyway, just changed b4 to b2 and got this. |
Bitcoin: 1GPjrqoWGQfqyCEYnPhbA3nWN9dmMwFHRE
Elementrem: 0xF4789b95826C4474B3E7C780Fd90f639b51C4B6c
|
|
|
|
PatrickMacH (OP)
|
|
November 09, 2015, 09:37:39 PM
Last edit: November 09, 2015, 09:54:02 PM by PatrickMacH |
|
My wallet is runing perfectly Curently at block 89772 Are you still on the beta4 fork with the las vegas bug? Because there was essentially a rollback to the point at which the blockchain originally got stuck, during the reversion to beta2. First: How to check wich version i have? When i go in my wallet is say:version 0.6.11 When i go to the link above from github i only see the beta4 to download, when i go to the website i can only download the beta4. I dont know wich version i have atm... But it looks like mining is working etc, but if all this coins are gone because i'm at the wrong blockchain or something(what means i am mining for nothing) i want to know that asap. Edit: i just re-opend the wallet, i got coins but it dont start syncing ( is that the beta4 bug?) here is that beta2 version anyway, just changed b4 to b2 and got this. Sorry guys - I know the current situation is very confusing and unsatisfactory. Rolling back to beta2 also means that the block chain is still stuck at block #21085 until this task has been resolved at "difficulty" level 4692.86619945. So we are in dire need of some powerful mining ressources to resolve the next blocks until difficulty recalculation. Can anyone following this thread please check out if merged mining does work successfully using beta2: Merged mining should work like described for Namecoin here: https://github.com/namecoin/namecoin-legacy/blob/b043fba28018721b68c90edfc81b9eacb070b47d/doc/README_merged-mining.mdJust replace the Namecoin port 8331 with the 611 (SixEleven) port 8661. Or should we discuss to move the PoW concept to a non asic compatible code to make sure that the new block mining rate and difficulty levels gets more resistant against big mining pool attacks? Thanks for your feedback. |
|
|
|
|
p3yot33at3r
|
|
November 09, 2015, 10:22:24 PM
Last edit: November 09, 2015, 10:42:39 PM by p3yot33at3r |
|
Port 8661? I will try again then - can you confirm what the rpc port for 611 is? ...I can't test merge mining unless you post the correct port & rpcport 611 uses.......a search on your git repo for them reveals nothing. |
|
|
|
|
|
PatrickMacH (OP)
|
|
November 09, 2015, 11:43:17 PM |
|
Port 8661? I will try again then - can you confirm what the rpc port for 611 is? ...I can't test merge mining unless you post the correct port & rpcport 611 uses.......a search on your git repo for them reveals nothing. 611d standard port 8661, rpc port 8663: that's where you can find the relevant parts in the source code -> $ grep -n 866 * 611.cpp:2738: return fTestNet ? 18661 : 8661;
bitcoinrpc.cpp:62: return GetBoolArg("-testnet", false) ? 18663 : 8663; The forked original source code of namecoin is really painfully unsystematic  |
|
|
|
|
