[ANN] [SUMO] SUMOKOIN - 🔏 Digital Cash For Highly-Confidential Transactions 🔏

[sumogr]

Sumocoind stack at 116522 . Daemon version is 0.3.0.  What is going on?

delete the p2pstate.bin file and restart your wallet (Programdata\sumokoin). It is trying to connect to not updated nodes

[cdrc-]

can anybody post working xmr-stak amd.txt for RX VEGA 64 .....
for my old config got this error .. probably due wrong intensity settings ...
[2018-04-05 13:52:32] : WARNING: backend NVIDIA disabled.
[2018-04-05 13:52:32] : Compiling code and initializing GPUs. This will take a while...
[2018-04-05 13:52:32] : Device 0 work size 8 / 32.
[2018-04-05 13:52:32] : Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer.
[2018-04-05 13:52:32] : WARNING: AMD device not found
[2018-04-05 13:52:32] : WARNING: backend AMD disabled.
[2018-04-05 13:52:32] : ERROR: No miner backend enabled.

as a start, you can take your old config and divide intensity by 2. That should start the miner. After that, optimization process starts (it seems that getting intensity above 1000 is tricky)

EDIT: you can also check with this telegram group: https://t.me/joinchat/GzwfBFHKcnXYU1jw24kvXw

[hitmandn]

Sumocoind stack at 116522 . Daemon version is 0.3.0.  What is going on?

delete the p2pstate.bin file and restart your wallet (Programdata\sumokoin). It is trying to connect to not updated nodes

WTF updated, i can't not mine, downloaded  xmr-stak  virus found.

Anythings elses, thanks

[m42orion]

can anybody post working xmr-stak amd.txt for RX VEGA 64 .....
for my old config got this error .. probably due wrong intensity settings ...
[2018-04-05 13:52:32] : WARNING: backend NVIDIA disabled.
[2018-04-05 13:52:32] : Compiling code and initializing GPUs. This will take a while...
[2018-04-05 13:52:32] : Device 0 work size 8 / 32.
[2018-04-05 13:52:32] : Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer.
[2018-04-05 13:52:32] : WARNING: AMD device not found
[2018-04-05 13:52:32] : WARNING: backend AMD disabled.
[2018-04-05 13:52:32] : ERROR: No miner backend enabled.

as a start, you can take your old config and divide intensity by 2. That should start the miner. After that, optimization process starts (it seems that getting intensity above 1000 is tricky)

EDIT: you can also check with this telegram group: https://t.me/joinchat/GzwfBFHKcnXYU1jw24kvXw

I try made two thread with 960 intesity, but i got about 1200H/s ..... do you have sb better result for vega and sumo ?

[cdrc-]

can anybody post working xmr-stak amd.txt for RX VEGA 64 .....
for my old config got this error .. probably due wrong intensity settings ...
[2018-04-05 13:52:32] : WARNING: backend NVIDIA disabled.
[2018-04-05 13:52:32] : Compiling code and initializing GPUs. This will take a while...
[2018-04-05 13:52:32] : Device 0 work size 8 / 32.
[2018-04-05 13:52:32] : Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer.
[2018-04-05 13:52:32] : WARNING: AMD device not found
[2018-04-05 13:52:32] : WARNING: backend AMD disabled.
[2018-04-05 13:52:32] : ERROR: No miner backend enabled.

as a start, you can take your old config and divide intensity by 2. That should start the miner. After that, optimization process starts (it seems that getting intensity above 1000 is tricky)

EDIT: you can also check with this telegram group: https://t.me/joinchat/GzwfBFHKcnXYU1jw24kvXw

I try made two thread with 960 intesity, but i got about 1200H/s ..... do you have sb better result for vega and sumo ?

Expect to lose around 30% of H/s with CN-Heavy. On my side, I went down from 1650 to 1150 @ 115W with my Vega 56... So I guess this drop is perfectly normal and matches average values.

EDIT: Try with 880/880, some people got better results with this setting

[m42orion]

can anybody post working xmr-stak amd.txt for RX VEGA 64 .....
for my old config got this error .. probably due wrong intensity settings ...
[2018-04-05 13:52:32] : WARNING: backend NVIDIA disabled.
[2018-04-05 13:52:32] : Compiling code and initializing GPUs. This will take a while...
[2018-04-05 13:52:32] : Device 0 work size 8 / 32.
[2018-04-05 13:52:32] : Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer.
[2018-04-05 13:52:32] : WARNING: AMD device not found
[2018-04-05 13:52:32] : WARNING: backend AMD disabled.
[2018-04-05 13:52:32] : ERROR: No miner backend enabled.

as a start, you can take your old config and divide intensity by 2. That should start the miner. After that, optimization process starts (it seems that getting intensity above 1000 is tricky)

EDIT: you can also check with this telegram group: https://t.me/joinchat/GzwfBFHKcnXYU1jw24kvXw

I try made two thread with 960 intesity, but i got about 1200H/s ..... do you have sb better result for vega and sumo ?

