dappdevconsulting / easytcr Goto Github PK

View Code? Open in Web Editor NEW

26.0 4.0 15.0 873 KB

License: Apache License 2.0

Shell 0.23% HTML 0.58% CSS 2.99% JavaScript 96.20%

easytcr's Introduction

Token Curated Registries UI

Installation

Clone this repo.
Install dependencies using npm install.

Configure src/cfg.json.

Set the "geteway" and "apiServer" parameters for IPFS:

"IPFS": {
    "gateway": "https://ipfs.infura.io",
    "apiServer": "https://ipfs.infura.io:5001"
},

Set the Web3 fallback provider (in case of local provider type http://localhost:7455 or any other address):
```
"WEB3": {
   "http": "https://rinkeby.infura.io/API_KEY"
},
```
Set the Ethereum network id (1 – mainnet, 4 – rinkeby, * – any network).
```
...
"network": "4",
...
```

Set the TCR of TCRs Registry contract address:

"TCRofTCRs": {
    "registry": "YOUR_CONTRACT_ADDRESS"
}

By the end, you should get the following config:

{
  "IPFS": {
    "gateway": "https://ipfs.infura.io",
    "apiServer": "https://ipfs.infura.io:5001"
  },
  "WEB3": {
    "http": "https://rinkeby.infura.io/API_KEY"
  },
  "network": "4",
  "TCRofTCRs": {
    "registry": "YOUR_CONTRACT_ADDRESS"
  }
}

Run npm start to start the development server.

Local Ethereum Network

ethereum-tcr-ui is completely compatible with Ganache (TestRPC) client and it can be used as any other network. In order to check the Ganache deploying process of TCR, please refer to oficial TCR repo and Ganache CLI repo

Important files

public/index.html is the page template;
src/index.js is the JavaScript entry point.
src/cfg.json is the core cinfiguration file.
src/defaultConfig.json an example of TCR of TCRs IPFS config.
src/defaultLocalization.json default/fallback localization file.

Deploying

To completely install all dependencies via npm install you have to add an SSH key of the machine you're working on in order to pull a ethereum-tcr-api package.

License

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

easytcr's People

Contributors

Stargazers

Watchers

Forkers

it-tash levelkdev somethingwrong bjornwgnr kwikiel eos21 elhomosiguiente thetta tylev shyblugs skillunion swader bitfalls twygod

easytcr's Issues

Whitelisted/successful registry applicants aren't visible in the web UI

I've been testing the repo with several TCRs based on mgoldin's implementation on the Rinkeby network and have deployed a parent registry ("0xf30b5fc08fa57b084ff5bbb41ab53737232fb332") and submitted a child registry ("0xf62391156eefc4696325d7a149da76f70517fcb6") to it. I've also made some applications to the child registry (e.g. listinghash "0x58d90e7a4d71aabc0dfe41805bab3379d324186b63a46df6d5e8da153548992c") using the web interface and I'm able to see those transaction and the corresponding event "_Application" on Etherscan: https://rinkeby.etherscan.io/address/0xf62391156eefc4696325d7a149da76f70517fcb6#events

However, despite the "updateStatus" transactions succeeding and the TCR contract updating to show isWhitelisted=true, the entries don't show up in the EasyTCR web UI. Any ideas why?

is TCR design dead?

Hi!

I'm studying about TCR implementations and I have the impression that this design hasn't stayed alive through the years, is something to do with the mechanics of TCR or it's because the community is not robust enough yet to implement it in ways it can success as a project?

I'll appreciate any experience or opinion about it, thanks :)

Help installing, npm install error.

When installing following the installation instructions, I get this error:

Then I try again executing this command: "C:\Program Files\Git\cmd\git.EXE" ls-remote -h -t ssh://[email protected]/DAppDevConsulting/tcr-api.git
Which results in a similar error:
npm ERR! Error while executing: npm ERR! C:\Program Files\Git\cmd\git.EXE ls-remote -h -t ssh://[email protected]/DAppDevConsulting/tcr-api.git npm ERR! npm ERR! Host key verification failed. npm ERR! fatal: Could not read from remote repository. npm ERR! npm ERR! Please make sure you have the correct access rights npm ERR! and the repository exists. npm ERR! npm ERR! exited with error code: 128 npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Nesquil\AppData\Roaming\npm-cache\_logs\2018-09-08T19_21_08_436Z-debug.log

When i change contract address

uncaught at root at root at flow at takeLatest at init Error: Couldn't decode address from ABI: 0x

Where to set contract ABI?

When I upload JSON file it display error.

I run this project in localhost.

My sample JSON file text

{"id":"QmPcixWuK7fjiRkCQhrovij8yvNQtFvGwML3g9pZiDcj5q","title":"test for easy tcr"}

where "QmPcixWuK7fjiRkCQhrovij8yvNQtFvGwML3g9pZiDcj5q" is ipfs address.

Can you give me sample JSON file format?

Npm install not working.

npm ERR! Error while executing:
npm ERR! C:\Program Files\Git\cmd\git.EXE ls-remote -h -t ssh://[email protected]/DAppDevConsulting/tcr-api.git
npm ERR!
npm ERR! Host key verification failed.
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128

Nothing shows up in the tables after submitting a candidate.

Hey guys, I've deployed a TCR contract in my local ganache network and configured EasyTCR to work with it.

But after submitting a candidate successfully, it doesn't show up anywhere.
I checked and the listing was created on the contract and also the data was saved on IPFS.

Any ideia of whats going on?
Any help would be appreciated.