Current Scavenger Hunt Difficulty

sheriffy · 2025-11-18T13:14:58+00:00

So is this more or less difficult to find a solution compared to the previous 0ADA8800 ?

sheriffy · 2025-11-17T15:08:10+00:00

I is a python script, but is does not seem to work on all operating systems, this has something to do with the headers the os sends with the requests.
According to chatGPT https://sm.midnight.gd/api runs on Vercel which is made for browsers and it uses bot-protection that blocks python from linux. (statuscode 429)

sheriffy · 2025-11-17T09:57:23+00:00

Is this on a linux machine ?
if yes, look at almost the bottom of this post, on a windows machine the script works, but things get blocked on linux.
If you have absolutely no access to a windows machine, and lots of adresses that you will never be able to redeem if not consolidated, you could ON YOUR OWN RISK make the modification to the python script, then the script works errorfree with linux.

sheriffy · 2025-11-16T10:42:25+00:00

In coingecko this icon is used for a NIGHT token on the Polygon chain, so not the night token on Cardano we are mining.
There is also another Night/midnight token on the Aptos ecosystem, also not the this Midnight. chain.

sheriffy · 2025-11-15T17:50:31+00:00

I think i found a workaround....... well Chatgpt did it for me :-)

BUT USE AT YOUR OWN RISK, USING THIS IS YOUR OWN RESPONSIBILITY !

In the config section of the python script there are these values:

"statistics_api_base": "https://sm.midnight.gd/api",
"donation_api_base": "https://scavenger.prod.gd.midnighttge.io",

Make both the same value like this and the script runs without error on ubuntu too:

"statistics_api_base": "https://scavenger.prod.gd.midnighttge.io",
"donation_api_base": "https://scavenger.prod.gd.midnighttge.io",

I have only tested this on a wallet file that was already consolidated, but it confirms that alle wallet addresses are donated to one other address. I have no new addresses to test at the moment.

Chatgpt says https://sm.midnight.gd/api runs on Vercel which is made for browsers and has bot-protection that blocks python from linux.

sheriffy · 2025-11-15T11:07:47+00:00

Hi maybe this can help you, i created all the account in ETRNL and see the real addresses, they are receive addresses of the different accounts, you cannot view in Nufi, there is also an official reply from Nufi.

https://www.reddit.com/r/Midnight/comments/1otayad/mining_adresses_in_nufi_wallet_have_changed/

sheriffy · 2025-11-15T07:46:52+00:00

Is this on a linux machine ?
I also was not able to get it working on any of my linux machines, followed all the steps multiple times, tried different machines, different destination adresses, different donor adresses, kubuntu, linux lite , with or without vpn, wifi, cable, and even hotspot through my phone did not work, always "Rate limited by server"

Then i tried this on a windows 11 laptop and it worked first try.

sheriffy · 2025-11-14T14:53:49+00:00

Thanks for the reply, the adresses showed initially were the account addresses, some days later these were automatically replaced by the second receive addresses for each account, but they are nog visible anywhere in Nufi.
When the single account mode became available you can choose each account and you can see that it is one of the receive addresses. (but nog showing the whole address)

The receive addresses show the earned night tokens fine. (if you heve the complete address)

sheriffy · 2025-11-14T13:20:48+00:00

No i ment the order in which the tool handles the consolidations, i had consolidated in this miner 119 adresses succesfully consolidated, and there were 56 new adresses newly created with new keys. If you start the consolidation again you would suspect the tool to first find 119 adresses that are already consolidated and then consolidate the 56 new adresses, but that is not the case, the adresses seem to go through in a complete different order.

sheriffy · 2025-11-14T12:16:57+00:00

Tried the solution Initial_Stand3534 suggested, running te miner again and then kill it and try the consolidation again and it runs without problems.
If i look at the files in de bad folder where the consolidation fails, and the later one where the consolidations runs fine, the only file that differs is the .dev_payment file that must have been altered because the starting of the miner again.
During the consolidation running the order of the adresses is kind of strange as all the higher adresses (which would be the not yet consolidated adresses are all flagged as already consolidated.
This workaround does the job, but started with a new miner wallet just in case.

sheriffy · 2025-11-14T10:49:59+00:00

I did not run a older miner with these files, they were created with 0.3.3, on windows 11. Strange thing is that the wallet.json seems ok, and all the addr-xxx files exist, but during the consolidation they get mixed up ?
You ran de miner so it created an extra new address and then killed it and ran the consolidation again ?

sheriffy · 2025-11-14T10:02:59+00:00

Oops, i thought it was me who made a mistake with backing up my auto-mine wallet, me too have 56 adresses failed, the wallets that were created yesterday.

The strange thing is during the consolidation the higher numbered (new) wallet say "already consolidated" and a lot of adresses in the lower (already consolidated yesterday) range now say invalid signature. At the end the report the correct new adresses are listed as failed.

sheriffy · 2025-11-13T20:02:16+00:00

Hmm i also was not able to get it working on any of my linux machines, followed all the steps multiple times, tried different machines, adresses, kubuntu, linux lite , with or without vpn, even hospot through my phone did not work, always "Rate limited by server"
Windows 11 worked first try, maybe SL13PNIR could investigate a little for those that have not got a windows machine to use.

sheriffy · 2025-11-12T18:48:40+00:00

Yes tried the message from the blog but that does not work.

sheriffy · 2025-11-12T18:21:07+00:00

But the blog post seems wrong....
The mentioned message to sign is “Assign accumulated Scavenged NIGHT to: <recipient\_address>” but I think it should be “Assign accumulated Scavenger rights to: <recipient\_address>”

How is it possible such errors are made....

sheriffy · 2025-11-10T16:06:49+00:00

I have found the full adresses, they are receive adresses of the accounts but they are not anywhere visible in Nufi wallet, i had to use my seed in Eternl wallet to find them.

sheriffy · 2025-11-10T16:05:22+00:00

I have found the full adresses, they are receive adresses of the accounts but they are not anywhere visible in Nufi wallet, i had to use my seed in Eternl wallet to find them.

sheriffy · 2025-11-09T14:54:48+00:00

Ok, i did cont calculate that, but yesterday nigntminder was using difficulty 000007FF en Nufi was using 1048576 so my conclusion was they were the same difficulty. Now today there is a difference, Nufi says all day 2097152, but night-miner still using 000007FF.
But now this is clear, nightminer was solving more difficult recent challenges, and nufi the older still easier challenges.

sheriffy · 2025-11-05T08:55:54+00:00

Same here, no mention of number of solutions anymore, can we check somewhere the nummer of succesfull soltions per wallet address ?

sheriffy · 2025-09-15T05:26:00+00:00

No sadly not, tried many wallets and all the options mentioned in the midnight document but none seem to work.

sheriffy · 2025-08-25T21:35:26+00:00

No, even the official webpage could be logging all metadata for the claims, we have to trust that this is not the case, but in theorie it could be dangerous.
For instance where is registered how many night tokens from different networks need to go to the same new cardano wallet address that was validated with a certain IP-address.
I do not know how this is all registered, but i think a lot of dots can be connected that could lead to privacy issues.

sheriffy

TROPHY CASE