The aforementioned Betanet concept:
I think we should also clearly distinguish between
HyperQube and hyperqube_z
HyperQube will be an ecosystem of extension chains
hyperqube_z is a specific extension chain serving as a betanet
One good question that Stark had was âWhen do things deserve their own names?â such as the Hyperion he suggested?
Does a betanet need one?
1 Like
Maybe we could ditch the Hyperxxxxx terms and roll with:
Zenon Alphanet
Zenon Betanet
I am a very creative person but in reality self-descriptive branding is a best practice. And we want to concentrate on reinforcing âZENONâ
Zenon is already a great brand. There may be no need to invent another one.
It would be easy to just say âitâs live on the betanetâ - you can bridge to âthe betanetâ, âit was tested on Betanetâ - and it would be a lot easier for anyone to understand what that means without saying âwell, itâs like Kusama, have you heard of Kusama? Itâs thing other chain related to Po⌠
â.
âBetanetâ saves a lot of energy from perpetual branding and marketing and educating, because itâs name says what it is.
And it is immediately clear that Betanet emissions exist for Betanet utility.
1 Like
hyperqube_z will be A betanet, but not necessarily THE betanet
The HC1 incubator will also be a product, on a specific chain
i do think from a marketing perspective, âlaunching hyperqubesâ is more memetic than âlaunching zenon extension chainsâ, even if they mean the same thing
1 Like
i agree we need to focus on the Zenon Brand as the underlying ecosystem
But we shouldnât go against the natural force of language to create names for things that need them for communication efficiency
Especially out of fear
iirc, you are a fan of Ordinals
Would it be smart to drop the name Ordinals and talk about them using the phrase âBitcoin segwit data NFTsâ?
Zenon Network: Efficient and feeless L1 with Bitcoin ethos
HyperQube: Community Driven. L2 Extension Chains. [for] Zenon the Network of Momentum.
(thatâs what is on the https://www.hyperqube.network/ website right now)
hyperqube_z: HyperCore Oneâs flagship extension chain. AZ incubator for collaborative development. Betanet features for rapid development.
I think it is fairly straightforward. The branding just needs to clearly communicate these relationships.
1 Like
We need a branding for HyperQube. For hyperqube_z, the specific extension chain, I donât think we need much.
just drop the segwit data 
Not all Bitcoin NFTs are Ordinals, but those probably all are
Can we stack two of these cubes on top of each other?
put a Z in one, and an N in another?
it would be take on the classic ZN logo, and adding in another dimension
HyperQube: A community-driven framework for developing extended features for Zenon the Network of Momentum.
BetaNet: A dynamic experimental network accelerating innovation through incentivized prioritization within the Accelerator-Z ecosystem.
So early on my thought was:
hyperqube_z: Zenon based betanet
hyperqube_s: Solana based extension chain
hyperqube_b: Bitcoin/elements based extension chain
aliencoder suggested supernova under hyperqube as
hyperqube_nova
1 Like
BetaNet HyperQube
Supernova HyperQube
Solanom HyperQube
thatâs even more names to keep track of 
HyperQube is the ecosystem, the framework, the tooling stack
hyperqube_<something> are just codes to refer to specific chains within the ecosystem.
It was purposely done that way to de-emphasize any chain in particular. Itâs an ID.
Goerli Testnet
[name = random] [purpose = test stuff]
Supernova HyperQube
[name = random] [purpose = enhance Zenon]
long term weâll probably drop the lastname, nobody says testnet for goerli
In the future maybe, if extension chains really take off, maybe theyâll just have numbers
I need a branding package for HyperQube.
I donât need a chain specific one for hyperqube_z.