Stride is a blockchain ("zone") that provides liquidity for staked assets. Using Stride, you can earn both staking and DeFi yields across the Cosmos IBC ecosystem. Read our "Meet Stride" blog post to learn more about why we built Stride.
Stride is built using Cosmos SDK and Tendermint and created with Ignite. Stride allows users to liquid stake any IBC-compatible cosmos SDK native appchain token. Under the hood, Stride leverages the Inter-Blockchain Communication protocol, Interchain Accounts and Interchain Queries.
To install the latest version of Stride blockchain node binary, execute the following command on your machine:
git clone https://github.com/Stride-Labs/stride
Test your installation by navigating to the stride directory and executing:
ignite chain serve
The serve command installs dependencies, builds, initializes, and starts your blockchain in development mode. You should see logs bring printed to your shell.
If you have any issues with installation, please reach out to our team on Discord.
You can learn more about the install process here or reference these helpful resources:
Developers who wish to develop on Stride can easily spin up 3 Stride nodes, 3 Gaia nodes, 1 Hermes relayer and 1 interchain-queries relayer. The Gaia nodes simulate the Cosmos Hub (Gaia) zone in local development node, and the relayers allow Stride zone to interact with that instance of Gaia.
The fastest way to develop on Stride is local development mode.
Install the required git submodule dependencies (gaia, hermes, interchain-queries).
git submodule update --init
Build executables, initialize state, and start the network with
make start-docker build=sgjotrhi
You can optionally pass build arguments to specify which binary to rebuild
sThis will re-build the Stride binary (default)gThis will re-build the Gaia binaryjThis will re-build the Juno binaryoThis will re-build the Osmo binarytThis will re-build the Stargaze binaryrThis will re-build the Go Relayer binaryhThis will re-build the Hermes binaryiThis will re-build the ICQ binary
Example: make start-docker build=sg, this will:
- Rebuild the Stride and Gaia binarys
- Start 1 Stride and 1 Gaia node in the docker
- Start Relayers
To bring down the chain, execute:
make stop-docker
The easiest way to develop cosmos-sdk applications is by using the ignite cli to scaffold code. Ignite (developed by the core cosmos team at Tendermint) makes it possible to scaffold new chains, run relayers, build cosmos related proto files, add messages/queries, add new data structures and more. The drawback of creating thousands of lines of code using ignite is that it is difficult to discern which changes were made by the ignite cli and which changes were made manually by developers. To make it easier to review code written using ignite and to make it easier to retrace our steps if something breaks later, add a commit for each ignite command directly after executing it.
For example, adding a new message type and updating the logic of that message would be two commits.
// add the new data type
>>> ignite scaffold list loan amount fee collateral deadline state borrower lender
>>> git add . && git commit -m 'ignite scaffold list loan amount fee collateral deadline state borrower lender'
// make some updates to the keeper method in your code editor
>>> git add . && git commit -m 'update loan list keeper method'
An example of a PR using this strategy can be found here. Notice, it's easy to differentiate between changes made by ignite and those made manually by reviewing commits. For example, in commit fd3e254bc0, it's easy to see that a few lines were changes manually even though nearly ~300k LOC were scaffolded.
Opening a pull request (PR) will automatically create Summary and Test plan fields in the description. In the summary, add a high-level summary of what the change entails. For pull requests that scaffold ignite code, include the ignite scaffold commands run.
Add summary of the pull request here (E.g. This pull request adds XYZ feature to the x/ABC module and associated unit tests.)
To run unit tests for the whole project, execute:
make unit-test
To run unit tests for a particular module (e.g. the stakeibc module), execute:
make unit-test path=stakeibc
To run unit tests for a particular package (e.g. the stakeibc module), execute:
make unit-test path=stakeibc/types
To inspect unit test coverage, execute:
make test-cover
Your blockchain in development can be configured with config.yml. To learn more, see the Starport docs.
To release a new version of your blockchain, create and push a new tag with v prefix. A new draft release with the configured targets will be created.
git tag v0.1
git push origin v0.1
After a draft release is created, make your final changes from the release page and publish it.
Users stake their tokens on Stride from any Cosmos chain. Rewards accumulate in real time. No minimum. They will receive staked tokens immediately when they liquid stake. These staked tokens can be freely traded, and can be redeemed with Stride at any time to receive your original tokens plus staking rewards.
On the backend, Stride permissionly stakes these tokens on the host chain and compounds user rewards. Stride lets users use your staked assets to compound their yields. Continue to earn staking yield, and earn additional yield by lending, LPing, and more. They can set their own risk tolerance in Cosmos DeFi.
Users can always redeem from Stride. When they select "redeeem" on the Stride website, Stride will initiate unbonding on the host zone. Once the unbonding period elapses, the users will receive native tokens in their wallets.
Stride is proud to be an open-source project, and we welcome all other projects to use our repo. We use modules from the cosmos-sdk and other open source projects.
We operate under the Apache 2.0 License, and have used the following modules from fellow Cosmos projects. Huge thank you to these projects!
We use the following modules from Osmosis provided under this License:
x/epochs
x/mint
We use the following module (marketed as public infra) from Quicksilver provided under this License:
x/interchainqueries
Relevant licenses with full attribution can be found in the subdirectories.