About Stargaze Airdrop
Stargaze Airdrop is a protocol that re-imagines the social network from a purely crypto-native context. Stargaze is built as a proof-of-stake Cosmos zone, giving it maximum flexibility in protocol design, interoperability, and scalability right out of the gate. The governance-driven development process of Cosmos chains allows rapid development and iteration required for a consumer social protocol.
Stargaze is airdropping 25% of the total supply to ATOM stakers and OSMO stakers or LPs. The snapshot was taken on October 11th, 2021 and Stargaze validator stakers on Cosmos Hub, Osmosis and Regen network, ATOM stakers who had staked at least 5 ATOM and OSMO stakers or LPs who had staked at least 50 OSMO are eligible to claim the airdrop.
| Platform | Total Supply | Max. Participants | Website |
|---|---|---|---|
| Cosmos | 25% of the total supply | Unlimited | Click Here To Visit |
The First Interoperable Layer 1 for NFTs
NFT Launchpad
NFT Marketplace
Community-owned
Zero Gas
Carbon Neutral (Proof-of-Stake)
Secured by 100+ Validators
Programmable via CosmWasm
Interoperable via Cosmos IBC
Ethereum Interoperability via Gravity Bridge
CosmWasm Smart Contracts
Stargaze is one of the first, if not the first protocol to run CosmWasm in a community-governed environment. This means that smart contracts on Stargaze have to be voted on by the community and uploaded via governance.
Why not permissionless CosmWasm?
Stargaze is an application-specific chain for NFTs just like Osmosis is an application-specific chain for AMMs. If Stargaze allowed completely permissionless smart contracts, it would no longer be an application-specific chain, and would be a general-purpose blockchain. If you’re looking to deploy a DeFi protocol, or something that doesn’t integrate with Stargaze, you’re probably better off deploying on a general-purpose blockchain like Ethereum.
Why community-governed CosmWasm?
Because Stargaze is an application-specific chain, custom contracts have to integrate with the rest of the protocol. By going through governance, custom contracts can be verified and reviewed before they are uploaded and become part of the Stargaze protocol.
How do write a contract that works with Stargaze?
- 1.Fork Stargaze smart contracts at: https://github.com/public-awesome/stargaze-contracts.
- 2.Write your contract, deploy it on testnet, and make sure it works as intended.
- 3.Add your contract as a draft pull request. If it charges any fees, be sure to use Stargaze’s Fair Burn mechanism, which burns STARS and rewards stakers.
- 4.Submit a signaling proposal on Commonwealth, detailing what your contract does, and how it plans to integrate with and provide value to the Stargaze protocol and community. Also include a request for funds to get your contract audited.
- 5.After validating your project with community support, submit a governance proposal requesting funds for an audit.
- 6.Following the audit, submit a pull request to be included as part of Stargaze’s contracts.
- 7.Once merged in, submit your contract to on-chain governance. See the following command to submit your proposal:
starsd tx gov submit-proposal wasm-store -h.
Protocol Governance
Governance is a key part of a community-owned project like Stargaze. Governance is generally performed via on-chain proposals and token-weighted voting. Based on proposal outcomes, the blockchain performs automated actions. Because blockchain operations are typically non-reversible, proposals should be first discussed before being submitted as an on-chain proposal. Proposals submitted to the chain should be well-written, comprehensive, and leave no room for ambiguity or misinterpretation.
The following process to submit a proposal is recommended:
- 1.Gauge community support for your proposal by bringing it up on Stargaze’s social media such as Discord, Twitter, and Reddit.
- 2.Create a signaling proposal on Commonwealth. This is where you can fine-tune the parameters and specific asks for your proposal.
- 3.Create an on-chain proposal with very clear, specific, and actionable items. At this point, all issues have been flushed out in the previous two steps. This is considered the definitive version of a proposal and results in an on-chain action upon passing.
