Lavender.Five has joined the group of node operators that help secure the Allora Network. As a dedicated provider of secure infrastructure and pragmatic software solutions, Lavender.Five runs validators on more than 60 mainnet blockchains. Our setup includes bare metal servers with a minimum of 2 full nodes per network, each hosted at a different provider and a different geographical location. To ensure optimal performance and security, Lavender.Five maintains secure, high bandwidth, encrypted connectivity between their data center networks and public nodes, enabling node relocation, data duplication, and encrypted communication across sites.

With our extensive track record, including securing more than $500M in assets and maintaining the most-used monitoring solution for tendermint chains (Tenderduty), Lavender.Five is uniquely positioned to help the Allora Network establish a strong foundation and enable it to thrive by deploying as a node operator in the beginning days of the network.

“As an experienced blockchain operator, we are happy to lend our resources and tooling to the wider Allora validator set and ecosystem, contributing to the chain’s redundancy with our distributed bare metal validation,” says Dylan Schultz, CEO of Lavender.Five. “Allora tackles the intersection between AI and blockchain in a pragmatic manner by creating a reputation-based market for AI models and ML algorithms, mitigating user privacy concerns and model non-determinism issues. We are excited to be a part of Allora’s mission while creating new business opportunities for data scientists.”

Evolution of the Allora Network and Lavender.Five

AI is the most deflationary, expressive form of compute to ever exist and can intelligently process large amounts of information. For the past 3 years, Allora Labs (formerly known as Upshot) has been building AI-powered crypto infrastructure to power new applications and protocols in gaming, lending, market making, and more. Models built by the Allora Labs team have effectively produced price predictions for more than 400 million assets with a 95–99% confidence for the most accurate predictions.

The team’s earlier work in subjective consensus mechanism design, along with learnings gathered from building AI-powered crypto infrastructure, led them to create the Allora Network, a self-improving decentralized AI network that harnesses both the efficiency of AI and the wisdom of the collective to reach one mission: transform intelligence itself into a digital commodity.

As an Allora node operator, Lavender.Five furthers that mission by operating both a validator to secure the Allora chain and a Reputer to rate the performance of the ML models delivered by Allora Workers, performing a critical service that reinforces the self-improvement mechanism of Allora.

“Collaborating with veteran secure systems builders like Lavender.Five is crucial to the success of Allora,” says Nick Emmons, Co-Founder of Allora Labs. “Dylan and his team’s dedication to secure blockchain infrastructure directly contributes to the growth and security of the network.”

Why Lavender.Five and Allora Are Working Together

As a leading provider of secure infrastructure and pragmatic software solutions, Lavender.Five offers a comprehensive range of services to support blockchain networks and developers:

• Block Production and Validation — Lavender.Five ensures industry-leading uptime and continually advances the security boundary. Their services include 24/7 redundant monitoring, hardware key storage, remote signers with always-ready backups, 100% soft-slash protection, SSH and VPN based firewall protection, and geographically redundant dedicated bare metal servers.
• Infrastructure and tooling for the Allora ecosystem — Lavender.Five helps make blockchain accessible by providing public API nodes (RPC, gRPC, and REST) that assist developers in connecting their dApps, explorers, and tools to the blockchain, lowering the barrier to adoption. Additionally, our seed nodes and state snapshots ensure higher uptime for every validator in the business, while our IBC relayers will power interoperability for Allora to the wider Cosmos ecosystem.
• Open source development and consulting — With over 25 years of experience in software development and 3 years in the blockchain industry, Lavender.Five has created automation tools to streamline validator operations, maintains the largest Cosmos monitoring suite, contributed to 10+ public libraries, and led the genesis of 25+ networks. Lavender.Five has successfully delivered over 100 emergency patches and can actively help Allora with their security exposure, strategy, documentation and other core network necessities.

With over 100.000 individual delegates Lavender.Five will help onboard a diverse web3 community to the Allora network and we are excited to lend all our resources and expertise to make the network an outstanding success.

About Lavender.Five

