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

[Germining]

For all of you who don't know: Sumo will have a Mobile Wallet soon. Check the new community twitter account for further info 

[Wekkel]

For all of you who don't know: Sumo will have a Mobile Wallet soon. Check the new community twitter account for further info 

The APK won't install yet but exciting that mobile wallets are close.

[syncmaster913n]

For all of you who don't know: Sumo will have a Mobile Wallet soon. Check the new community twitter account for further info  

The APK won't install yet but exciting that mobile wallets are close.

Just to be clear: this mobile wallet which is about to be released is not the official wallet promised by the core devs. It's an alternative one released by our community devs.

[d3athgu1s3]

Look like hashing rate is catching up now. Starting getting harder and harder to mine.

[rodyw]

Look like hashing rate is catching up now. Starting getting harder and harder to mine.

Yep, it's just no fun anymore to mine with my small pool. Last block found a week ago! 

[Germining]

Price goes up and HR follows. That's the law of crypto-nature

[Mattthev]

For all of you who don't know: Sumo will have a Mobile Wallet soon. Check the new community twitter account for further info 

Nice! Monerujo port :3

[wtfpdf]

any idea who is the big guy destroying the whole mining effort?
EDIT: nicehash?

[cryptomaxsun]

help is needed. abnormally low pool luck http://sumo.ms-pool.net.ua/# . the miners fled.
who can - help with hashrate.

[h0g0f0g0]

Merry Christmas folks!

[cdrc-]

help is needed. abnormally low pool luck http://sumo.ms-pool.net.ua/# . the miners fled.
who can - help with hashrate.

Hello,

I just switched to your pool momentarily. Let's see if it attracts some more miners. I'll stay for 2 blocks at least, perhaps more if you can't get more rigs on your pool (I see that your pool was a huge one few weeks ago: what happened?).

@All sumo miners/enthusiasts: Merry Christmas

[cryptomaxsun]

help is needed. abnormally low pool luck http://sumo.ms-pool.net.ua/# . the miners fled.
who can - help with hashrate.

Hello,

I just switched to your pool momentarily. Let's see if it attracts some more miners. I'll stay for 2 blocks at least, perhaps more if you can't get more rigs on your pool (I see that your pool was a huge one few weeks ago: what happened?).

@All sumo miners/enthusiasts: Merry Christmas

Thanks you! Luck left the pool and the miners fled. I already wrote, in the network of sumo very low luck.
I do not know of any coins with such low luck. Look at the luck of other coins on different pools.

[Mattthev]

I found this voting so I add SUMO, this exchange seems little bit strange but I haven't checked it much...
So if devs or community don't agree with listing there I will delete it.

https://nextexchange.featureupvote.com/suggestions/3059/sumokoin-sumo
It still need moderation so it should be active in hours maybe days...

[cdrc-]

-snip-

I see that you use fixed difficulty. For instance, if you start on diff 500, you constantly stay at 500. Other pools have a more dynamic approach. Is there a way I can increase diff manually? My GPU on diff 10000 sends your pool hashes every 6.4 seconds, my CPU on diff 5000 sends every 14.5 seconds... on official pool, my CPU stabilizes around dif 30000 and my GPU around 150000.

[rodyw]

I try to transfer some Sumo with the sumo-wallet-cli (Sumokoin 'Sapporo' (v0.2.0.0-release)), but every time it crashes with 'Segmentation fault (core dumped)'. I am using the command transfer Sumoo-address-receiver amount.

There is a message that the default mixin 12 is being used and I have to confirm that I don't want to use a payment id. After that it crashes. My wallet has enough unlocked balance, the blockchain is fully synced, so what is going wrong?

[mrtrevorphilly]

I try to transfer some Sumo with the sumo-wallet-cli (Sumokoin 'Sapporo' (v0.2.0.0-release)), but every time it crashes with 'Segmentation fault (core dumped)'. I am using the command transfer Sumoo-address-receiver amount.

There is a message that the default mixin 12 is being used and I have to confirm that I don't want to use a payment id. After that it crashes. My wallet has enough unlocked balance, the blockchain is fully synced, so what is going wrong?

Did you compile the wallet on the same machine where you get the segfaults?
Has it ever worked before?

I don't run Sapporo yet, since I don't need subaddresses but the previous version needs following libraries:

