Add proposal for v6.1.1 upgrade

[Thaleszh]

Description

Add proposal for v6.1.1 upgrade

Type of change

• Documentation (updates documentation on the project)

[coderabbitai]

Walkthrough

This PR adds a new JSON file containing a Cosmos upgrade proposal for KiiChain version v6.1.1. The proposal includes a software upgrade message with specified authority and upgrade plan parameters (target height 1663538), IPFS metadata reference, deposit amount in akii tokens, title, summary with changelog link, and expedited flag set to true.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete; it omits the 'How Has This Been Tested?' section which is required by the template.	Add the 'How Has This Been Tested?' section with details on how the proposal was validated and tested.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding a proposal file for the v6.1.1 upgrade.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@kiichain/proposals/proposal_2.json`:
- Line 15: The proposal's metadata field currently uses a placeholder
"ipfs://CID"; replace this with the actual IPFS content identifier for the
proposal metadata (e.g., "ipfs://Qm..." or "ipfs://bafy...") so validators can
fetch and verify off-chain data—update the "metadata" value in proposal_2.json
to the real CID string corresponding to the uploaded metadata.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Metadata contains a placeholder value.

The "ipfs://CID" value appears to be a placeholder that should be replaced with an actual IPFS Content Identifier. Real IPFS CIDs typically look like ipfs://QmXoypiz... or ipfs://bafybei.... Validators and users won't be able to verify the off-chain proposal metadata with this placeholder.

🤖 Prompt for AI Agents

In `@kiichain/proposals/proposal_2.json` at line 15, The proposal's metadata field
currently uses a placeholder "ipfs://CID"; replace this with the actual IPFS
content identifier for the proposal metadata (e.g., "ipfs://Qm..." or
"ipfs://bafy...") so validators can fetch and verify off-chain data—update the
"metadata" value in proposal_2.json to the real CID string corresponding to the
uploaded metadata.