Unfortunately this project will have to open up in the traditional way for ASICs and others. That's ok, I'd rather see it live on than die.
Note to all, I'm going to adjust the PoW scheduling to react better with ASIC level hashing. It'll be more or less the same as it is now with less extreme difficulty adjustments. And... as with the 0.15.2, this next release will be a mandatory update. I'll keep the board well informed of the status.
No No NO! To ASICS...
Please don't do that.
That makes this coin no different from every other broken ASIC coin....please stick with the plan.
If people don't want to stay, fine, let them go, but enough people will stay to mine coin.
It only needs 2 people to actually keep coin alive, and from there it can grow steadily over time.
Please try and limit back to cpu only via wallet only...if you do, your coin will stand alone against a tide of sh*t coins...
Give it a chance...as they say Rome wasn't built in a day
J
I tend to agree.
Is the fact that it's hard to mine really a bad thing?
If the dev can somehow have it so it works via wallet mining etc only. I'm more than happy to put my time into mining this coin and having wallet open and could even host a node if needed if it's easy enough to set up a node for the wallet.
total agrre no asic please but the initial idea was good but sha means asic so.... i will let my pc mining and will see.

{
"blocks": 14031,
"currentblockweight": 4900,
"currentblocktx": 1,
"difficulty": 231473.3310863087,
"errors": "",
"networkhashps": 365652529055.8644,
"pooledtx": 1,
"chain": "main"
}
can you lock only for wallet, pools are horrible for simples miners.
but somebody has created a custom build which brings back RPC commands needed for ASIC mining. Whomever did this is destroying the future value of ROBO ... still thinking about how to overcome this. Swapping out the algorithm might be the only option, but it's going to take a good amount of time for me to learn crypto-programing.
If any crypto devs are out there... I'm up for ideas on ASIC resistance. Think outside of the box! If we can figure this out, it'll be a game changer... ASIC person, I really wish you could see the massive potential here.
High level ideas: - block-submission throttling (e.g. even if an asic infiltrates, the network would reject blocks when they come in to fast)
- hash-rate throttling
- geared toward the CPU miner.
- adjust local hashrate one-by-one so all nodes on the network have an equal shot an solving a block.
- devise validations on blocks that fail when they are submitted externally
- even possible? I have no clue at this point.
Don't know if any of that will come to light, just some thoughts I've had since yesterday. Request for input from other developers.
, may give you some ideas, the ROI devs are very friendly, talk to them on Discord: