 Show Posts
|
|
Pages: [1] 2 3 4 »
|
can anybody explain the difference between x11 and c11? (or drk and chc)  Both are basically the quark hashing algorithms + the qubit hashing algorithms. X11 and C11 use the same hashing algorithms, just in different order. Afaik, both were independently developed around the same time. |
|
|
|
Nice. Thanks for the MiriadCoin tip. I have the hash algorithm blocks for a kein or Miriad FPGA miner, but I'm missing the little details like what the initial header fed to the hasher looks like, how the different hash ins/outs connect together (Skein is 512 bits and SHA-256D is 256 bits), if there's anything unique about the difficulty/target calculation, etc. Any advice on where to find these details? I've picked apart source code for other coins before for these details and would rather avoid that frustration if the details are available in a more user friendly form.
The headers should be the same as for Bitcoin. The Skein algo used by Skeincoin and Myriadcoin is actually SHA2(SKEIN512(Data)), in other words one round of SKEIN512, and then SHA2 on the SKEIN512 hash to get 256 bits: sph_skein512_init(&ctx_skein);
sph_skein512(&ctx_skein, (pbegin == pend ? pblank : static_cast<const void*>(&pbegin[0])), (pend - pbegin) * sizeof(pbegin[0]));
sph_skein512_close(&ctx_skein, static_cast<void*>(&hash1));
SHA256((unsigned char*)&hash1, 64, (unsigned char*)&hash2);
|
|
|
|
 I think we should get FLO added to Poloniex's network. Here's a link to the form that must be filled in to issue a request for a coin to be added: https://poloniex.com/coinRequestI requested FLO! So can you |
