Timeline for Parity private chain: Contract deployment transaction not getting mined
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2017 at 19:35 | vote | accept | Ajoy Bhatia | ||
| Mar 23, 2017 at 19:27 | answer | added | Ajoy Bhatia | timeline score: 1 | |
| Mar 22, 2017 at 10:56 | comment | added | q9f | If this resolves your issue feel free to answer your own question. | |
| Mar 11, 2017 at 1:13 | comment | added | Ajoy Bhatia | This issue was seen when I tried to deploy the contract with either the JSON RPC API or with the Parity browser UI. Instead, I tried deploying with Parity's web3 Javascript API (with the Javascript code running as a NodeJS app) and that consistently works. The contract deployment transaction is mined, and code exists at the assigned address. | |
| Feb 24, 2017 at 22:06 | comment | added | Ajoy Bhatia | Hmm... I tried sending the contract deployment transaction to another peer node on the chain. This time, it did get mined. So I guess it is up to me now to figure out what is wrong on the node where it does not get mined. | |
| Feb 24, 2017 at 19:07 | history | edited | Ajoy Bhatia | CC BY-SA 3.0 |
Yet another edit, sorry :-) Specified that it is a PoA chain
|
| Feb 24, 2017 at 19:02 | history | edited | Ajoy Bhatia | CC BY-SA 3.0 |
Added contract code
|
| Feb 24, 2017 at 18:45 | history | asked | Ajoy Bhatia | CC BY-SA 3.0 |