🌟 [SIL] 611 (SixEleven) ◥◣ FREE ANONYMOUS DOMAIN NAME SYSTEM ◥◣ 🌟 - page 32.

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: p3yot33at3r on November 09, 2015, 09:22:11 PM

Quote from: PatrickMacH on November 09, 2015, 09:12:32 PM

Have you setup a pool supporting 611 (SixEleven) merged mining or is this your private mining equipment?

It's my own p2pool node, not public - my internet is crap Tongue

I had to lower the hash rate, it was causing too many doa's. Hopefully when a few more miners jump in it will smooth out a little & I can raise it again gradually.

Thanks for the feedback. A new block should be mined on average every five minutes.

You are running merged mining successfully now using the merged-mine-proxy script from contrib?
i.e.:

Code:

contrib/merged-mine-proxy -w $PORT_to_direct_mining_equipment -p http://pw:[email protected]:8332/ -x http://pw:[email protected]:8663/

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: PatrickMacH on November 09, 2015, 09:12:32 PM

Have you setup a pool supporting 611 (SixEleven) merged mining or is this your private mining equipment?

It's my own p2pool node, not public - my internet is crap Tongue

I had to lower the hash rate, it was causing too many doa's. Hopefully when a few more miners jump in it will smooth out a little & I can raise it again gradually.

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: p3yot33at3r on November 09, 2015, 08:48:11 PM

Quote from: PatrickMacH on November 09, 2015, 06:43:17 PM

Quote from: p3yot33at3r on November 09, 2015, 05:22:24 PM

Quote from: PatrickMacH on November 09, 2015, 04:37:39 PM

Can anyone following this thread please check out if merged mining does work successfully using beta2:
[...]

...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: ...

Allrighty then - we have some movement. Merge mining tested OK with a small amount of hash, so I'm gradually increasing to see how it goes. Diff has risen & the blockchain is moving again Wink

I'll keep an eye on it for a while....

Yes, looks good!
Movement again and the difficulty factor is rising in steps like expected: Cool

Code:

...:$ 611d getinfo
{
    "version" : 61100,
    "balance" : 17.42289792,
    "blocks" : 21279,
    "timeoffset" : -3,
    "connections" : 12,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : 1,
    "difficulty" : 75087.00781482,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1442356160,
    "keypoolsize" : 102,
    "paytxfee" : 0.06110000,
    "mininput" : 0.00010000,
    "txprevcache" : false,
    "errors" : ""
}

Have you setup a pool supporting 611 (SixEleven) merged mining or is this your private mining equipment?

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: PatrickMacH on November 09, 2015, 06:43:17 PM

Quote from: p3yot33at3r on November 09, 2015, 05:22:24 PM

Quote from: PatrickMacH on November 09, 2015, 04:37:39 PM

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.md

Just replace the Namecoin port 8331 with the 611 (SixEleven) port 8661.

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 *

Code:

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 Undecided

Allrighty then - we have some movement. Merge mining tested OK with a small amount of hash, so I'm gradually increasing to see how it goes. Diff has risen & the blockchain is moving again Wink

I'll keep an eye on it for a while....

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: p3yot33at3r on November 09, 2015, 05:22:24 PM

Quote from: PatrickMacH on November 09, 2015, 04:37:39 PM

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.md

Just replace the Namecoin port 8331 with the 611 (SixEleven) port 8661.

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 *

Code:

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 Undecided

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: PatrickMacH on November 09, 2015, 04:37:39 PM

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.md

Just replace the Namecoin port 8331 with the 611 (SixEleven) port 8661.

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

sr. member

Activity: 443

Merit: 251

Quote from: minerjoen on November 09, 2015, 02:01:12 PM

Quote from: cliffmadsen on November 09, 2015, 10:09:16 AM

Quote from: minerjoen on November 09, 2015, 07:46:19 AM

Quote from: notsofast on November 09, 2015, 06:55:12 AM

Quote from: wildduck on November 09, 2015, 02:23: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.

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?)

https://github.com/fflo/sixeleven/releases/tag/v6.1.1-b2

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. Huh

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.md
Just 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.

minerjoen

hero member

Activity: 644

Merit: 500

Quote from: cliffmadsen on November 09, 2015, 10:09:16 AM

Quote from: minerjoen on November 09, 2015, 07:46:19 AM

Quote from: notsofast on November 09, 2015, 06:55:12 AM

Quote from: wildduck on November 09, 2015, 02:23: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.

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?)

https://github.com/fflo/sixeleven/releases/tag/v6.1.1-b2

here is that beta2 version anyway, just changed b4 to b2 and got this.

cliffmadsen

member

Activity: 109

Merit: 10

DigiByte

Quote from: minerjoen on November 09, 2015, 07:46:19 AM

Quote from: notsofast on November 09, 2015, 06:55:12 AM

Quote from: wildduck on November 09, 2015, 02:23: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.

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

hero member

Activity: 644

Merit: 500

Quote from: notsofast on November 09, 2015, 06:55:12 AM

Quote from: wildduck on November 09, 2015, 02:23: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.

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?)

notsofast

legendary

Activity: 1517

Merit: 1042

@notsofast

Quote from: wildduck on November 09, 2015, 02:23: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.

wildduck

legendary

Activity: 966

Merit: 1001

My wallet is runing perfectly

Curently at block 89772

minerjoen

hero member

Activity: 644

Merit: 500

Quote from: PatrickMacH on November 08, 2015, 06:19:04 PM

Quote from: minerjoen on November 08, 2015, 12:16:24 PM

mining working well here ( just normall, not merge, just by using the console Cheesy

, 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 Cry

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 Huh

Ah

But where to download that beta2 version? This because also on the website u see beta4 and nothing about beta2.

notsofast

legendary

Activity: 1517

Merit: 1042

@notsofast

Quote from: PatrickMacH on November 08, 2015, 06:19:04 PM

Quote from: minerjoen on November 08, 2015, 12:16:24 PM

mining working well here ( just normall, not merge, just by using the console Cheesy

, 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 Cry

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 Huh

aaaand stuck there once again.

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: minerjoen on November 08, 2015, 12:16:24 PM

mining working well here ( just normall, not merge, just by using the console Cheesy

, 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 Cry

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 Huh

minerjoen

hero member

Activity: 644

Merit: 500

mining working well here ( just normall, not merge, just by using the console Cheesy

, get some orphans but thats it )

How many coins are u guys making in like 1 hour?

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: sssergy on November 08, 2015, 10:09:48 AM

beta 2 working

With merge mining?

sssergy

full member

Activity: 366

Merit: 100

beta 2 working

p3yot33at3r

sr. member

Activity: 266

Merit: 250

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:

Code:

merged block submital result:false expected:true

My conf file:

Code:

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:

Code:

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

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: p3yot33at3r on November 08, 2015, 06:51:48 AM

Quote from: PatrickMacH on November 08, 2015, 05:37:41 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:

Quote from: p3yot33at3r on November 07, 2015, 10:18:33 PM

All stale blocks when merge mining....... Sad

This was using p2pool, port 8330, rpcport 8331.

Code:

[...]
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

Code:

        //// 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#Stales
The 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?

Topic: 🌟 [SIL] 611 (SixEleven) ◥◣ FREE ANONYMOUS DOMAIN NAME SYSTEM ◥◣ 🌟 - page 32. (Read 80006 times)