Lavender.Fives Nodes is a company of 3 dedicated to bringing secure infrastructure and pragmatic software solutions to over 50 proof-of-stake blockchains. With 15+ years in software development and system administration experience we guarantee safety for the funds of over 100,000 delegators. This makes us one of the most trusted Proof of Stake validators. Our team is able to maintain industry-leading uptime by using dedicated servers around the world, multiple 24/7 alerting systems, and a remote signing solution with always-ready backups.

To learn more about Lavender.Five, visit the website, follow on Twitter, join the Discord, and check out the Github.

About the Allora Network

Allora is a self-improving decentralized AI network.

Allora enables applications to leverage smarter, more secure AI through a self-improving network of ML models. By combining innovations in crowdsourced intelligence, reinforcement learning, and regret minimization, Allora unlocks a vast new design space of applications at the intersection of crypto and AI.

To learn more about the Allora Network, visit the Allora website, Twitter, Medium, Discord, and Developer docs.

NOTE: This is intended to be a very basic guide on Linux security practices. If you want to more in-depth information, you can read about it here.

The following topics will be covered:
1. SSH Key Setup

2. Server Configuration

3. Setting up a Basic Firewall

When you receive your server, you will be provided a root user login, and a password. You’ll be inclined to log in with that login and password, but we have steps before we do that! We first want to create out ssh key as we’ll be disabling password login shortly.

SSH Key Setup

Create SSH Key

An SSH (Secure Shell) key is a way to identify yourself as a user without using a password. It has 2 parts: the pubkey and private key. When you create the SSH key, you give your pubkey to a computer you wish to log into. You can then “show” the server your private key and it will admit you automatically. This makes it far more secure than a password, as then only you will have access to the server via your key.

This document assumes you’re using a Mac. If you need instructions for Linux or Windows, see the Github instruction for generating an SSH key.

1. Open Terminal
2. Generate the SSH key:

$ ssh-keygen -t ed25519 -C “your_email@example.com”

3. When you’re prompted to “Enter a file in which to save the key,” press Enter. This accepts the default file location.

4. At the prompt, type a secure passphrase. For more information, see “Working with SSH key passphrases.”

> Enter passphrase (empty for no passphrase): [Type a passphrase]
> Enter same passphrase again: [Type passphrase again]

Your SSH key is now created, but we have to add it to the agent for it to be usable.

Adding your SSH key to the ssh-agent

1. Start the ssh-agent in the background

$ eval "$(ssh-agent -s)"
> Agent pid 59566

2. Open your SSH config file

$ open ~/.ssh/config

3. Add the following text block to your file

Host *
  AddKeysToAgent yes
  UseKeychain yes
  IdentityFile ~/.ssh/id_ed25519

4. Add your SSH key to the ssh-agent

$ ssh-add -K ~/.ssh/id_ed25519

Your SSH key is now set up! This only has to happen once, so you can skip this if you need to refer back to this document.

Server Configuration

In this section we will cover:

1. Logging In
2. Creating a new user
3. Disable root login
4. Disable password login

Logging in

When you provision a new server, you will be provided a username, password, and ip address. Generally that username will be root. Let’s log in with them now in the form of ssh username@ip .

1. Initiate login to server

2. Type Yes

3. Enter password

You are now logged into root. However, we do NOT want this as an option, so let’s fix it.

Create New User

Since we no longer want to be able to log in as root, we’ll first need to create a new user to log into.

1. Create a new user

You’re going to want to choose a unique username here, as the more unique, the harder it’ll be for a bad actor to guess. We’re going to use mellamo .

$ adduser mellamo

You will then be prompted to create a password and fill in information. Don’t worry about the information, but make sure your password is complicated!

2. Give them sudo privileges

sudo is the name for “master” privileges, so we need to modify the user to add them to that group.

$ usermod mellamo -aG sudo

3. Verify user has sudo access

$ su - mellamo
$ sudo ls /root

Disable Root Login

Disabling root login takes away an easy method for hackers to get in. The easiest way of accessing remote servers or VPSs is via SSH and to block root user login under it, you need to edit the /etc/ssh/s

Copy SSH key

1. Return to you local machine.

$ exit 

2. Copy your ssh key to the server

$ ssh-copy-id mellamo@

3. Confirm you can login with just your SSH key

$ ssh mellamo@104.149.129.250

Done! You can now log in exclusively with your SSH key.

Disable Password Login

