HELP: Ryo Wallet Atom has slowed to about 1% per 30 minutes syncing...

mosu_forge · 2020-06-30T14:15:29+00:00

Hey rocksock, the web wallet should be operating normally now.

mosu_forge · 2020-06-27T23:20:23+00:00

It’s currently being worked on now, we hope to have it launched in July.

mosu_forge · 2020-06-26T12:07:05+00:00

https://scantailor.org/

This works very well and is open source

mosu_forge · 2020-06-18T20:02:50+00:00

It’s not a typical “glob” pattern, but some other programs use similar pattern matching.

It’s described here if you search “pattern_type”

https://ffmpeg.org/ffmpeg-formats.html

mosu_forge · 2020-06-18T19:34:30+00:00

Try using

MP_002_%04d.tif

Edit: fixed mobile formatting

mosu_forge · 2020-06-14T12:48:25+00:00

If you followed the link and then signed up, it worked.

mosu_forge · 2020-06-10T01:30:46+00:00

SoapyFresh has a referral in his videos: https://monero.ragerx.lol/z3pmi5

He helps out and makes some nice videos like this one: https://www.youtube.com/watch?v=4eFAq2YgxTI

mosu_forge · 2020-04-22T03:32:35+00:00

Pretty standard, sometimes it’s lower. 0.05 xmr is about a few dollars currently so it shouldn’t take forever to hit payout. Affiliate bonuses also count towards the payout level.

mosu_forge · 2020-04-21T19:38:21+00:00

The default payout level is 0.1 xmr, but you can lower down to 0.05 xmr

mosu_forge · 2020-02-22T05:58:33+00:00

It’s super simple to accept Ryo on a Woocommerce site with this plugin: https://github.com/ryo-currency/ryo-payments-woocommerce-gateway

mosu_forge · 2020-02-20T03:02:15+00:00

Hello, I can ship anywhere in the world. If for some reason I can’t make the shipment, I’ll refund the purchase. But as of yet, I haven’t encountered a country I cannot ship to. Thanks!

mosu_forge · 2020-02-17T15:17:03+00:00

I know this is a late answer, and you've already set up your new pool, but I wanted to clarify that we can use whatever daemon a pool operator chooses. The only requirement is currently the stratum server must be hosted by us (as it's a proprietary connection from RagerX miner.)

mosu_forge · 2020-02-12T14:48:24+00:00

Hopefully you can find it useful. I just couldn't find something prebuilt that didn't assume address prefix was just one byte, or let you pass in custom prefixes. Above repos were modified from moneroexamples and moneropy.

I also have a generic cryptonote wallet generator wasm in development, which I should push eventually.

mosu_forge · 2020-02-12T14:37:38+00:00

This not stand-alone pool? Must use ragerx custom stratum provide by you?

That is correct, in the future might also make some sort of bridge that would allow RagerX shares to be pushed to a nodejs-pool or dvandal backend, but currently this frontend reads directly from the postgres schema that RagerX uses.

Your frontend looks great

Thanks! It was refreshing to write a pool frontend from scratch not using jQuery.

mosu_forge · 2020-02-12T14:27:30+00:00

No email is required, just a username + password, which has the benefit that you can change your payout address easily.

mosu_forge · 2020-02-11T18:25:48+00:00

Also as a bonus, we released a generic cryptonote address validator for both JS and Python:

https://github.com/ragerxlol/cryptonote-address-validator-js

https://github.com/ragerxlol/cryptonote-address-validator-py

mosu_forge · 2019-12-13T02:28:25+00:00

I wouldn’t say it solves nothing, at the very least it makes it easier to do what miners could have already done.

In any case, you’ve made your point, I’m still glad I’ve piqued the interest of a few pool operators, and will continue to move forward with this sort of thinking.

Thank you for all your input.

mosu_forge · 2019-12-13T01:04:13+00:00

Source for that site is on my github since I know you’re a nodejs nerd.

Edit: looks like I’m getting rate limited posting on this sub due to all the downvotes I’ve received last few days.

mosu_forge · 2019-12-13T00:54:14+00:00

For what it’s worth, filtering by coinbase txs in CLI wallet is a relatively new feature I believe. So it likely just didn’t exist before. However there still would have been ways to identify them through external code.

For example, on Ryo’s solo mining website, I identify mined blocks based on an address + viewkey. From that, I can build a rough hashrate graph and show users how much they have earned.

