# Pre and post v0.9 task list

**URL:** <https://discourse.peercoin-library.org/t/pre-and-post-v0-9-task-list/10277>\
**Category:** General\
**Created:** [May 14, 2020, 2:46pm UTC](https://discourse.peercoin-library.org/t/pre-and-post-v0-9-task-list/10277 "2020-05-14T14:46:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![peerchemist](https://discourse.peercoin-library.org/letter_avatar_proxy/v4/letter/p/bbce88/32.png) [@peerchemist](https://discourse.peercoin-library.org/u/peerchemist)\
**Post date:** [May 14, 2020, 2:46pm UTC](https://discourse.peercoin-library.org/t/pre-and-post-v0-9-task-list/10277/1 "2020-05-14T14:46:10Z")

</div>

Hello community, below you can find the list of tasks which are to be done following the release of the v0.9.  
If you are interested in helping out with any individual task please post bellow that you are taking a task to yourself so we don’t duplicate work.

- make sure all the community operated tools are up to date
- update electrum-server to v0.9
- ~~reach out to all the exchanges and services to update to v0.9~~
- reach out to all the mining pools to update to v0.9
- reach out to all the block explorers to update to v0.9
- update the relevant docs to v0.9, like the [json-api-interface](https://docs.peercoin.net/#/json-rpc-api-reference)
- ~~update the debian and other packages to v0.9~~
- ~~update the docker image to v0.9~~
- Implement the Bug Bounty program
- more testing of the v0.9 branch, issue a point release if needed.

---

<div class="post-metadata">

**Author:** ![Sentinelrv](https://discourse.peercoin-library.org/user_avatar/discourse.peercoin-library.org/sentinelrv/32/24_2.png) [@Sentinelrv](https://discourse.peercoin-library.org/u/Sentinelrv)\
**Post date:** [May 15, 2020, 5:20am UTC](https://discourse.peercoin-library.org/t/pre-and-post-v0-9-task-list/10277/2 "2020-05-15T05:20:41Z")

</div>

It’s not listed, but I’ll work on the announcement thread.

---

<div class="post-metadata">

**Author:** ![belovachap](https://discourse.peercoin-library.org/user_avatar/discourse.peercoin-library.org/belovachap/32/96_2.png) [@belovachap](https://discourse.peercoin-library.org/u/belovachap)\
**Post date:** [May 16, 2020, 4:21pm UTC](https://discourse.peercoin-library.org/t/pre-and-post-v0-9-task-list/10277/3 "2020-05-16T16:21:09Z")

</div>

`peercoin.peercoin-library.org` (v0.9.0 full node, staking=0)  
`tpeercoin.peercoin-library.org` (v0.9.0 full node, staking=0)  
`seed.peercoin-library.org` ([GitHub - belovachap/coin-seeder · GitHub](https://github.com/belovachap/coin-seeder) more-or-less)  
`tseed.peercoin-library.org` ([GitHub - belovachap/coin-seeder · GitHub](https://github.com/belovachap/coin-seeder) more-or-less)

Are good to go 👍

I built a new AppImage using [packaging/appimage at master · peercoin/packaging · GitHub](https://github.com/peercoin/packaging/tree/master/appimage) and uploaded it to [https://files.peercoin.net/](https://files.peercoin.net/) 🚀

It also happens to be the client I use for minting, transactions, etc. so… “[Peercoin-x86\_64.AppImage](https://files.peercoin.net/download/Peercoin-x86_64.AppImage): At least one user! **™** ” 😜

One weird thing I noticed on the testnet seed output, there are a lot of Strider nodes that are on a block chain with more blocks than mine (448509 v.s. 455992):

```auto
:~# cat /dnsseed.dump 
# address good lastSuccess %(2h) %(8h) %(1d) %(7d) %(30d) blocks svcs version
157.245.230.123:9903 1 1589643960 100.00% 99.58% 83.93% 23.01% 5.92% 448509 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0ppc Strider)/"
[2a01:7e01::f03c:91ff:fed4:fd56]:9903 0 1589644080 99.43% 72.47% 34.95% 5.96% 1.42% 448509 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0.0-89a6c3672-dirty)/"
78.46.234.212:9903 1 1589644080 99.43% 72.47% 34.95% 5.96% 1.42% 455992 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0ppc Strider)/"
172.104.159.149:9903 0 1589644080 99.43% 72.47% 34.95% 5.96% 1.42% 448509 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0.0-89a6c3672-dirty)/"
[2604:a880:2:d1::12b:a001]:9903 1 1589643961 99.42% 72.36% 34.86% 5.94% 1.42% 448509 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0ppc Strider)/"
165.227.135.156:9903 1 1589643712 99.39% 72.11% 34.66% 5.90% 1.41% 455992 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0ppc Strider)/"
[2a02:8109:9f40:5140:e2d5:5eff:feee:de03]:9903 1 1589643712 99.39% 72.11% 34.66% 5.90% 1.41% 455992 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0ppc Strider)/"
95.216.170.47:9903 1 1589643712 99.39% 72.11% 34.66% 5.90% 1.41% 455963 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0ppc Strider)/"
159.69.37.17:9903 1 1589643712 99.39% 72.11% 34.66% 5.90% 1.41% 455992 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0ppc Strider)/"
91.64.193.64:9903 1 1589643712 99.39% 72.11% 34.66% 5.90% 1.41% 455992 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0ppc Strider)/"
[2a01:4f8:c2c:218b::1]:9903 1 1589643712 99.39% 72.11% 34.66% 5.90% 1.41% 455992 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0ppc Strider)/"
145.239.189.106:9903 1 1589643712 99.39% 72.11% 34.66% 5.90% 1.41% 448508 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.9.0(v0.9.0ppc Strider)/"
188.26.200.80:9903 0 1589643712 86.34% 60.86% 29.01% 4.92% 1.17% 455963 0000040d 70015 "/Satoshi:0.16.3/Peercoin:0.8.5.1(v0.8.5.1ppc)/"
35.182.218.189:9903 0 1589644325 94.61% 51.82% 21.61% 3.42% 0.81% 842 00000001 70002 "/Satoshi:0.8.6/Peercoin:0.7.3(v0.7.3ppc)/"

```

Maybe they didn’t sync from scratch and missed a hardened checkpoint or something? 🤷‍♂️

Anyway, exciting stuff 🍀

---

<div class="post-metadata">

**Author:** ![backpacker69](https://discourse.peercoin-library.org/user_avatar/discourse.peercoin-library.org/backpacker69/32/31_2.png) [@backpacker69](https://discourse.peercoin-library.org/u/backpacker69)\
**Post date:** [May 17, 2020, 5:00pm UTC](https://discourse.peercoin-library.org/t/pre-and-post-v0-9-task-list/10277/4 "2020-05-17T17:00:42Z")

</div>

hardened checkpoint doesn’t make you switch to different chain afaik, so if you update to strider from older 0.9 version, you’ll be stuck on the wrong fork.