larry0x

module playground

go 1.21

require github.com/linxGnu/grocksdb v1.8.4

larry0x

Configure gpg signing (importing an existing private key):

git config --global user.name 'your-name'
git config --global user.email 'your-email'
git config --global user.signingkey 'your-gpg-pubkey'
git config --global commit.gpgsign true
git config --global --list

sudo apt install gpg

larry0x

CW-SDK's bank contract will manage both fungible and nonfungible tokens.

• Each fungible token is identified by a denom
• Each nonfungible token is identified by a tuple (denom, sequence) where sequence is a u64; the 1st token in the collection gets a sequence of 0, the 2nd gets 1, so on

An NFT collection cannot share the same denom with a fungible token.

struct Coin {
    pub denom:  String,

larry0x

{
  "genesis_time": "2023-05-23T00:00:00.000000Z",
  "chain_id": "dev-1",
  "initial_height": "1",
  "consensus_params": {
    "block": {
      "max_bytes": "22020096",
      "max_gas": "-1"
    },
    "evidence": {

larry0x

#!/bin/bash

# Some helper functions for working with cosmos-sdk txs from the command line or
# in bash scripts.
#
# Example: say, if you want to send coins to multiple recipients. We need to:
#
# - compose a tx containing multiple "send" messages
# - set an appropriate gas limit and fee amount
# - sign it

larry0x

# update ubuntu packages
sudo apt update && sudo apt upgrade -y && sudo apt autoremove -y

# update rust
rustup update
rustc -V

# update cargo global dependencies
# dependencies:
# sudo apt install build-essential libssl-dev wget pkg-config

larry0x

//! ```cargo
//! [dependencies]
//! chrono    = "0.4"
//! csv       = "1"
//! ethers    = "2"
//! reqwest   = { version = "0.11", features = ["json"] }
//! rustc-hex = "2"
//! serde     = "1"
//! thiserror = "1"
//! tokio     = { version = "1", features = ["full"] }

larry0x

package main

import (
	"encoding/json"
	"fmt"
	"reflect"

	"cosmossdk.io/simapp"
	"github.com/cosmos/cosmos-sdk/codec"
	codectypes "github.com/cosmos/cosmos-sdk/codec/types"

larry0x

//! ```cargo
//! [dependencies]
//! bech32    = "0.9"
//! bip32     = "0.5"
//! dialoguer = "0.10"
//! hex       = "0.4"
//! k256      = "0.13"
//! ripemd    = "0.1"
//! thiserror = "1"
//! ```

larry0x

The data field in cosmwasm_std::Response is underused. We should use it more! Here's why.

Often we want to program contracts that do this:

1. call another contract
2. after the call is completed, handle the response and do some extra actions

For example,

1. swap some token A to token B at Astroport