Show Posts
|
Pages: [1] 2 3 »
|
add 0x3211 for MagicInternetMoney please
I used the value 0x86 from your current .git, is that correct?
|
|
|
Nyan + USC... My USC address for the bounty if I've proved this correctly ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) - Ueme85xiVZyoqBQu8eEprGXonUKJV9bgfi Verified and paid again! Thanks to almightyruler for his quick response to Hyacin. Users of precompiled binaries should not expose SSL to the outside world (the default configuration does not use SSL). Safe binaries will arrive in due course.
|
|
|
MNC + USCMy USC address for the bounty if I've proved this correctly ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) - Ueme85xiVZyoqBQu8eEprGXonUKJV9bgfi Verified and paid! 4 bounties left ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
Yeah where do i dump this crap? UnitedScryptCoin???
You don't dump USC, you HODL ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Added BUR. Note, the table is in decimal. So "BUR 32 Burbucoin".
|
|
|
... My USC address for the bounty if I've proved this correctly ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) - Ueme85xiVZyoqBQu8eEprGXonUKJV9bgfi Verified. Bounty sent! Also requested payment address of P2Pooler. 5 bounties left...
|
|
|
USC miners, you should try our merged mining pool at http://manicminer.inWe are mining all of this coins at merged mining, and it is actually working great: LiteCoin PesetaCoin UnitedScryptCoin HunterCoin OrgCoin CatCoin DogeCoin PotCoin DigitalCoin Give it a try!! erm. those coins arent merged mined...... Erm... Yes they are. UnitedScryptCoin, PesetaCoin, HunterCoin and OrgCoin are 100% merged. The other ones are used as the main chain to merge mine, and the pool divides the work between these main coins (LTC, DOGE, DGC, POT, CAT) so you get the maximum profit. The other ones are obviously merge mined all the time, free money. Good news! (pool website, however, is unclear about which coins are merged minable and which are not) On a side note: please vote for USC on http://www.allcrypt.com/beta/voting.phpWRT exchanges: I asked poloniex and cryptorush to add USC, they haven't responded yet. Feel free to ask them to add it.
|
|
|
One more thing, you should update to 0.8.6.2 due to a few issues in 0.8.6.1.
Thanks for the heads-up. Update will follow ASAP.
|
|
|
Well, diff is high, but 95% comes from the same source (can be seen from the LTC payout address in the parent coinbase). Currently, this coin is not secure at all.
I'm working on a merged scrypt pool, it will be LTC/USC initially. Payout PPS. Bonus for finder of block. Pool interface will be like bitparking.
Stay tuned...
In fact 99% comes from us. Yesterday (UTC) we mined 536 blocks out of 543. We are also introducing UnitedScryptCoin merged mining today. For every Bitcoin you mine at our pool, you get 1 USC, and for every Litecoin you mine, you get 5 USC. BTC/LTC/USC daily auto payout at ~04:00 UTC if balance >= 0.0005 BTC/0.01 LTC at 00:00 UTC on that day. BTC/LTC PPS at 4% fee. We are currently world's 3rd largest Bitcoin mining pool (after GHash.IO and BTC Guild) and 2nd largest Litecoin mining pool (only after WeMineLTC). Our website is currently only in Chinese. http://www.f2pool.com/Good news! Nice to know where all the hashpower is coming from.
|
|
|
Well, diff is high, but 95% comes from the same source (can be seen from the LTC payout address in the parent coinbase). Currently, this coin is not secure at all.
I'm working on a merged scrypt pool, it will be LTC/USC initially. Payout PPS. Bonus for finder of block. Pool interface will be like bitparking.
Stay tuned...
|
|
|
Is it that you can find USC blocks independently, but they're linked to/secured by the parent chain? IOW, you don't need to win a block on the parent chain to get USC? If this is the case, then you'd be mad not to merge mine... although it does sound a little fiddly for early adopters. I've read this thread through once, will have to do it again later I think. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Yes, you can find USC blocks with LTC as parent, without winning a block on LTC (since the difficulty of LTC is higher than that of USC). Multiple people are currently in the process of writing software to make merged mining easier.
|
|
|
Thanks! Bounty paid! (19376 is part of DOGE implies 19375 is part of DOGE, so it doesn't matter that much)
|
|
|
So I am currently switching between LTC/USC and DOGE/USC. But I want to have my cake and eat it too! I want to mine LTC/DOGE/USC all at once! How in the name of all the gods can we make that possible?
Did you get any blocks with DOGE? If you are the first to prove existence of such blocks in the USC blockchain, you get USC 100. For LTC/DOGE/USC merged mining to happen, either LTC or DOGE needs to accept the 'merged mining as child chain patch'. LTC has little to gain, how the DOGE community feels about it: no idea.
|
|
|
Pardon my newbieness but could you help me identifying which part of the USC block contains the Litecoin hash ? Is it encoded in the transaction script ? First: find the hash of the USC block (either on the commandline or the debug console): $ unitedscryptcoind getblockhash 10001 642639f20776313da4c16028388576c68abd96292e963303552d543b5a9b13df
Then get the block (also, either on the commandline or the debug console): $ unitedscryptcoind getblock 642639f20776313da4c16028388576c68abd96292e963303552d543b5a9b13df { "hash" : "642639f20776313da4c16028388576c68abd96292e963303552d543b5a9b13df", "pow_hash" : "b6238d5686e023cef880c54d1e54c84119060aaed517494bd5c55b2e33d268e3", "confirmations" : 13361, "size" : 755, "height" : 10001, "version" : 65794, "merkleroot" : "5abc1162b885a65647f86c99921a118270066eb912ce4b4c977f5ff11b3c66ee", "auxpow" : { "size" : 523, "coinbasetx" : { "txid" : "082c3ad598cde99850626cda979f120def107c4b2f8fbce2d2aea53da44f812a", "version" : 1, "locktime" : 0, "vin" : [ { "coinbase" : "03772f07fabe6d6d7897ed5c196dab5acdd4f2e4fcaa5053a6c161932f682a679218dc3a9f4583cf04000000000000004014150500000000f0000000", "sequence" : 4294967295 } ], "vout" : [ { "value" : 50.57290762, "n" : 0, "scriptPubKey" : { "asm" : "OP_DUP OP_HASH160 aa3750aa18b8a0f3f0590731e1fab934856680cf OP_EQUALVERIFY OP_CHECKSIG", "hex" : "76a914aa3750aa18b8a0f3f0590731e1fab934856680cf88ac", "reqSigs" : 1, "type" : "pubkeyhash", "addresses" : [ "UdW36McKmnRXjRLx8vnv9asH8aaciTFMYq" ] } } ] }, "coinbaseMerkleBranch" : [ "554f31be09c3595593af8ce7a2c8991fade90a0cc32386a2ffeb9f00763d2c15", "723355cedcbfec93f15c91dce2b74306534f199a353f92a0a79bf8094af26ba1", "0c5ded666e627d29ec239c30e8cc3494d118d9d132a13d89ecebb4c73c7d1700", "2a367327c0c174846625808bb182301cde78420531d17db453953763aa1e0cd0", "3c051b3c07e4a8baf9d01bb64174e87c5fb60026502f6254a6c04c195d656376", "ca596bfebcaceb304cc9d15b3be6acd09cdc9f7e215ce4fd1789dbee54560994" ], "coinbaseIndex" : 0, "chainMerkleBranch" : [ "0000000000000000000000000000000000000000000000000000000000000002", "c2bf026e62af95cd7b785e2cd5a5f1ec01fafda85886a8ebd34482c0b05dc2c2" ], "chainIndex" : 3, "parent_block" : { "hash" : "a67a73b6dfd5dbb2edd562ba0a42df49d64d3647901af1fc450e3d5ede910752", "pow_hash" : "000000002a3bd0933fb8ff6e550c7ab77869677f3c0e48bc94d52b05a35a7fd8", "version" : 2, "previousblockhash" : "51dd1b4131d9577c78e5dbcd3f0d1d25e360ed343f18792a98ae91d2d18b9d63", "merkleroot" : "1fd0691c974e0f74cad3dbd4ead2df556cd462b0a0a54567bf15e4d8e5d901e0", "time" : 1385977750, "bits" : "1b25ca66", "difficulty" : 1734.16053808, "nonce" : 3129217792 } }, "tx" : [ "5abc1162b885a65647f86c99921a118270066eb912ce4b4c977f5ff11b3c66ee" ], "time" : 1385977749, "nonce" : 0, "bits" : "1d0ffff0", "difficulty" : 0.06250000, "previousblockhash" : "ca341881775ac6dc35016335a347723ec88200fbbd06084ee9aa411829305273", "nextblockhash" : "4d5f5ac55554e376cee23f3dfcf87cc5a428f458e377237b53958c658de28e1e" }
Now look at auxpow -> parent_block -> previousblockhash This is the hash of the block on which the parent block is built. Unless it is an orphan, it will exist in the parent's blockchain. In this example, it is LTC block 51dd1b4131d9577c78e5dbcd3f0d1d25e360ed343f18792a98ae91d2d18b9d63.
|
|
|
Good point! You only need to firewall p2pool, so that you run a solo node, and point pushpool towards it.
|
|
|
I have a user on my pool that brought this coin to my attention. If i read correctly this coin has source to integrate with p2pool but that is it. It seems the next step to get ltc pools on board is a patch to stratum and pushpool. Is this correct assumption?
Stratum doesn't need to change, but the supplied coinb1 needs to contain the merged mining header and the hash returned by getauxblock. pushpool needs to be modified to ask USC for the hash, submit solutions to USC and distribute generated coins among users. (will also look into this myself, pushpool looks promising) It would be great if you'd add support for USC in your pool. I would be willing to give this a try if someone can assist me with it. Pushpool would be a fine start if someone wants to give me a patch. If the coins show up in the wallet i can handle the rest. As in distribution to users. I will freely admit i have never setup a merged mining pool. Some thoughts about a solution. A proxy should be written that sits between - litecoind
- unitedscryptcoin
- pushpool
It should getauxblock from unitedscryptcoin, getblocktemplate from litecoind, put USC hash in LTC block and provide a getwork interface to pushpool. Then pushpool doesn't have to be modified. Getting acquainted with libblkmaker now...
|
|
|
I have a user on my pool that brought this coin to my attention. If i read correctly this coin has source to integrate with p2pool but that is it. It seems the next step to get ltc pools on board is a patch to stratum and pushpool. Is this correct assumption?
Stratum doesn't need to change, but the supplied coinb1 needs to contain the merged mining header and the hash returned by getauxblock. pushpool needs to be modified to ask USC for the hash, submit solutions to USC and distribute generated coins among users. (will also look into this myself, pushpool looks promising) It would be great if you'd add support for USC in your pool.
|
|
|
Hi Just a doubt. I configured p2pool under windows. It created automatically a destination address in the litecoin wallet, but not in the Unitedscryptcoin wallett. Is it correct ? At the moment I can see litecoin grow up but USC is still 0. I used the --merged http://user@pass:unitedserveraddress port option. But I don't see any gain on USC. In the miner client I use my litecoin wallet as username. What's wrong ? thanks Crazy The difficulty of USC is crazy high. If you'd have 1 MH/s of hashing power, generating an USC block will take 11 days on average. Just have patience. I expect difficulty to decrease in about 1.5 weeks. Edit: merged mining in p2pool is merged solo mining. So LTC is mined in the pool, but USC is mined solo. If you find a USC block, it is entirely for you.
|
|
|
|