Niffler Wallet not reachable

Trying to get a mining payout. My local node is synced and appears to be working, however when checking it shows my address is unreachable.

Any ideas?

I opened the port in Windows Firewall, tried a VPN, no luck.

Did you try using Tor Bridges? I don’t know if Niffler supports them though.

1 Like

Hey, thanks for your reply.

I haven’t tried tor bridges & I’m not sure how to do so.

If Niffler doesn’t support them, is it possible to start a Grin++ wallet and import my seed phrase while still being able to receive from the current address?

The payout is not very high but it would be nice to receive the payout from the blocks I managed to hit.

Also, I am using the default slatepack receiving address. Is there a different address I should be using? I’ve used the slatepack memo thing before on tradeogre, but 2miners doesn’t do the memo thing they just send to your address as long as wallet is online.

yes, niffler wallet have not support tor right now.
I think it is possible to import my seed phrase generate in niffler to g++

1 Like

Yes it is.

The memo thing is not part of the defined standard. The only problem is that if you restore your seed on Grin++ you might not have the same address.

1 Like

Ah I see. Thanks for the help!

I’m going to try restoring the seed to a Grin++ wallet and see if that works.

I guess if it randomly generates an address then I definitely won’t have the same address… would be nice if it works somehow though haha.

Ayyeee! It worked! Same address after copying my Niffler seed to the Grin++ seed. Wallet is now online and reachable.

Thanks again for you guys’ help!

1 Like

Ed25519 pubkey is derived from the seed, slatepack address uses this ed25519 pubkey for tor, that’s why it’s listening on the same tor address. That’s afaik, please correct me if I’m wrong

Maybe this was fixed wallet shows incorrect BIP32 derivation paths · Issue #663 · mimblewimble/grin-wallet · GitHub or it was only a problem displaying the paths.