---
tags: archive
---

# OBSOLETE !!! - MOVED TO https://hackmd.io/@crtahlin/HkCSUt4YH
NOTE: @significance - might you "unpublish" this version? I think it is quite public

# Epic - Fairdrop stability

TODO: please:
- [ ] **add your name next to story**
- [ ] check if story really 2-3 days (if longer than one sprint, split)
- [ ] assign priority (write S1 next to it if for first sprint)
- [ ] the user stories that you copied to github use strikethrough ~~like this~~ since they will no longer be maintaned here

## geth
- USERSTORY LEVEL
- add 2 new nodes (not sealer) with good SSD [nikola, effort?, sprint?]
- set up load balanced geth gateway [nikola, effort?, sprint?]
- Script to detect if out of sync ([nikola, effort?, sprint?]
- fix unhealthy node automatically [nikola, effort?, sprint?]
- spawn new nodes to handle increased capacity [nikola, effort?, sprint?]

## inform users (HQ team - they should refine user stories)
We need to inform users we are releasing new infrastructure.
This is basically about (but check with devs): account names will be reset, grab your account name!
legacy files will be available from legacy.fairdrop.xyz until a certain date
inform users of potential access addresses for fairdrop fairdrop.xyz, fairdrop.eth, swarm gateway
- USERSTORY LEVEL
~~- call Dan - find out what needs to be communicated about upgrades to Fairdrop [Andrej, 4 EH, S1]~~
- write newsletter text for Fairdrop changes [Čebokli, effort, sprint]
- send out newsletter about changes to Fairdrop [Gašper, effort?, sprint?]
- publish on Twitter about changes to Fairdrop [Čebokli, effort?, sprint?]
- post to Telegram about changes to Fairdrop [Čebokli, effort, sprint?]
- write a blog post about changes to Fairdrop [Čebokli, effort?, sprint?]

## fds.js
- USERSTORY LEVEL
- upgrade (fds.js) to new branch and release to npm [Dan, effort?, sprint?]
- NOTES LEVEL
- update readme.md
- release to npm
- fix ENS security issue x
- update to new ENS contract x
- move over to using new ENS contracts x
- add in tadej's kvt stuff
- fix ENS contract to remove release domain after certain time
- fixed leading zero bug x
- fix/test import/export wallet
- research (fds.js?) calls to geth [Tadej, effort? , in progress]
- deploy new ENS x
- deploy new ENS
- improved the ENS contracts x
- research (fds.js?) calls to swarm [who?, effort?, sprint?]
- update to agreed node id scheme x
- more research
- maintenance (update of repos and npm libraries?) [who?, effort?, sprint?]
- update release the npm module
- create new repo FAIR (Dan, backlog)

## upload photo devcon

## fairdrop
- USERSTORY LEVEL
- increase stablility of fairdrop [who?, effort?, sprint?]
- NOTES LEVEL
- upgrade to new fds.js

- increase stability of fairdrop react app [who?, effort?, sprint?]
- undisable buttons if account fails
- test for edge cases and fix resultant bugs
- upgrade to new fds.js
- fix subdomain case sensitive issue x
- mitigate for swarm url bug (spaces) x
- mitigate for swarm url bug (special characters)
- increased user testing XXX
- create automated testing specification for gitcoin (d,c,g)
- pick test runner / framework etc.
- run locally
- create 2 accounts and send file
- fairdrop hosting must be bulletproof (backlog)
- host production on AWS S3, Cloudfront

- increase stability of swarm [who?, effort?, sprint?]
- ensure swarm always available and working, and not GC'ing
- upgrade swarm
- install swarm on new hardware with bigger space (nikola)

- i want to see whether the swarm and noordung networks are connected
- create spec x
- add to gitcoin
- administrate gitcoin process and manage developer
- review pull request
- merge
- release

- infrastructure (is this part of stability Epic?)
- create datafund/zahoor/fds fork of swarm

- pinning (is this part of stability Epic?)
- include pinning contract (Tadej) (Update on Telegram group - will become an Epic probably with some cooperation)

############### TO BE PUT INTO ANOTHER EPIC BELOW THIS LINE ###########