2021-01-30 11:52:15 UTC IO Worker #2 INFO import #5037588 48/100 peers 1 GiB chain 392 MiB db 0 bytes queue 707 MiB sync RPC: 0 conn, 0 req/s, 0 µs
2021-01-30 11:53:12 UTC IO Worker #3 WARN sync 37 -> GetNodeData: item 32/384 – slow state fetch for hash 0xfd07a35aa1f08f6d000ac25693940ae7d1e08a398f57c0a32bc6fb203863d1db; took 100.459783ms, total 1.085668698s
2021-01-30 11:53:54 UTC IO Worker #0 WARN sync 59 -> GetNodeData: item 80/384 – slow state fetch for hash 0x6a8b0b2e9f491ec71f0520fe926e61e4d196677d9b2b9f433cf11960c3f3256d; took 58.694255ms, total 2.053041414s
2021-01-30 11:54:09 UTC IO Worker #3 WARN sync 36 -> GetNodeData: item 9/146 – slow state fetch for hash 0x2428697803410342b4bb85f89c3b68be470f31dc4f1ac89e0b93b10e848a8c98; took 149.416089ms, total 409.285426ms
2021-01-30 11:54:57 UTC IO Worker #2 WARN sync 101 -> GetNodeData: item 43/384 – slow state fetch for hash 0xb6652dcbd21ab24e7214f79799fa7685e1142aa6ec2102c957c8d97831665f28; took 101.86054ms, total 1.631807213s
2021-01-30 11:54:58 UTC IO Worker #3 WARN sync 66 -> GetNodeData: item 38/345 – slow state fetch for hash 0x6ae4b83a634d04c9d80bfbe986f8bff6cd5ad69a0b277fd973ad61530f910880; took 164.739382ms, total 1.422686605s
2021-01-30 11:57:19 UTC Verifier #1 INFO import Imported #11757114 0xfbe1…e05e (243 txs, 12.47 Mgas, 7111 ms, 55.24 KiB)
2021-01-30 11:57:32 UTC Verifier #1 INFO import Imported #11757115 0x2167…d5c7 (244 txs, 12.47 Mgas, 8167 ms, 53.97 KiB)
2021-01-30 11:57:36 UTC IO Worker #2 INFO import #5043258 79/100 peers 1 GiB chain 392 MiB db 0 bytes queue 102 MiB sync RPC: 0 conn, 0 req/s, 0 µs
2021-01-30 11:53:12 UTC IO Worker #3 WARN sync 37 -> GetNodeData: item 32/384 – slow state fetch for hash 0xfd07a35aa1f08f6d000ac25693940ae7d1e08a398f57c0a32bc6fb203863d1db; took 100.459783ms, total 1.085668698s
2021-01-30 11:53:54 UTC IO Worker #0 WARN sync 59 -> GetNodeData: item 80/384 – slow state fetch for hash 0x6a8b0b2e9f491ec71f0520fe926e61e4d196677d9b2b9f433cf11960c3f3256d; took 58.694255ms, total 2.053041414s
2021-01-30 11:54:09 UTC IO Worker #3 WARN sync 36 -> GetNodeData: item 9/146 – slow state fetch for hash 0x2428697803410342b4bb85f89c3b68be470f31dc4f1ac89e0b93b10e848a8c98; took 149.416089ms, total 409.285426ms
2021-01-30 11:54:57 UTC IO Worker #2 WARN sync 101 -> GetNodeData: item 43/384 – slow state fetch for hash 0xb6652dcbd21ab24e7214f79799fa7685e1142aa6ec2102c957c8d97831665f28; took 101.86054ms, total 1.631807213s
2021-01-30 11:54:58 UTC IO Worker #3 WARN sync 66 -> GetNodeData: item 38/345 – slow state fetch for hash 0x6ae4b83a634d04c9d80bfbe986f8bff6cd5ad69a0b277fd973ad61530f910880; took 164.739382ms, total 1.422686605s
2021-01-30 11:57:19 UTC Verifier #1 INFO import Imported #11757114 0xfbe1…e05e (243 txs, 12.47 Mgas, 7111 ms, 55.24 KiB)
2021-01-30 11:57:32 UTC Verifier #1 INFO import Imported #11757115 0x2167…d5c7 (244 txs, 12.47 Mgas, 8167 ms, 53.97 KiB)
2021-01-30 11:57:36 UTC IO Worker #2 INFO import #5043258 79/100 peers 1 GiB chain 392 MiB db 0 bytes queue 102 MiB sync RPC: 0 conn, 0 req/s, 0 µs
after one week syncing
but @Hamed_ta_gitlab
it is time to change to openethereum somehow,
worth to check the actual version available at
https://github.com/openethereum/openethereum/releases
it is time to change to openethereum somehow,
worth to check the actual version available at
https://github.com/openethereum/openethereum/releases
Apologies for this simple question. I had old, plain Parity on my computer, and am trying to clean up my wallets (invested my allocation in 2017-2018, then no more).. Parity Chrome extension is no longer on my computer. Don't know why. But, I have my original login and password, and phrase. Where do I find plain old Parity (not Parity Signer that has to be on an old phone offline), and sign in to recover my info? If it has to be Parity Signer, then what do I put in the New Account space since I don't see an option to recover an old wallet? Again apologies for bothering you, and thank you for your assistance. And don't bother to ask me for my ID info and phrase because I won't give it to you.
1 reply
can y'all help me out?
click that link
hi folks can you post a new invite to discord group? link above https://discord.gg/WrCAwrEE is expired....
I also have a query about how to access an old parity wallet... like earlier OP if i start process to import into Parity Mobile App I get warning
[[ " .. recovery phrase is not a valid BIP39 seed.it will be treated as a legacy parity brain wallet. make sure you understand the risks" ]]
Hi!
I need some help with ethereum located on old Parity wallet.
I have keystore and private key but I'm able only to restore primary eth address:
0x0009171Cc22A62D9565FAA401a91a54281815bCe
but funds are located on:
0x0eDfdd7393a1AFdf2dB9955d92C927942057254c
I have Parity 1.8 but it can't do full sync. I'm trying to execute function on contract but confirm button is disabled( probably due to lack of sync).
Is there any possibility to move this funds in 2021.
Can I use other wallet or write some "contract code" to transfer eth?
hi @leweokocyklopa @bspaugh
come and visit us in https://discord.gg/PVEtj74G
and ask your questions over there-
@leweokocyklopa if you still have the parity client, try to export the relevant wallet to a json,
i could help with importing that into metamask
come and visit us in https://discord.gg/PVEtj74G
and ask your questions over there-
@leweokocyklopa if you still have the parity client, try to export the relevant wallet to a json,
i could help with importing that into metamask
@ShellCrypto_twitter https://discord.gg/PVEtj74G
@roninkaizen @bspaugh Hi. Thaks for reply.
I have imported json to MetaMask already but problem is that funds are located on 0x0eDfdd7393a1AFdf2dB9955d92C927942057254c. It is kind of multisig wallet contract , it does not look like regular eth address. Parity wallet forced me to make this contract and move funds after update in 2017. MetaMask (and others) does not recognise this contract but only main address:0x0009171Cc22A62D9565FAA401a91a54281815bCe .
I asume that i should know some contract code from 2017 and probably only old Parity developers could help.
When I try to read the contract :
https://etherscan.io/address/0x0eDfdd7393a1AFdf2dB9955d92C927942057254c#code
there is problem with showing source code and i don't know why.
I find it dificult do contact with them. I'll keep trying.
I have imported json to MetaMask already but problem is that funds are located on 0x0eDfdd7393a1AFdf2dB9955d92C927942057254c. It is kind of multisig wallet contract , it does not look like regular eth address. Parity wallet forced me to make this contract and move funds after update in 2017. MetaMask (and others) does not recognise this contract but only main address:0x0009171Cc22A62D9565FAA401a91a54281815bCe .
I asume that i should know some contract code from 2017 and probably only old Parity developers could help.
When I try to read the contract :
https://etherscan.io/address/0x0eDfdd7393a1AFdf2dB9955d92C927942057254c#code
there is problem with showing source code and i don't know why.
I find it dificult do contact with them. I'll keep trying.
so you wrote and injected the contract
although i cannot read it
i guess there is a slight chance of getting the 3.687 ETH out of it
keep that account, as i need to somebody able to read it and
to give hints
to give hints
did i understand it right that you simply want to have the ETH out of it?
@roninkaizen Yes, ofcourse i want my eth back :)
@roninkaizen I have always thought that private key is enough to restore funds but not this time :(
@roninkaizen ling https://discord.gg/PVEtj74G does not work for me. Is it the same with discord.io/openethereum
How to synchronize kovan nodes
any help
im using parity 2.7.2
hey guys , https://github.com/openethereum/parity-ethereum shall I follow this to upgrade existing parity client on my nodes?
As bash <(curl https://get.parity.io -L) -r stable doesn't work anymore
is this README.md upto date?
