In the file, the goroutines used for fetching balance information lack proper error handling. This can lead to unhandled errors and affect the robustness of the tool in production environments. It is crucial to implement comprehensive error handling to ensure the tool's reliability.

Referencing PR: #204
Referencing comment: #204 (comment)

Let's add the latest version of the ibc wasm client.

Let's make Eve the first chain with fee abstraction running live.

• make sure FA is good to go for sdk 50
• Integrate FA into eve

• allow delegators to choose whether or not they would like the validator to represent them
• implement madcatattack3's present concept

In the tradition of Osmosis, eve will be launching without a formal audit, though we will have gone through the code and checked as carefully as possible, as many times as possible.

I will also be posting this issue to Twitter, and offering some sort of bounty or such for performing an audit of eve and making findings.

2 nodes

Leave one on 1317 26657, move the other with new val & up ports +10 across the board

testnet.go kinda bleh if we can just test native builds directly

Then I can learn relaying off it anyways.

Let's integrate support for github.com/cosmos/interchain-security

this may require upgrading ics to ibc v8

the team at x.com/cyber_devs has built a modified cosmos-sdk that supports nvidia gpus natively.

It would be great to get this support in eve so that eve can support next generation computing models

• Pass Threshold - 2/3rds (66.7%)
• No Downtime slashing, jailing occurs after 1000 missed blocks
• 10% equivocation slashing
• No Community Pool tax
• 300 validators

Contributors should receive an allocation in Genesis of some sort, so that we can attract and retain, as a decentralized community, the finest talent.

I don't really know the amount and no promises are being made here but certainly something should be done so that we are able to engage with developers over the decades to come.

This is a notable historic weakness of the distribution of atom，for example.

This benefit should be vested and as independent of any allocation reserved for the quicksilver foundation.

This benefit does not apply to contributions that occured before March 1, 2024

This should include individuals who are providing advisory

Eve requires a testnet, which will continue to run after mainnet launches.

This issue contains a proposal for a permanent, incentivized testnet.

• testnet can have up to 300 validators just like mainnet
• anyone may participate in the testnet
• sibyl avoidance by phone call / referral system
• testnet incentivization to equal some % of supply over some number of years
• validators who stop participating in the testnet are removed from the incentive list

service feeabstraction.feeabs.v1beta1.Msg does not have cosmos.msg.v1.service proto annotation
service alliance.alliance.Msg does not have cosmos.msg.v1.service proto annotation
File at mytestnet/config/genesis.json is a valid genesis file
service alliance.alliance.Msg does not have cosmos.msg.v1.service proto annotation
service feeabstraction.feeabs.v1beta1.Msg does not have cosmos.msg.v1.service proto annotation
service feeabstraction.feeabs.v1beta1.Msg does not have cosmos.msg.v1.service proto annotation
service alliance.alliance.Msg does not have cosmos.msg.v1.service proto annotation

What is the purpose of the change

Updates the GitHub Actions CI to push docker images due to the deprecation of set-output commands in Github Action (source: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/).
The functionality's still the same.
Put all docker.yaml in a same file.

Brief Changelog

• Update GitHub action logic
• Rename it to push-docker-images.yaml

we need a module for whitelist ica connections, connections will need to pass gov to add to whitelist

Eve is going to have very low inflation, so the minimum commission level should be set to 11.69420808%

Let's integrate PFM, because Skip will want that

Python Script to convert

• another chains CW20 raw

-> Eve tokenfactory

(if you are the owner, have an import [file.json] function)

reason:
Makes moving your platform over to eve easier

SCRIPT RUNDOWN

- get all RPCs from cosmos.directory for a given chain (example is juno)
- query all and connect, get 25-50 per query, have a promise timer to ensure we don't go over
- query all balances & save to a file

- if promise errors out, just put it back to try again later
(DO NOT TRY TO PROMISE ALL)

See Gaia -

github.com/cosmos/gaia

Maybe do just how they did, give credit to them for the 46 converty and to tgrade for origination. I think this is a very desirable feature.

We may not need to copy Gaia's x folder though. Might just be able to smoothly import it.

If we are copying Gaia at all, it might actually make sense to have a look at her test suite. Let's get eve very sharp, pointed and deterministic.

