Looks like around when you made this post, it swapped over.

Are you also running the Sumokoin wallet?  I'm not sure this applies anymore, but they used to fight over the same port, causing the other to appear to hang during sync

Apologies -- you are correct, it is idealized to 4 minutes.  The rest of my logic still holds, however.  I do remember a few block times of around an hour due to difficulty spikes back when original Sumo was still on CN -- ASICs would join, snap up some blocks, then leave.  This lead to the difficulty spiking, and with the now-reduced hasrate, it took a long time for the rest of the network to find the next 1-2 blocks (at which point the difficulty would correct). This "situation" lead to the fork to CN-Heavy.  +10 minutes, tho not ideal, isn't near as bad as +60 minutes.

Block time is only designed to average every 10 minutes.  If difficulty spikes, a few blocks will be quicker.  As difficulty drops, a few blocks will be longer.  That's just the lag inherent in the difficulty calculation, to keep wild swings in check.

At present, it's trending upward, with some noticeable dips along the way -- so some block times will be greater than 10 minutes, and some less than.

They just never updated their url from before the split -- still using CN-Heavy, so it's a Ryo pool.

You just need the seed words you got from your old Sumo wallet

At present (and, for code reasons, probably forever) you can use your Sumo address to accept Ryo.  I still am -- too lazy to change to a new address.

You get both (checked that for myself last night).  I will say, running both GUI wallets at the same time causes whichever you launch second to not work properly (if you launch Sumokoin GUI wallet, then Ryo GUI wallet, Ryo wallet hangs; launch Ryo before Sumo, and Sumo hangs).  Long-and-short:  It's a minor bug (both wallets are trying to use the same rpc port) that both parties should resolve soon (*nudge* *nudge*).

Now, why is SumoGUIWallet feeling the need to access 007guard.com?

Edit: False alarm. Was an issue w/ my hosts file & reverse lookup.

I am having an issue where the sync is not progressing past block 137511 for some reason.

Should add: Everyone from old dev team but Vu resigned as a result of this mess.

So:
Vu is running Sumokoin (returning to old CN).
Fireice & Psychocrypt are running Ryo (staying on CN-Heavy)

I believe it was noted to expect the sync to be slow after the fork, as not everyone has nodes online w/ the new codebase.  I know I've been too busy to update my own node. /sheepish

As of the fork at 137500, you now have both.  You'd need to download the wallet for each, restore the wallet from your seed words, etc., just like if you were setting up a new computer.

I've heard that at some point, the Ryo codebase will start generating Ryo-prefixed addresses (it would be silly if it didn't eventually), but the current/legacy Sumo-prefixed ones will continue to be supported for some time (probably forever, in all practicality).

Reading the entire tweet, they're supporting both Ryo & Sumo.  And checking their site, they list both coins separately.

I expect the exchanges that don't drop Sumo/Ryo will treat it as any other coin fork, w/ Sumo being the CN fork, and Ryo being the CN-Heavy fork.  FWIW, that's how I read TradeOgre's statement on the matter.

CN-Heavy (Ryo).  They announced the result of their vote around 12 hours ago, as best I can tell.

Wanted to single this out, as it's quite important, and bears repeating: Even if the goal of the devs is to pump & dump this coin, they (either camp) are gaining nothing by having this strife continue.  The old dev team's actions just compound confusion on top of that strife -- which strikes me as more of an emotional knee-jerk reaction, rather than some well-reasoned strategy.  Cutting off your nose to spite your face, as it were.  To my knowledge, they are under no financial burden by using CN-Heavy (no license or royalties), and this really would only serve to anger exchanges -- hard forks generally seem to require more effort on the part of exchanges compared to soft forks.  It seems reasonable that short notice would only compound this issue.

More, based on how little time there is before this fork happens (and the lack of specific details involved), there's no guarantee that if they do remit your coins, that that transaction would be fully confirmed/honored by both chains.

Admittedly, that seems like a fair & measured response from Cryptopia

As a coder: I suspect fireice will be going over the codebase with a fine-toothed comb, then announcing a decision/strong opinion on what to do next.

That's just my opinion, not affiliated w/ Ryo's dev team.

I'll admit, I'm not  in favor of changing the name (and potentially creating confusion), but I see the practicality of picking something that more succinctly represents the methods & goals of the coin.