Pages:
Author

Topic: [ANN][USC] First merged minable scryptcoin UnitedScryptCoin, exchange available! - page 9. (Read 51743 times)

full member
Activity: 163
Merit: 100
can anyone confirm actual merged mining is happening?

I tried to get it to work with Grandcoin and couldn't get it to work. Obviously the difficulty on litecoin is way too high to solo mine it merged mine with USC so without a pool it's too bad.

Can you explain exactly what you did and what didn't work? Did a block get rejected? What does the debug.log say?

BTW: if you use p2pool + LTC + merged mining USC, you mine LTC in a pool (so the high difficulty does not matter) and you mine USC solo.

I couldn't get p2pool to work with grand coin. I obviously don't know what I'm doing with p2pool because I didnt realize that about LTC. I would still have to setup litecoind and download the whole block chain though, right?
newbie
Activity: 48
Merit: 0
can anyone confirm actual merged mining is happening?

I tried to get it to work with Grandcoin and couldn't get it to work. Obviously the difficulty on litecoin is way too high to solo mine it merged mine with USC so without a pool it's too bad.

Can you explain exactly what you did and what didn't work? Did a block get rejected? What does the debug.log say?

BTW: if you use p2pool + LTC + merged mining USC, you mine LTC in a pool (so the high difficulty does not matter) and you mine USC solo.
newbie
Activity: 48
Merit: 0
Found USC block with LKY as primary chain  Smiley, block got orphaned immediately   Sad.

Log
Code:
2013-12-03 16:59:38 AUX proof-of-work found  
     our hash: c91fd86faeeebc01873ed5719d3ea0451cfa9a163f9f967c5cf68e996b4671f1  
  parent hash: 000000000984c9976d6d0e6498b01cdc4980c81de9e73fb456b5a9e11ca4a7c6  
       target: 000000000ffff000000000000000000000000000000000000000000000000000
2013-12-03 16:59:38 CBlock(hash=7b0b30717e1ed487585aa022e992dca1c40900e43abbbde105a1364db0c06e93, input=0
2010100aa1ac0f27fd33f36de89cdccf94bb3cd90e8797d125e3b7d7ec9ce586e542cc837f41f03d05818228978b8617f59931d0d
201b26870949dbbb36ec6ff98c90bff30d9e52f0ff0f1c00000000, PoW=c91fd86faeeebc01873ed5719d3ea0451cfa9a163f9f9
67c5cf68e996b4671f1, ver=65794, hashPrevBlock=c82c546e58cec97e7d3b5e127d79e890cdb34bf9cccd89de363fd37ff2c
01aaa, hashMerkleRoot=bf908cf96fec36bbdb490987261b200d1d93597f61b87889221858d0031ff437, nTime=1386089971,
 nBits=1c0ffff0, nNonce=0, vtx=1)
2013-12-03 16:59:38   CTransaction(hash=bf908cf96fec36bbdb490987261b200d1d93597f61b87889221858d0031ff437,
 ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinba
se 04f0ff0f1c010152)
    CTxOut(nValue=50.00000000, scriptPubKey=03ee55b352f137a01616b9813e9be3)
  vMerkleTree: bf908cf96fec36bbdb490987261b200d1d93597f61b87889221858d0031ff437
2013-12-03 16:59:38 generated 50.00
2013-12-03 16:59:38 AddToWallet bf908cf96fec36bbdb490987261b200d1d93597f61b87889221858d0031ff437  new
2013-12-03 16:59:38 Committing 1 changed transactions to coin database...
2013-12-03 16:59:38 SetBestChain: new best=7b0b30717e1ed487585aa022e992dca1c40900e43abbbde105a1364db0c06e93  height=16908  log2_work=46.504831  tx=17388  date=2013-12-03 16:59:31 progress=0.999996
2013-12-03 16:59:38 ProcessBlock: ACCEPTED

