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
Before WIP0019: RADType::Unknown are accepted, and treated as HttpGet.
WIP0019: RADType::Unknown are rejected.
WIP0020: RADType::Unknown are accepted, and resolved with RadonTypes::RadonError(UnhandledIntercept { inner: None, message: Some("inner: UnknownRetrieval") }).
This is implemented in the validate_rad_request function:
So this looks like a bug introduced when implementing WIP0020. I believe that the intended behavior was to reject RADType::Unknown sources, because they were already being rejected after WIP0019, so that should be fixed.
However, this issue shouldn't have any negative effects on the network, because we used to accept this kind of transactions in the past, and all the other validations are working correctly so it is not possible to abuse this bug to perform double spends or anything like that.
The text was updated successfully, but these errors were encountered:
Data requests with RADType::Unknown sources are wrongly accepted into blocks since WIP0020.
Example transaction: 38d8cf497622082fa8fd4e89831641834918a99472b722310d60664046a29883
Summary of the behavior:
RadonTypes::RadonError(UnhandledIntercept { inner: None, message: Some("inner: UnknownRetrieval") })
.This is implemented in the validate_rad_request function:
witnet-rust/validations/src/validations.rs
Line 239 in 11d37d3
So this looks like a bug introduced when implementing WIP0020. I believe that the intended behavior was to reject RADType::Unknown sources, because they were already being rejected after WIP0019, so that should be fixed.
However, this issue shouldn't have any negative effects on the network, because we used to accept this kind of transactions in the past, and all the other validations are working correctly so it is not possible to abuse this bug to perform double spends or anything like that.
The text was updated successfully, but these errors were encountered: