MOVED TO A WORKING GROUP HERE https://discord.gg/yabbPU64gA

python

python interaction with juno chain (mospy, skip / white whale bots have some good work)
https://github.com/ctrl-Felix/mospy & https://github.com/skip-mev/skipper/blob/main/src/transaction.py

Queries / getting data

• query etc of a contract state (including past state with rest? and can do with RPC/CosmJS?)
• Link to https://interchainacademy.cosmos.network/tutorials/6-cosmjs/2-first-steps.html
• subscribe to Tendermint

# python example from my CosmosCache repo. Then these links show GOLang
You can subscribe to a query via the RPC websocket
https://rpc.cosmos.bh.rocks/subscribe?query=_
https://docs.tendermint.com/v0.34/rpc/
https://docs.tendermint.com/v0.34/tendermint-core/subscription.html

• show mintscan.io of seeing contract data / information. (Include screenshots)

Misc

How keyring-backend works with CLI (test, os) many have issues with this
How to get all votes from a proposal? (Link cosmoscontracts repo but embed code directly)
How does gas work?

Explain gas = amount of compuate
Most networks in cosmos charge 0.0025ujuno per gas
So if you use 1,000,000 gas, it cost 0.0025*1000000 = 2500ujuno
Some validators may only allow a higher rate to ensure no spam transaction get though, so you may want to set the gas price to be more like 0.003 or 0.004 to be safe

Authz - grant voting example

# https://github.com/cosmos/cosmos-sdk/blob/main/proto/cosmos/gov/v1beta1/tx.proto
junod tx authz grant <new_address> generic --msg-type=/cosmos.gov.v1beta1.MsgVote --from validator
junod tx authz exec <(junod tx vote withdraw-rewards <valoper> -y --from <validator_bech32_address> --generate-only) --from grantedWallet -y
junod tx authz exec <(junod tx gov vote 202 yes -y --from juno1t8ehvswxjfn3ejzkjtntcyrqwvmvuknzy3ajxy --generate-only)> --from juno1 -y

tokenfactory

I want to make a faucet for my token for people to get, how can I faucet funds?
https://github.com/Reecepbcups/cosmos-faucet/tree/main

internal

• steps for a release ( tag, discord, proposal, height requierments, timelines, etc -- may make sense to do in the main repo instead)

relaying

hermes

note

How to enable REST API & Make the RPC public (0.0.0.0 instead of localhost) + sed replace commands

NFTs (CW721)

Example marketplace? I have one from craft, simple example

(These are from BlockCreators, in the future we may decide to upstream to the cosmwasm book repo)
How do you submit an svg for a nft? (Check how CW20 base package does it in cw-plus)
Proxy contract: How can you have a contract call another contract to mint and send an nft?
How can you have an limited mint of nft that lets users buy until it reaches 0
How do I create a nft via an api call in my application?
How do I query all the nfts that an address holds?
how can you query the metadata of an nft that a user has? (get specific NFT information)
how to burn an NFT
how to mint an NFT on some function call of a contract (ex: after a burn, like a 1:1 redeem)
How can you have an unlimited mint of nft that lets users buy forever (mint the same NFT to any user who interacts with it)
how can you display an svg nft by getting it from an address from application?
How do I send an nft to a contract via an api call in my application?
How to save a map to storage? (BTreeMap)

Contracts

• How do I store a list in a contract and each unique address can add a name to it by calling a function, and can override their own one.
• How can I query this list in the contract and get the stored name by supplying the unique address.
• how do I check if a change has been made on a contract? must I do a call every time period?
• how do I check if a change has been made on a list within a contract? must I do a call every time period?

The docs suggest that running junod tx wasm store ... will give some JSON output from which the code ID of the contract can be extracted. Walking through the commands in those docs though the output looks like yaml:

gas estimate: 1836558
code: 0
codespace: ""
data: ""
gas_used: "0"
gas_wanted: "0"
height: "0"
info: ""
logs: []
raw_log: '[]'
timestamp: ""
tx: null
txhash: 1405DEEA2C3947526B265FDD199578A7377143FAB397C034A953E1866B06FEF6

I can then get the code ID by running junod query tx <txhash> and looking at the raw_log field.

Is this the expected way to go about this now? If it is I can open a PR to update the docs.

My junod config:

$ junod version                                                        
v2.0.0-alpha.1
$ junod config 
{
	"chain-id": "",
	"keyring-backend": "os",
	"output": "text",
	"node": "https://rpc.uni.junomint.com:443/",
	"broadcast-mode": "sync"
}

No instructions have been added here. Suggest we remove if it is not a good relayer solution. Hermes seems to have become the defacto relayer.

Many changes to Juno modules. Need to capture cli reference.

wasm
authz
etc? can someone help list.

@faddat

Update for latest testnet.

See here:

• https://docs.junonetwork.io/smart-contracts-and-junod-development/tutorial-erc-20/compile#uploading
• https://github.com/CosmosContracts/docs/blob/master/smart-contracts-and-junod-development/tutorial-erc-20/compile.md#uploading

Following this tutorial from install to this point, was unaware of how to setup keys, will search deeper.

Needs to include information for:
a) syncing from genesis to current block.
b) syncing from snapshot.

Statesync still not viable for public without wasm folder solution.

Update delegations handbook with new dates, any other changes required.

First, find the location of the binary you want to use:

which junod

Then use the path returned to copy it to the directory Cosmovisor expects. Let's assume the previous command returned /home/your-user/go/bin/junod:

cp $HOME/go/bin/junod $DAEMON_HOME/cosmovisor/genesis/bin

cp $HOME/go/bin/junod $DAEMON_HOME/cosmovisor/genesis/bin

The above data is obtained from docs/validators/setting-up-cosmovisor.md there we can see the cp junod instruction is duplicated.

We need to improve the default page either:

• with a nice description of juno and a couple of links to groups to get started, or
• keep the way it is and update all the page links.

It seems like keeping it in this format will make it difficult to maintain.