could be a user self compiled executable, forgot to setup the correct PK.
OR, some bug in our arm build release flow, that used incorrect key.
1 Like
I’m also seeing this “wrong” key in all of my logs (but I believe I’m on the latest version):
$ safenode --version
safenode cli 0.108.4
$ grep -h "Using default PAYMENT_FORWARD_PK" ~/.local/share/safe/node/*/logs/safenode.log*
[2024-06-29T17:51:59.405497Z WARN sn_transfers] Using default PAYMENT_FORWARD_PK: a585839f0502713a0ed6a327f3bd0c301f9e8fe298c93dd00ed7869d8e6804244f0d3014e90df45cd344a7ccd702865c
I used safeup to get the latest version. Wondering how widespread this problem is?
2 Likes
Just to clarify, that’s the standard ARM binary, as downloaded by safenode_manager, not compiled
2 Likes
Maybe was fixed for the alpha releases, but not for the regular releases, @chriso (I believe you were on leave when that happened)?
1 Like
This sounds familar to me - i suspect i’m experiencing the same issue here.
2 Likes
1 Like
I don’t think it can be widespread. All I’m running is ARM based nodes and they are earning and that is being relfected using ‘/rank’ in Discord.
I tried that search for the "Using default PAYMENT_FORWARD_PK"
and found it on 5 nodes all on the same machine:-
[2024-07-01T10:16:10.571967Z WARN sn_transfers] Using default PAYMENT_FORWARD_PK: a585839f0502713a0ed6a327f3bd0c301f9e8fe298c93dd00ed7869d8e6804244f0d3014e90df45cd344a7ccd702865c
[2024-07-01T10:17:03.896764Z WARN sn_transfers] Using default PAYMENT_FORWARD_PK: a585839f0502713a0ed6a327f3bd0c301f9e8fe298c93dd00ed7869d8e6804244f0d3014e90df45cd344a7ccd702865c
[2024-07-01T10:17:56.788396Z WARN sn_transfers] Using default PAYMENT_FORWARD_PK: a585839f0502713a0ed6a327f3bd0c301f9e8fe298c93dd00ed7869d8e6804244f0d3014e90df45cd344a7ccd702865c
[2024-07-01T10:18:49.878621Z WARN sn_transfers] Using default PAYMENT_FORWARD_PK: a585839f0502713a0ed6a327f3bd0c301f9e8fe298c93dd00ed7869d8e6804244f0d3014e90df45cd344a7ccd702865c
[2024-07-01T10:19:42.932975Z WARN sn_transfers] Using default PAYMENT_FORWARD_PK: a585839f0502713a0ed6a327f3bd0c301f9e8fe298c93dd00ed7869d8e6804244f0d3014e90df45cd344a7ccd702865c
that’s 5 different nodes at the same location on the same machine. There was a powercut there this morning and that is the time the machine came up again.
It looks like it was part of the startup:-
[2024-07-01T10:16:10.542264Z INFO sn_networking::driver] Listening on ListenerId(1) with addr: "/ip4/0.0.0.0/udp/0/quic-v1"
[2024-07-01T10:16:10.556492Z INFO safenode::rpc_service] RPC Server listening on 127.0.0.1:44947
[2024-07-01T10:16:10.569530Z DEBUG sn_node::node] Replication interval set to 35s
[2024-07-01T10:16:10.570845Z DEBUG sn_node::node] BadNodesCheck interval set to 220s
[2024-07-01T10:16:10.571967Z WARN sn_transfers] Using default PAYMENT_FORWARD_PK: a585839f0502713a0ed6a327f3bd0c301f9e8fe298c93dd00ed7869d8e6804244f0d3014e90df45cd344a7ccd702865c
2 Likes
Hmmm, I’m a bit confused (probably just my ignorance)…
According to @qi_ma above, the key starting with “a585839f” is the wrong key, so I’m a bit lost!
Depends on the version you are running. I am guessing it was the latest version
Yes, I’m definitely running the latest version:-
Version: 0.108.4
But my point is that this message that @lis was talking about seems to be a result of a normal startup.
On looking further in the logs I see this from a few seconds later:-
[2024-07-01T10:16:11.996725Z WARN sn_transfers::genesis] Using compile-time GENESIS_PK: b38f61b8df2cc7d86ceb1039cc23c9e1e2857a97e59ce01a6b1a5d6f7fa5311b521efb158fcdb66113986058ec9e25c8,GENESIS_SK=32b5510bf273d5e15bbb31b65987cee62d41ab2b38f398ed780a47a8d3e281e2,FOUNDATION_PK=84418659a8581b510c40b12e57da239787fd0d3b323f102f09fae9daf2ac96907e0045b1653c301de45117d393d92678,NETWORK_ROYALTIES_PK=8c027130571cea2387a0ceb37c14fec12849015be1573ea6d0a8e4d48da2c1fbe2907ae7503bb7c385b21e2d7ac9d6ff,PAYMENT_FORWARD_PK=8c2f406a52d48d48505e1a3fdbb0c19ab42cc7c4807e9ea19c1fff3e5148f3bbe53431ec5a07544aaeef764e073e4b2f,NETWORK_VERSION_MODE=
So it looks like the PAYMENT_FORWARD_PK is then changed to what other nodes use. Because I see that address being used on other nodes.
The point was that the ARM build was wrong. There is at least 2 ARM builds for 0.108.4 if I am not mistaken
That’s right, I believe the only one that had the right PK was 108.3-alpha, but the full release reverted back to the wrong PK
1 Like
There has not been a build fixing the key issue on ARM yet. It should be coming very soon.
2 Likes
Sorry for the negativity - but it would have been nice to know this a couple of weeks ago.
There has been a lot of complaints about nanos not showing up in discord - but this is practically the first time I’ve seen this problem confirmed (maybe my bad, maybe I missed it?)
How do I compile launch pad for Ubuntu 24 and not make any mistakes? I want to use this for the Beta.
1 Like
Should I downgrade my arm nodes or does the ranking bot pick up the other earnings too? (since this issue is known for >3 weeks now…?)
1 Like
Thank you for pointing this out - my earnings were lower than I expected but I thought I screwed up my deployment…
1 Like
For the records, I restarted my nodes with 108.3-alpha.1 and got 10 nanos forwarded with the correct PK,
grep "Total forwarded amount" /var/log/safenode/safenode*/*.log* | awk '$NF
> 0'
/var/log/safenode/safenode4/safenode.log:[2024-07-03T03:50
:15.902585Z INFO sn_node::node] Reward forwarding sending
1 spends in this iteration. Total forwarded amount: 10
/var/log/safenode/safenode4/safenode.log:[2024-07-03T03:54
:25.912072Z INFO sn_node::node] Reward forwarding sending
1 spends in this iteration. Total forwarded amount: 10
and they got registered correctly by the bot.
This confirms my suspicions above.
1 Like
While we wait for the correction by the development team, do you know what the instructions are to ask safenode-manager to use version 108.3-alpha.1 instead of the current one ?
…
Ok I found the answer above… I should have read 
safenode-manager add --count 1 --version 0.108.3-alpha.1
2 Likes