 Show Posts
|
|
Pages: « 1 [2] 3 »
|
I didn't bother reading the thread so you may already know this: Litecoin is on 0.8.6.1, please update.
p2pool.lurkmore.com:9327 has merged mining going but I don't know how it'll end up paying out USC.
New version expected this weekend. |
|
|
|
Instead of worrying too much about that, focus should be on creating a fix. i would introduce a this fix :- add a condition that if a block is not solved in a set given amount of time, difficulty returns to previous level or reduces by a certain amount. Regardless of which pool raped your coin, if you do not fix your own difficulty algo, any pool or individual with a farm can upset the diificulty with ease.
We can't battle a 51% with anything else than more hashpower. Asymmetric difficulty adjustments will decrease security of the coin further. Our benevolent merged miner is currently the largest holder of USC, and therefore has an incentive to keep this coin alive. |
|
|
|
USC block with hash 58149cf0201c09a13acda604540f0d7d936b8004fd5fd497835449bdaf34faba was mined using WDC as a parent. I mined it.
Nice. I've added your proof to the announcement. Where shall I send the USC 100 bounty? |
|
|
|
Status update: Of the latest 557 blocks, 557 blocks are made by our mysterious merged miner. He/she seems adjust his/her mining power to ease our difficulty down (Thanks for that  ; you are probably reading this, please feel free to speak up!). A step down by a factor of four takes at least 4*3.5 days = 2 weeks. Once our mysterious merged miner has < 50% of the blocks, normal growth of USC can begin. |
|
|
|
I just sent the following message to pooler, admin of litecoinpool.org. Asking him for help identifying the pool that used to mine on this coin... Hi pooler / [ANN][USC] readers ('open letter'),
I'm the creator of UnitedScryptCoin, a scrypt coin that can be merge mined with LTC for free.
Our difficulty has been racked up to 225, probably by a pool. This pool seems to have stopped mining our coin, leaving the blockchain dead in the water.
I would like to know which pool it is/was.
Since you have a nice hashrate breakout on your pool's website, I'd like to ask you to help me with this.
Said pool mines to LajyQBeZaBA1NkZDeY8YT5RYYVRkXMvb2T, LTC block 473042 was mined by this pool.
Can you help me identifying pool?
On a side note: would you be interested to merged mine this coin alongside USCLTC?
Unfortunately, pooler was unable to help us. Anyone know which pool generated this block? If you are with a pool, please check the statistics page to see if block 473042 was mined by your pool. |
|
|
|
Also I just noticed I am having trouble syncing my wallet and it has been stuck at block 22313 for about half a day now, I even deleted the blockchain and tried to download it again and still it gets stuck on the same block  i just tried, same with me curious as to what the issue is, maybe the giant pool stopped mining? Hmm I forced it to rebuild the block data base and now I am synced up and at block 22330 atm As can be seen on the block explorer: there were no new blocks for a time. Probably because the large pool (10% of LTC) stopped mining USC for a couple of hours. |
|
|
|
Any plans on getting this on an exchange? It must be extremely popular because the difficulty is already at 195 but no one here is really talking about it and I don't see anyone really trading it.
The coin is still very young, and most >95% of the blocks are generated by the same entity. The parent coinbase almost always pays to OP_DUP OP_HASH160 aa3750aa18b8a0f3f0590731e1fab934856680cf OP_EQUALVERIFY OP_CHECKSIG , which is Litecoin address LajyQBeZaBA1NkZDeY8YT5RYYVRkXMvb2T. Probably a pool, which pool is it? We should probably ask this pool to advertise they are mining USC and share it with their users.... (for example litecoin block 1cbe5cf12497add684aeab2be976695a531b238476412ae992b627f4c2bbb51c is used to mine USC block da40a636f943ab8c9254a99fbd3509e2f2b44f3db4a6f494925971c1ccef25bf, see the output of unitedscryptcoind getblock da40a636....) Yesterday, this large miner stopped mining for some time, and the blockrate of USC dropped to 1 block per hour (while 24 blocks are the normal amount). We need more distribution of hashrate, and large pools that advertise they are mining USC and share it with users. I expect this coin to be on an exchange within 6 months, if not, I will probably build an exchange myself. |
|
|
|
Sorry if these questions have already been asked and answered:
How hard is it to apply the merged mining patch to other scryptcoins and to coins using other algos like YAC and QRK and their clones, would those builds be valid to the network and how many people are doing this already?
If you apply the merged mining patch to some coin, you create a hard fork in the network. One fork that accepts merge mined blocks and one fork that doesn't. Merged mined blocks are only valid if the maintainer says so and the community of the corresponding coin agrees. |
|
|
|
thanks, received! btw, what is the block time target? 2.5 min, just like LTC. Feel free to find other parent chains. The is no 1 per person limit. (only 1 per blockchain and 10 in total). |
|
|
|
ill just run the client in my pools and any merged coins ill use to do a giveaway that we can keep an always running giveaway
That would be okay, IF you inform your users. It would be bad to use their hashingpower to generate coins they can't get. Maybe you can make USC optional. Every user that does not supply an address, loses his/her coins to you. |
|
|
|
I suggest 1 USC because of the current difficulty of almost 200 and Block reward of 50.
This is quiet a lot, a decent VGA card (~500Kh/s) gives 2,5 coins a day right now.
To mine one coin it costs me more than USD 0,5 (germany)
ahmed_bodi, are you willing to do a thread with 500 giveaways of USC 1? Otherwise, maybe we should limit the amount to, say USC 250 or lower? |
|
|
|
i can add usc to one of my DGC PPS pools and i will distribute USC in giveaways if u like?
That would both be great. I will donate USC 350 to a giveaway. What is a reasonable amount to give? USC 1? USC 2? (that will be a looong thread...) Pool support of merged mining is needed. Please add USC to one (or all) of your pools! (if you are the first to prove a block is mined against an other major scryptcoin, you can claim a bounty of USC 100) |
|
|
|
i guess thoose who figured out how to merge mine this properly will keep their knowledge for a while.
if you are running a big pool this could be quiete profitable if that thing hits an exchange.
--->6Gh/s
That. According to the hashrate display at vircurex, USC is now second only to LTC in hashrate. It is low risk for exchanges to carry it, because a 51% attack is quite unfeasible. On the other side: this coin is not even 4 days old... Note, however, that the goal of this coin is to be the most secure scrypt coin. This can be done by combining most of the hashing power of all LTC-compatible coins. In this way it is theoretically possible to get more GH/s than LTC. These are interesting times  Have you all read about the bounty (USC 100) for finding LTC-compatible coins to use as merged mining parent chain? (see at the top of this thread) i wondered about this.. what happens when USC has more hash power than parent chain, it just works like normal except if you solve parent chain block it can't "solve" secondary chain block? i.e. atm with namecoin, (i believe) if you solve a bitcoin block it can also solve the namecoin block at the same time? something like that.. can you clear that up? (i know i've read the answer a long time ago but has slipped my mind) -- edit - if people are using multiple parent chains (seperate people) then USC could have more hash than LTC, how does that work or does USC never have more hash power than biggest parent chain.. confusing actually now There is no problem. I'm currenly experimenting with LKY as parent chain and USC as child. I have an LKY solution, which is not accepted by USC, because it is too 'easy'. USC can, in theory, if enough people start to merged mine, have a higher rate than LTC. |
|
|
|
i guess thoose who figured out how to merge mine this properly will keep their knowledge for a while.
if you are running a big pool this could be quiete profitable if that thing hits an exchange.
--->6Gh/s
That. According to the hashrate display at vircurex, USC is now second only to LTC in hashrate. It is low risk for exchanges to carry it, because a 51% attack is quite unfeasible. On the other side: this coin is not even 4 days old... Note, however, that the goal of this coin is to be the most secure scrypt coin. This can be done by combining most of the hashing power of all LTC-compatible coins. In this way it is theoretically possible to get more GH/s than LTC. These are interesting times Have you all read about the bounty (USC 100) for finding LTC-compatible coins to use as merged mining parent chain? (see at the top of this thread) |
|
|
|
Request: can you add support for mining UnitedScryptCoin? This coin can be merge mined together with any coin similar enough to LTC. Highlevel overview of merged mining (explanation for 1 child chain, with more it becomes more complex): - request work from USC with getauxblock
- put hash of block in coinbase script of parent blockchain (preceded by merged mining header)
- solve block of parent chain of difficulty in getauxblock
- provide auxpow (auxiliary proof of work) to USC with the following info
- block header of parent chain
- coinbase transaction of parent chain (this contains the hash of the USC block)
- MerkleBranch linking parent coinbase to parent block
- you have mined a block of USC based on a solution to a block of the other blockchain!
For a detailed description, see for example the sourcecode of p2pool. |
|
|
|
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? you can replace LTC in what he said with GRAND coin (don't know anything about grandcoin but that is what he means, i think ) Yes. It's best to try it with LTC first. You need to run a full litecoin node. Point p2pool to it. If that works, you can add the --merged commandline option to p2pool. It seems to work for a lot of people; hashrate is 5GH/s (faster than FTC!). |
|
|
|
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. |
|
|
|
Every coin that can be merge mined with LTC, needs to have it's own ChainID. I will keep a list in this topic. If you are the maintainer of a scrypt-coin and you want to allow your coin to be merge mined against LTC (or same PoW), please propose an unused ChainID below, I will add it to this list. Let's limit the ChainID to 8 bits for now, the protocol allows for 14 bits. --- 0 reserved
USC 1 UnitedScryptCoin
HUC 2 Huntercoin
BSS 4 Bosscoin
RSV 7 ReserveCoin
ORG 8 Orgcoin
BUR 32 Burbucoin
TPC 36 Templecoin
SPH 53 Sapphire
PST 71 PesetaCoin
LEAF 77 Leafcoin
KAR 87 KarpelesCoin
MIM 134 MagicInternetMoney
Want to know how to implement merged mining for your coin? Take a look at the merged-mining branch of unitedscryptcoin.git. It contains recent Litecoin + (disabled) merged mining patches. To enable merged mining for your coin, you need to merge with this branch (if possible), set the ChainID and set the starting block. Addendum: note that the merged-mining patch messes up your block header database. A reindex is needed after this patch. |
|
|
|
Found USC block with LKY as primary chain , block got orphaned immediately  . Log 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: {
"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: {
"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... |
|
|
|
|
