# \[SNIP\] Naming convention: ‘Starknet’, not ‘StarkNet’ **URL:** \ **Category:** SNIPs\ **Created:** [January 19, 2023, 8:52am UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279 "2023-01-19T08:52:44Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Talwag](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/talwag/32/2960_2.png) [@Talwag](https://community.starknet.io/u/Talwag)\ **Post date:** [January 19, 2023, 8:52am UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/1 "2023-01-19T08:52:45Z")
Hi community - I’m Tal, designer at StarkWare. 👋 This is a meta-SNIP regarding the spelling of [Starknet](https://www.starknet.io/). As part of a light rebrand work we’ve been doing in the last couple of months, we realized that spelling “StarkNet” - in CamelCase - is confusing and creates inconsistency. Why do we prefer Starknet? 1. **Starknet is more intuitive.** Insisting on using StarkNet creates inconsistencies: even in this forum, many users use the form ‘Starknet’ over ‘StarkNet’. 2. **‘StarkNet’ looks outdated** - this is based on our surveys. Think about Facebook, Dropbox, Microsoft, Internet, Starknet vs. FaceBook, DropBox, MicroSoft, InterNet, StarkNet We’d like to change all official documentation to use the spelling “ **Starknet** ” (lower case) instead of “StarkNet” (camel case), and we encourage all community projects to do the same when they refer to Starknet. ---
**Author:** ![Cillian](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/cillian/32/2975_2.png) [@Cillian](https://community.starknet.io/u/Cillian)\ **Post date:** [January 19, 2023, 12:45pm UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/2 "2023-01-19T12:45:52Z")
This is great @Talwag I agree and think this is a a move in the right direction. The camel case version “StarkNet” has always felt awkward, both visually and in practical terms. It is harder to read it, it introduces a pause that requires you to read it like it’s two words and it’s a pain to write! The upgrade to “Starknet” solves all of the issues you describe, will create consistency in its use and importantly feels more confident as a brand. ---
**Author:** ![metamorph](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/metamorph/32/2577_2.png) [@metamorph](https://community.starknet.io/u/metamorph)\ **Post date:** [January 23, 2023, 4:09am UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/3 "2023-01-23T04:09:26Z")
> [@Talwag](#): > > **‘StarkNet’ looks outdated** - this is based on our surveys. Think about Facebook, Dropbox, Microsoft, Internet, Starknet vs. FaceBook, DropBox, MicroSoft, InterNet, StarkNet @Talwag totally agree, looks old-fashioned ---
**Author:** ![s0lness](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/s0lness/32/1391_2.png) [@s0lness](https://community.starknet.io/u/s0lness)\ **Post date:** [January 23, 2023, 3:21pm UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/4 "2023-01-23T15:21:05Z")
I’m fine with the change! It’s true that I have to double-check everytime I type “StarkNet” 😄 ---
**Author:** ![robertkodra](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/robertkodra/32/85379_2.png) [@robertkodra](https://community.starknet.io/u/robertkodra)\ **Post date:** [January 25, 2023, 2:33pm UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/5 "2023-01-25T14:33:35Z")
Interesting suggestion @Talwag. Indeed the CamelCase can be confusing at times and for the sake of consistency Starknet would be better. However, since a lot of projects where based on CamelCase, such as StarGate, we would probably need to change those as well to keep consistence, which might be a bit of a hassle. ---
**Author:** ![konradkokosa](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/konradkokosa/32/3095_2.png) [@konradkokosa](https://community.starknet.io/u/konradkokosa)\ **Post date:** [January 27, 2023, 7:41am UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/6 "2023-01-27T07:41:58Z")
So now I need to update all my Obsidian notes 😅 Will the same apply to Starkware vs StarkWare? ---
**Author:** ![galronx](https://avatars.discourse-cdn.com/v4/letter/g/bbce88/32.png) [@galronx](https://community.starknet.io/u/galronx)\ **Post date:** [January 28, 2023, 10:28am UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/7 "2023-01-28T10:28:55Z")
> [@konradkokosa](#): > > Will the same apply to Starkware vs StarkWare? Nope, afaik StarkWare will remain StarkWare. ---
**Author:** ![justforinfo](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/justforinfo/32/3176_2.png) [@justforinfo](https://community.starknet.io/u/justforinfo)\ **Post date:** [January 28, 2023, 12:28pm UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/8 "2023-01-28T12:28:13Z")
As a marketer, I wrote “StarkNet” until now, I don’t know why but I’m convinced now. Starknet is better. Good point. Thank you Tal! ---
**Author:** ![0xMentorNotAPseudo](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/0xmentornotapseudo/32/909_2.png) [@0xMentorNotAPseudo](https://community.starknet.io/u/0xMentorNotAPseudo)\ **Post date:** [January 30, 2023, 12:54am UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/9 "2023-01-30T00:54:37Z")
While I’m convinced by the arguments you have no idea how many changes we need to make now 😄 I will apply suggestions on [Starknet-ecosystem.com](http://Starknet-ecosystem.com) ---
**Author:** ![xJonathanLEI](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/xjonathanlei/32/93_2.png) [@xJonathanLEI](https://community.starknet.io/u/xJonathanLEI)\ **Post date:** [February 1, 2023, 3:04pm UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/13 "2023-02-01T15:04:09Z")
`starknet-rs` has done its part 🙂 > > > Changes the spelling of "StarkNet" from "StarkNet" to "Starknet" everywhere in t…he codebase following the recommendations in \[this SNIP\](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet). ---
**Author:** ![Bal7hazar](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/bal7hazar/32/3870_2.png) [@Bal7hazar](https://community.starknet.io/u/Bal7hazar)\ **Post date:** [February 9, 2023, 1:54am UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/14 "2023-02-09T01:54:38Z")
Starknet is better to me too, also should we consider to rename SNIP into SIP for the same reason? ---
**Author:** ![ivpavici](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/ivpavici/32/662_2.png) [@ivpavici](https://community.starknet.io/u/ivpavici)\ **Post date:** [February 15, 2023, 8:47am UTC](https://community.starknet.io/t/snip-naming-convention-starknet-not-starknet/5279/15 "2023-02-15T08:47:02Z")
Starknet.js done 🙂 [Change “StarkNet” to “Starknet” by kongtaoxing](https://github.com/0xs34n/starknet.js/pull/517)