Let's integrate github.com/osmosis-labs/mesh-security but only if @JakeHartnell or @sunnya97 think it is ready to go

• move docker -> script
  init_docker.sh

ReadMe for all scripts

Cleanup compose to use same node ids on gentx?

Eve should lunch with a very clear definition of purpose, and that purpose should be stated in Genesis in a constitution.

This will help to guide the user community and governance community in their activities on Eve. She should tell people how to use her.

The constitution is only amendable by governance. Unconstitutional desires that can't pass a governance proposal should fork.

Eve's genesis Parameters

Note: not every field is correctly named. Please update the field names as we come across the correct names.

The comet team is building out a really neat configuration reference manual that I think will be helpful in determing an ideal configuration for eve's genesis parameters:

• cometbft/cometbft#2352

the parameters

Comet

max_bytes: 2000000
max_gas: 100000000

Cosmos-sdk

Parameters for the cosmos-sdk

Slashing

Goal: heavily penalize equivocation, while not even bothering to slash for downtime, but instead ensure that validators are removed from consensus to allow the chain to function ideally and reduce the risk of a halt.

slashing_jail_window: 1000 blocks
downtime slash: 0%
equivocation slash: 10%

Governance

Goal: minimize the role of governance on Eve, while ensuring that governance functions well for the few key activities where it's essential:

• chain upgrades
• community pool funding
• taxation (tax is initally set to zero)
• light client updates
• formation and dissolution of alliances
• onboarding and offboarding consumer chains

quorum: 40% of staked tokens must vote
pass threshold: 2/3rds yes
Veto: let's try to disable it, we don't need veto because the pass threshold is 2/3rds

Staking

• Minimum inflation = 10%

• Maximum inflation = 35%

• target_bonded_rate = 75%

• VALIDATORS: 300

• MINIMUM COMMISSION: 11.69420808%

• Eve has no maximum supply concept. She'll inflate over time, and that is fine. Track market cap, not unit price (duh)

Additional Configuration

Interchain accounts

We should attempt to block liquid staking chains that do not allow validator choice from connecting to Eve.

Stargeate Queries

If we feel that it is safe to do so, let's configure stargate queries as * to allow contract devleopers maximum configuratbility when using eve.

Block Time

Eve should attempt to make 2 second blocks. She won't always succeed, but the extra responsiveness will allow for a wide range of use cases that other chains cannot accomodate. It is perfectly reasonable to look into reducing block times to 1 second, but we should not spend a lot of time on that, and it may not be possible.

./scripts/start_local_node.sh

1. determine if Alliance will work on eve even if we're using ICS, Fee Abstraction, and Mesh Security
2. If alliance can work on eve, let's implement it
   github.com/terra-money/alliance

• terra-money/alliance#333

We've got a chat with TFL in on telegram, if we need integration support I can add Notional team members to it.

Also might be cool to do this as a contract where you burn your cw20 to mint the corresponding Token Factor token.

• Jake Hertnell idea

idea2:
a cw20-tokenfactory (same interface as cw20, but uses TF for balances) that can migrate an existing cw20

Connect Tfactory -> wasm messages (so a CW1 could create a denom)

Must have for CW contracts to mint & create denoms from a DAO or proxy

We should generally follow the approach taken by Celestia since there hasn't been a massive increase in airdrop farming spam of stuff on git.

I think that their code for this is open source, but even if it isn't I bet we can simply ask.

Personally I think that pull requests correcting spelling mistakes or other minor matters are in fact a public good, even if they're driven by desire for airdrops.

This should include:

• ibc-go contributors since Jan 1 2022
• SDK contributors since Jan 1 2022
• all wasmd contributors
• contributors to osmosis
• token factory contributors
• comet contributors
• iavl contributors
• Certain individuals by fiat

The error when run ibc transfer with interchaintest:

07-tendermint-0: light client module route not found [cosmos/ibc-go/[email protected]/modules/core/02-client/keeper/client.go:37] with gas used: '55786': unknown request"

Reference:

osmosis-labs/fee-abstraction@3e468b0

Eve needs some hot CW action if she's ever to get with her beloved Juno

when start chain, testing have issues related tokenfactory
service tokenfactory.v1beta1.Msg does not have cosmos.msg.v1.service proto annotation

Let's integrate ibc hooks, becasue skip will want that

Well, it is likely reasonable that the osmosis epoch module makes sense for this and they just made it importable but it isn't 46ified.

Propose we 46ify it here and let folks import right?

3 min block heartbeat

Sei Network config root.go commit timeout
& emoney for pulse

Setup e2e using https://github.com/cosmology-tech/starship

Eve's airdrop is a bit complex, because it will snapshot a number of different cosmos chains:

Weights aren't finalized. Percentages add up to more or less than 100%. Numbers aren't final. Various anti farming measures will be taken but zero pruning will be done. Eve is surely airdropping with the intent of achieving alignment.

• Composable - 13%
• Celestia - %
• Osmosis - 35%
• Quicksilver - 35%
• Bad Kids - 1 bk is 1/4th a cryptonium
• cryptonium - 4x a bk
• Sentinel - 13%
• Akash - 13%
• Cyber - 13%
• Stargaze - 13%
• Neutron - %
  • Neutron is extremely well managed by an extremely professional team
• Luna - %
• Lunc
• Cosmos hub - %
  • potentially this could go to governance participants, or be unlocked upon exit from the cosmos hub? Seems wrong to exclude so many long term participants

Snapshot process

• get accounts and their current balances
• prune all dust staking accounts:
  • remove all accounts staking tokens worth less than $20 to ensure that we filter out governance manipulation accounts
• determine the % of supply that each account has on the 6 included chains
• put these weights together and issue 1,000,000,000 eve

1. determine if Alliance will work on eve even if we're using ICS, Fee Abstraction, and Mesh Security
2. If alliance can work on eve, let's implement it

github.com/terra-money/alliance

Follow osmosis way of denoms & such

Mix best of osmosis & CW20 messages

Ban ueve / eve creation?

• Way to add --flags to init command? To specify metadata

• don’t allow /‘s in the subdenom

main branch

./test_node.sh
panic: unknown field "exemption_factor" in types.Params (from liquid staking module, why the issue now though?)

Issue

running node not work

The error when run ibc transfer with interchaintest maybe because missing light client module 07-tendermint-0 in app/app.go:

07-tendermint-0: light client module route not found [cosmos/ibc-go/[email protected]/modules/core/02-client/keeper/client.go:37] with gas used: '55786': unknown request"

Reference:

osmosis-labs/fee-abstraction@3e468b0

Should we wait for sdk47 for global fee and we can remove our global-fee module ?

Pebbledb broke CodeQL from PR #4

re-enable after fix: https://github.com/notional-labs/eve/actions/workflows/codeql.yml

For:

• most for contributors [includign CosmosSDK, gaia, writing code]
• select chains?
• What about gov participation?

NOTE: design airdrop per section, output to .sh file with add-genesis-account --append is used.

Requirements:

• state exports of chains
• PLEASE NO EVM CHAINS! (Only 118)

I can do this, just need to know:

• token->eve convert rate
• Any other airdrop considerations / logic wanted

How to airdrop to contributors:

• github crawl commits from main repos
• get their github username / uuid
• webapp sign in, get their name
• connect keplr
• deposit eve on a per commit basis / pr / # of lines of code?

Contributor Airdrop Core/Chains:
@cosmossdk
@Tendermint_Core
@cosmosibc
tmdb
cosmos-db
@CosmWasm
@CockroachDB

@osmosiszone
@cosmoshub
@akashnet_
@StargazeZone
@JunoNetwork
@DA0_DA0

For now, we should use this issue for things that block eve from launching.

As we get closer, this will be for coordination.

• #141
• #180
• [ ]

Right before stuff got wierd some months ago, Notional was to assist Osmosis in bringing token factory up to date with:

• sdk v0.45.x
• v0.46.x
• v0.47.x
• v0.50.x

I think that Matt from Osmosis has finished up with 45, but i'm not sure -- the repository is here:

https://github.com/osmosis-labs/tokenfactory

Let's make sure that eve supports token factory, because cw20 is a pain, and let's also make sure that we've contributed a helpful public good over at Osmosis -- let's make sure all of the branches named above work correctly.