# Simple Subnet Development Checklist This is a collection of practical guides and checklists for Subnet development, assembled to share with our partners and others in the ecosystem who might find it useful. It is not intended to be comprehensive; it skews towards practical and opinionated recommendations that we find to be appropriate particularly for teams developing and managing early versions of a protocol. For any feedback/revisions/additions, please message `@ggp_steven` on Telegram. ## Launch Checklist - [ ] General Security ([precompile templates](https://docs.avax.network/subnets/customize-a-subnet#precompiles), DOS / firewall considerations, incident response plan) - [ ] 3rd party audits (VM security, operations and tooling setup, protocol audit. [Example audit firm](https://entersoftsecurity.com)) - [ ] Bridging approach (AWM vs native liquidity on Subnet vs LayerZero) - [ ] Mainnet Validator Set (how many validators are required, node regional location, providers, VM sizing, permissioned vs permissionless) - [ ] Consider Monitoring and Alerting tools and KPIs (eg. PagerDuty alerting on "% of stake weight offline") - [ ] RPC Network Set (regional locations, how many, sizing, providers) (can you use the Avalanche provided RPC? ) - [ ] Custom Testnet (launch on Fuji or a private testnet to iterate on tooling + networking faster, scalability stress tests for latency and hardware bechmarking) - [ ] Native token scheme and deployment (distribution, TGE, [faucet](https://github.com/ava-labs/avalanche-faucet), token minted on C Chain or on Subnet) - [ ] Choose flagship wallet (eg. integrate into [Avalanche's Core](https://core.app/)) (or create your own? ) - [ ] Decide on Customer Support channel (Twitter / Discord are common in web3. Intercom/ZenHub/HubSpot on website nice-to-have. ) Other common questions: - [ ] Understand regulatory implications of your entity holding native tokens and user funds (eg. do you need a [Money Transmitter License](https://www.dfs.ny.gov/apps_and_licensing/money_transmitters/) to operate in the US? ) - [ ] Decide on custodial, non-custodial, or hybrid Wallet experience for users - [ ] Consider regulatory implications on the validator set (eg. do you need to have less than 75% of validator nodes within one region? ) - [ ] Consider on and offramp experience for user liquidity into the Subnet/game
Last changed by  
 
Steven Gates

Read more

Omnigram

Context I am trying to create a fork of the open source Telegram client, TelegramSwift: https://github.com/overtake/TelegramSwift/ When trying to set up my local development environment using XCode, I am recieving package resolution errors: Steps to recreate my problem Follow the instructions here to install and build the project: https://github.com/overtake/TelegramSwift/blob/master/INSTALL.md For any errors in building the project, follow these instructions: https://github.com/overtake/TelegramSwift/issues/771#issuecomment-1384436656

1/17/2023
Onboarding Ideas

1 sentence explainer: GoGoPool is building a decentralized staking protocol for Avalanche subnets. Mission/Vision/Purpose Our current mission is to be the easiest way to stake AVAX. Our vision to build out the Subnet Economy, and our purpose is to create the "wordpress" moment for web3. Write down any questions you have while going through this in a doc! Avalanche

10/26/2022
Stable DAOFusion

Abstract Midjourney is a very popular service for running Stable Diffusion -- it is a centralized service that has a free plan for people to try out SD, and eventually move to a paid plan for more GPU minutes. This paper explores creating a decentralized version of Midjourney, underpinned + monetized by the DFSN coin and powered by Avalanche's Elastic Subnets (built at first for a crypto-enthusiastic audience). Motivation It would be cool to build one of the first Proof of Stake Subnets as an appchain to help illustrate why the appchain thesis is a perfect fit for Subnets. Specification Focusing on a v0.01, with friendly-audience assumptions being made.

10/23/2022
Security Considers

RE Pause, I feel like we should have ONE global Protocol Paused flag and thats it. Pausing will happen in an "Oh Shit!" moment of high stress, bad things are happening. We dont want to have to figure out which thing to pause, or do several txs to pause multiple things. Just one. Defining Oh Shit moments; Rialto got hacked Protocol got hacked AVAX ggAVAX float

10/19/2022
Read more from Steven Gates
Published on HackMD