DATUM Gateway Retropex

This is going to be a stab in the dark because I have not seen it mentioned here.

I’m testing my DATUM gateway with Convoy in pool mode but I cant seem to get it working. The gateway is #pow:0.4.1:23 from mempool.guide repository

I am using MRR and HashGG (0.7.2:2) to port to my gateway and setting it like so for pool mining:

The results is: No shares. Status: Not ready

Doesn’t seem to be working.

In non-pool mode the settings:

The result: Local shares showing up but nothing else:

I went to the Knots discord and got all kinds of advice but nothing worked.

I’m a expert with Datum for OCEAN but this ones got me baffled? Does anyone have a clue why pool mining isn’t working with Convoy?

I’m not renting hash but this the address I’m using for Convoy and it is working.

2 Likes

Yep. That works. I had tried that host once before but I must have entered it incorrectly. Thanks

1 Like

When you "search by username " for your address do you get your Dashboard for My Stats?

I do not.

Also curious: my Datum settings screen is different than yours?

Yes when I go to the convoy website convoy.xyz then dashboard then my stats then enter my bitcoin address, I see my stats. I’m using the retropex Datum version #pow:0.4.1.23, I think it’s the most recent. Mine looks like that I just have to scroll down to see the rest.

1 Like

Yep. Same version I have. It looks like CONVOY has some kind of issue with my address.

Thanks for verifying things for me.

You should be able to use a Sparrow B2b address, but I just use an address from my Knots wallet for Convoy then send them from there to my Sparrow B2b wallet. It has worked so far. Fyi the payouts on Convoy aren’t live yet but should be soon.

2 Likes

Really? I might go at it from that avenue and see how it shakes out. If anything it will be a test for the sparrow address too.

Thanks

Note that wallet addresses are common on both chains. It is the transactions themselves that may or may not be compatible between the two chains.

2 Likes

Sorry for this long post :-P. Newbie here, boy I have learned a lot in the last few weeks, had the Start9 running on Core for about 6 months (Thanks to you Paul and Matthew of course!), then got it updated to the Knots services back as soon as it was available. Around Aug 25th I ordered an SC5Pro II from China, got it in after wiring in the 240. Unfortunately I was on vacation during the fork so only able to get Solo Mining going a week later afterwards. After a week or so of not hitting a block I decided to see if I could Pool mine and make sure my configurations were sound. I asked Grok for a recommendation on the best reputable Pooled Knots Blake2b and out came Convoy. After now 5 days I discovered that I am not actually getting a payout and according to Grok this could just be “Luck Theater”. I’ve accumulated Unpaid Earnings but given the uncertainty I switched back to Solo. I will most likely try again but try out Connor and Paperclip , just wasn’t sure where to paste that snippet of code required for Datum. I will Ask my Grok buddy for help on that I guess. Thanks for all your hard-work. I am here for the experience and original vision, so grateful to be apart of it. Any advise would be appreciated but I know your all busy :slight_smile:

1 Like

I’m sure you’ll get your payout. It’s just not live yet on Convoy as I think Luke has been busy with the proposed soft fork to knots. If you want to try a different pool, Lazarus pool has worked well for me.

1 Like

Update, I just rebooted my Rig and Start9 and now I see a payout, coincidence? Did I knock something loose or did Convoy update code to release payments? I have no clue.

1 Like

Convoy sent out their first payments last night.

1 Like

Paul is the Datum setup change since the spilts, I was solo ming BTC, using your setup from your earlier YouTube video on setting up Datum, my miners are running but not sure if the old setup needs changing

You’re on the SHA256 network? I think as long as you have Bitcoin Knots Pre-RDTS running, the previous setup should still be good. I’ll have a newer version of Knots for SHA256 out soon. I’m just being a little paranoid about making sure there are no issues with it at all – I know this will likely be the most extensively used app that I’ve ever released, and I can’t afford to make any errors.