ordian on ao-github-actions
initial github actions (compare)
s3krit on mp-de-parityify
sed magic find . -type f -exec… (compare)
ordian on perf
ordian on master
Faster kill_garbage (#11514) *… (compare)
ordian on na-engine-signer-dont-use-msg-only-zeroes
ordian on master
[EngineSigner]: don't sign mess… (compare)
niklasad1 on na-engine-signer-dont-use-msg-only-zeroes
forgot formatting change (compare)
miketang* Hi, anybody using module gossip_network? I am doing some works on consensus, and use gossip_network directly. There are 4 nodes now, for each one node, the underlying p2p network has recognized other 3 nodes, but in the layer of gossip network, the peers set is empty? Why? Should I do some configurations or settings? I have done register_notifications_protocol. Thank you.
miketangIs this related to authority_discovery service? I don't spawn this service in my node.
Hello Parity! We at gnosis found ourselves writing some duplicate code converting
U256 to and from
f64 and thought it would make the most sense to upstream this chunk of code. I have just submitted a PR containing this, but it is my first contribution to your parity-common project so pleas let me know if there is anything missing! Cheers
"Bridge" -- Transaction was not mined within750 seconds, please make sure your transaction was properly sent. Be aware that it might still be mined!.`
`Error: *** Deployment Failed ***
Hi All, I am using s-8vcpu-32gb 32768 8 core 640 SSD server and started to sync to 2.5.13-stable. start command is this.
parity --warp-barrier=11077521 --allow-ips=public --cache-size=16384 --min-peers=400 --max-peers=500 --max-pending-peers=200 --no-periodic-snapshot -l txqueue
parity started more the 10 hour but stoped snapshot syncing process after 375 like this
2020-11-06 19:55:17 UTC IO Worker #3 INFO import Syncing snapshot 375/6080 #0 272/400 peers 832 bytes chain 512 KiB db 0 bytes queue 233 KiB sync RPC: 0 conn, 0 req/s, 0 µs
can any one salve problem ?
How does one use parity these days? I haven't used it since 2018, when it was an windows executable. Is there an article/docs for migrating to the new process. I still have an old wallet+passphrase etc.
I mean to say, there seems to be a plethora of products now. Which to use to access the early 2018's era wallet?
Hello, sorry for invading your privacy
Please I will appreciate if you read
I am Logan Dexter from Netherlands
I want to introduce you to a money making opportunity. Its a bitcoin trading company that helps you generate profit through trading cryptocurrency
It’s a highly profitable investment platform, it helps you trade and generate profits and then send it to your account daily. You will be able to earn 10% of your investment daily for up to 30 days and you also get your principal
I know it sounds too good to be true, I understand because I also felt like that when I first met them but now am fully convinced that it’s all true because I have earned up to $5000 with them.
You can also earn 5% in referral bonus if you don’t have capital, All you need to do is refer someone and you can also earn. As am doing now
It doesn’t require much of your time, all you need to do is register and deposit and you will start earning daily
If you don’t know anything about bitcoin you can also text me on Whatsaap so I will educate you more.
Parity Ethereum version: 2.7.1
Operating system: Linux(ubuntu16)
Installation: built from source
Fully synchronized: no
My parity version is "parity Ethereum / v2.5.5-stable-3ebc769-20190708/x86_ 64-linux-gnu/rustc1.36.0”
Why can't I sync my wallet when it's started
The output has always been like this:
0/ 5 peers 832 bytes chain 512 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 29 req/s, 20 µs
0/ 5 peers 832 bytes chain 512 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 743 req/s, 19 µs
0/ 5 peers 832 bytes chain 512 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 538 req/s, 18 µs
0/ 5 peers 832 bytes chain 512 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 119 req/s, 18 µs
0/ 5 peers 832 bytes chain 512 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 24 req/s, 18 µs
0/ 5 peers 832 bytes chain 512 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 336 req/s, 19 µs
0/ 5 peers 832 bytes chain 512 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 476 req/s, 20 µs
0/ 5 peers 832 bytes chain 512 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 626 req/s, 20 µs
Hi, can someone please explain me the difference between
parity_nextNonce? I'm reading the code but as a beginner to the codebase, it's not clear to me how the results of both calls relate to each other.
Am I right in thinking that
eth_getTransactionCount only considers mined transactions, while
parity_nextNonce also considers the pool of pending transactions? Is a signed but not submitted transaction increasing the nonce returned by