nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz3rhwvaz7tekd3jks6rev3ehyargv9nk66tnxe6h2dn5w43kuerk0fmnwcm4vfc8z6mgweu8j7fhdfhkjmmrxs6k66mnwg6x2cty9ehku6t0dchsz9mhwden5te0wfjkccte9ehx7um5wghxjmnxduhs5nd6j2 I have set-up Datum server and I followed all instructions. It worked good, but then I wanted to solo mine instead of mining on nostr:nprofile1qqsq9k04vahllseell55m74n3047y88pzlr0z5yany32st29fapqmgsppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctc87ckyu. It seemed to be working but when a new block was mined by Ocean today I got a share... So it seems I am still mining for Ocean even though I have removed the pool host and unchecked pooled mining only...

On the Datum interface it still shows the pool host so I think that's the issue... But looking at the config in StartOS even by ssh in the terminal I see that the pool host is null.

So I am a bit lost as to what is happening...

nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4sppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg4waehxw309aex2mrp0yhxummnw3ezucn89ur9eu8h nostr:nprofile1qqs0m40g76hqmwqhhc9hrk3qfxxpsp5k3k9xgk24nsjf7v305u6xffcpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9u0es8hy #asknostr

Reply to this note

Please Login to reply.

Discussion

Maybe you had some work done, shares, while you were still in the pool. And they paid that out? Ocean only pays on blocks found.

What do you see when you go to ocean website and put in your Bitcoin address?

Thank you for the help! It was a config issue it seems, see above comments 😉

latest datum version?

Sounds like the same issue I had… workaround is to update the host name in the config file from Null to “”I don’t think the latest Datum version with the fix has made it to StartOS yet

that was fixed on latest

I don’t recall seeing an update come through on StartOS (and I’ve just been running with the manual fix). I see v2.2 is running and that is latest on GitHub (Jan 13). I thought I had my issue after that

The "" fixed it for me too! So I am running 0.2.2 according to nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz3rhwvaz7tekd3jks6rev3ehyargv9nk66tnxe6h2dn5w43kuerk0fmnwcm4vfc8z6mgweu8j7fhdfhkjmmrxs6k66mnwg6x2cty9ehku6t0dchsz9mhwden5te0wfjkccte9ehx7um5wghxjmnxduhs5nd6j2. As I see on GitHub that should be the latest version but maybe Start9 are doing something else to it? I edited the config through the StartOS interface and not through the terminal.

Oh there it is! Hmm it hasn't come through to StartOS yet though... I will try to sideload it to try it out 😉

Thanks nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr … I see I was not looking at the startOS Datum repository on GitHub. Do you know how long it should take for new versions to show up in StartOS marketplace?

t Y 4 thread/