You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
debug log shows some issues with messages sent by some nodes
if node can't get previeous_hash and block_height it still sends messages with empty block_height and previous_block_hash
example:
Another issue - some messages have no public_address field. That's leading to a validation error.
validate_data: Error
Sun 22 Aug 2021 19:45:39 UTC
-----------------------------------------------------------------------------------------------
Function Calls:
#1 validate_data: Invalid message
MESSAGE: {
"message_settings": "BLOCK_VERIFIERS_TO_BLOCK_VERIFIERS_ONLINE_STATUS",
}
The same issue with 'non-standard' messages
Function Calls:
#1 verify_data: Could not find the public key to verify the message
MESSAGE: NODE_TO_BLOCK_VERIFIERS_GET_RESERVE_BYTES_DATABASE_HASH|850951|XCA1pBdRSiveCMWgkbExKXW1D8UcjeDuHh72oKvmApYaPmKhWDnS18M9M4pyM2aXiFKHVdeBCgq6dWVjJwRegRTa543gaesH2M|RSx1Ips4ViIYF0zrWpDiOuPwhUcm40cLJyBfNR9zZHnuvKJiZaoCs1YzLYLFPMfmaEpNlma8RnqcVXiJXx9fmVCYJdrmNuyNYLp7|f41ec9ce7110f8cd311aff4b5d20bde4275cb58e5f0f4f8284112bd40c4c350a88210a88317c6c8a4922037245f431
The text was updated successfully, but these errors were encountered:
For the third one, that is correct. If a xcashd sends that type of message with a public address and key, then it gets validated by the delegates that they are part of db of delegates when the DDOS check happens. If a node just sends the block height then it just checks the IP for DDOS
so the above would error if that delegate is not in the db
🐛 BUG REPORT
debug log shows some issues with messages sent by some nodes
if node can't get previeous_hash and block_height it still sends messages with empty block_height and previous_block_hash
example:
Another issue - some messages have no public_address field. That's leading to a validation error.
The same issue with 'non-standard' messages
The text was updated successfully, but these errors were encountered: