@@ -18,12 +18,12 @@ timestamping functionality assumes that it has exclusive use of the wallet.
1818
1919Install the requirements:
2020
21- ```
21+ ``` shell
2222pip3 install -r requirements.txt
2323```
2424
2525Create the calendar:
26- ```
26+ ``` shell
2727mkdir -p ~ /.otsd/calendar/
2828echo " http://127.0.0.1:14788" > ~ /.otsd/calendar/uri
2929echo " bitcoin donation address" > ~ /.otsd/calendar/donation_addr
@@ -50,28 +50,28 @@ protocol does *not* distinguish between mainnet, testnet, and regtest, so make
5050sure you don't mix them up!
5151
5252To use your calendar server, tell your OpenTimestamps client to connect to it:
53- ```
53+ ``` shell
5454ots stamp -c http://127.0.0.1:14788 -m 1 FILE
5555```
5656
5757OpenTimestamps clients have a whitelist of calendars they'll connect to
5858automatically; you'll need to manually add your new server to that whitelist to
5959use it when upgrading or verifying:
6060
61- ```
61+ ``` shell
6262ots -l http://127.0.0.1:14788 upgrade FILE.ots
6363```
6464
6565If your server is running on testnet or regtest, make sure to tell your client
6666what chain to use when verifying. For example, regtest:
67- ```
67+ ``` shell
6868ots --btc-regtest -l http://127.0.0.1:14788 upgrade FILE.ots
6969```
7070
7171Tip: with regtest you can mine blocks on demand to make your timestamp confirm
7272with the ` generate ` RPC command. For example, to mine ten blocks instantly:
7373
74- ```
74+ ``` shell
7575bitcoin-cli -generate 10
7676```
7777
@@ -81,6 +81,6 @@ example configuration for nginx is provided under `contrib/nginx`.
8181
8282## Unit tests
8383
84- ```
84+ ``` shell
8585python3 -m unittest discover -v
8686```
0 commit comments