ldd sumo-wallet-cli
   linux-vdso.so.1 (0x00007fff7d3f2000)
   libdl.so.2 => /lib64/libdl.so.2 (0x00007f3068de4000)
   libm.so.6 => /lib64/libm.so.6 (0x00007f3068ae3000)
   libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f30688c6000)
   libc.so.6 => /lib64/libc.so.6 (0x00007f306851e000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f3068fe8000)

run ldd on your Linux and check if no lib is missing.

[rodyw]

I try to transfer some Sumo with the sumo-wallet-cli (Sumokoin 'Sapporo' (v0.2.0.0-release)), but every time it crashes with 'Segmentation fault (core dumped)'. I am using the command transfer Sumoo-address-receiver amount.

There is a message that the default mixin 12 is being used and I have to confirm that I don't want to use a payment id. After that it crashes. My wallet has enough unlocked balance, the blockchain is fully synced, so what is going wrong?

Did you compile the wallet on the same machine where you get the segfaults?
Has it ever worked before?

I don't run Sapporo yet, since I don't need subaddresses but the previous version needs following libraries:

ldd sumo-wallet-cli
   linux-vdso.so.1 (0x00007fff7d3f2000)
   libdl.so.2 => /lib64/libdl.so.2 (0x00007f3068de4000)
   libm.so.6 => /lib64/libm.so.6 (0x00007f3068ae3000)
   libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f30688c6000)
   libc.so.6 => /lib64/libc.so.6 (0x00007f306851e000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f3068fe8000)

run ldd on your Linux and check if no lib is missing.

No, I didn't compile the wallet on my machine, I downloaded and extracted it. The libs are all there and 'automatic' transfers from my pool are fine, but transferring with cli gives me this error.

Update: I put some extra SUMO in my sending wallet and now the transfer is processed succesfully. Maybe somehow there wasn't enough SUMO in it before, but I would have expected a nice error about this instead of a crash.

[rodyw]

-snip-

I see that you use fixed difficulty. For instance, if you start on diff 500, you constantly stay at 500. Other pools have a more dynamic approach. Is there a way I can increase diff manually? My GPU on diff 10000 sends your pool hashes every 6.4 seconds, my CPU on diff 5000 sends every 14.5 seconds... on official pool, my CPU stabilizes around dif 30000 and my GPU around 150000.

You can set your diff fixed at the clientside. At least with my pool @ sumo.pandapool.nl (which also suffers bad luck as I mentioned earlier in this thread). Just put the diff behind your wallet address, like: "Sumooxxxxxxxx.100000". This will set your diff to 100K.

[cdrc-]

-snip-

I see that you use fixed difficulty. For instance, if you start on diff 500, you constantly stay at 500. Other pools have a more dynamic approach. Is there a way I can increase diff manually? My GPU on diff 10000 sends your pool hashes every 6.4 seconds, my CPU on diff 5000 sends every 14.5 seconds... on official pool, my CPU stabilizes around dif 30000 and my GPU around 150000.

You can set your diff fixed at the clientside. At least with my pool @ sumo.pandapool.nl (which also suffers bad luck as I mentioned earlier in this thread). Just put the diff behind your wallet address, like: "Sumooxxxxxxxx.100000". This will set your diff to 100K.

Thanks for the tip. I used this on fairpool a while ago, but ms-pool's faq didn't mention they supported this feature.

It's true that with higher network diff, smaller pools are experiencing huge luck issues.

[rodyw]

-snip-

I see that you use fixed difficulty. For instance, if you start on diff 500, you constantly stay at 500. Other pools have a more dynamic approach. Is there a way I can increase diff manually? My GPU on diff 10000 sends your pool hashes every 6.4 seconds, my CPU on diff 5000 sends every 14.5 seconds... on official pool, my CPU stabilizes around dif 30000 and my GPU around 150000.

You can set your diff fixed at the clientside. At least with my pool @ sumo.pandapool.nl (which also suffers bad luck as I mentioned earlier in this thread). Just put the diff behind your wallet address, like: "Sumooxxxxxxxx.100000". This will set your diff to 100K.

Thanks for the tip. I used this on fairpool a while ago, but ms-pool's faq didn't mention they supported this feature.

It's true that with higher network diff, smaller pools are experiencing huge luck issues.

Yep, it's hard. The current Hash Rate of 15+ MH/sec and Difficulty of 3.5G+ are not in favour of small pools.