Parity-ethereum: New Token Deployment and registry not working with Parity

Created on 22 Mar 2018 · 13Comments · Source: openethereum/parity-ethereum

_Before filing a new issue, please provide the following information._

I'm running:

Which Parity version?: 1.8.4

Which operating system?: Linux

How installed?: via installer binaries

Are you fully synchronized?: yes

Which network are you connected to?: private network having POW

Did you try to restart the node?: yes

_Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue._
Expected behaviour:

Token deployment and token registry should work for new tokens as mentioned here https://github.com/paritytech/parity/wiki/Token-Deployment

Actual behaviour:
1.Parity connected to private network .

Go to applications/token deployment tab
Try to deploy a token : Mycoin, MAC, 100 tokens using my main account.
It says token is deployed. but doesn't show any address or confirmation.
How can I register the same in "Token Registry " ?
I want to make transactions with these new generated tokens between multiple accounts and should be able to see in Parity wallet.

Screenshots:
tokendeployment
token_deploy_2
token_3
token_6

M8-dapp 💎 Z1-question 🙋‍♀️

Source

aditbhrgv

All 13 comments

Can you update to the latest release
Can you verify if the token deployment transaction went through ?
You should find your contract address in the token overview :

Tbaut on 22 Mar 2018

Hey @Tbaut,

I updated Parity to latest release 1.10.0
But now when I am starting parity with Ropston chain, My parity doesn't start up on localhost port 8180.

Logs:

parity --chain ropsten --bootnodes "enode://20c9ad97c081d63397d7b685a412227a40e23c8bdc6688c6f37e97cfbc22d2b4d1db1510d8f61e6a8866ad7f0e17c02b14182d37ea7c3c8b9c2683aeb6b733a1@52.169.14.227:30303,enode://6ce05930c72abc632c58e2e4324f7c7ea478cec0ed4fa2528982cf34483094e9cbc9216e7aa349691242576d552a2a56aaeae426c5303ded677ce455ba1acd9d@13.84.180.240:30303"
2018-03-22 15:58:28 Starting Parity/v1.10.0-beta-0a9d41e-20180320/x86_64-linux-gnu/rustc1.24.1
2018-03-22 15:58:28 Keys path /home/fsti/.local/share/io.parity.ethereum/keys/Ropsten
2018-03-22 15:58:28 DB path /home/fsti/.local/share/io.parity.ethereum/chains/test/db/ae90623718e47d66
2018-03-22 15:58:28 Path to dapps /home/fsti/.local/share/io.parity.ethereum/dapps
2018-03-22 15:58:28 State DB configuration: fast
2018-03-22 15:58:28 Operating mode: active
2018-03-22 15:58:28 Configured for Ropsten using Ethash engine
2018-03-22 15:58:33 Public node URL: enode://fd71cad69ee812b3e958fe7dae3aa304a771becc7a3e41440caa905e53d0debd9139a356dd528f6b5ff9b3481da1793f61f32647abb22907f29436b78e804d83@192.168.1.63:30303
2018-03-22 15:58:58 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 15:59:28 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 15:59:58 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 16:00:28 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 16:00:58 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 16:01:28 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 16:01:58 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 16:02:28 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 16:02:58 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 16:03:28 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 16:03:58 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 16:04:28 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-03-22 16:04:58 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs

parity_error

aditbhrgv on 22 Mar 2018

@aditbhrgv here is the new way of accessing your parity wallet

Tbaut on 22 Mar 2018

👍1

Hi @Tbaut

I tried with my private blockchain with POW using ethminer and still I cannot deploy a new token.
How can I check if my "token deployment transaction went through" ?
I mean the Dapp on parity shows that your "Token has been deployed" but it doesn't show in Overview section of "Token deployment Tab" . It always has 0 tokens

Also, I am still waiting for some test ethers on my Ropston network to test same on Ropsten test net.

aditbhrgv on 22 Mar 2018

As a side note, did you have a look at the private dev blockchain ? It's a nice alternative to private blockchain with POW to test things.
Does your private blockchain support Ethereum smart contract ?
To check if it went through on Ropsten for instance, you can see it on https://ropsten.etherscan.io/

Tbaut on 22 Mar 2018

aditbhrgv on 22 Mar 2018