Complete, orphaned block:
Code:
{
    "hash" : "7b0b30717e1ed487585aa022e992dca1c40900e43abbbde105a1364db0c06e93",
    "confirmations" : 0,
    "size" : 638,
    "height" : 16908,
    "version" : 65794,
    "merkleroot" : "bf908cf96fec36bbdb490987261b200d1d93597f61b87889221858d0031ff437",
    "auxpow" : {
        "size" : 454,
        "coinbasetx" : {
            "txid" : "407c373055182e4fba2a6dd84503ee73b833e113e7fc8ad46972496439d91193",
            "version" : 1,
            "locktime" : 0,
            "vin" : [
                {
                    "coinbase" : "03055c012cfabe6d6d7b0b30717e1ed487585aa022e992dca1c40900e43abbbde105a1364db0c06e930100000000000000062f503253482f",
                    "sequence" : 4294967295
                }
            ],
            "vout" : [
                {
                    "value" : 88.10000000,
                    "n" : 0,
                    "scriptPubKey" : {
                        "asm" : "OP_DUP OP_HASH160 ffad31ef9e76429275a624f56247bda86386edb1 OP_EQUALVERIFY OP_CHECKSIG",
                        "hex" : "76a914ffad31ef9e76429275a624f56247bda86386edb188ac",
                        "reqSigs" : 1,
                        "type" : "pubkeyhash",
                        "addresses" : [
                            "UmHuk74vY2VDjVVE5JeSaZk4jxc4B9BttM"
                        ]
                    }
                },
                {
                    "value" : 0.00000000,
                    "n" : 1,
                    "scriptPubKey" : {
                        "asm" : "04ffd03de44a6e11b9917f3a29f9443283d9871c9d743ef30d5eddcd37094b64d1b3d8090496b53256786bf5c82932ec23c3b74d9f05a6f95a8b5529352656664b OP_CHECKSIG",
                        "hex" : "4104ffd03de44a6e11b9917f3a29f9443283d9871c9d743ef30d5eddcd37094b64d1b3d8090496b53256786bf5c82932ec23c3b74d9f05a6f95a8b5529352656664bac",
                        "reqSigs" : 1,
                        "type" : "pubkey",
                        "addresses" : [
                            "Ugy6MxjyW9qSLYvjAcXvjJd1MzeVBtUdVa"
                        ]
                    }
                },
                {
                    "value" : 0.00000000,
                    "n" : 2,
                    "scriptPubKey" : {
                        "asm" : "OP_RETURN 5292f0b35b75e09b353946c47e3c38a8c1ce1c30847e6a62cd3aa061c2e7f9ad0000000001000000",
                        "hex" : "6a285292f0b35b75e09b353946c47e3c38a8c1ce1c30847e6a62cd3aa061c2e7f9ad0000000001000000",
                        "type" : "nonstandard"
                    }
                }
            ]
        },
        "coinbaseMerkleBranch" : [
            "266c767672bbb0897b9d050a12348b9658439a38ca841ad6c1896dcaa715d9f4",
            "8f2919395550ae29ea540ce77c500d30642397d67c501b03a97d63762908eba1"
        ],
        "coinbaseIndex" : 0,
        "chainMerkleBranch" : [
        ],
        "chainIndex" : 0,
        "parent_block" : {
            "hash" : "[color=red]30e8ad303800072f7ef08ead63f1e6ba38517f260b7826437611ffd0b50bee98[/color]",
            "version" : 1,
            "previousblockhash" : "3723a68b1822688e200bf3770d82f9919d76edee00f7b106533a31626aa5187b",
            "merkleroot" : "872c6e7698cdddc6195453c16788090f96ec0b11b0f4c8b42c38a195c5781c4e",
            "time" : 1386089966,
            "bits" : "1c2f7c7c",
            "nonce" : 3301052416
        }
    },
    "tx" : [
        "bf908cf96fec36bbdb490987261b200d1d93597f61b87889221858d0031ff437"
    ],
    "time" : 1386089971,
    "nonce" : 0,
    "bits" : "1c0ffff0",
    "difficulty" : 16.00000000,
    "previousblockhash" : "c82c546e58cec97e7d3b5e127d79e890cdb34bf9cccd89de363fd37ff2c01aaa"
}

