I can say with certaintly that if it is not registered at Parity, it will not show up. so go to registry in applications and see if the token symbol shows up in your query
I have just tried to upgrade from 1.6.8 to 1.6.9 ( https://github.com/vincentserpoul/paritypoa ) and I can't access the UI or RPC anymore (it's running, and the block are being created, as normal)
If I downgrade to 1.6.8 everything is fine (container rebuilt from scratch)
I can't see anything in the changelog that can be linked to this, any clue?
If I downgrade to 1.6.8 everything is fine (container rebuilt from scratch)
I can't see anything in the changelog that can be linked to this, any clue?
@danielwalton yes, talk to me :)
@dragonmaiden could you try a refresh on that page and report if it persists?
@Logannj which token are you talking about? did you check whether the toke is registered with the parity token registry (see applications).
@5chdn
@btcmacroecon thanks for reply. The people doing the ICO just gave some token details saying that's all that I would need. They didn't give any step by step on what to do on parity. I put in address I sent my eth to for there coin in the registry and its all zeros. I checked on ethplorer.io and it does show that I'm owner of tokens I bought. so it looks like they did send me tokens. I'm just stuck on part on what is supposed to happen in parity next. I put in token info so I can watch it in parity. I thought I would have another wallet or a section just showing the number of tokens I bought that I can do something with one day if they ever get listed in an exchange. this is link to the ICO - https://www.slogn.net/ico.html . I'm not trying to spam, just wanted you to see details they on token. I already posted to the ICO people for some step by step instructions in parity but they haven't so far. I'm just not sure if I'm supposed to do more. thanks again for any help.
way longer than git itself takes...
I can't find a mention on your twitter
SECURITY ALERT
- Severity: Critical
- Product affected: Parity Wallet
- Affected implementations: Parity 1.5 or later
- Summary: A vulnerability in a version of the multi-sig wallet contract has been reported.
- Mitigation steps: Any user with funds in a multi-sig wallet created in Parity with the affected implementations should immediately move their funds to a secure address.
yes
was removed/delayed to give the whitehats at the foundation a chance to save the funds.
however, since it's tweeted anyway now...
if you have a parity-based multisig, move your funds to a secure address ASAP
if you don't have funds in a multisig, or it wasn't created with parity, then you've nothing to do.
three accounts have been compromised; those visible here: https://etherscan.io/address/0xb3764761e297d6f121e79c32a65829cd1ddb4d32#internaltx
there is an effort by the foundation underway to secure funds in other wallets to prevent any further compromises; they will make an announcement in their own time.
and I guess accounts created by parity are safe still?
Only Multisig wallets are the problem.
@KurtKnudsen sure
