-
Notifications
You must be signed in to change notification settings - Fork 8
Testnet FAQ
For more help, please join
please join https://t.me/phalafaucet and send /drip [your testnet address]
Set on-chain Identity would need 10 test tokens. Please try to obtain more test tokens.
Secret Price Guessing Game is now paused for function improvement. We are developing a special address for Phala team member to check the detail of the private transfer amount (Which means, we can't identify the source of private transfer either). Please stay tuned with the change of pin message :)
Yes.
Please refer to our tutorial with a VPS or Ubuntu 18.04 computer.
Input ./phala-node --chain poc2 --name "node name | testname"
Please upgrade your node runtime to poc2-3.0-alpha1 using
curl -sL https://github.com/Phala-Network/phala-blockchain/releases/download/poc2-3.0-alpha1/phala-node -o phala-node
rm -f ./phala-node
curl -sL https://github.com/Phala-Network/phala-blockchain/releases/download/poc2-3.0-alpha1/phala-node -o phala-node
./phala-node --chain poc2 --name "h4x | Fz6if35RXq2jgYeGELBXiTBnSdE8NqDkA3iah5dG3hBaWXd"
- Node: Full-node
- TEE: Set Gatekeeper node up but waiting to be enrolled
- GK: successfully enrolled Gatekeepers
One node can only be bonded with one testnet account. If you are running 20 nodes, you have to create 20 testnet accounts and set on-chain identities for them all. :)
Please go to https://poc2-dashboard.phala.network/#/
Gatekeeper node IS VERY IMPORTANT to Phala Network. It has to run 24/7 with a stable and wide-bandwidth network environment, and has to keep upgraded with all Phala updates.
For now, you can only use Linux codes to operate your Gatekeeper node. Besides, you might get slashed and lose your PHA once you went offline or committed the wrong operation. We would not suggest you set up a Gatekeeper node unless you are familiar with Linux system. :)
To set up a Gatekeeper Node, you need:
- a device with Intel CPU higher than 6th generation and pass the SGX test. You may refer to the device list which has passed before.
- follow the tutorial.
Error while dialing /dns/telemetry.polkadot.io/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Other(B(A(Transport(ResolveError { domain_name: "telemetry.polkadot.io", error: Custom { kind: Other, error: "failed to lookup address information: Temporary failure in name resolution" } })))) }
2020-07-19 00:05:46 Syncing 22.0 bps, target=#14892 (1 peers), best: #10939 (0xf733…4443), finalized #10939 (0xf733…4443), 21.2kiB/s 0.4kiB/s
2020-07-19 00:05:47 Discovered new external address for our node: /ip4/112.93.255.201/tcp/30333/p2p/12D3KooWRmyyn4it51aWwD5CEh5bqN4A4Ya6aoNZ5P7YptTFVM2j
It could be caused by your unstable network. And It's only a warning which would not affect the node setting.
Please download the latest version of SGX driver at https://01.org/intel-softwareguard-extensions/downloads/intel-sgx-dcap-1.7-release
Nope. But there could be possibility of going offline if you are running with an intranet IP.
One SGX-abled device can only run ONE Gatekeeper node.
Please go to https://poc2-dashboard.phala.network/#/
Less trust, more truth.
- Testnet Rorschach
- Prize Giving
- Airdrop
- Wave I: KSM Stakedrop (ended)
- Wave II: Polkadot Parachain Auction
- Wave III: TBC
- Bounty
- Web3 Analytics
- Reference