tbruyelle

forge_addr.go — vanity cosmos/gno address finder

go run forge_addr.go [flags]

flag	default	meaning
-prefix	th0mas	wanted chars right after the 1 separator
-suffix	(none)	wanted chars at the very end of the address

tbruyelle

Here's the full lifecycle of a coordinated upgrade on the Cosmos Hub. There are actually two distinct eras — the old hard-fork style (cosmoshub-1→4) and the modern in-place style (cosmoshub-4 onward). Both are "coordinated upgrades" but work very differently.

---

Era 1: Hard Fork with Chain ID Increment (cosmoshub-1 → 2 → 3 → 4)

Used when the SDK lacked an in-place upgrade module. The chain literally stops, exports state, and restarts as a new chain.

Step 1 — Social Coordination

tbruyelle

VAAS Rewrite Plan

Rewrite x/ccv/provider and x/ccv/consumer in a new vaas folder as a new Go module with package path github.com/allinbits/vaas.

---

Feature Decisions Summary

Provider Module

tbruyelle

atomoned tx gov submit-proposal ./v3_upgrade_proposal.json --from ACCOUNT (... other flags like fees, gas etc...)

tbruyelle

{
  "deposit": "512000000uatone",
  "messages": [
    {
      "@type": "/atomone.gov.v1.MsgProposeConstitutionAmendment",
      "amendment": "--- src\n+++ dst\n@@ -38,18 +38,18 @@ universe of the Cosmos.\n ### Section 1: Fundamental Principles\n \n This Constitution of the AtomOne Hub, hereinafter **“Constitution”**, hereby\n-establishes the foundations of the governance model, economical model, and\n+establishes the foundations of the governance model, economic model, and\n operating system of the AtomOne Hub.\n \n All subsequent governance proposals shall align with the provisions of this\n Constitution, and proponents of each proposal, along with all active governance\n voters, are required to ensure consistency between such proposals and this\n-Constitution, and cannot violate any explicit restriction. \n+Constitution, and cannot violate any explicit restriction.\n \n Amendments are permitted to innovate and adapt this Constitution, but they must\n still respect and adhere to the fundamental principles up

tbruyelle

atomoned tx gov submit-proposal ./prop.json --from ACCOUNT (... other flags like fees, gas etc...)

tbruyelle

{
 "messages": [
  {
   "@type": "/atomone.photon.v1.MsgUpdateParams",
   "authority": "atone10d07y265gmmuvt4z0w9aw880jnsr700j5z0zqt",
   "params": {
    "mint_disabled": false,
    "tx_fee_exceptions": [
      "/atomone.photon.v1.MsgMintPhoton"
    ]

tbruyelle

{
  "deposit": "512000000uatone",
  "metadata": "https://common.xyz/atomone/discussion/27055-signaling-proposal-to-make-proposal-deposits-dynamic",
  "summary": "This signaling proposal aims to gather community feedback on updating the `x/gov` module to implement a dynamic proposal deposit mechanism. This feature would replace the current static `MinDeposit` and `MinInitialDeposit` values with an adaptive system that automatically adjusts deposits based on governance activity. If approved, this feature will be included in a future AtomOne software upgrade.\n\n# Motivation\n\n### Addressing Governance Spam\n\nMany Cosmos-based chains suffer from governance spam, where users submit low-cost proposals containing misleading information or scams. While frontend filtering and initial deposit requirements exist, dynamically adjusting `MinInitialDeposit` in response to governance activity can provide a more robust solution.\n\n### Preventing Proposal Overload\n\nAn excessive number of active governance proposals can 

tbruyelle

$ATONE distribution (ratio: x0.170, nonVotersMultiplier: 0.975, icfSlash: 12,590,970 $ATOM)

	TOTAL	DID NOT VOTE	YES	NO	NOWITHVETO	ABSTAIN	NOT STAKED
Distributed	58,204,801	6,287,512	6,374,676	26,675,549	5,988,892	3,414,384	9,463,788
Percentage over total		11%	11%	46%	10%	6%	16%

tbruyelle

[sendemail]
	smtpserver = smtp.gmail.com
	smtpuser = xxxx
	smtpencryption = tls
	smtpserverport = 587
	smtpPass = xxxx
[user]
	email = thomas.bruyelle@tendermint.com
	name = Thomas Bruyelle
[alias]