are you seeing any chain-proofs received from 167.235.35.172?
Folks check if you are seeing any chain-proofs received from 167.235.35.172 after the bootstrap node is enforced.
GridScript console available.
$ sct testnet
[Local:GridScript VM]: Commit target set. You may proceed.
$ sync
[TestNet:GridScript VM]: Terminal has been Synced to Perspective: bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
$ chain -show -block 34704
v------[ Block #34704: ] ------v
[BLOCK ID]: 2rYY5AGPYHCSLrhiZeJC7AZHogv9TSwcc8ip3heDsQ3NDcBNyR
[Type]: Key Block
[Key Height]: 32421
[Solved at]: Nov 20 20:49:01 2023
[Miner's ID]: 8Hc94oPkRL9nio5pnx1k1Lp6uGCGm1R7Awq6XxV22yub5FKHvSuh
[Difficulty]: 0.000
[Block Perspective]: BhKJQz3XsErwhHoquBR5bBxVVm9aARUNZTFePPFbbwdt8o4Vu
[Effective Perspective]: bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[Parent ID]: 2HA8671BcyTL3S5azCeowfCDrwZ2TggewvRgU1Vs4HMLG2gDj7
[ERG used]: 0
[ERG limit]: 0
[Nonce]: 0
[Reward]: unknown
[Total Reward]: 90000000000000000007
[Receipts #]: 1
[Transactions #]: 0
[Verifiables #]: 1
The Block is available locally.
$ chain -show -heaviest -block 34704
v------[ Block #34704: ] ------v
[BLOCK ID]: 2rYY5AGPYHCSLrhiZeJC7AZHogv9TSwcc8ip3heDsQ3NDcBNyR
[Type]: Key Block
[Key Height]: 32421
[Solved at]: Nov 20 20:49:01 2023
[Miner's ID]: 8Hc94oPkRL9nio5pnx1k1Lp6uGCGm1R7Awq6XxV22yub5FKHvSuh
[Difficulty]: 0.000
[Block Perspective]: BhKJQz3XsErwhHoquBR5bBxVVm9aARUNZTFePPFbbwdt8o4Vu
[Effective Perspective]: bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[Parent ID]: 2HA8671BcyTL3S5azCeowfCDrwZ2TggewvRgU1Vs4HMLG2gDj7
[ERG used]: 0
[ERG limit]: 0
[Nonce]: 0
[Reward]: unknown
[Total Reward]: 90000000000000000007
[Receipts #]: 1
[Transactions #]: 0
[Verifiables #]: 1
The Block is available locally.
[ GridScript-View (#) Activated. Status: Ready
$
Ultimium: released!
Sub-Task 484: finished.
Sub-Task 483: doneTargetMet (accomplished).
[Local:GRIDNET]: Average Mhps (NVIDIA-1) average Mhps: 6.998613
[Local:GRIDNET]: initializing worker: NVIDIA GeForce RTX 3070 (cloned) ( NVIDIA-1 )
[Local:GRIDNET]: NVIDIA-1 is warming up..
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[TestNet:Blockchain Manager]: Processing block (ID: iu8XJL3ZCf79Sh2m9YqwM89iSZGqxapUMpZE1NdwbTN4aaoUE )
[TestNet:Blockchain Manager]: The block does NOT aim to extend the current Main Chain..
[TestNet:Blockchain Manager]: Block is forking thus assuming prior key-leader.
[TestNet:Blockchain Manager]: Block is forking thus assuming prior leader.
[TestNet:Blockchain Manager]: Validating an incoming Key Block. ID: 2sysPsL6Fw8Rwqcws5pc4295keTw4JysXgueigkgGPeH2jg2Dp
[TestNet:Blockchain Manager]: I was unable to verify FRAUD at this stage. Assuming the block is OK.
[TestNet:Blockchain Manager]: Assuming an alternative Initial Effective Perspective bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Starting the Flow; Perspective: bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:Transaction Manager]: Reverting perspective back to bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Processing 0 transactions..
[TestNet:Transaction Manager]: Processing 0 verifiables..
[TestNet:Transaction Manager]: Processing 1 verifiables..
[Local:GRIDNET]: worker NVIDIA-1 is now ready.
Sub-Task 483: finished.
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:Transaction Manager]: Reverting perspective back to bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:StateDomain Manager]: Exiting the Flow..
[TestNet:Blockchain Manager]: Block candidate for height 34705 was decided to be INVALID. Reason: The time-difference between the block proposal and its parent is too high!
[TestNet:Blockchain Manager]: Cleaning up the blockchain Mem-Cache
[TestNet:Blockchain Manager]: Pruned 0 blocks
[TestNet:Blockchain Manager]: Freed 0 blocks
[TestNet:Blockchain Manager]: Scheduled to be Freed 0
[TestNet:Blockchain Manager]: Current Hot Storage Blockchain Cache Length: 156
[TestNet:Blockchain Manager]: Note: Blockchain Hot-Storage Cache pruning was NOT effective
[TestNet:Blockchain Manager]: ❎ Blockchain Manager chose to discard the block.
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: Aiming to generate a key block at height: 34705
[TestNet:Transaction Manager]: Operating Identity:1L4uFTMEvnCz5sFk5yNNRZKyxtdj3xFDu6
[TestNet:Transaction Manager]: An attempt to form a block is commencing..
Sub-Task 485: enqued.
[TestNet:Transaction Manager]: Commencing Proof-of-Work computations..
[Local:Work Manager]: Work 485 was divided into 1 parts. IDs: 2APaRzhmjn9g1YVFtquwLQp6VM3rS7Zm3MgHt4fi52doXmWM4v ShortID:486
Sub-Task 486: assigned to a worker.
NVIDIA-1 switched tasks.
Task 486: <----------------[[ assigned to NVIDIA-1 ]]
Sub-Task 486: getting prepared.
Sub-Task 486: prepared.
NVIDIA-1 is now working..
Activating a prepared task.
Sub-Task 485: being worked on. (reported by a sub-task)
Sub-Task 486: being worked on.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[TestNet:Blockchain Manager]: Freed 7 UDT Conversations
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
Ultimium: .-=========-.
'-=======-'/
_| .=. |_
((| {{1}} |))
| /| |/
__ '`' __/
_`) (`_
jgs _/________
/___________\n
Sub-Task 486: doneTargetMet (accomplished).
Sub-Task 485: doneTargetMet (accomplished). (reported by a sub-task)
Sub-Task 485: finished.
[TestNet:Transaction Manager]: Starting the Flow; Perspective: bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Processing known uncle blocks..
[TestNet:Transaction Manager]: Processing 0 verifiables..
[TestNet:Transaction Manager]: Processing 1 verifiables..
[TestNet:Transaction Manager]: aborting the Flow; Perspective: jLyRJocw82DQU1arVxwk4X5LNTu4fh8MSgDrL5BNhGmf8kqiB
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:Transaction Manager]: Reverting perspective back to bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:StateDomain Manager]: Exiting the Flow..
[TestNet:Transaction Manager]: The new block was formed properly.
[TestNet:Transaction Manager]: Block-Statistics:
[TestNet:Transaction Manager]: Block Type: Key Block
[TestNet:Transaction Manager]: 0of Basic Key-Block Reward
[TestNet:Transaction Manager]: 676.633668 difficulty
[TestNet:Transaction Manager]: My KEY block heading for processing! ID: zABdkshMM8kxPbpyMznFjZ1WjGKDMigaXDu6REWDaSVMZXMdG
[TestNet:Transaction Manager]: Block size:607 Bytes
[TestNet:Transaction Manager]: I'm dispatching the newly formed block to the Blockchain Manager for consideration.
[TestNet:Blockchain Manager]: Adding block zABdkshMM8kxPbpyMznFjZ1WjGKDMigaXDu6REWDaSVMZXMdG to processing queue. Position:0
[DSM-sync]: won't try 167.235.35.172 since tried recently.
Sub-Task 486: aborted.
worker's ( NVIDIA-1) task was stopped.
Ultimium: I'm releasing my resources..
Ultimium: released!
Sub-Task 486: finished.
Sub-Task 485: doneTargetMet (accomplished).
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[DSM-sync]: won't try 31.207.47.44 since tried recently.
[DSM-sync]: won't try 88.198.49.67 since tried recently.
[DSM-sync]: won't try 148.63.156.239 since tried recently.
[DSM-sync]: won't try 195.162.68.212 since tried recently.
[DSM-sync]: won't try 193.143.121.226 since tried recently.
[DSM-sync]: won't try 167.235.35.172 since tried recently.
[Local:GRIDNET]: Average Mhps (NVIDIA-1) average Mhps: 7.173015
[Local:GRIDNET]: initializing worker: NVIDIA GeForce RTX 3070 (cloned) ( NVIDIA-1 )
[Local:GRIDNET]: NVIDIA-1 is warming up..
[DSM-sync]: won't try 91.218.20.171 since tried recently.
[DSM-sync]: won't try 109.173.230.150 since tried recently.
[TestNet:Blockchain Manager]: Processing block (ID: zABdkshMM8kxPbpyMznFjZ1WjGKDMigaXDu6REWDaSVMZXMdG )
[TestNet:Blockchain Manager]: The block does NOT aim to extend the current Main Chain..
[TestNet:Blockchain Manager]: Block is forking thus assuming prior key-leader.
[TestNet:Blockchain Manager]: Block is forking thus assuming prior leader.
[TestNet:Blockchain Manager]: Validating an incoming Key Block. ID: 2a6DnUkysTKWivyu2RroDoGUNszUqfarLZnaHjwPuMF6bTZ81r
[TestNet:Blockchain Manager]: I was unable to verify FRAUD at this stage. Assuming the block is OK.
[TestNet:Blockchain Manager]: Assuming an alternative Initial Effective Perspective bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Starting the Flow; Perspective: bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:Transaction Manager]: Reverting perspective back to bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Processing 0 transactions..
[TestNet:Transaction Manager]: Processing 0 verifiables..
[TestNet:Transaction Manager]: Processing 1 verifiables..
[Local:GRIDNET]: worker NVIDIA-1 is now ready.
Sub-Task 485: finished.
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:Transaction Manager]: Reverting perspective back to bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:StateDomain Manager]: Exiting the Flow..
[TestNet:Blockchain Manager]: Block candidate for height 34705 was decided to be INVALID. Reason: The time-difference between the block proposal and its parent is too high!
[TestNet:Blockchain Manager]: Cleaning up the blockchain Mem-Cache
[TestNet:Blockchain Manager]: Pruned 0 blocks
[TestNet:Blockchain Manager]: Freed 0 blocks
[TestNet:Blockchain Manager]: Scheduled to be Freed 0
[TestNet:Blockchain Manager]: Current Hot Storage Blockchain Cache Length: 156
[TestNet:Blockchain Manager]: Note: Blockchain Hot-Storage Cache pruning was NOT effective
[TestNet:Blockchain Manager]: ❎ Blockchain Manager chose to discard the block.
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: Aiming to generate a key block at height: 34705
[TestNet:Transaction Manager]: Operating Identity:1L4uFTMEvnCz5sFk5yNNRZKyxtdj3xFDu6
[TestNet:Transaction Manager]: An attempt to form a block is commencing..
Sub-Task 487: enqued.
[TestNet:Transaction Manager]: Commencing Proof-of-Work computations..
[Local:Work Manager]: Work 487 was divided into 1 parts. IDs: utweHgtbB4a5gtE2f8pi1gMcgA5zSoM6CJbHw7UgK649vukG8 ShortID:488
Sub-Task 488: assigned to a worker.
NVIDIA-1 switched tasks.
Task 488: <----------------[[ assigned to NVIDIA-1 ]]
Sub-Task 488: getting prepared.
Sub-Task 488: prepared.
NVIDIA-1 is now working..
Activating a prepared task.
Sub-Task 487: being worked on. (reported by a sub-task)
Sub-Task 488: being worked on.
[TestNet:Transaction Manager]: Min. # of objects for block formation: 1
Ultimium: .-=========-.
'-=======-'/
_| .=. |_
((| {{1}} |))
| /| |/
__ '`' __/
_`) (`_
jgs _/________
/___________\n
Sub-Task 488: doneTargetMet (accomplished).
Sub-Task 487: doneTargetMet (accomplished). (reported by a sub-task)
Sub-Task 487: finished.
[TestNet:Transaction Manager]: Starting the Flow; Perspective: bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Processing known uncle blocks..
[TestNet:Transaction Manager]: Processing 0 verifiables..
[TestNet:Transaction Manager]: Processing 1 verifiables..
[TestNet:Transaction Manager]: aborting the Flow; Perspective: jLyRJocw82DQU1arVxwk4X5LNTu4fh8MSgDrL5BNhGmf8kqiB
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:Transaction Manager]: Reverting perspective back to bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:StateDomain Manager]: Exiting the Flow..
[TestNet:Transaction Manager]: The new block was formed properly.
[TestNet:Transaction Manager]: Block-Statistics:
[TestNet:Transaction Manager]: Block Type: Key Block
[TestNet:Transaction Manager]: 0of Basic Key-Block Reward
[TestNet:Transaction Manager]: 676.628232 difficulty
[TestNet:Transaction Manager]: My KEY block heading for processing! ID: eXAeNXSKn9xps4GCq3KziNWEa5yPoJA12oKE9kv6AKCtrupbP
[TestNet:Transaction Manager]: Block size:607 Bytes
[TestNet:Transaction Manager]: I'm dispatching the newly formed block to the Blockchain Manager for consideration.
[TestNet:Blockchain Manager]: Adding block eXAeNXSKn9xps4GCq3KziNWEa5yPoJA12oKE9kv6AKCtrupbP to processing queue. Position:0
Sub-Task 488: aborted.
worker's ( NVIDIA-1) task was stopped.
Ultimium: I'm releasing my resources..
Ultimium: released!
Sub-Task 488: finished.
Sub-Task 487: doneTargetMet (accomplished).
[Local:GRIDNET]: Average Mhps (NVIDIA-1) average Mhps: 7.186988
[Local:GRIDNET]: initializing worker: NVIDIA GeForce RTX 3070 (cloned) ( NVIDIA-1 )
[Local:GRIDNET]: NVIDIA-1 is warming up..
[TestNet:Blockchain Manager]: Processing block (ID: eXAeNXSKn9xps4GCq3KziNWEa5yPoJA12oKE9kv6AKCtrupbP )
[TestNet:Blockchain Manager]: The block does NOT aim to extend the current Main Chain..
[TestNet:Blockchain Manager]: Block is forking thus assuming prior key-leader.
[TestNet:Blockchain Manager]: Block is forking thus assuming prior leader.
[TestNet:Blockchain Manager]: Validating an incoming Key Block. ID: 4GSGtJbWNmEfshqUZbcZvUyoZPpKVNaqta6LWBQkbVmxoZPaL
[TestNet:Blockchain Manager]: I was unable to verify FRAUD at this stage. Assuming the block is OK.
[TestNet:Blockchain Manager]: Assuming an alternative Initial Effective Perspective bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Starting the Flow; Perspective: bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[Local:GRIDNET]: worker NVIDIA-1 is now ready.
Sub-Task 487: finished.
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:Transaction Manager]: Reverting perspective back to bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Processing 0 transactions..
[TestNet:Transaction Manager]: Processing 0 verifiables..
[TestNet:Transaction Manager]: Processing 1 verifiables..
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:Transaction Manager]: Reverting perspective back to bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNet:Transaction Manager]: Cleaning up the Flow
[TestNet:StateDomain Manager]: Exiting the Flow..
[TestNet:Blockchain Manager]: Block candidate for height 34705 was decided to be INVALID. Reason: The time-difference between the block proposal and its parent is too high!
[TestNet:Blockchain Manager]: Cleaning up the blockchain Mem-Cache
[TestNet:Blockchain Manager]: Pruned 0 blocks
[TestNet:Blockchain Manager]: Freed 0 blocks
[TestNet:Blockchain Manager]: Scheduled to be Freed 0
[TestNet:Blockchain Manager]: Current Hot Storage Blockchain Cache Length: 156
[TestNet:Blockchain Manager]: Note: Blockchain Hot-Storage Cache pruning was NOT effective
[TestNet:Blockchain Manager]: ❎ Blockchain Manager chose to discard the block.
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: Aiming to generate a key block at height: 34705
[TestNet:Transaction Manager]: Operating Identity:1L4uFTMEvnCz5sFk5yNNRZKyxtdj3xFDu6
[TestNet:Transaction Manager]: An attempt to form a block is commencing..
Sub-Task 489: enqued.
[TestNet:Transaction Manager]: Commencing Proof-of-Work computations..
[Local:Work Manager]: Work 489 was divided into 1 parts. IDs: 2jrR8JmDRPPFF16NoKoEQF9kMHo9qZJqmZapVKjHheTeNSGjc3 ShortID:490
Sub-Task 490: assigned to a worker.
NVIDIA-1 switched tasks.
Task 490: <----------------[[ assigned to NVIDIA-1 ]]
Sub-Task 490: getting prepared.
Sub-Task 490: prepared.
[TestNet:Blockchain Manager]: Freed 21 UDT Conversations
NVIDIA-1 is now working..
Activating a prepared task.
Sub-Task 489: being worked on. (reported by a sub-task)
Sub-Task 490: being worked on.
Ultimium: .-=========-.
'-=======-'/
After this command ^^^
net -boot 167.235.35.172
Folks please refrain from submitting logs as images @chill_dj_azm
(we cannot search through these among others).
In your logs search for chain-proof analysis results. Forget the results of block 34705 processing. We already know that nodes are producing blocks on their own.
What we need to close in on is the reason for which you are not receiving valid chain-proofs.
Right now are are implementing tools which would allow you to set only a specific node with which communication is to be maintained on order to lower the search space of possible errors and to make nodes more resilient against data eclipsing attacks.
It is possible that some of the community provided nodes (acting now as bootstrap nodes) the IPs of which are hard-coded into Core have been into data eclipsing practices’ themselves.
So in short look for chain-proof analysis results.
Chai-Proofs are data structures instructing your nodes which blocks to download further.
These need to be delivered by other nodes.
Here’s the assessment which we’ve carried out on YouTube LIVE
-
34705 is not being accepted due to data integrity issues
-
the resulting Merkle Patricia Root differs from what expect
-
34704 was the recent hard-fork point
-
yet the block candidate for 34705 is part of the currently proclaimed global chain proof
-
your nodes wouldn’t agree to accept
-
your nodes would truncate heaviest chain proof and keep looking for something valid
-
in worst case scenario they would move on forking an alternative history of events on their own
-
and those blocks you mine would be rejected as well… because too much time has passed since 3704 was created.
we will be assessing this further…
The most interesting aspect of this situation though is that some Operators were successfully synchronizing their nodes from block 0, while others such as yourselves folks, you were unable.
Thus either someone is lying or we haven’t researched the situation sufficiently yet.
We have performed a full-resync on this node and let is sync from Genesis Block.
Let’s see how it goes. We might be having multiple issues at same time as well.
after trying resync we run into another issue some Operators were reporting
WARNING: During the Genesis Block formation 'money' will be generated out of the blue!
[TestNet:Transaction Manager]: During this stage, initial ICO investors etc. will be rewarded.
[TestNet:Transaction Manager]: Preparing to generate the initial State Domains..
[TestNet:Transaction Manager]: Genesis Facts-File found (GenesisFacts.txt) ! Loading..
[TestNet:Transaction Manager]: Genesis Rewards' fingerprint: 2MiMYJLWt9NWDzGag48QV6FKrWtZfSwEJKaVvW2m6MfHZHHPeQ
[TestNet:Transaction Manager]: The integrity of the Genesis Facts File verified.
[TestNet:Transaction Manager]: Operating Identity:1Lozhs8YAt5DkRwix1fbYchARyxupTXJ29
[TestNet:Transaction Manager]: An attempt to form a block is commencing..
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: The blockchain is empty! I'll aim to generate the Genesis Key Block
[TestNet:Transaction Manager]: Initiating VMMaintenance procedure (Overwatch' privileges overridden).
[TestNet:Transaction Manager]: Genesis Rewards' fingerprint: 2MiMYJLWt9NWDzGag48QV6FKrWtZfSwEJKaVvW2m6MfHZHHPeQ
[TestNet:Transaction Manager]: The integrity of the Genesis Facts File verified.
[TestNet:Transaction Manager]: Operating Identity:1Lozhs8YAt5DkRwix1fbYchARyxupTXJ29
[TestNet:Transaction Manager]: An attempt to form a block is commencing..
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: The blockchain is empty! I'll aim to generate the Genesis Key Block
[TestNet:Transaction Manager]: Initiating VMMaintenance procedure (Overwatch' privileges overridden).
[TestNet:Transaction Manager]: Forming the Genesis Rewards Block..
[TestNet:Transaction Manager]: WARNING: During the Genesis Block formation 'money' will be generated out of the blue!
[TestNet:Transaction Manager]: During this stage, initial ICO investors etc. will be rewarded.
[TestNet:Transaction Manager]: Preparing to generate the initial State Domains..
[TestNet:Transaction Manager]: Genesis Facts-File found (GenesisFacts.txt) ! Loading..
[TestNet:Transaction Manager]: Genesis Facts-File found (GenesisFacts.txt) ! Loading..
tried commands below
sct testnet
overwatch
net -boot 167.235.35.172
resync
found this in booting phase 2
[TestNet:Network Manager]: User provided Bootstrap node (167.235.35.172) will be the first one to try.
Whitelisting IP Address: 127.0.0.1
Whitelisting IP Address: 0.0.0.0
Whitelisting IP Address: 112.0.171.45
[TestNet:Network Manager]: Pre-flight checks for the internal HTTP/WWW sub-system..
[Networking Assistant]: No process found using port 443
[Networking Assistant]: No process found using port 80
Solid Storage: File directory was initialized at: 'C:\Users\m010\AppData\Roaming\GRIDNET'
Detected valid Certificate and Private-Key!C:\Users\m010\AppData\Roaming\GRIDNET\cert.pem
[TestNet:Blockchain Manager]: WWW Server (RAW) successfully bound to: http://0.0.0.0:80
[TestNet:Blockchain Manager]: WWW Server (TLS) successfully bound to: https://0.0.0.0:443
[TestNet:Blockchain Manager]: Note: blockchain formation for Local Sandbox is *NOT* advised except for development and testing.
[TestNet:Blockchain Manager]: [ Setting-up Network Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Local System Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Decentralized VM Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Debug Info Notifications ]
[TestNet:Blockchain Manager]: I'm now running
[TestNet:Blockchain Manager]: [ Setting-up Unknown Notifications ]
[TestNet:Settings]: keyChain for: 1QEvoe1fxthiz5vHK2x3MPbYFKbHz32c35 was FOUND!
[TestNet:Blockchain Manager]: Operator's Key-Chain ID:
[TestNet:Blockchain Manager]: Operator's State Domain ID: 1QEvoe1fxthiz5vHK2x3MPbYFKbHz32c35
[TestNet:Blockchain Manager]: Note: Your current ID within the network is: 1QEvoe1fxthiz5vHK2x3MPbYFKbHz32c35 use 'getNextID' to generate and set new ID from your key-chain at any moment.
[TestNet:Blockchain Manager]: Retrieving paths from cache..
[TestNet:Blockchain Manager]: getting the Chain-Proof from Cold Storage..
[TestNet:Blockchain Manager]: Verified Chain-Proof retrieved.
[TestNet:Blockchain Manager]: Validating availability of the recent Perspective..
Seems that i can’t get the chain-proof from 167.235.35.172 . it still read the cold storage in my device.
Another log
[TestNet:Blockchain Manager]: Initializing Kademlia-based node discovery..
[TestNet:Blockchain Manager]: Bootstrapping Peer Discovery Service at 0.0.0.0:443
[TestNet:Blockchain Manager]: Bootstrap peer is set to: 167.235.35.172:443
[TestNet:Network Manager]: created with id '4955b41a67d711a6cc2052aa89cc2ae3eda2a7dd6df1ee9d64de5186d940 (addr): 1QEvoe1fxthiz5vHK2x3MPbYFKbHz32c35'.
[TestNet:Network Manager]: Network View bootstrapping using peer '167.235.35.172:443'.
[TestNet:Transaction Manager]: Initiating Mem-Pool clean-up
[TestNet:Transaction Manager]: Initiating Mem-Pool clean-up
[TestNet:Network Manager]: Bootstrap node responded.
[TestNet:Blockchain Manager]: Launching the Kademlia thread..
[TestNet:Blockchain Manager]: I'll wait for 60 (sec) for peers' discovery..
[TestNet:Blockchain Manager]: Nr. of discovered peers: 21
[TestNet:Transaction Manager]: Initiating Mem-Pool clean-up
[TestNet:Blockchain Manager]: Total number of discovered GRIDNET Core Peers: 21
[TestNet:Network Manager]: All the enabled communication sub-system INITIALIZED. Commencing further..
[TestNet:Network Manager]: I'm now running
[TestNetSB:Blockchain Manager]: Lo and behold; initializing the Great GRIDNET TestNetSB Blockchain Manager..
[TestNetSB:Blockchain Manager]: Note: disabling blockchain formation as data-analysis won't be performed..
[TestNetSB:Blockchain Manager]: Note: blockchain formation for Local Sandbox is *NOT* advised except for development and testing.
[TestNetSB:Blockchain Manager]: [ Setting-up Network Notifications ]
[TestNetSB:Blockchain Manager]: [ Setting-up Local System Notifications ]
[TestNetSB:Blockchain Manager]: [ Setting-up Decentralized VM Notifications ]
[TestNetSB:Blockchain Manager]: [ Setting-up Debug Info Notifications ]
[TestNetSB:Blockchain Manager]: [ Setting-up Unknown Notifications ]
[TestNetSB:Settings]: keyChain for: 1QEvoe1fxthiz5vHK2x3MPbYFKbHz32c35 was FOUND!
[TestNetSB:Blockchain Manager]: Retrieving paths from cache..
[TestNetSB:Blockchain Manager]: getting the Chain-Proof from Cold Storage..
[TestNetSB:Blockchain Manager]: Verified Chain-Proof retrieved.
[TestNetSB:Blockchain Manager]: Validating availability of the recent Perspective..
[TestNetSB:Blockchain Manager]: Current perspective available.
[TestNetSB:Blockchain Manager]: Heaviest Chain-Proof retrieved.
[TestNetSB:Blockchain Manager]: Retrieved body of current Leader block: 2rYY5AGPYHCSLrhiZeJC7AZHogv9TSwcc8ip3heDsQ3NDcBNyR
[TestNetSB:Blockchain Manager]: Current Blockchain height: 34704
[TestNetSB:Blockchain Manager]: Cached perspective for the current 'check-pointed' Leader has been retrieved: 0
[TestNetSB:Blockchain Manager]: Current Effective Perspective: bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[TestNetSB:Blockchain Manager]: Testing the main StateTrie DB. This might take some time..
[TestNet:Transaction Manager]: Initiating Mem-Pool clean-up
[TestNetSB:Blockchain Manager]: Finished. There are 1444 State Domains in total.
[TestNetSB:Blockchain Manager]: 1444 State Domains found.
[TestNetSB:Transaction Manager]: Waiting for Blockchain Manager to become ready..
[TestNetSB:Transaction Manager]: Waiting for myself to become ready..
[TestNetSB:Transaction Manager]: I'm ready, commencing further..
[TestNetSB:Transaction Manager]: Waiting for Blockchain Manager to become ready..
[TestNetSB:Transaction Manager]: Waiting for myself to become ready..
[TestNetSB:Transaction Manager]: I'm ready, commencing further..
[TestNetSB:Transaction Manager]: Waiting for Blockchain Manager to become ready..
[TestNetSB:Transaction Manager]: Waiting for myself to become ready..
[TestNetSB:Blockchain Manager]: I'm now running
[TestNetSB:Blockchain Manager]: Initializing #GridScript (De)Compiler..
[TestNetSB:Transaction Manager]: I'm ready, commencing further..
[TestNetSB:Transaction Manager]: Blockchain Manager ready, commencing further..
[TestNetSB:Transaction Manager]: Running
[TestNetSB:Transaction Manager]: I'm ready; Firing up block-formation sub-systems! (Key-Blocks:Disabled Data-Blocks:Disabled)
[TestNetSB:Transaction Manager]: Blockchain Manager ready, commencing further..
[TestNetSB:Transaction Manager]: Running
Provide this for refer @CodesInChaos @vega4
My node is also stuck on block 34704.
$ chain -show -heaviest -block 34704
v------[ Block #34704: ] ------v
[BLOCK ID]: 2rYY5AGPYHCSLrhiZeJC7AZHogv9TSwcc8ip3heDsQ3NDcBNyR
[Type]: Key Block
[Key Height]: 32421
[Solved at]: Nov 20 12:49:01 2023
[Miner’s ID]: 8Hc94oPkRL9nio5pnx1k1Lp6uGCGm1R7Awq6XxV22yub5FKHvSuh
[Difficulty]: 0.000
[Block Perspective]: BhKJQz3XsErwhHoquBR5bBxVVm9aARUNZTFePPFbbwdt8o4Vu
[Effective Perspective]: bFzPKiA16iK3XcwgqyTF6DcXJMK7PR3bqy6YYDzGqQJuZ1MPz
[Parent ID]: 2HA8671BcyTL3S5azCeowfCDrwZ2TggewvRgU1Vs4HMLG2gDj7
[ERG used]: 0
[ERG limit]: 0
[Nonce]: 0
[Reward]: unknown
[Total Reward]: 90000000000000000007
[Receipts #]: 1
[Transactions #]: 0
[Verifiables #]: 1
The Block is available locally.
Despite issuing the command:
net -boot 167.235.35.172
nothing has changed and the node is still in the loop.
This issue is now fixed.