How to stop payments after graceful exit?

Hello,

I completed a Graceful Exit with my node, timing it so that it was finalized shortly before the end of October. The timing was crucial to ensure that I earned enough STORJ to exceed the payout threshold. My goal was for this to be the final payout, allowing me to include the STORJ income in my tax declaration for 2024 for the last time.

However, I was unaware that earnings could still accumulate even after a Graceful Exit – a mechanism whose purpose I still do not understand. In my case, the earnings for the current month already amount to $4.78, which likely means I won’t reach the payout threshold for November.

Since I do not want to receive any payouts after 2024 for tax reasons, I am looking for a solution. At the same time, I’d prefer not to deal with zkSync just for this final payout. My questions are as follows:

1. Can someone at Storj reset my current earnings to zero to prevent a payout?
2. Is it possible to delete my payout address entirely?
3. If not, could I provide an alternative (invalid) address to block future payouts?

I would greatly appreciate any helpful advice!

Thanks,
Spectral

1 Like

Before we try anything else, let’s give this a try: can you restart your node with a 0x0000000…00 wallet address? Your node will still accrue some level of earnings until it is disqualified, but they won’t be paid to a 0x000…000 address.

1 Like

After I changed the payout address in config.yaml to 0x000000000000000000000000000000000000000000000000, the STORJ service can unfortunately no longer be started under Windows.

In the last time I have received my payouts from the address 0x303EDCD8DbE1607fe512D45CC15d3E41fa4db44B. Should I try setting this as the payout address in config.yaml? Maybe that will work?

Edit: I was able to successfully define the address 0x303EDCD8DbE1607fe512D45CC15d3E41fa4db44B and the STORJ service can also be started. This address can now be seen in the dashboard. I think that could work. What do you think?

How long does it take for the new payout address to be transferred to the STORJ network so that I can shut down my node? And how long will it then take for my node to be disqualified?

1 Like

Wouldn’t this just burn the Tokens? Wouldn’t it be better to “donate” the Token back to you?

Or just use a random public address, make someone’s day! You can have mine if you want to :slight_smile:

This makes sense. You need the same number of zeros as a real address. Try 0x0000000000000000000000000000000000000000. (0x followed by 40 more 0s)

As long as your node is online, it will check in and send information (such as wallet address) to the Satellite once an hour, even if it is disqualified.

Disqualification is something that happens if your node is offline too long or fails audits. I don’t know how long a node in otherwise good standing has to be offline for to be disqualified, but the process I would advise (if you want to be assured of no more payments) is to set your wallet address to 0x0000000000000000000000000000000000000000 specifically, run your node for a couple of hours, then shut it off and leave it off.

Nope! We have special code that ignores the all-zero wallet address. This is the way to tell our system to keep the tokens.

4 Likes

I have tried it with the 0x followed by 40 more 0s. Unfortunately, even with this address I get an error message as soon as I try to restart the STORJ service.

Can you share what the error message is?

You should use the wallet address with exact 40 zeroes after 0x, i.e. 0x0000000000000000000000000000000000000000.
Just checked.

And there are mechanisms in place to prevent these from being reported in form 1099 correct? (Just making sure I won’t accidentally be taxed on money not received)

Here is the error message:

I don’t know why, but in my case the address doesn’t work. I have checked three times whether the address is correct and actually has 40 zeros after the 0x.

You need to check the node’s logs for the reason.
If there is nothing, perhaps you duplicated some options in the config.yaml file.

The following entries appear in the log file if i specify 0x0000000000000000000000000000000000000000 as the operator address and try to start the service:

2024-12-01T18:16:26+01:00	ERROR	failure during run	{"error": "Invalid configuration: operator wallet address isn't valid", "errorVerbose": "Invalid configuration: operator wallet address isn't valid\n\tmain.cmdRun:62\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tstorj.io/common/process.ExecWithCustomConfigAndLogger:77\n\tstorj.io/common/process.ExecWithCustomConfig:72\n\tstorj.io/common/process.Exec:62\n\tmain.(*service).Execute.func1:107\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2024-12-01T18:16:26+01:00	FATAL	Unrecoverable error	{"error": "Invalid configuration: operator wallet address isn't valid", "errorVerbose": "Invalid configuration: operator wallet address isn't valid\n\tmain.cmdRun:62\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tstorj.io/common/process.ExecWithCustomConfigAndLogger:77\n\tstorj.io/common/process.ExecWithCustomConfig:72\n\tstorj.io/common/process.Exec:62\n\tmain.(*service).Execute.func1:107\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}

If I change the address to 0x303EDCD8DbE1607fe512D45CC15d3E41fa4db44B, the service can be started without any problems. If I change it back to 0x0000000000000000000000000000000000000000, the error message appears again.

However, the initial problem is still solved for me, as I no longer receive any payouts to my own address 0x303EDCD8DbE1607fe512D45CC15d3E41fa4db44B.

1 Like