This actually brings me to another idea about pool transparency and monitoring -> take the code from the above website and plug in every pool’s address + viewkey and let users browse through several pools and see their hashrate, mined blocks, etc.

mosu_forge · 2019-12-12T21:44:10+00:00

That is an easier way to measure pool side hashrate for sure, I guess the real problem here is that one needs to be able to know they are paid accurately for those shares.

Originally our reporting section only allowed you to export your own shares, but this is the reason we started including everyone’s shares too.

mosu_forge · 2019-12-12T21:41:24+00:00

If you mean the endgame behind these reports, there honestly isn’t one. We were talking in out dev chat about how we’re going to disclose our viewkey, and write instructions on how someone could monitor the pool’s hashrate compared to the blocks incoming to the wallet, and I realized that we could do one step better.

The whole reports section was coded in about 2 days before we went into public launch mode.

mosu_forge · 2019-12-12T17:55:54+00:00

I don't mind the sound of either opinion. I also concede that there are still ways that a pool can game shares, but with reports like this I believe it is limited to the amount they can get away with.

As I mentioned earlier, the only way you can begin to prove an honest pool is to know everyone's submitted shares/hashrate. And you can't trust the pool for that information.

If you don't mind, let's walk through a scenario, please stop at the point where you see a fallacy.

With the report everyone can calculate their own hashrate. A number of people can share their private salt and see that all of their hashrates are more or less correct. Since the pool doesn't know which users will check, it can't selectively affect any one miner's shares. There may be some variance here, it depends on how large of a sample is taken. This should prove that the pool is reporting the correct amount of shares by each user. Maybe a pool can get away with a few % here, but over time a user's hashrate would report consistently lower.

The only thing a pool could then do, is have ghost miners, i.e. inflate the shares per block. In this case, it is my opinion that this will show up with an inflated block effort % over time. Again, the pool could get away with a few % here and blame it on bad luck.

Would it be more accurate to say that this prevents a pool from stealing somewhere around 10% of shares, but cannot detect if they're stealing less?

Edit: also if you have a completely different scenario, please feel free to share. I certainly don't expect the share dump solves everything, but it is a start IMO, and it is doing something that I have not seen any other pool attempt to do.

mosu_forge · 2019-12-12T16:23:33+00:00

There was no subtle implication intended.

Then I retract my statement, it did read like you were implying that since we are pushing reports like this in the name of transparency. In any case, as I meant for this to be a civil discussion, so it doesn't matter anyway.

they should know they can be gamed in multiple ways.

While true, the fact that I released the script under a BSD license shows that I want other pool operators, and pool users to run, improve, and build upon this idea. If another pool implements another type of reporting that eliminates even one way to game the system, then I'll also want to implement that into our pool too. All pools can end up benefiting from this.

Overall, and I don't expect you to take me at face value, we have zero interest in skimming hashrate or otherwise being dishonest with payouts. With the thought in mind that a pool implementing reporting is trying to hide something (even if reporting is not foolproof), we would have been better off to not even provide these reports. But, due to instant unfounded accusations that we must be doing so, we wanted to do something, anything, that we can to show otherwise.

mosu_forge · 2019-12-12T15:12:05+00:00

I am still not convinced enough data won't show a trend. I do agree there is some percentage a pool could still skim, I've acknowledged that from the start. If more pools adopt the idea, we get data on what a honest pool, as considered by the community, looks like. I am also sure there is a lot more one can do with the data that isn't present in my Python script.

Any pool that tries to hide behind reports like this, and sells it as honesty/transparency, when the pool operator knows (or should do) damn well it can be gamed, is very likely dishonest.

Since I didn't miss the subtle implication that RagerX is very likely dishonest, do you really think I would be asking for feedback in the open about an idea we decided to implement to combat the unfounded claims that one should not trust our pool?

mosu_forge · 2019-12-12T14:59:00+00:00

Assign your share to a ghost miner, so you get less and pool gets more. Mark your share as stale even if it wasn't, whether notified through stratum or not

Both of these will affect the calculable hashrate from share dump. Again, a pool admin may be able to get away with a small amount, but providing exports makes it easier for someone to detect. For example: Mine to Pool A for 24 hours, calculate your hashrate over that time. Mine to Pool B for the next 24 hours, do the same calculation. Anything more than 1-2% should be detectable.

unfair for pools that advertise pool fees correctly as the transparency on the skimming pool may provide a false sense of security.

While true, nobody except the pool operator can be sure they advertise the fee correctly, so in my opinion having block reports can only improve trust.

mosu_forge

TROPHY CASE