epheph that could just be like 1 word
epheph also, MyCrypto can be downloaded, you can try old versions
epheph anyway, if you go to "print" on the address widget, do you see a "private key"?
epheph in MEW
epheph wow, this is a terrible bug in MyEtherWallet, not showing you the private key in the print page when you use a 12w seed. i'm filing it now
do you have an address i can send you a tip to?
epheph oh did you get it?!
epheph nbd, thx for the offer. good luck!
epheph i'm glad i found this bug in MEW while we were looking into this, it's pretty serious for MEW to say "here is your paper wallet" and NOT give you a private key! that's what the prod version does right now
Are there any recommended items abount parity-bridge? I can't find the contracts of parity-bridge now.
Hello~
I'm running a ropesteen testnet through Parity (v2.7.X), and it's stuck syncing at block #8579999.
But when you look at etherscan, it's currently sinking from #8569345, and some other explorer's sync is stuck at #8579999, like me.
Ropsten's chain seems to have divided, so I'd like to know which is right.
When I try sign a transaction to transfer KSM from polkadot.js UI i get the ' Unable to parse transaction: No private key found for account ..' error. I readded the account using the QR code and i can see the balance.
Anyone know what the issue is
@MinwooJ @denis_artemenko_twitter you're not alone, I've created an issue here - openethereum/openethereum#11862
this channel seems to be dead though no more support from parity/OpenEthereum devs anymore :(
Jam Taixu Chen (Gitter): you might want to move towards the substrate technical channel (on riot/element), but github.com/paritytech/frontier models one way to do this, where basically you need to create a pallet to wrap around blocks of the chain you are forking
hello, I want to test a simple wasm contract with latest openethereum, but I can't find the way to deploy and test my contracts. Any idea on this ? Thanks in advance...
the tutorial in https://github.com/openethereum/parity-poa-tutorial is broken due to
the tutorial in https://github.com/openethereum/parity-poa-tutorial is broken due to
unable to unlock accounts...
where should I start ?
Hello, guys! New here.
I am trying to compile polkadot on armbian but its failing paritytech/polkadot#1712
I am trying to compile polkadot on armbian but its failing paritytech/polkadot#1712
am seeing some odd behavior on a POA node, and our transactions are failing:
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | [Tx 6] UnverifiedTransaction { unsigned: Transaction { nonce: 126927, gas_price: 0, gas: 1600000, action: Call(0x67e90a54aeea85f21949c645082fe95d77bc1e70), value: 0, data: [1
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | [Tx 5] UnverifiedTransaction { unsigned: Transaction { nonce: 126926, gas_price: 0, gas: 1600000, action: Call(0x67e90a54aeea85f21949c645082fe95d77bc1e70), value: 0, data: [2
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | [Tx 4] UnverifiedTransaction { unsigned: Transaction { nonce: 126925, gas_price: 0, gas: 1600000, action: Call(0x67e90a54aeea85f21949c645082fe95d77bc1e70), value: 0, data: [1
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | [Tx 3] UnverifiedTransaction { unsigned: Transaction { nonce: 126924, gas_price: 0, gas: 1600000, action: Call(0x67e90a54aeea85f21949c645082fe95d77bc1e70), value: 0, data: [1
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | [Tx 2] UnverifiedTransaction { unsigned: Transaction { nonce: 126923, gas_price: 0, gas: 1600000, action: Call(0x67e90a54aeea85f21949c645082fe95d77bc1e70), value: 0, data: [1
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | [Tx 1] UnverifiedTransaction { unsigned: Transaction { nonce: 126922, gas_price: 0, gas: 1600000, action: Call(0x67e90a54aeea85f21949c645082fe95d77bc1e70), value: 0, data: [1
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | Transactions:[Tx 0] UnverifiedTransaction { unsigned: Transaction { nonce: 126921, gas_price: 0, gas: 1600000, action: Call(0x67e90a54aeea85f21949c645082fe95d77bc1e70), value
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | Uncles:
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | Header: Header { parent_hash: 0xdf2a6b1347a2398a8e71ca51d868ac1875fb76296549c9aa49e979e2206c253f, timestamp: 1600955460, number: 17313560, author: 0xcf260ea317555637c55f70e55
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | RLP: f90b52f90233a0df2a6b1347a2398a8e71ca51d868ac1875fb76296549c9aa49e979e2206c253fa01dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d4934794cf260ea317555637c55f70e
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | ) } })
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 11: clone
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 10: start_thread
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 9: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 8: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 7: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 6: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 5: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 4: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 3: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 2: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 1: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 0: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | Bad block detected: Error(Execution(InvalidNonce { expected: 0, got: 126921 }), State { next_error: None, backtrace: InternalBacktrace { backtrace: Some(stack backtrace:
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 2020-09-24 13:51:00 UTC
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | ) } })
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 11: clone
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 10: start_thread
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 9: <unknown>
Sep 24 13:51:00 ip-10-0-1-223 docker-compose[16070]: parity | 8: <unknown>
Anyone know about full stack solutions to actually roll out a token? What I mean is....I know how to deploy an ERC20 smart contract...However, I think you'd agree there are tons of other parts to the execution if someone like a restaurant wants to do their own coin!? Like.....How sell the tokens in a secure manner to the public? How implement something like gift cards? What wallet to use? etc. Any advice?
I am having some problems with running my node. I am connecting via websockets and listening to pending transactions. I try to fetch the transaction data when I receive a pending transaction and it takes many seconds, even minutes, to receive the response. I can't find anything related via searching. Has anybody run in to this problem?
at times, there is a burst of speed where a bunch of them will respond within 50ms. but then it will go right back to 30 seconds+
2020-10-15 05:52:51 UTC main INFO openethereum::run Starting OpenEthereum/v3.0.1-stable-8ca8089-20200601/x86_64-unknown-linux-gnu/rustc1.43.1
2020-10-15 05:52:51 UTC main INFO openethereum::run Keys path /home/ubuntu/.local/share/openethereum/keys/ethereum
2020-10-15 05:52:51 UTC main INFO openethereum::run DB path /home/ubuntu/.local/share/openethereum/chains/ethereum/db/906a34e69aec8c0d
2020-10-15 05:52:51 UTC main INFO openethereum::run State DB configuration: fast
2020-10-15 05:52:51 UTC main INFO openethereum::run Operating mode: active
2020-10-15 05:52:51 UTC fetch DEBUG fetch processing requests ...
2020-10-15 05:52:51 UTC main INFO openethereum::run Keys path /home/ubuntu/.local/share/openethereum/keys/ethereum
2020-10-15 05:52:51 UTC main INFO openethereum::run DB path /home/ubuntu/.local/share/openethereum/chains/ethereum/db/906a34e69aec8c0d
2020-10-15 05:52:51 UTC main INFO openethereum::run State DB configuration: fast
2020-10-15 05:52:51 UTC main INFO openethereum::run Operating mode: active
2020-10-15 05:52:51 UTC fetch DEBUG fetch processing requests ...
Any advice?
miketang Hi, anybody using module gossip_network? I am doing some work 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 configuration or settings? I have done register_notifications_protocol. Thank you.
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.
miketang Is 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