So this block was orphaned from USC, but the parent block still is in the LuckyCoin blockchain:
Code:
{
    "hash" : "30e8ad303800072f7ef08ead63f1e6ba38517f260b7826437611ffd0b50bee98",
    "confirmations" : 17,
    "size" : 1026,
    "height" : 89093,
    "version" : 1,
    "merkleroot" : "872c6e7698cdddc6195453c16788090f96ec0b11b0f4c8b42c38a195c5781c4e",
    "tx" : [
        "407c373055182e4fba2a6dd84503ee73b833e113e7fc8ad46972496439d91193",
        "266c767672bbb0897b9d050a12348b9658439a38ca841ad6c1896dcaa715d9f4",
        "48316f3b78ce0f2b8daa4e1050dae735a7d157a6ea0542353f3f8117f439611b",
        "7c1a86d22486c5d728cefba885ac6dec547ea10e9d576fd569005874ef2627a5"
    ],
    "time" : 1386089966,
    "nonce" : 3301052416,
    "bits" : "1c2f7c7c",
    "difficulty" : 5.39095005,
    "previousblockhash" : "3723a68b1822688e200bf3770d82f9919d76edee00f7b106533a31626aa5187b",
    "nextblockhash" : "7ab17c04d30843395053491de7b5a31a717c78f938aeed638c5ecd0b304959c0"
}

Hopefully my next block won't be orphaned...
sr. member
Activity: 324
Merit: 260
full member
Activity: 163
Merit: 100
can anyone confirm actual merged mining is happening?

I tried to get it to work with Grandcoin and couldn't get it to work. Obviously the difficulty on litecoin is way too high to solo mine it merged mine with USC so without a pool it's too bad.
member
Activity: 65
Merit: 10
just noticed:

"networkhashps" : 1358113148  = 1.3 Gh/s (to compare: litecoin average 24h : 57Gh/s)

awsome!


