 Show Posts
|
|
Pages: [1]
|
|
Greetings all,
What exchange and currency pair do you recommend? I have been trying to sell this coin on several of the listed exchanges but market liquidity seems very low and my orders are just sitting there.
Thanks in advance.
|
|
|
|
As a follow up to this post, I am mining Haven. Some additional observations - I am seeing this same behavior with all my RX Vega 56 cards, doesn't matter what vendor or in what machine they are installed. Interestingly, in one machine I have both Vega 56's and RX 580's installed. When the "issue" occurs, only the Vega 56's hashrate drops....RX 580's are unaffected. Hello,
Am noticing an issue after upgrading to Cast XMR 1.6+....after running for several minutes (sometimes as long as an hour) the hashrate on my rigs (4xRX Vega 56) will drop by 30%. In tandem with this drop, the miner will report at least one "network error." Other AMD rigs I have running the same version of Cast XMR (but 10xRX 580's) are unaffected as are any NVIDIA rigs. I have played for a long time with the overclocking settings on the RX Vega 56's, and nothing seems to help with this issue. When the rigs with the RX Vega 56's "hiccup" the network error they drop from roughly 1500 H/s to 1200 H/s. Have also tried the Adrenaline 18.5.1, 18.11.1, and 18.12.1 with the same results.
Conclusion I am coming to at this point is that there is a bug in version 1.66 which causes the RX Vega 56's to "downshift" if there is a network error...is anyone else seeing the same behavior?
|
|
|
|
|
Hello,
Am noticing an issue after upgrading to Cast XMR 1.6+....after running for several minutes (sometimes as long as an hour) the hashrate on my rigs (4xRX Vega 56) will drop by 30%. In tandem with this drop, the miner will report at least one "network error." Other AMD rigs I have running the same version of Cast XMR (but 10xRX 580's) are unaffected as are any NVIDIA rigs. I have played for a long time with the overclocking settings on the RX Vega 56's, and nothing seems to help with this issue. When the rigs with the RX Vega 56's "hiccup" the network error they drop from roughly 1500 H/s to 1200 H/s. Have also tried the Adrenaline 18.5.1, 18.11.1, and 18.12.1 with the same results.
Conclusion I am coming to at this point is that there is a bug in version 1.66 which causes the RX Vega 56's to "downshift" if there is a network error...is anyone else seeing the same behavior?
|
|
|
|
|
Dev Team,
Can you comment on the brutal price slide in BTXC over the last 72 hrs? An update on this project and dates for some future milestones would be a good idea about now...
|
|
|
|
Hey Devs! How about a brief update? any news about project ?  huh they built two platforms in a month no project has ever done the same what more news do you want? this is actual project not the shit coin you used to any news about project ? huh they built two platforms in a month no project has ever done the same what more news do you want? this is actual project not the shit coin you used to |
|
|
|
I like the concept of this project. Well prepared team and business. I hope you rock in cryptocurrency market and create very cool product. My all blessing with you.
But now I have seen some interested investors here in the ann thread and this is great help to the project if more and more investors are going to check and invest. I am expecting for more good updates. I agree...I think the dev team is making a mistake by not setting any future deadlines or announcements. Although the currency will certainly get punished if they fail to meet those deadlines / expectations, they will have difficulty attracting more investors, and generating excitement about Xorn, without setting and then achieving various goals. It would be a shame if this crypto died, as it seems (in my experience) to be fairly fast and stable. |
|
|
|
BEWARE INJECS SEEMS TO BE A SCAM
Why do you believe it is a scam? |
|
|
|
Just an update on this....the only algo I am having trouble with is Heavy, and specifically Sumokoin. This is universal, across all my machines running Cast. Have tested both with EasyHash and HashVault with same result. Anyone have a solution to this?
Geez, really don’t know what to tell you. I’ve never mined Sumo, but been mining Haven with little problem, and it also uses Heavy. Been running Cast v 1.0. I am also mining haven but with 9.6. I tried the latest version (v 1.0) but was having all sorts of stability problems. Even upgrading my video drivers to 18.3.4 I still had issues. I don't want to sound like I am bashing Cast because a) it is "strange" that the Sumokoin pools are generating an error suggesting the you use XMRig or XMR-STAK (but no message of Cast), b) Cast 1.0.0.0 Cryptonightv7 with the --nomem flag is hashing for me at around 2000 KH/s with the 18.3.4 driver, and c) I have, for some time, found Cast to be a very solid program that just runs (and I think the devfee is reasonable). The above being said, I would like to hear from the Cast development team on the Sumo issue....wouldn't be such a big deal but Sumo is one of the more profitable cryptos right now. Sumo is cryptonight heavy. Use the proper flag in your batch file. I have. It still doesn't work. "support for CryptoNight Heavy set --algo=2 to mine" is not working. --algo=1 does work as to other variants. --algo=2 does not work. |
|
|
|
Just an update on this....the only algo I am having trouble with is Heavy, and specifically Sumokoin. This is universal, across all my machines running Cast. Have tested both with EasyHash and HashVault with same result. Anyone have a solution to this?
Geez, really don’t know what to tell you. I’ve never mined Sumo, but been mining Haven with little problem, and it also uses Heavy. Been running Cast v 1.0. I am also mining haven but with 9.6. I tried the latest version (v 1.0) but was having all sorts of stability problems. Even upgrading my video drivers to 18.3.4 I still had issues. I don't want to sound like I am bashing Cast because a) it is "strange" that the Sumokoin pools are generating an error suggesting the you use XMRig or XMR-STAK (but no message of Cast), b) Cast 1.0.0.0 Cryptonightv7 with the --nomem flag is hashing for me at around 2000 KH/s with the 18.3.4 driver, and c) I have, for some time, found Cast to be a very solid program that just runs (and I think the devfee is reasonable). The above being said, I would like to hear from the Cast development team on the Sumo issue....wouldn't be such a big deal but Sumo is one of the more profitable cryptos right now. |
|
|
|
Hello Everyone,
I am a fan of Cast XMR, running it on several machines. I have run into trouble lately with the fork however, beginning with version 0.92. Most issues I was able to workaround / resolve, but the one remaining issue is using the CryptoNight-Heavy algo (Sumokoin). With version 0.96, I was able to manually set the algo using =-2. Hashrates were low, however, hovering in the 1500 KHash/s range. When I upgraded to 1.0.0, Cast seemed to disregard the flag (at least there was no confirmation on startup it was using the Heavy algo) and immediately generated a socket error when trying to connect to the pool (on Hashvault, it tells me there has been a fork and that I should be using a different miner). I have been able to reproduce this issue on several machines with no apparent workaround.
Anyone have a solution to this issue or do we need to wait until the release of the next version?
Thanks in advance,
Fox
Algo is 2, not -2. Sorry, typo...meant =2. Still not working. Just an update on this....the only algo I am having trouble with is Heavy, and specifically Sumokoin. This is universal, across all my machines running Cast. Have tested both with EasyHash and HashVault with same result. Anyone have a solution to this? |
|
|
|
Hello Everyone,
I am a fan of Cast XMR, running it on several machines. I have run into trouble lately with the fork however, beginning with version 0.92. Most issues I was able to workaround / resolve, but the one remaining issue is using the CryptoNight-Heavy algo (Sumokoin). With version 0.96, I was able to manually set the algo using =-2. Hashrates were low, however, hovering in the 1500 KHash/s range. When I upgraded to 1.0.0, Cast seemed to disregard the flag (at least there was no confirmation on startup it was using the Heavy algo) and immediately generated a socket error when trying to connect to the pool (on Hashvault, it tells me there has been a fork and that I should be using a different miner). I have been able to reproduce this issue on several machines with no apparent workaround.
Anyone have a solution to this issue or do we need to wait until the release of the next version?
Thanks in advance,
Fox
Algo is 2, not -2. Sorry, typo...meant =2. Still not working. |
|
|
|
i have an error with sumokoin, i've already set --algo=2 but it's not working with sumokoin.hashvault.pro, somebody else?
[10:02:01] Connected to pool.
[10:02:01] SOCKET ERROR - Sumo has forked to new algo. You should use XMRig 2.6 or XMR-Stak 2.4.2.
[10:02:01] SOCKET ERROR - RECEIVE error: Operazione di blocco interrotta da una chiamata a WSACancelBlockingCall.
[10:02:01] Connecting to Pool failed. Retrying in 20 secs ...
Yes, having the same problem as of version 1.0.0........ |
|
|
|
|
Hello Everyone,
I am a fan of Cast XMR, running it on several machines. I have run into trouble lately with the fork however, beginning with version 0.92. Most issues I was able to workaround / resolve, but the one remaining issue is using the CryptoNight-Heavy algo (Sumokoin). With version 0.96, I was able to manually set the algo using =-2. Hashrates were low, however, hovering in the 1500 KHash/s range. When I upgraded to 1.0.0, Cast seemed to disregard the flag (at least there was no confirmation on startup it was using the Heavy algo) and immediately generated a socket error when trying to connect to the pool (on Hashvault, it tells me there has been a fork and that I should be using a different miner). I have been able to reproduce this issue on several machines with no apparent workaround.
Anyone have a solution to this issue or do we need to wait until the release of the next version?
Thanks in advance,
Fox
|
|
|
|
|
Hello,
I am having some difficulties with the wallet since 1.2.2....I attempted to send coins to an exchange yesterday, and they never were added to the blockchain. In investigating further and checking "details", the wallet showed zero confirmation but there is a transaction hash of A09C29BC917BC3877E423354948BAFE00D9118022230E23D65AD43E2F3A5E1ED. I thought that maybe this was a sync problem, so I upgraded the wallet to version 1.2.3. Now, however, in the details of the two most recent transactions (one incoming and the beforementioned outgoing transaction) the transactions show as "cancelled." The wallet balance has not, however, been changed to reflect those transactions being cancelled. As far as the wallet is concerned at the moment, the coins are lost.
Any idea what is going on here? In particular, I would like to recover the coins that I attempted to send to the exchange. Thanks in advance.
|
|
|
|
|