Expect to lose around 30% of H/s with CN-Heavy. On my side, I went down from 1650 to 1150 @ 115W with my Vega 56... So I guess this drop is perfectly normal and matches average values.

EDIT: Try with 880/880, some people got better results with this setting

thx for reply ... i tried 880/880 and u are right ... this setup give me better results than 960 .... My old hash rate on V64 was 1750@135W

[zot57]

Why is wallet installing full node on my C drive on which I have SDD with low space? Why wallet didn't simply ask for directory to install this?
I don't have enough space on my SSD so what do I do now? any light Wallets for Windows 64?

[cryptomaxsun]

I repeat, which miner to use?

I updated the pool does not work, no starts, everything is in accordance with the instructions, what's the problem?
https://github.com/sumoprojects/cryptonote-sumokoin-pool/commit/55242c71fb87f80dd6b61d276d6dc20a594cbce6

[cdrc-]

Why is wallet installing full node on my C drive on which I have SDD with low space? Why wallet didn't simply ask for directory to install this?
I don't have enough space on my SSD so what do I do now? any light Wallets for Windows 64?

Lightweight wallet will be released soon, according to what I've heard (probably a week or two? - to be confirmed by a more official way, though). If you have an android phone and a wifi connection, you may use the android wallet in the mean time.

[miticoin]

What happened to the network, so it went down so much, did many not update the programs, so while they done it...

[Germining]

I repeat, which miner to use?

I updated the pool does not work, no starts, everything is in accordance with the instructions, what's the problem?
https://github.com/sumoprojects/cryptonote-sumokoin-pool/commit/55242c71fb87f80dd6b61d276d6dc20a594cbce6

Could you please check our reddit? Xmr stack and xmrig are updated and can be used.

[miticoin]

I repeat, which miner to use?

I updated the pool does not work, no starts, everything is in accordance with the instructions, what's the problem?
https://github.com/sumoprojects/cryptonote-sumokoin-pool/commit/55242c71fb87f80dd6b61d276d6dc20a594cbce6

Try this pool, https://pool.sumokoin.com/#  and update xmr stak.

[cryptomaxsun]

I repeat, which miner to use?

I updated the pool does not work, no starts, everything is in accordance with the instructions, what's the problem?
https://github.com/sumoprojects/cryptonote-sumokoin-pool/commit/55242c71fb87f80dd6b61d276d6dc20a594cbce6

Try this pool, https://pool.sumokoin.com/#  and update xmr stak.

my pool does not start, why do developers ignore obvious problems?

[miticoin]

On this pool https://sumokoin.hashvault.pro/en/#!/dashboard  i have ERROR ... that was the problem..

[sumogr]

I repeat, which miner to use?

I updated the pool does not work, no starts, everything is in accordance with the instructions, what's the problem?
https://github.com/sumoprojects/cryptonote-sumokoin-pool/commit/55242c71fb87f80dd6b61d276d6dc20a594cbce6

Try this pool, https://pool.sumokoin.com/#  and update xmr stak.

my pool does not start, why do developers ignore obvious problems?

Your pool wont start cause you cannot make it start. Every other pool has updated. There is no problem that devs should be looking into

[UMINEMEME]

Sumocoind stack at 116522 . Daemon version is 0.3.0.  What is going on?

delete the p2pstate.bin file and restart your wallet (Programdata\sumokoin). It is trying to connect to not updated nodes

WTF updated, i can't not mine, downloaded  xmr-stak  virus found.

Anythings elses, thanks

I repeat, which miner to use?

I updated the pool does not work, no starts, everything is in accordance with the instructions, what's the problem?
https://github.com/sumoprojects/cryptonote-sumokoin-pool/commit/55242c71fb87f80dd6b61d276d6dc20a594cbce6

This claymore is working for me, you'll have to make exceptions in your windows defender, make a new folder and just make an exception for the entire folder if you can: https://mega.nz/#F!Hg4g1bLT!4Upg8GNiEZYCaZ04XVh_yg

I found it here: https://bitcointalk.org/index.php?topic=647251.0

I'm mining with a small pool @ http://sumo.aleajecta.com/ with no problems

I can't get xmr stak to work on my computer so maybe claymore will work for you too.

[Herp-a-derp]

Well, what is the meaning of this fork? Does someone really buy anyone who does not need a crypto currency

[annapotpot]

Difficulty went down. Is it because of the ASICs or the miners forgot to update their miners?

Check the difficulty here: https://www.difficultychart.com/sumokoin

[sumogr]

Difficulty went down. Is it because of the ASICs or the miners forgot to update their miners?

Check the difficulty here: https://www.difficultychart.com/sumokoin

ASICs (miners that havent updated their miners are sure to have spotted that something has changed by now)

[rodyw]

Difficulty went down. Is it because of the ASICs or the miners forgot to update their miners?

Check the difficulty here: https://www.difficultychart.com/sumokoin

ASICs (miners that havent updated their miners are sure to have spotted that something has changed by now)

Well, that was what I would think also. But my pool is not one of the biggest and it's flushed with bad shares from my miners. I put a warning on my homepage and announced it in the discord channel, but nothing...