this should confirm the merged mining.
legendary
Activity: 882
Merit: 1000
can anyone confirm actual merged mining is happening?
legendary
Activity: 2198
Merit: 1014
Franko is Freedom
sr. member
Activity: 519
Merit: 253
So this only works with p2p? No way to solo another coin and merge mine?
legendary
Activity: 1807
Merit: 1020
difficulty atm is 1.000000 ?
Yes, it is.  There is probably a 4x limit on difficulty increase each interval (I didn't check), otherwise it would have gone up more.  Blocks are pouring in much faster than every 2.5 minutes, so expect the difficulty to rise again at block 14112.

good point.
hero member
Activity: 577
Merit: 500
Sad I was very happy to mine my very first one ... Anyway with my laptop I can´t do much... and have no room for a PC
sr. member
Activity: 287
Merit: 250
difficulty atm is 1.000000 ?
Yes, it is.  There is probably a 4x limit on difficulty increase each interval (I didn't check), otherwise it would have gone up more.  Blocks are pouring in much faster than every 2.5 minutes, so expect the difficulty to rise again at block 14112.
legendary
Activity: 1807
Merit: 1020
Is it enough to "setgenerate true -1" for solo mining??

no you probably won't get any cpu mining, you need to use a GPU.
I managed to mine a few blocks with my nvidia


Hi guys, I think that I started solo mining Smiley And when listing transactions this appears:

{
"account" : "",
"address" : "UhWDdsoaAqbqYxUAcCuZ1VnrfgXSeSxpXc",
"category" : "orphan",
"amount" : 50.00000000,
"confirmations" : 0,
"generated" : true,
"txid" : "d09ece8ebc8d74582f8f7acb6659bef6b6a5f9def3bd2bd3d5474e01bd3e63ee",
"time" : 1386023494,
"timereceived" : 1386023494
}

Does that mean that I mined 50 coins?? Why they don't appear in my wallet? Why this address does not appear in my normal addresses tab? Do they need confirmation? Sorry for the noob questions... Smiley

it means you won't get those coins, probably you mined it around the same time as someone else

------------

difficulty atm is 1.000000 ?
hero member
Activity: 577
Merit: 500
Hi guys, I think that I started solo mining Smiley And when listing transactions this appears:

{
"account" : "",
"address" : "UhWDdsoaAqbqYxUAcCuZ1VnrfgXSeSxpXc",
"category" : "orphan",
"amount" : 50.00000000,
"confirmations" : 0,
"generated" : true,
"txid" : "d09ece8ebc8d74582f8f7acb6659bef6b6a5f9def3bd2bd3d5474e01bd3e63ee",
"time" : 1386023494,
"timereceived" : 1386023494
}

Does that mean that I mined 50 coins?? Why they don't appear in my wallet? Why this address does not appear in my normal addresses tab? Do they need confirmation? Sorry for the noob questions... Smiley
hero member
Activity: 577
Merit: 500
Is it enough to "setgenerate true -1" for solo mining??
legendary
Activity: 2940
Merit: 1090
Bitcoin does know bout merged mining. But it only knows enough to be the parent chain, as teaching it to also be able to be a child chain would require a hard-fork.

Any scrypt coin that based itself on bitcoin code without stripping out the ability to act as a parent chain in a merge should be able to act a a parent.

But did merged mining even exist when litecoin was first created?

If not, did litecoin inherit the ability to be parent chain at some point in the course of updating itself from newer bitcoin code?

You do not need to specify the parent, in fact for example GeistGeld calls itself chain number zero (each chain in a merge needs a different number, I think the number is used as index into an array of chains when recording the proofs in the parent and child chains or something like that), even though bitcoin is actually chain zero. If bitcoin ever did learn to be a child chain it could not be merged with GeistGeld unless GeistGeld was used as parent, since otherwise there would be two chains both claiming to be index zero in the array of merkle trees or whatever the chain number is actually used for.

With p2pool for example you run the p2pool of the parent chain, and its chain number is irrelevant, most chains probably just call themselves chain zero like bitcoin does since their programmers probably didn't even know what the chain number/index was about or for, and they did not have being a child chain in mind.

But each chain that is going to be able to serve as a child chain needs a unique number/index.

For example:

Code:
# Chains:
#  0 geistgeld 8777
#  1 namecoin 8336
#  2 ixcoin 8339
#  3 i0coin 7332
#  4 devcoin 52332
#  5 groupcoin 51332
#  7 rucoin 8082
# 16 coiledcoin 9442

RUcoin of course is closed source and has mutated gosh knows how much or how many times since the ancient times of its original incarntion in which it was purported to be able to be merged mined and has the child number/index 7.

GeistGeld is probably a bug, the idiot who wrote it was probably totally ignorant so didn't know to assign it a chain index/number so the value was just left as zero like it is in bitcoin.

-MarkM-
sr. member
Activity: 569
Merit: 250
not a single block on the pool yet -.-
legendary
Activity: 1807
Merit: 1020
from all this:

Why aren't sha256 coin pools,  like ppc merge mining namecoin... obviously it may be difficult to get a block, but still a chance..
is possible?
donator
Activity: 1218
Merit: 1079
Gerald Davis
The child coin needs to be programmed to work with a SPECIFIC PARENT.  In this case USC (child) merge mines with LTC (parent) because that is the way USC was programmed.

I don't believe this to be true. USC does not care if a parent block comes from LTC or a similar copycat (with ChainID != 1, the only coin with ChainID == 1, is USC, other coins wanting to merge mined, should choose another ChainID). The reason is: USC does not know the genesis block of LTC, so it can't know if a block belongs to LTC. If no-one steps up to experiment, I will try to generate a block against an LTC clone.

The git repository contains the branch merged-mining. This branch is LTC + merged mining (starting at block INT_MAX, ChainID == 0). It can be a starting point for other developers to adopt merged mining as secondary chain.

Hmm that is a good point.  I hadn't considered that but looking both at USC code and NMC code I believe you are right it was an incorrect assumption on my part.  Since all SHA-256 coins use Bitcoin as parent I assumed that was encoded but it looks like it was not.  Would be interesting way to gain hashpower from many chains.   Obviously LTC is the biggest bang for the buck (10% of LTC network is worth a lot more than anyone else) but it may it does mean the coin isn't limited to the success of the parent as it can switch to whatever parent(s) are viable at the current time.  Thanks you helped me learn something today.

Another interesting idea (and it would be a little more complex probably requiring two different difficulty values) would be to create a coin which can use either hashing algorithm and support merge mining against chains with either algorithm.

Pages:
Jump to: