blob: a59eb220471db054be1bbf16c1f7d2f44f6ce14f (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
|
There are a few options on how to access the current testnet. The first is to use the public DEXON RPC endpoint, the second one is to sync the fullnode locally.
## Public RPC Endpoint
The public testnet endpoints is available at:
Testnet:
http: https://testnet-rpc.dexon.org
websocket: wss://testnet-rpc.dexon.org/ws
Taipei testnet:
http: https://taipei-rpc.dexon.org
websocket: wss://taipei-rpc.dexon.org/ws
Just point your DEXON/Ethereum client to this endpoint, and you should be able to send transactions and query account info.
## Syncing Fullnode
The testnet could be synchronized with the following command:
```
gdex --testnet
```
If you don't know how to build the `gdex` binary, please follow the wiki page [here](https://github.com/dexon-foundation/wiki/wiki/Building-DEXON).
It may take a few hours before your fullnode is fully-synchronised. When it does, you can now point your DEXON/Ethereum client to http://localhost:8545
Note: DEXON's current testnet is still unstable, it might be reset at some point. If it does, you might have to remove the data directory (`$HOME/.dexon` on Linux, and `$HOME/Library/Dexon` on MacOS) and re-sync the node.
|
