Topic: [SUMO] SUMOKOIN - 🔏 Digital Cash For Highly-Confidential Transactions 🔏 (MOD) - page 16. (Read 29310 times)

import wallet from seed, "make your own new password" not sure why thats a thing, but i put the right one and it shows balance, but then i cant send coins, it just says "sending might take a while"
and it doesnt send, it sits like that for hours, i restart the rig and it says last block 1 min ago up to date latest wallet, and same s h i t again.
and i see others here with the same issue and you guys give no reply.
also this sumo wallet was imported to RYO a while back is that the reason? that my sumo is now ruined because of that? does it also affect ryo wallet?

What wallet needed to be fixed?

Sumokoin will be listed on Exrates for trading soon.


Exrates is one of the top 40 exchanges with a daily volume > 5000 btc.

We are happy about this additional market and work hard on even more listings in the future.

https://twitter.com/sumokoin/status/1022381644760711168?s=19

Just ignore the negs, focus on the facts and see the future. All the fud can be countered with facts. Some people wanted to hijack the coin and failed so the hate is strong and the fud offensive is still ongoing.
Strong dev backbase though, combined with an iron spined core-community. This coin is not going to die, because this is the coin for our grandchildren.

What happened with Sumokoin. I saw this project as the litecoin of Monero. Very promising.
Now I see so much negativity.

I give up. I dont know what happened to this coin but it flat out doesnt work anymore. I CANNOT send any money out the wallet regardless if its synced to the network.

GUI just says "sending coins this may take a while"

and the CLI doesnt even connect to the daemon to actually send the coins but it is still actually connected to your network. It just flat out wont send.

both regardless of being 100% in sync.

Your coin didnt do this before. Guess im out. This way too much of a hassle. Im not going to spend anymore on electricity. Your wallet shouldnt be this tough to use.

http://i152.photobucket.com/albums/s197/Itsaboom/Untitled_zpsdgnef9bc.png

This is all I ever get. This whole fork non sense is really affecting your supporters. You arent really leaving me any other choice. There is too much SUMO locked in this wallet.

SYNCHRONIZATION started
2018-Jul-14 07:09:56.953412 [P2P1][76.20.201.79:19733 OUT]Sync data returned a new top block candidate: 172956 -> 144447 [Your node is 28509 blocks (79 days) ahead]
SYNCHRONIZATION started
2018-Jul-14 07:11:17.643299 [P2P2][79.111.43.157:19733 OUT]Sync data returned a new top block candidate: 172957 -> 150000 [Your node is 22957 blocks (63 days) ahead]
SYNCHRONIZATION started
2018-Jul-14 07:14:58.950247 [P2P9][103.82.240.208:2004 OUT]Sync data returned a new top block candidate: 172958 -> 172959 [Your node is 1 blocks (0 days) behind]
SYNCHRONIZATION started
2018-Jul-14 07:15:02.548198 [P2P7][103.82.240.208:2004 OUT]Synced 172959/172959
2018-Jul-14 07:15:02.549199 [P2P7][103.82.240.208:2004 OUT] SYNCHRONIZED OK
2018-Jul-14 07:16:57.704609 [P2P9][76.20.201.79:19733 OUT]Sync data returned a new top block candidate: 172960 -> 144447 [Your node is 28513 blocks (79 days) ahead]
SYNCHRONIZATION started
2018-Jul-14 07:17:08.549459 [P2P7][128.75.65.213:19733 OUT]Sync data returned a new top block candidate: 172960 -> 172961 [Your node is 1 blocks (0 days) behind]
SYNCHRONIZATION started
2018-Jul-14 07:17:12.455407 [P2P7][128.75.65.213:19733 OUT]Synced 172961/172961
2018-Jul-14 07:17:12.457407 [P2P7][128.75.65.213:19733 OUT] SYNCHRONIZED OK

When it actually does connect:

** No mixin value specified, default mixin 12 will be used for this transaction.
constructed tx too big: tx size = 298895 bytes, limit = 269736 bytes; retrying with smaller tx_size_target_factor = 0...
** No mixin value specified, default mixin 12 will be used for this transaction.
constructed tx too big: tx size = 298961 bytes, limit = 269736 bytes; retrying with smaller tx_size_target_factor = 0...
** No mixin value specified, default mixin 12 will be used for this transaction.
constructed tx too big: tx size = 298940 bytes, limit = 269736 bytes; retrying with smaller tx_size_target_factor = 0...
** No mixin value specified, default mixin 12 will be used for this transaction.
constructed tx too big: tx size = 298992 bytes, limit = 269736 bytes; retrying with smaller tx_size_target_factor = 0...
** No mixin value specified, default mixin 12 will be used for this transaction.
constructed tx too big: tx size = 298952 bytes, limit = 269736 bytes; retrying with smaller tx_size_target_factor = 0...
** No mixin value specified, default mixin 12 will be used for this transaction.
constructed tx too big: tx size = 298968 bytes, limit = 269736 bytes; retrying with smaller tx_size_target_factor = 0...
** No mixin value specified, default mixin 12 will be used for this transaction.
constructed tx too big: tx size = 298924 bytes, limit = 269736 bytes; retrying with smaller tx_size_target_factor = 0...
** No mixin value specified, default mixin 12 will be used for this transaction.
constructed tx too big: tx size = 299022 bytes, limit = 269736 bytes; retrying with smaller tx_size_target_factor = 0...
** No mixin value specified, default mixin 12 will be used for this transaction.
constructed tx too big: tx size = 298984 bytes, limit = 269736 bytes; retrying with smaller tx_size_target_factor = 0...
** No mixin value specified, default mixin 12 will be used for this transaction.

Just spams this for hours. No matter the amount being sent. I dont see how any "average joe" will be able to use you successfully. How can mass adoption even be possible if these kinds of technical complications arise. People cant even tie their own shoes. Food for thought.

Im over it.


edit: took it to my office and refreshed it there and i got my funds out. i had to use a computer thats never seen a wallet but it worked.