Now that you can log in with just your ssh key, you should now disable password login.

1. Return

Setting Up a Basic Firewall

Uncomplicated Firewall (UFW) is a program for managing a netfilter firewall designed for easy use. It uses a command-line interface (CLI) with a small number of simple commands, and is configured with iptables. UFW is available by default in all Ubuntu installations after 18.04 LTS, and features tools for intrusion prevention which we will cover in this guide.

1. Start by checking the status of UFW.

$ sudo ufw status

2. Enable SSH

$ sudo ufw allow ssh/tcp

3. Enable p2p

This is the default p2p port for Tendermint systems, but if you’ve changed the port, you’ll need to update the ufw setting.

$ sudo ufw allow 26656

4. Enable UFW

$ sudo ufw enable

5. Confirm UFW is enabled

$ sudo ufw status

Note that at any time you can disable ufw by doing:

$ sudo ufw disable

Full disclosure: Lavender.Five Nodes has a conflict of interest with a 135,000 $JUNO delegation from the whale in question.

edit: The core development team has asked everyone to vote down Proposal 16. We are changing our vote from ABSTAIN to NO.

C1 on Twitter: "1/3 🧵We as Core-1 sincerely ask the $JUNO community to down-vote #prop16. The text of the proposal was rushed. Parts do not reflect core principals that Juno holds dear. After a period of gathering more information and consulting with the community 👇 / Twitter"

1/3 🧵We as Core-1 sincerely ask the $JUNO community to down-vote #prop16. The text of the proposal was rushed. Parts do not reflect core principals that Juno holds dear. After a period of gathering more information and consulting with the community 👇

Juno Network Governance Proposal: Correcting the gamed stakedrop is controversial to say the very least. This article is a representation of current events, and more information is likely to come out after it is published. This will include a breakdown of Prop 16, an analysis of the malicious actor accusations, and a discussion about the pros and cons of the proposal. It concludes with our final thoughts and ultimate vote.

What is Proposal 16

Juno Network Proposal 16 is an initiative to extract funds from a “whale” that “gamed” the genesis airdrop of Juno Network. The Juno Network team implemented a “whale cap” for a maximum of 50,000 $JUNO to be granted per person or entity. You can read more about it here. This was to ensure a fair distribution of the tokens, and that no entity could gain a controlling/dangerous stake in the network.

The whale in question utilized 53 separate wallets reaching the “whalecap.” of $50k $ATOM at the time of the snapshot. After Juno Network started and they received their tokens automatically, they combined all wallets into a single, mega-wallet with more than 2.5M $JUNO, and an arguably disproportionate and controlling stake in the network.

The execution of this Proposal 16 seeks to:

1. Revoke excess funds from the whale, and place them in the community fund
2. Leave the whale 50,000 $JUNO ($2,000,000 USD at time of writing)
3. Compensate validators the whale is currently delegated to using the community fund

Proposal 16 requires a software upgrade changing the state of the blockchain.

Why Now?

Juno Network Proposal 4 sought to correct the genesis in the very beginning. At the time, there was significant support until Wolfcontract came forward to tell the story of the whale: they’re a fund and aren’t bad actors.

Wølfcontract on Twitter: "1/3The $JUNO whale has reached out to me last night. The address belongs to a fund.The fund is managing $ATOM and now $JUNO for dozens of individuals. The fund is offering to support the network and is not interested in hurting $JUNO. pic.twitter.com/7pWLAEWTWH / Twitter"

1/3The $JUNO whale has reached out to me last night. The address belongs to a fund.The fund is managing $ATOM and now $JUNO for dozens of individuals. The fund is offering to support the network and is not interested in hurting $JUNO. pic.twitter.com/7pWLAEWTWH

What changed in the coming months? The behavior of the whale was deemed hostile.

Wølfcontract on Twitter: "What changed?It's a single entity hurting the network.Since launch 1.5 mill gamed $Juno were dumped ie. $60,000,000 at current valuations. The stakedrop rules were circumvented. The entity is linked to various investigations. The entity is still a threat to gov to name a few https://t.co/TJrIL2IcgU / Twitter"

What changed?It's a single entity hurting the network.Since launch 1.5 mill gamed $Juno were dumped ie. $60,000,000 at current valuations. The stakedrop rules were circumvented. The entity is linked to various investigations. The entity is still a threat to gov to name a few https://t.co/TJrIL2IcgU

The whale has contested this accusation, stating:

as we said in a direct message to the core team, we were actually selling only less than 1% slippage per day for these few months.

We do know this isn’t entirely true, as their sell activity on January 8th dropped the price of $JUNO from $15.28 to $12.72 per token. These transactions can be seen here and here.

Good investment strategies include taking profits, which they did. In addition, despite the selling pressure, we can see the price of $JUNO immediately rebounded. The whale selling isn’t enough to deem them a hostile actor.

Boiling It Down

We know they can’t be the only other whales in the ecosystem. A small amount of sleuthing discovered another whale that combined multiple 50k $JUNO wallets into a single mega-wallet. They aren’t in the same magnitude of size, but if the goal here is to “right wrongs”, should we not address all of the whales that gamed the drop?

This isn’t about all the whales, this is about a single whale. This is about the GAME validator, previously known as CCN (Cosmos Club Network), the allegations against them, and whether the future of the network should be beholden to the whims of one ethically ambiguous entity.

What are those allegations?

The Ponzi/MLM scheme

CCN has been accused of scamming users via a ponzi scheme.

You pay CCN, and they purchase $ATOM on your behalf, and stake it with their validator. If you purchase $500 in $ATOM, you receive 4% APR. However, you receive a higher return as you increase your $ATOM purchase, up to a total of 10% APR.

With a staking return of 15.45%, a max of 10% seems like a reasonable number. Traditionally ponzi/Multi-level marketing (MLM) schemes promote way higher returns. What gives?

The ponzi scheme-like behavior comes from their referral bonus structure. It works like this:

—

If you invest in a $10,000 plan, the “binary bonus” is 8%. If the referrer invests in a $ 2,000 plan, 8% of the $2000, $160, will be returned to you.

Also, please note that your investment amount = the largest possible amount of referral fee you can receive each month. For example, if you’re investing in a $10,000 plan, no matter how many referrals you add, you won’t receive more than $10,000 per month.

The introducer branches into two and spreads under himself, and the return is from the one with the lowest sales in the left and right organizations. In other words, the key to maximizing profits is to arrange the left and right sides in a well-balanced manner.

—

This scheme certainly screams multi-level marketing, and takes on a significant amount of risk based on $ATOM’s price movement, but the returns are modest in the face of the staking returns possible.

This is not enough to mark them a malicious entity.

The Telegram Seed Phrase Scam

The other big allegation against the whale is they ran a seed phrase scam ring. However, I was unable to trace down any evidence of this happening. Only speculation.

As far as I’m concerned, this is hearsay.

Arguments for Reclaiming the Whale’s Tokens

1. They “gamed” the drop via insider information, therefore foul play

This is proven to be untrue. The whale in question began accumulating their $ATOM and wallets in May of 2020. They would fill a wallet to 100k $ATOM, then begin filling the next wallet. Joe Abbey has outlined this in their article here.

Through 2020–2021, the Anonymous Whale delegated funds in new addresses as each address reached a threshold of approximately 100K $ATOM. As each address filled up a new one would be started…The Anonymous Whale had already spent 12 months loading up 50 addresses with near even amounts of delegation.

The wallets were systematically funded over the course of a year prior to the snapshot. It was not gamed or an inside job. The whale received the airdrop via sheer dumb luck.

2. Threat to Juno Network governance

This is partially true. At the current bonding rate, they control ~10% of the voting power, or 50% of the quorum threshold. With that level of power, they can easily sway the vote. History has shown that they have chosen to either ABSTAIN on all votes or vote YES on clear-answer votes — like software upgrade proposals.

3. Threat to price action/stability

This is also partially true. At the time of publishing this article, they’ve sold 1.5M $JUNO. At current prices that would mean ~$60,000,000 USD, but they were not all sold at $40/$JUNO. What’s clear about this is they are instituting clear supply-side pressure, with only their staking rewards. Were they to un-delegate and sell a larger portion of their tokens, they could crash the market. They have more $JUNO to sell than all of JunoSwap and Osmosis have in liquidity, combined.

Having such a significant portion of $JUNO’s value in a wallet with no “skin in the game,” (they didn’t purchase the tokens, but were airdropped them) is extraordinarily dangerous. $JUNO isn’t just about “number go up;” Juno Network is depended upon by many professionals for their livelihoods. This isn’t just software engineers that can make money anywhere — it’s community managers, marketers, influencers, and everyday people.

However, there is no incentive for the whale to dump their tokens, rather than continuing to accumulate. They have the economic incentive to keep Juno healthy. In addition, as shown above, when they dumped significant amounts the market immediately recovers.

4. Upholding the intent of the network

This is the most compelling argument for why their tokens should be reclaimed. The intent of Juno was to create a grassroots network, free of mega-whales at the genesis. This whale flies in the face of that ethos. Indeed, there is historical precedent for making corrections of the genesis due to external conditions.

• Osmosis Prop 32 “claws” back unclaimed airdropped $ION and $OSMO to the community pool.
• Cosmos Hub Prop 29 granted $ATOM to “genesis block accounts” that lost access to their funds.

Both proposals passed and ultimately had the same outcome — changing the state of the chain. The big difference with Juno is it’s addressing a single entity, and the scale is far more grand.

5. They are malicious actors in the ecosystem

As outlined above, this is unproven. Further, what statement does this make that we as a community can decide the fate of one entity without giving them a fair opportunity for rebuttal?

The whale has made a statement, including an alternative resolution:

Our proposal to the community is ‘Stake all Juno we own forever. Sell the reward and if we change it to another tokens, we have to provide liquidity to Junowap with that token pair. Also, we can’t unbond the liquidity for 2 years from now.’ [sic]

This is a strikingly reasonable take on the situation, and gives both parties an opportunity to come out ahead without going against the spirit of blockchain.

Arguments Against Reclaiming the Whale’s Tokens

1. Code is law

A core tenet within blockchain is the immutability of the chain. There was a “bug” in the genesis, yes, but that was as the code was written. Given the length of time that has gone on since genesis, this is tantamount to stealing ~$120M USD worth of property from the entity.

2. Philosophy

For the short-term health of the network removing the whale’s tokens makes complete sense. Their sum of tokens went against the spirit of the airdrop. They have significant control over the price action of the network. They do sell frequently, causing supply-side pressure.

But is it our place to revoke those tokens? Are we always supposed to adhere to the original vision of the founders/creators? Doesn’t that go against the spirit of decentralization?

The Meta Discussion

The currently proposed solution (Proposal 16) is to forcibly remove their tokens, and put them in the community fund. The singular whale would be left with 50,000 $JUNO, the maximum amount considered allowable per entity.

Consumer Protections

This vote sets a precedent for the blockchain ecosystem as a whole. A wallet (a hacker that exploits a smart contract, say?) may be punished by the community if it’s deemed not in the community’s best interest. A tenet of Web3 is taking back control — is this not the logical conclusion of doing so? Discovering a malicious actor and undoing their wrong?

Is this vote opening up precedent for us, the blockchain community, to police ourselves when it comes to consumer protections?

Censorship Resistance

In contrast, immutability of the chain is what protects against censorship, and this proposal is going against that founding ethos. Enabling arbitrary state changes on the blockchain breaks down the core trust system in the blockchain.

It takes the database from read/write to read/write/edit.

The Role of the Validator Vote

Validators and delegators have different responsibilities when voting on-chain. The core responsibility of a validator voting is maintaining the security of the chain, be that ensuring the code is correct (a la being active in testnets), or looking further out into the horizon. It is our job to protect and serve the community.

Voting YES on Prop 16 as a validator has two ramifications:
1. Chain Security. Due to the amount staked with the whale, and how they’ve spread out their delegations, having their funds removed severely decreases the security of the chain. Given that they have 10% of all voting power, spread across 29 validators, they are a significant power in securing the network. They are acting far more decentralized than is the norm. More power will be pushed to the top.

2. Wallet Security. Giving “express” permission to remove funds from a wallet that we, as a community, disagree with opens up the opportunity for it to happen again. It is our sole job as a validator to protect accounts and uphold the immutability of the chain.

Closing Thoughts

Fundamentally, the question is whether it’s the identity of the whale that matters, or the intent of the creators of Juno Network.

If this proposal seeks to correct the intent of the drop…

We can say definitively that this whale existing goes against the intent of the airdrop, however we disagree with the implementation of this proposal. If it were to be done correctly, it should have addressed all the whales that exhibited gaming of the airdrop. As it currently stands, there are other whales that aren’t being accounted for. This opens the door for subsequent proposals to be put forth to address other genesis wallets.

If this proposal seeks to correct this single whale due to it being a malicious actor…

We want more proof. All that has been shown is hearsay and emotional rhetoric.

We believe for this proposal to be done correctly, a clearer outline of the implementation should have been included. It should also have been pre-empted with a community discussion to ensure proper protections, such as a Juno Network Constitution so that this type of proposal can’t be repeated. Finally, this should have been resolved with Juno Network Proposal 4.

For that reason, we will be voting to ABSTAIN from this proposal.

Additional reading:

• Polkachu’s analysis resulting in a YES: https://polkachu.com/blogs/people-vs-juno-whale
• Needlecast’s analysis resulting in a NO: https://needlecast.envoys.io/posts/prop16.html
• CryptoCrew Validators’ analysis resulting in NO with VETO: https://ccvalidators.medium.com/a-critical-decision-about-the-future-of-dpos-about-juno-proposal-16-439f4c0f2e2f

Sources

• Tx verifying whale’s identity, with attached response: https://www.mintscan.io/juno/txs/BC2DDD77054B64234CCA86E4347269924BCE717D637C1B651FA5AAF7567B6199
• Whale’s response: https://medium.com/@WhaleJuno/our-statement-on-juno-prop-16-5a06b26e6cff
• Articles about CCN (in Japanese):
  https://kakuduke-tsuka.com/ccn/ https://moneytopics-truth.com/ccncosmos-club-network#CCNCosmos_Club_Network-5 https://twitter.com/takumiasano_jp/status/1493201182428626947?s=20&t=uNk3110u3ryhQN2Pen2fWQ https://sites.google.com/site/cryptokarakuchi/index/page10 https://web.archive.org/web/20201101043732/https://ccn.promo/
• Juno price history: https://www.coingecko.com/en/coins/juno-network

$SCRT is the native token of the Secret Network. Secret Network is the first blockchain with data privacy by default, allowing you to build and use applications that are both permissionless and privacy-preserving. This unique functionality protects users, secures applications, and unlocks hundreds of new use cases for Web 3.

Because of this privacy-by-default ethos, $SCRT proves difficult to purchase within the United States, similarly to Monero. However, with Secret Network now being IBC enabled, $SCRT can easily be purchased through Osmosis, the best decentralized exchange (DEX) in the cosmos ecosystem.

NOTE: if you prefer video guides, please see Secret Code Podcast’s excellent guide: https://www.youtube.com/watch?v=b9_F14eAcKE

A few assumptions are going to be made here before we start.

1. You already have a Coinbase Pro account, or any exchange that has $ATOM
2. You already have funds on Coinbase Pro with which you can purchase $ATOM
3. You are using one of the following browsers: Brave, Chrome, or Edge. We recommend Brave.
4. You have Keplr browser extension installed. You can install it by following this guide.

With that out of the way, let’s get started.

Purchase ATOM on Coinbase Pro

We’re first going to need to purchase $ATOM, as it is one of the primary assets traded on Osmosis.zone. This guide is going to use Coinbase Pro to purchase the $ATOM, but these steps apply to any exchange that has $ATOM.

1. Purchase ATOM from Coinbase.
2. Navigate to your portfolio.
3. Select Withdraw in the top right corner.

1. Select ATOM -> Crypto Address. You should now be in a window that says WITHDRAW ATOM.
2. Copy the cosmos... address you saved earlier.
3. Paste the copied cosmos... address where it says Enter ATOM Address.
4. Make sure to select the checkbox where it says This transaction does not require an ATOM Memo. A memo is only necessary when sending to an exchange.
5. Enter the amount of ATOM you wish to withdraw.
6. Select Withdraw. This may require going through several multi-factor authentication steps. It should look like the image below.

Once this is complete, you should be able to see your funds in your Keplr Extension! Now we need to transfer them to Osmosis.

Trade $ATOM for $SCRT on Osmosis

Osmosis is the best way to purchase many Cosmos-based assets, including $SCRT, $OSMO, and $JUNO. We’re going to use it to trade $ATOM for $SCRT.

1. Navigate to the Osmosis Assets website.

1. In the bottom left corner there’s a Connect wallet button. Select it and a popup will emerge from Keplr - hit Approve.
2. You should now be in the Assets page. Find Cosmos Hub - ATOM and select where it says Deposit. This will send your $ATOM from the $ATOM wallet to your Osmosis Network wallet. Don't worry, you'll still have full control over your funds and will be able to see them in your Keplr extension by selecting Cosmos -> Osmosis.

1. In the Deposit IBC Asset popup, enter the amount of $ATOM you wish to deposit and select Deposit. This will cause another Keplr wallet popup to occur. Select Approve.
2. Your asset is now being sent from the Cosmos Network to the Osmosis Network. It may take several minutes to arrive. Refresh the page and you should see your deposited $ATOM under the Balance category.
3. Navigate to the trade page. Here you will be trading your $ATOM for $SCRT.

1. Enter the amount of $ATOM you wish to trade for $SCRT and hit Swap. This will cause another Keplr popup. Select Approve.

You now have $SCRT, but it’s on the wrong network! Let’s go ahead and send it to the Secret Network.

Send $SCRT from Osmosis Network to Secret Network

Osmosis is great, but what if you want the privacy features enabled by the Secret Network, or to stake your $SCRT? You’ll need to transfer them over just like you did with $ATOM.

1. Return to the Assets page of Osmosis.
2. Find Secret Network - SCRT and select Withdraw.

1. In the Withdraw IBC Asset popup, enter in the amount of $SCRT you wish to withdraw and select Withdraw.
2. The Keplr extension will pop up. Select Approve.
3. Congratulations! You now have your $SCRT on the Secret Network! You can see your $SCRT by going into your extension, select Cosmos -> Secret Network.

Conclusion

From here, you can stake your SCRT for 30%+ APR (consider staking with us, Lavender.Five Nodes!) or make privacy-preserving trades using SecretSwap.

Keplr Wallet Extension https://wallet.keplr.app/
Keplr Help Desk https://keplr.crunch.help/
Osmosis Zone https://app.osmosis.zone/
Secret Network https://scrt.network
Coinbase Pro https://pro.coinbase.com/

OSMO and SCRT incentives for ATOM/SCRT and OSMO/SCRT pairs are live on Osmosis Zone. This guide will help you get started on preparing to join the LP pool to earn both OSMO and SCRT rewards.

Osmosis Zone is a decentralized exchange (DEX) for IBC assets that exists on the Osmosis chain, an IBC implemented blockchain built on Cosmos SDK (just like Secret). Osmosis Zone allows users to deposit IBC-enabled assets directly to their wallet address on Osmosis and use those assets for trading and LP.

To get started you’ll first need to make sure you have a Keplr Wallet installed (follow this guide).

Depositing SCRT from Secret to Osmosis Zone

Select “Assets” on the left panel on Osmosis Zone, find Secret Network/SCRT and click “Deposit.” If this is your first time, an approval transaction will appear that you must approve. Enter the amount of SCRT you would like to send to Osmosis Zone and click “Deposit.”

Your SCRT should arrive within a few seconds to a few minutes (note: If funds do not arrive, IBC will automatically revert your funds back to Secret). You’ll be able to confirm your deposit by checking on both the Osmosis Zone Assets page and on your Mintscan profile for Osmosis.

Withdrawing SCRT from Osmosis Zone to Secret

Select “Assets” on the left panel on Osmosis Zone, find Secret Network/SCRT and click “Withdraw.” Type in the amount of SCRT you wish to send to Secret and click Send. After approving the transaction in Keplr, you’ll see a transaction status at the bottom of your assets page. Your SCRT should arrive within a few seconds to a few minutes (note: If funds do not arrive, IBC will automatically revert your funds back to Osmosis). You’ll be able to confirm your deposit by checking on both the Osmosis Zone Assets page and on your Secret Nodes profile for Secret.

Trading SCRT on Osmosis Zone

Click on “Trade” on the left panel on Osmosis Zone, select SCRT as the first asset and select the asset of your choice for the second. Input the amount of SCRT you are willing to trade and click swap. An approval transaction will appear from Keplr. Once your trade is successful, you will see a less amount of SCRT and a greater amount of the currency you traded for on your Osmosis Zone Assets page. You can also trade ATOM or OSMO for SCRT!

Providing LP to ATOM/SCRT and OSMO/SCRT

To provide liquidity to Osmosis pools and earn both OSMO and SCRT, click on the “Pools” page and find Pools 584 & 585. Select the pool you wish to deposit in (if you wish to do both, the same steps will apply to both). For this example we will use OSMO/SCRT — click “Add Liquidity” at the top of the pool page for OSMO/SCRT and enter the amount you wish to deposit (it must be 50% SCRT and 50% OSMO) and approve the transaction in Keplr.

You will receive GAMM tokens in your Osmosis wallet in exchange for providing liquidity.

At this stage you are only earning transaction fees, so you’ll need to bond your LP in order to earn OSMO and SCRT incentives. Look for the balance of the deposit in the pool near the button that says “Earn.” Click that button and deposit the amount of GAMM you wish (100% if you want to earn on all of it), and select the type of pool you wish to join.

1 Day — Bonded LP will take 1 day to unbond. This is the smallest APR of the three.

7 Day — Bonded LP will take 7 days to unbond.

14 Day — Bonded LP will take 14 days to unbond. This is the largest APR of the three.

Please note that APR listed on Osmosis Zone is for OSMO rewards, not SCRT rewards.

Once you approve the bonding transaction, refresh your pool page and check to see that your GAMM tokens are bonded in the correct bonding pool.

Unbonding and removing LP from ATOM/SCRT and OSMO/SCRT

To unbond, click and Pools and go to the pool page you have bonded LP in and find the “My Bondings” section. Click “Unbond All” and approve the transaction in Keplr. Depending on which unbonding period you selected (1/7/14) will determine the amount of time it takes for your GAMM tokens to show in your wallet. During this time, you will still earn OSMO/SCRT rewards but at a deprecated rate.

Once the time period of unbonding has finished, you will be able to remove your LP by clicking “Add/Remove Liquidity” at the top of the pool page. Select the amount of GAMM you wish you withdraw and click “Remove Liquidity.”

Conclusion

And that’s it — as long as you’ve followed the steps in this guide you are now bonding LP and earning both OSMO and SCRT rewards. OSMO and SCRT rewards will automatically appear in your Osmosis wallet daily after each epoch (530PM UTC). Please refer below for further information.

Keplr Wallet Extension https://wallet.keplr.app/
Keplr Help Desk https://keplr.crunch.help/
Osmosis Zone https://app.osmosis.zone/
Secret Network https://scrt.network
Secret Network Starter Guide https://medium.com/@secretnetwork/secret-network-starter-guide-8a6231c7c5b4

Welcome to the Medium page for Lavender.Five, a professional team running validator nodes on different Cosmos blockchains. This space will be for updates on new mainnet launches, user guides, and other news related to Lavender.Five. Be sure to follow to get the latest updates on our services.

List of Mainnet Nodes
ixo
https://blockscan.ixo.world/validator/ixovaloper1wd02ktcvpananlvd9u6jm3x3ap3vmw59wh7me3

Juno
https://www.mintscan.io/juno/validators/junovaloper1wd02ktcvpananlvd9u6jm3x3ap3vmw59jv9vez

Kava
https://www.mintscan.io/kava/validators/kavavaloper1vze5p4n0uj6h6fakczsj3e0npr8ud93lnffge3

Osmosis
https://www.mintscan.io/osmosis/validators/osmovaloper1glmy88g0uf6vmw29pyxu3yq0pxpjqtzqr5e57n

Secret
https://secretnodes.com/secret/chains/secret-3/validators/84BC2C72491187FAB144F628166E10D592786616

Find out more
Website http://www.lavenderfive.com
Twitter https://twitter.com/lavender_five/
Discord http://discord.gg/Gwrs35VH3f
Reddit http://reddit.com/r/lavender_five