public-awesome / stargaze

Stargaze Cosmos proof-of-stake blockchain

Stargaze

Stargaze is a Cosmos zone (layer 1 proof-of-stake blockchain). It is the base layer node software for the Stargaze NFT Marketplace.

Install

Run a local, single-node chain

Requires Go.

make install

./startnode.sh

Test smart contracts

See ./scripts/wasm/README.md.

Disclaimer

STARGAZE SOFTWARE IS PROVIDED “AS IS”, AT YOUR OWN RISK, AND WITHOUT WARRANTIES OF ANY KIND. No developer or entity involved in running Stargaze software will be liable for any claims or damages whatsoever associated with your use, inability to use, or your interaction with other users of Stargaze, including any direct, indirect, incidental, special, exemplary, punitive or consequential damages, or loss of profits, cryptocurrencies, tokens, or anything else of value. Although Public Awesome, LLC and it's affiliates developed the initial code for Stargaze, it does not own or control the Stargaze network, which is run by a decentralized validator set.

stargaze's Issues

Stake module ABCI

• query all delegations
• query delegations by post and vendor ids
• update app.go
• create custom SimApp for testing
• post test
• delegation test
• abci end blocker + tests
• client cli
• client rest
• genesis state

Remove sell option

Explore using the modular ante-handler to make gas constant to prevent front-running

Compare this approach with batching.

Figure out how to handle the result of governance moderation

Options:

• Fork the Cosmos Governance module, adding a new proposal type for content moderation. Add events to signal the result of governance votes, so rewards can be paid out (or slashed). Furthermore, the post and upvotes have to be either deleted or flagged, or curation has to resume, accounting for the moderation delay.
• See if just a text proposal is enough, but if its possible to hook into the results to do the redistribution.

Integrate interchain-accounts and interchain-staking modules

Check if proper events are fired for ABCI functions

Add creator/curator split param

Post handler

Add negative staking for moderation

• keep track of vote direction (upvote/downvote)
• add downvote to MsgDelegate
• embed staking Delegation in a stake Delegation that includes a downvote
• store this new type in the queue as another key

Appeal process

The Santa Clara Principles on Transparency and Accountability in Content Moderation have a core principle of appeal:

Companies should provide a meaningful opportunity for timely appeal of any content removal or account suspension.

While I feel we are doing well with regard to the other principles, an appeal process is something that is definitely worth looking into supporting on chain.

Make post creator optional and don't assign it to the curator during an upvote

adding a comment to this part (for some reason can't comment)

err = k.CreatePost(ctx, vendorID, postID, "", deposit, curator, rewardAccount)

Now that I think it , shouldn't the post already exists ? I mean if the post doesn't previously exists on chain a transaction should be submitted before from the creator with reward_address = curator

The conflict is that the post would not contain the real author address

Originally posted by @jhernandezb in https://github.com/public-awesome/stakebird/pull/64/files

Mint token from bonding curve with Bancor formula

Currently we're minting 1 new token for each ATOM that goes into the community pool. This is fine for early testnets. But since we want to incentivize early adopters, new tokens should be minted on a curve.

Background reading:

1. https://blog.relevant.community/how-to-make-bonding-curves-for-continuous-token-models-3784653f8b17
2. https://blog.relevant.community/bonding-curves-in-depth-intuition-parametrization-d3905a681e0a
3. https://yos.io/2018/11/10/bonding-curves/

The last article includes Solidity contracts that can be ported over to Go.

Todo

• Implement creating many curves for different assets using the Bancor formula (with reserve ratio)
• Implement buying from curve, making sure all math is deterministic. Use sdk.Dec.Power() instead of float calculations, for example.
• Write tests, comparing against a model such as https://www.desmos.com/calculator/8gxacjujal.

Other related Cosmos implementations:

• https://github.com/ixofoundation/cosmic
• https://github.com/ixoworld/bonds

Setup gaia and relayer on devnet

Quadratic finance matching rewards

Treat protobuf generated files as binary

Upvote REST query commands

REST equivalent of #58.

Stake module specs

Post REST query commands

REST equivalent of #57.

Distribute ATOM to community pool (DAO)

Generate curating module

Quadratic voting redistribution

Keep track of FUEL supply and amount burned with a module account

REST tx route for upvote

Proto for MsgPost

Yeah I don't think embedding is actually possible golang/protobuf#192 (comment)

The only work around I see is duplicating fields, its a bit boilerplate but that would make it work, I'm ok duplicating that unless you think there is some methods attached to MsgDelegate that would requite to also be copied to MsgPost ?

Originally posted by @jhernandezb in #15 (comment)

automate releases

• Build and release assets on tags
• Build and release containers on tags

Curating module spec

Moderation handler

Related to #51.

Curator rewards

• retrieve staking reward amount
• amplify staking reward with a bonus from the reward pool
• add param for bonus multiplier

Scaffold module

Time-decaying rewards

Distribute QF rewards based on curation time.

Add reward pool module account

• add account
• divert percentage of inflation to reward pool
• create parameter for reward pool percentage
• tests

Upvote handler

Sell FUEL from the curve and get back ATOM

Change account prefix

Revert to rkt: prefix when cosmos/relayer#43 is fixed

Create a voting pool module account

Stake module CRUD

• scaffold code
• delegation msg, handler, client
• delegation queue type
• delegation queue keys
• add to queue on delegation

Post CLI query commands

• all posts for a vendor_id
• individual post given vendor/post_id

Update README with instructions for staking

Persist upvote time for time-based rewards

Buy FUEL from the curve

Stake module TODO

• check if expected events are fired in abci functions
• add Msgs to proto
• update README
• issue with exported validator type

Delete expired posts and upvotes from chain

Scale quadratic matching pool by governance or chain params

Need to think of params or chain properties can be used to scale the matching pool.

The matching pool is currently unbounded. So it’s possible that if enough upvotes happen, it’ll empty up the reward pool and the chain will halt.

Convert Msgs to protobufs

Make IBC connection constants into parameters

Return deposits after curation window

Upvote CLI query commands

• all upvotes
• upvotes for a given a vendor/post_id

Add a faucet

Add instructions for running locally with gaia and relayer

Lock ATOM as collateral

• relayer scripts to do an IBC xfer of ATOM from Cosmos Hub to a Stakebird account
• lock ATOM in a module account representing the reserve token for the curve