-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Allow whitelisting of tokens. #6783
Comments
Note: This particular technique is clever in that it costs me ETH at the moment to clear the Simoleans out of my account. Not only do I have to pay the cost of transferring them, but I also have to pay the cost to initialize them into my account since the airdrop mechanism made it so users pay initialization costs. |
I'm also tired of seeing tiny bits of worthless tokens in my accounts just because some dumb marketing airdropped them, and Simolean scheme can be exploited to write anything in all Parity UI clients, even offensive words. |
Yeah, we already have an idea for this. Stay tuned. Meanwhile, I will remove spammy tokens like SIM. Just nuked it. |
What about using it to inject javascript code? I hope that field is sanitized in the web client. |
There is no JS inject avenue. The issue with the SIM tokens, is as follows -
In the case of SIM it returns > 0 balance for all addresses. |
Spammy tokens like Simleon and Penis won't show up if you upgrade to 1.8.1 (stay tuned for binaries in a couple of hours). |
I'm on 1.8.4 beta, and I still see the PNS token. |
I'm on 1.8.4 beta and I still see the PNS token. |
@5chdn can this be reopened? It is still an issue. |
@43061b4a Did you trying clearing your browser local storage? window.localStorage.clear() Did the trick for me! |
window.localStorage.clear() - This goes where exactly? Saying things like this is like saying "we don't expect non-technical users to use our product" or "penis coin is not real just get over it" Its gross and in very poor taste. Do something about it. Its one of the first things a user notices when using the Parity wallet and it means I can't really tell my friends to use it, its embarrassing. |
This goes in the web-developer console area. See more details here for firefox. Local storage is somewhat newer data storage mechanisms and hence browser and software may not be as mature just yet. But I agree that this is something that should be addressed. |
Unable to make a connection to the Parity Secure API. To update your secure token or to generate a new one, run parity signer new-token and paste the generated token into the space below. Ensure that both the Parity node and this machine connecting have computer clocks in-sync with each other and with a timestamp server, ensuring both successful token validation and block operations. Pathetic |
And its STILL THERE even after going to all the trouble |
What version of Parity are you running? and on what OS? Clearing storage fixed it for me, I'm running on Ubuntu. |
Windows |
Are you fully synchronized? |
Those spam tokens are taking space on my display, now there are 2PR, BET, HSC, ROT, WIT... A blacklist functionality is really needed. |
Moved to parity-js/shell#80 |
The recent Simolean airdrop to every Ethereum account has made it so all of my accounts/contractsin Parity now show me as having 10,000 Simoleans. This is quite annoying since they are worthless and this is really just an advertising scheme. As a user, I would like the ability to click on a token in the UI and have it blacklisted so it no longer shows up for me.
I'm worried that the whole "automatically list tokens" thing is going to become more and more problematic as advertisers realize that for a couple of dollars they can make their random worthless token show up on everyone's account in Parity (and likely other wallet UIs). I'm not sure what the best long-term solution for this is since I think we are all generally against censorship, but at the same time I think we need a way to mitigate this sort of low-cost spam.
The text was updated successfully, but these errors were encountered: