1. Run the following commands on a Debian:stretch image
2. apt-get update
3. apt-get install -y apt-transport-https ca-certificates
4. echo "deb [trusted=yes] http://packages.o1test.net unstable main" | tee /etc/apt/sources.list.d/coda.list
5. apt-get update
6. apt-get install -y curl coda-testnet-postake-medium-curves=0.0.16-beta7+-feature-mainnet-parameter-test-93b0059 --allow-downgrades
7. wget -O ~/daemon.json https://gist.githubusercontent.com/es92/fcab320a4822911e8fdfe127940b8cd0/raw/df8bba0e1e309504e75c701dd993a4813b0818cd/daemon-10-11-2020.json
8. coda daemon -peer /dns4/seed-two.pickles-nightly.o1test.net/tcp/10001/p2p/12D3KooWFcGGeUmbmCNq51NBdGvCWjiyefdNZbDXADMK5CDwNRm5/ -peer /dns4/35.227.48.78/tcp/10001/p2p/12D3KooWAFFq2yEQFFzhU5dt64AWqawRuomG9hL8rSmm5vxhAsgr -config-file ~/daemon.json -generate-genesis-proof true -log-json -log-level Trace | coda-logproc | tee ~/coda-log.txt
9. Send us logs shortly after connecting (~1hr) and after the node has been running a while (~24hr) if you can. Send your discord username, coda-log.txt, coda client status > status.log, and details on the platform you’re using via email to logs@o1labs.org
10. Post any issues to github. Please include your coda-log.txt, details on your platfrom, and a printout of coda client status to the issue. If an issue exists already, please add your above information to the issue

Issue priority labels:

• Critical: Anything that stops a node from connecting to the network. For example, if a node crashes, is unable to sync, or is unable to connect to peers.
• High: Anything that doesn’t stop a node from syncing, but causes bad functionality of other features. For example, anything to do with connectivity that doesn’t break connectivity, or some transaction types not working as expected.
• Medium: Unintended behavior that does not break nodes or features. For example bad logging or error handling.
• Low: Convenience improvements