|
|
|
No mention of Myriad-Groestl
It is not a matter of opinion. It is a matter of FACT the algos are different.
Groestl-coin doesn't use pure Groestl either. It uses 512 bit Groestl x 2, then throws away 256 bits. Myriad uses 512 bit Groestl, then uses SHA256 to get 256 bits. Slightly more secure IMO since there is more entropy in the final result. Either way, both uses 512 bit Groestl then reduces the result to 256 bits through different means. |
|
|
|
|
Doesn't compile on linux from github source.
No rule to make cryptopp/libcryptopp.a
|
|
|
|
[14:13] squaggle: And, more generally, that hash function is a speed benchmark of sprintf.
[14:13] curiouser: yeah seems pretty silly
[14:13] squaggle: sprintf is called 32 times every iteration of the loop.
This is the part that is more worrisome to me. I didn't benchmark, but all the sprintf's and string conversions are extremely slow. Is this deliberate attempt to slow down mining in the wallets/daemons? |
|
|
|
Whats Up there Myriad guys! I just wanted to step in today and wish you guys well. BTW "foodies123" is a really good guy! The UNB Team (especially me) is a fan of the MyriadCoin Group, even if foodies starts swearing like a drunken sailor  Haha, he has a fowl language sometimes, but can't beat a character person rather than an untouchable slimey 0815 guy. We like our foodies. The smartest thing about Myriad is the clever implementation of Foodies (PoGTFO). Lol. "Fowl" language = bird language. We all love foodies and his fowl language |
|
|
|
Always interesting to see new algos. As far as I can tell the hashing algo is: SHA2(Twister(SHA2(X))) where X is the message. From hash.h uint256 hash1;
SHA256((pbegin == pend ? pblank : (unsigned char*)&pbegin[0]), (pend - pbegin) * sizeof(pbegin[0]), (unsigned char*)&hash1);
BitSequence hashval[32];
Hasht1( 256, (const unsigned char*)hash1.ToString().c_str(),256, hashval );
////// BEGIN ////
char s[128]={};
int offset=0;
for( int i= 0; i<32; i++ )
{
offset+=sprintf(s+offset, "%02x", hashval[i] );
}
s[offset+2]='\0';
///// END ////
uint256 hash2;
SHA256((unsigned char*)&hashval, sizeof(hashval), (unsigned char*)&hash2);
return hash2;
}
The part I marked between BEGIN and END seems unnecessary..? From what I read about Twister, it is an AES variant, and it is comparable in speed to SHA2. With the reported hash rates it seems this implementation of Hasht1 could benefit from some optimisation. |
|
|
|
hello i have a problem with my wallet when i open qt then it will close with this error   help me please no one can help me?  Try turning your computer off and on again The wallet is probably still running. Go to task manager and kill the process. |
|
|
|
2 days of solo-mining is a tiny fraction of all coins, and people were very successfully solo-mining the first 2 days. 2 days is nothing compared to the pre-mine of this coin. except for it was more like on the order of 2 fucking weeks before the amoutn of miners were even close on each algo! and then there were shitty pools that had like all the hashrate on skein and no others It's irrelevant. It's still nothing compared to this pre-mine. It's still nothing compared to the total coins that will be produced. |
|
|
|
Untrue. The skein and qubit miners were available for months.
no they fucking werent people didnt even know HOW to mine skein/qubit/groestl it only got popularized AFTER it got instamined I was in early myr and I mined both skein and groestl withing minutes of launch. with only the instructions in OP and the search function on the forum. and how much did you get? probably a lot more than the scrypt/sha256 miners cuz there were a lot fewer miners. cuz there was no win compile. only source. unfair. so for linux miners only no win compile Untrue again. Just read a few posts later (still MONTHS BEFORE myriad), you'll see there was windows binaries too. |
|
|
|
2 days of solo-mining is a tiny fraction of all coins, and people were very successfully solo-mining the first 2 days. 2 days is nothing compared to the pre-mine of this coin. |
|
|
|
How is this anything other than an inferior clone of Myriad with a scammy IPO?
how they are going to scam? only escrow myriad most unfair launch ever Myriad had 0% pre-mine and and had pre-announcement (admittedly it was short). Wallets and source code on launch. You can still mine Myriad because of the slow distribution. How is that the "most unfair launch ever"? 3 out of the 5 algos did not have optimized miners on launch. Pools did also not exist for these algos so only people with enough hashpower could mine these algos on launch. The launch heavily favored people with large rigs and people who know how to make GPU miners. Lack of stable and reliable pools at launch meant that people solo mining less popular algos made much more than people who did not. Untrue. 4 of the 5 algos had optimised miners (Skein and Qubit already had GPU miners). they werent compiled i know a guy that mined 4 millino cuz he dominated skein and groestl and qubit in like 2 days. They were compiled for weeks/months before. You could use the miners from Skeincoin and Qubitcoin. There were no pools. The point remains that lots of people who wanted to mine couldnt during launch. The first pool was available less than an hour after launch. So your only complaint is that you couldn't insta-mine within the first hour. With the quick difficulty adjustment, instamining was also limited. You could also solo-mine perfectly well for the first couple of days. Well, good luck with your pre-mined, pre-sold IPO, clone-coin. Just try to keep the lying and FUD about Myriadcoin to a minimum. no thanks if myriad slogan is fair mining why first 2 weeks were completely not fair mining? dev did not do enough to promote equal mining on all algo and smart user take advantage. i am 90% of qubit hashrate for first 3 days. skein/groestl someone compile gpu miner and no release. besides myriad shit talk came here first. i will shit talk back cuz i like the idea of this coin. So you moan about the first two weeks of Myriad mining (which was open to all), but you support a coin with more than 2 weeks worth of mining PRE-MINED. Lol. it was not open to all? r u stupid? in theory it was open to all but only a few poeple had softawre to mine the new algos Untrue. The skein and qubit miners were available for months. |
|
|
|
How is this anything other than an inferior clone of Myriad with a scammy IPO?
how they are going to scam? only escrow myriad most unfair launch ever Myriad had 0% pre-mine and and had pre-announcement (admittedly it was short). Wallets and source code on launch. You can still mine Myriad because of the slow distribution. How is that the "most unfair launch ever"? 3 out of the 5 algos did not have optimized miners on launch. Pools did also not exist for these algos so only people with enough hashpower could mine these algos on launch. The launch heavily favored people with large rigs and people who know how to make GPU miners. Lack of stable and reliable pools at launch meant that people solo mining less popular algos made much more than people who did not. Untrue. 4 of the 5 algos had optimised miners (Skein and Qubit already had GPU miners). they werent compiled i know a guy that mined 4 millino cuz he dominated skein and groestl and qubit in like 2 days. They were compiled for weeks/months before. You could use the miners from Skeincoin and Qubitcoin. There were no pools. The point remains that lots of people who wanted to mine couldnt during launch. The first pool was available less than an hour after launch. So your only complaint is that you couldn't insta-mine within the first hour. With the quick difficulty adjustment, instamining was also limited. You could also solo-mine perfectly well for the first couple of days. Well, good luck with your pre-mined, pre-sold IPO, clone-coin. Just try to keep the lying and FUD about Myriadcoin to a minimum. no thanks if myriad slogan is fair mining why first 2 weeks were completely not fair mining? dev did not do enough to promote equal mining on all algo and smart user take advantage. i am 90% of qubit hashrate for first 3 days. skein/groestl someone compile gpu miner and no release. besides myriad shit talk came here first. i will shit talk back cuz i like the idea of this coin. So you moan about the first two weeks of Myriad mining (which was open to all), but you support a coin with more than 2 weeks worth of mining PRE-MINED. Lol. |
|
|
|
How is this anything other than an inferior clone of Myriad with a scammy IPO?
how they are going to scam? only escrow myriad most unfair launch ever Myriad had 0% pre-mine and and had pre-announcement (admittedly it was short). Wallets and source code on launch. You can still mine Myriad because of the slow distribution. How is that the "most unfair launch ever"? 3 out of the 5 algos did not have optimized miners on launch. Pools did also not exist for these algos so only people with enough hashpower could mine these algos on launch. The launch heavily favored people with large rigs and people who know how to make GPU miners. Lack of stable and reliable pools at launch meant that people solo mining less popular algos made much more than people who did not. Untrue. 4 of the 5 algos had optimised miners (Skein and Qubit already had GPU miners). they werent compiled i know a guy that mined 4 millino cuz he dominated skein and groestl and qubit in like 2 days. They were compiled for weeks/months before. You could use the miners from Skeincoin and Qubitcoin. There were no pools. The point remains that lots of people who wanted to mine couldnt during launch. The first pool was available less than an hour after launch. So your only complaint is that you couldn't insta-mine within the first hour. With the quick difficulty adjustment, instamining was also limited. You could also solo-mine perfectly well for the first couple of days. Well, good luck with your pre-mined, pre-sold IPO, clone-coin. Just try to keep the lying and FUD about Myriadcoin to a minimum. |
|
|
|
How is this anything other than an inferior clone of Myriad with a scammy IPO?
how they are going to scam? only escrow myriad most unfair launch ever Myriad had 0% pre-mine and and had pre-announcement (admittedly it was short). Wallets and source code on launch. You can still mine Myriad because of the slow distribution. How is that the "most unfair launch ever"? 3 out of the 5 algos did not have optimized miners on launch. Pools did also not exist for these algos so only people with enough hashpower could mine these algos on launch. The launch heavily favored people with large rigs and people who know how to make GPU miners. Lack of stable and reliable pools at launch meant that people solo mining less popular algos made much more than people who did not. Untrue. 4 of the 5 algos had optimised miners (Skein and Qubit already had GPU miners). they werent compiled i know a guy that mined 4 millino cuz he dominated skein and groestl and qubit in like 2 days. They were compiled for weeks/months before. You could use the miners from Skeincoin and Qubitcoin. |
|
|
|
How is this anything other than an inferior clone of Myriad with a scammy IPO?
how they are going to scam? only escrow myriad most unfair launch ever Myriad had 0% pre-mine and and had pre-announcement (admittedly it was short). Wallets and source code on launch. You can still mine Myriad because of the slow distribution. How is that the "most unfair launch ever"? 3 out of the 5 algos did not have optimized miners on launch. Pools did also not exist for these algos so only people with enough hashpower could mine these algos on launch. The launch heavily favored people with large rigs and people who know how to make GPU miners. Lack of stable and reliable pools at launch meant that people solo mining less popular algos made much more than people who did not. Untrue. 4 of the 5 algos had optimised miners (Skein and Qubit already had GPU miners). |
|
|
|
How is this anything other than an inferior clone of Myriad with a scammy IPO?
how they are going to scam? only escrow myriad most unfair launch ever Myriad had 0% pre-mine and and had pre-announcement (admittedly it was short). Wallets and source code on launch. You can still mine Myriad because of the slow distribution. How is that the "most unfair launch ever"? |
|
|
|
Yea, there's something wrong in these lines in main.cpp: if (vtx[0].GetValueOut() > GetBlockValue(pindex->pprev->nBits, pindex->pprev->nHeight, nFees))
return state.DoS(100, error("ConnectBlock() : coinbase pays too much (actual=%"PRI64d" vs limit=%"PRI64d")", vtx[0].GetValueOut(), GetBlockValue(pindex->pprev->nBits, pindex->pprev->nHeight, nFees)));
and int64 reward = GetBlockValue(pindexPrev->nBits,pindexPrev->nHeight+1, 0);
It's using the difficulty/height from the previous block instead of the current block. |
|
|
|
|
