Topic: [ANN][CRW] CROWN (SHA256) | Platform | Governance | Systemnodes | Masternodes | - page 231. (Read 316957 times)
June 20, 2016, 10:44:17 PM
Have we been marked for delisting for a while or did it just happen? (c-cex)
June 20, 2016, 11:45:24 AM
Expect hashrate to rise, difficulty dropped bellow 1m
June 18, 2016, 09:25:21 AM
Another e1ightspace classic!
June 18, 2016, 02:55:00 AM
very nice job - will put it on our web soon! Thanks
Thanks eightspace! Bounty was sent
Cheers. Do you like the video? June 18, 2016, 01:15:44 AM
Thanks eightspace! Bounty was sent
Cheers. Do you like the video? June 18, 2016, 01:15:09 AM
Thanks eightspace! Bounty was sent
June 17, 2016, 06:12:15 AM
I made the video today and tomorrow I will upload it. (Everyone in my home was complaining of slow internet when I tried to upload today)
I sent a PM to crowncoin_knight regarding payment.
I sent a PM to crowncoin_knight regarding payment.
June 16, 2016, 12:45:40 PM
It has been updated
Holy shit, that is a big deal! Looking into it now.
Issue noted and will be resolved with the coming official update
Not a huge deal, but the Github link in the OP seems to be outdated.
Holy shit, that is a big deal! Looking into it now.
Issue noted and will be resolved with the coming official update
June 16, 2016, 09:05:13 AM
The crw merged mining function was taken from namecoin. Can you try connecting namecoin to your pool if it does the same?
Hi,
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
Is it known if this problem will be resolved?
Yes, this issue has been taken note of. It's one of the priority's for the dev team. We want as many Merge miners to mine crowncoin as we can, so this issue will be corrected. It would be super helpful if you could put some hash toward crowncoin and enforce the new linux client
This still hasn't been fixed? After two months? No wonder merge mine pools don't add CRW. Miners won't mine CRW if it breaks their other coins either.
This should have been fixed within hours, not months.
Is this for some particular pool software? I merge mine CRW, MYR and UNO in my personal p2pool, and haven't had any trouble hitting UNO and MYR blocks.
Maybe a quick conversation with zpool about both of your pools codes would clear things up.
If Crackfoo cant but zyzzyva can mine all coins thogether, then it's not something wrong with our code, maybe Crackfoos pool code needs to change
I don't know what pool software crackfoo is running, but I do know than UNOMP has a known issue that it can only merge mine one coin. If you specify more than one merge mined coin to UNOMP, it'll act like everything's fine, but all the merge mine coins except one will reject found blocks. That's why I switched to p2pool. I'm not sure where software other than UNOMP and p2pool stands on this, though.
Great thanks for the info!
Do you have the source code link for the p2pool software?
I'm running the stock p2pool, as available here: https://github.com/p2pool/p2pool
June 16, 2016, 08:55:56 AM
The crw merged mining function was taken from namecoin. Can you try connecting namecoin to your pool if it does the same?
Hi,
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
Is it known if this problem will be resolved?
Yes, this issue has been taken note of. It's one of the priority's for the dev team. We want as many Merge miners to mine crowncoin as we can, so this issue will be corrected. It would be super helpful if you could put some hash toward crowncoin and enforce the new linux client
This still hasn't been fixed? After two months? No wonder merge mine pools don't add CRW. Miners won't mine CRW if it breaks their other coins either.
This should have been fixed within hours, not months.
Is this for some particular pool software? I merge mine CRW, MYR and UNO in my personal p2pool, and haven't had any trouble hitting UNO and MYR blocks.
Maybe a quick conversation with zpool about both of your pools codes would clear things up.
If Crackfoo cant but zyzzyva can mine all coins thogether, then it's not something wrong with our code, maybe Crackfoos pool code needs to change
I don't know what pool software crackfoo is running, but I do know than UNOMP has a known issue that it can only merge mine one coin. If you specify more than one merge mined coin to UNOMP, it'll act like everything's fine, but all the merge mine coins except one will reject found blocks. That's why I switched to p2pool. I'm not sure where software other than UNOMP and p2pool stands on this, though.
Great thanks for the info!
Do you have the source code link for the p2pool software?
June 16, 2016, 07:12:21 AM
The crw merged mining function was taken from namecoin. Can you try connecting namecoin to your pool if it does the same?
Hi,
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
Is it known if this problem will be resolved?
Yes, this issue has been taken note of. It's one of the priority's for the dev team. We want as many Merge miners to mine crowncoin as we can, so this issue will be corrected. It would be super helpful if you could put some hash toward crowncoin and enforce the new linux client
This still hasn't been fixed? After two months? No wonder merge mine pools don't add CRW. Miners won't mine CRW if it breaks their other coins either.
This should have been fixed within hours, not months.
Is this for some particular pool software? I merge mine CRW, MYR and UNO in my personal p2pool, and haven't had any trouble hitting UNO and MYR blocks.
Maybe a quick conversation with zpool about both of your pools codes would clear things up.
If Crackfoo cant but zyzzyva can mine all coins thogether, then it's not something wrong with our code, maybe Crackfoos pool code needs to change
I don't know what pool software crackfoo is running, but I do know than UNOMP has a known issue that it can only merge mine one coin. If you specify more than one merge mined coin to UNOMP, it'll act like everything's fine, but all the merge mine coins except one will reject found blocks. That's why I switched to p2pool. I'm not sure where software other than UNOMP and p2pool stands on this, though.
June 16, 2016, 04:17:41 AM
The crw merged mining function was taken from namecoin. Can you try connecting namecoin to your pool if it does the same?
Hi,
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
Is it known if this problem will be resolved?
Yes, this issue has been taken note of. It's one of the priority's for the dev team. We want as many Merge miners to mine crowncoin as we can, so this issue will be corrected. It would be super helpful if you could put some hash toward crowncoin and enforce the new linux client
This still hasn't been fixed? After two months? No wonder merge mine pools don't add CRW. Miners won't mine CRW if it breaks their other coins either.
This should have been fixed within hours, not months.
Is this for some particular pool software? I merge mine CRW, MYR and UNO in my personal p2pool, and haven't had any trouble hitting UNO and MYR blocks.
Maybe a quick conversation with zpool about both of your pools codes would clear things up.
If Crackfoo cant but zyzzyva can mine all coins thogether, then it's not something wrong with our code, maybe Crackfoos pool code needs to change
June 16, 2016, 02:01:50 AM
The crw merged mining function was taken from namecoin. Can you try connecting namecoin to your pool if it does the same?
Hi,
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
Is it known if this problem will be resolved?
Yes, this issue has been taken note of. It's one of the priority's for the dev team. We want as many Merge miners to mine crowncoin as we can, so this issue will be corrected. It would be super helpful if you could put some hash toward crowncoin and enforce the new linux client
This still hasn't been fixed? After two months? No wonder merge mine pools don't add CRW. Miners won't mine CRW if it breaks their other coins either.
This should have been fixed within hours, not months.
Is this for some particular pool software? I merge mine CRW, MYR and UNO in my personal p2pool, and haven't had any trouble hitting UNO and MYR blocks.
I want to take responsibility to solve this problem but I need some help understanding exactly what the problem is. I don't know the history. How can it be recreated? What needs to change?
June 15, 2016, 04:28:52 PM
The crw merged mining function was taken from namecoin. Can you try connecting namecoin to your pool if it does the same?
Hi,
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
Is it known if this problem will be resolved?
Yes, this issue has been taken note of. It's one of the priority's for the dev team. We want as many Merge miners to mine crowncoin as we can, so this issue will be corrected. It would be super helpful if you could put some hash toward crowncoin and enforce the new linux client
This still hasn't been fixed? After two months? No wonder merge mine pools don't add CRW. Miners won't mine CRW if it breaks their other coins either.
This should have been fixed within hours, not months.
Is this for some particular pool software? I merge mine CRW, MYR and UNO in my personal p2pool, and haven't had any trouble hitting UNO and MYR blocks.
June 15, 2016, 04:10:22 PM
Hey guys, did you need any more videos/tutorials made?
If so please message me. I will be able to reply tomorrow morning. Night.
If so please message me. I will be able to reply tomorrow morning. Night.
Hold that thought.
I'll contact you very soon. We will 100% want a video doing for Thrones.
But we arnt quite ready yet. Most Thrones will be windows/linux vps.
So we're going to need windows wallet builds for you to demonstrate hosting a Throne using windows.
Cheers man, i'll be intouch
I only said no because I had to study for exams but now I'm on holidays.
I also recently had to sell my CRW so I'm not sure if I should be taken of the knight list, though I do plan on making back that investment through making you guys videos.
Edit: Ah it's the paper wallet tutorial. Do you guys want that done?
June 15, 2016, 12:14:23 PM
The crw merged mining function was taken from namecoin. Can you try connecting namecoin to your pool if it does the same?
Hi,
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
I have recently discovered that if I have CRW running on my sha port, it blocks UNO and MYR from generating blocks. As soon as I disabled CRW, they began creating blocks again...
Is there a known conflict with these coins? Is there some conflict with chainid's or something?
Some insight would be great,
Thanks!
Is it known if this problem will be resolved?
Yes, this issue has been taken note of. It's one of the priority's for the dev team. We want as many Merge miners to mine crowncoin as we can, so this issue will be corrected. It would be super helpful if you could put some hash toward crowncoin and enforce the new linux client
This still hasn't been fixed? After two months? No wonder merge mine pools don't add CRW. Miners won't mine CRW if it breaks their other coins either.
This should have been fixed within hours, not months.
June 15, 2016, 09:00:44 AM
Not a huge deal, but the Github link in the OP seems to be outdated.
Holy shit, that is a big deal! Looking into it now.
Issue noted and will be resolved with the coming official update
June 15, 2016, 08:23:11 AM
Hey guys, did you need any more videos/tutorials made?
If so please message me. I will be able to reply tomorrow morning. Night.
If so please message me. I will be able to reply tomorrow morning. Night.
Hold that thought.
I'll contact you very soon. We will 100% want a video doing for Thrones.
But we arnt quite ready yet. Most Thrones will be windows/linux vps.
So we're going to need windows wallet builds for you to demonstrate hosting a Throne using windows.
Cheers man, i'll be intouch
June 15, 2016, 08:05:58 AM
Hey guys, did you need any more videos/tutorials made?
If so please message me. I will be able to reply tomorrow morning. Night.
If so please message me. I will be able to reply tomorrow morning. Night.
Jump to: