# Testnet Known Limitations These limitations will NOT be applicable for Bug Bounty Reward. ----- ### 1. Generating dust could lead nodes memory issues Mini UXTOs (normally 1 WIT, known as dust) could produce significant RAM issues in a future. This could lead to generalized network disruption and technical impossibility to synchronize new nodes. ### 2. Using "Inconsistent Source Attack" to affect the Active Reputation Set As laid out in [this article](https://medium.com/witnet/how-can-decentralized-oracle-networks-deal-with-inconsistent-source-attacks-f1cdde838795) an attacker could use "inconsistent" requests that reduce the reputation of honest nodes, allowing them to collect enough distributed reputation to hold a majority in the consensus of a data requests. In addition, an affected Active Reputation Set could be used to stop the chain for a significant lapse of time. Currently, with trapezoidal eligibility, the risk has been significantly reduced. ### 3. Deanonymization Currently, creating a request to an API like whatsmyip website, allows anyone to see the IPs of node operators. Addresses containing a high number of WIT tokens or high reputation could be targeted in a possible DoS attack.