CryptoCrew Validators Governance Update October 2025
6. November 2025
Dear Community,
We’re pleased to share an update on our governance activities for October 2025. This month, we screened over 35 networks and participated in voting on 67 proposals across 15 different chains, consistently advocating for the best interests of our delegators. Below is a chart highlighting the top 10 most active networks and a breakdown of our votes:
Top 10 most active chains by governance and CryptoCrew vote breakdown
In total, CryptoCrew supported eight mainnet upgrades this month across Osmosis, Persistence, Akash, MANTRA, Nolus, and Chihuahua. These upgrades improved reliability, cross-chain interoperability, and validator operations while introducing several key protocol and SDK advancements.
CryptoCrew-supported upgrades (October 2025)
Osmosis Proposal #990 – v31.0.0: Deployed SDK v0.50.10, CometBFT v0.38.11, and IBC-Go v8.6.0, while adding automated taker-fee burning and non-OSMO buy-back mechanisms to strengthen economic efficiency and protocol self-sustainability.
Persistence Proposal #147 – PersistenceCore v14.0.0: Introduced Cosmos SDK v0.50.14-lsm-disabled and established groundwork for future Gaia × liquid integrations, improving system stability and interoperability.
Persistence Proposal #149 – PersistenceCore v15.0.0: Aligned with Cosmos SDK v0.50.14 and CometBFT v0.38.19, removed the custom SDK fork, and updated key dependencies to enhance reliability and compatibility across the Persistence stack.
Akash Proposal #308 – Akash v1.0.0: Rolled out SDK v0.53, introduced Expedited Governance, and implemented major protocol enhancements including AEP-75 (Multi-Depositor Escrow Account) and AEP-39 (Lease Termination Reason).
Chihuahua Proposal #96 – Chihuahua v9.0.6: Delivered a mainnet upgrade at block #20523000 that improved network performance and maintained compatibility with recent Cosmos SDK and CometBFT versions.
MANTRA Chain Proposal #24 – MANTRA Chain v6.0.0: Upgraded the Cosmos SDK to v0.53.4 and EVM to v0.5.0, enabling static precompiles and advancing MANTRA’s hybrid Cosmos-EVM infrastructure.
MANTRA Chain Proposal #25 – MANTRA Chain v6.1.0: Addressed IBC transfer reversion defects and upgraded core dependencies to Cosmos SDK v0.53.4-mantra and go-ethereum v1.16.2-cosmos-1, ensuring smoother interoperability and improved network resilience.
Nolus Proposal #320 – Nolus Pirin v0.8.2: Integrated CosmWasm v3.0 with IBC v2 support and introduced greater flexibility in the Tax Module, refining parameter management and boosting chain stability.
Beyond upgrades, several governance proposals this month touched on bridge security, application whitelisting, validator incentives, and voting process design:
We voted NO on dYdX Proposal #302, opposing the re-enablement of the wethDYDX bridge due to legal exposure and security risks.
On Osmosis, we voted NO on Proposal #985, declining to whitelist The Honorais deployer because of unclear audit status, unclear project transparency, and our belief that Osmosis should maintain its core role as a DEX and avoid unnecessary complexity.
For the Cosmos Hub’s Stride opt-in PSS (Proposal #1014), we abstained, maintaining neutrality on validator-income changes while acknowledging its impact on network incentives.
On MANTRA, we voted YES on Proposal #23, supporting the governance voting period change from 48 hours to 7 days (and expedited proposals to 24 hours), a structural improvement allowing more time for due diligence and informed participation.
You can find the full list of proposals we voted on this month by scrolling down below.
Your delegations allow us to maintain the quality of this service and represent our collective interests in governance. Remember, you can always override our vote with your own preferences on any active proposal. We appreciate your continued trust and support.
Kind regards,
The CryptoCrew Team ✅
| Proposal: | OSMOSIS #983 |
| Vote: | abstain |
| Title: | Remove Out-of-Range ETH Pair Liquidity Positions |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. This decision, made in April 2023, is intended to ensure that we accurately represent and uphold the interests of our community. We reserve the right to use our NO or NO_WITH_VETO option in specific cases. These cases include, but are not limited to, situations where the proposal is considered spam (i.e., irrelevant to the respective chain/community), disproportionately infringes on minority interests, or violates or encourages violation of the rules of engagement as currently established by the respective chain/community. By maintaining this stance, we aim to protect the integrity of the community and its governance processes, promote transparency, and safeguard against actions that may compromise the well-being of our members or the broader ecosystem. However, we recognize that our delegators may have differing opinions on these matters. To ensure that their voices are heard and respected, our delegators have the option to override our decision by participating in the voting process themselves. This enables a more inclusive and democratic approach to community decision-making, empowering our delegators to actively shape the direction and values of the community in alignment with their own perspectives and priorities. |
| Proposal: | OSMOSIS #984 |
| Vote: | abstain |
| Title: | Allocate additional USDC to OSMO buyback and liquidity strategy |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. * |
| Proposal: | INJECTIVE #564 |
| Vote: | yes |
| Title: | Update OPENAI/USDT PERP Hourly Funding Rate Cap on Injective Exchange dApps |
| Rationale: | CryptoCrew considers the adjustment of the OPENAI/USDT PERP funding cap a step toward deeper liquidity and more consistent pricing on the Injective Exchange dApps |
| Proposal: | DYDX PROTOCOL #291 |
| Vote: | yes |
| Title: | Wind down GOONER-USD market |
| Rationale: | CryptoCrew favors winding down GOONER-USD to concentrate liquidity on active markets and reduce operational overhead. |
| Proposal: | BAND PROTOCOL #17 |
| Vote: | abstain |
| Title: | BCIP-17: Strengthening Validator Operations for Band v3 |
| Rationale: | CryptoCrew would generally support the Band v3 upgrade for its performance and coordination benefits, but must abstain due to the validator set reduction from 100 to 53, which directly impacts validator rewards and income, leaving the final decision to the community. |
| Proposal: | BABYLON #15 |
| Vote: | abstain |
| Title: | Signalling Proposal: Inflation reduction and the introduction of co-staking |
| Rationale: | CryptoCrew abstains from voting on proposals related to incentive- or reward-structure adjustments as a fundamental policy since April 2023, allowing the community to dictate the outcome.* |
| Proposal: | AGORIC #111 |
| Vote: | yes |
| Title: | Ymax Portfolio Contract Beta Deployment |
| Rationale: | CryptoCrew recognizes the Ymax beta deployment, enabling cross-chain portfolio creation, allocation, and rebalancing through Agoric’s orchestration layer. |
| Proposal: | DYDX PROTOCOL #292 |
| Vote: | yes |
| Title: | Set NextBlockDelay to 0.2 seconds |
| Rationale: | CryptoCrew aligns with the 0.2-second NextBlockDelay update, following our prior support of Proposal #280 that reduced the interval to 0.3 seconds, further fine-tuning throughput and enhancing user experience on dYdX. |
| Proposal: | DYDX PROTOCOL #293 |
| Vote: | yes |
| Title: | Upgrade 2Z-USD and ZEC-USD markets from ISOLATED to CROSS and/or change liquidity tiers |
| Rationale: | CryptoCrew supports Proposal #293, upgrading the 2Z-USD and ZEC-USD perpetuals from isolated to cross margin, enhancing capital efficiency and trading flexibility. |
| Proposal: | INJECTIVE #565 |
| Vote: | abstain |
| Title: | OLP Reward Disbursement – Epoch 50 |
| Rationale: | CryptoCrew abstains from voting on proposals related to incentive- or reward-structure adjustments as a fundamental policy since April 2023, allowing the community to dictate the outcome. * |
| Proposal: | OSMOSIS #985 |
| Vote: | no |
| Title: | Whitelist The Honorais Deployment Address to Upload new smart contracts |
| Rationale: | CryptoCrew appreciates the detailed introduction of The Honorais project but votes no regarding the whitelisting, given the lack of published audit results and code transparency, our belief that Osmosis should maintain its core role as a DEX and avoid unnecessary complexity, also mentioning uncertainty regarding benefits of this deployment. |
| Proposal: | OSMOSIS #986 |
| Vote: | abstain |
| Title: | Monthly OSMO Taker Fee Burn: September 2025 |
| Rationale: | CryptoCrew abstains from voting on proposals related to incentive- or reward-structure adjustments as a fundamental policy since April 2023, allowing the community to dictate the outcome. * |
| Proposal: | PERSISTENCE #147 |
| Vote: | yes |
| Title: | PersistenceCore v14.0.0 |
| Rationale: | CryptoCrew supports the PersistenceCore mainnet upgrade to v14.0.0 at block #24153500, introducing Cosmos SDK v0.50.14-lsm-disabled and preparing groundwork for Gaia x/liquid integration, improving system stability and compatibility for future liquid staking development. |
| Proposal: | DYDX PROTOCOL #566 |
| Vote: | yes |
| Title: | Whitelisting Strategic Partner Addresses for Controlled Rollout of EVM on Mainnet |
| Rationale: | CryptoCrew votes in favor of Proposal #566, approving the whitelist of 40 strategic partner addresses for Injective’s controlled EVM rollout, enabling key ecosystem applications to deploy and launch smart contracts on mainnet in a secure and coordinated manner. |
| Proposal: | PERSISTENCE #148 |
| Vote: | yes |
| Title: | Persistence DEX Vault Contract Upgrade to v1.2.2 - Fix Query Pools Function for Defunct Pool Handling |
| Rationale: | CryptoCrew acknowledges the Persistence DEX Vault contract upgrade to v1.2.2 at block #24153500, resolving query failures from defunct pools, improving pagination, adding seamless migration support, and reinforcing security through updated code_upload_access parameters, while maintaining full backward compatibility. |
| Proposal: | COSMOS HUB #1012 |
| Vote: | no |
| Title: | Migrate Stride to opt-in PSS |
| Rationale: | CryptoCrew votes NO on Proposal #1012, as the submission includes an invalid Stride address (stride1fduug6m38gyuqt3wcgc2kcgr9nnte0n7ssn27e), causing the transaction to fail on-chain. |
| Proposal: | COSMOS HUB #1013 |
| Vote: | no |
| Title: | Migrate Stride to opt-in PSS |
| Rationale: | CryptoCrew also votes NO on Proposal #1013, as it repeats the same invalid Stride owner address error as #1012, making execution on the Hub technically impossible. |
| Proposal: | COSMOS HUB #1014 |
| Vote: | abstain |
| Title: | [Correct Owner Address] Migrate Stride to opt-in PSS |
| Rationale: | CryptoCrew abstains from Proposal #1014, which modifies Stride’s validator reward distribution by transitioning to an opt-in model of seven equal-weight validators directly compensated via fees. As this proposal affects validator income and reward structures, we defer the decision to the community in accordance with our long-standing governance policy. Since April 2023, CryptoCrew has abstained from voting on proposals tied to economic redistribution or validator remuneration, empowering delegators and the broader community to determine such outcomes. We reserve the right to cast a NO or NO_WITH_VETO vote only in cases of spam, malicious intent, or violations of community standards. This approach ensures neutrality, transparency, and respect for diverse perspectives among our delegators. |
| Proposal: | DYDX PROTOCOL #294 |
| Vote: | abstain |
| Title: | Surge Season 6 Incentive Distribution Proposal |
| Rationale: | CryptoCrew abstains from voting on proposals related to incentive- or reward-structure adjustments as a fundamental policy since April 2023, allowing the community to dictate the outcome. * |
| Proposal: | INJECTIVE #567 |
| Vote: | yes |
| Title: | Whitelisting Strategic Partner Addresses for Controlled Rollout of EVM on Mainnet |
| Rationale: | CryptoCrew votes in favor of whitelisting the 44 designated strategic partner addresses for Injective’s continued controlled EVM rollout, supporting a secure and coordinated expansion of the network. |
| Proposal: | DYDX PROTOCOL #295 |
| Vote: | abstain |
| Title: | CoinRoutes Order Router Rev Share Proposal |
| Rationale: | CryptoCrew abstains from voting on proposals related to incentive- or reward-structure adjustments as a fundamental policy since April 2023, allowing the community to dictate the outcome. * |
| Proposal: | AGORIC #112 |
| Vote: | abstain |
| Title: | [Inter Protocol Sunset] Liquidate the reserve module account |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. This decision, made in April 2023, is intended to ensure that we accurately represent and uphold the interests of our community. * |
| Proposal: | KAVA #206 |
| Vote: | abstain |
| Title: | Kava Rise Payouts June 2025 |
| Rationale: | CryptoCrew abstains from voting on proposals related to incentive- or reward-structure adjustments as a fundamental policy since April 2023, allowing the community to dictate the outcome. * |
| Proposal: | BITSONG #46 |
| Vote: | no |
| Title: | Upgrade v0.24.0 - Jimi |
| Rationale: | CryptoCrew votes no on Proposal #46 pending further clarification on its origin |
| Proposal: | AKASH NETWORK #305 |
| Vote: | abstain |
| Title: | Zealy 2025 Program Q4 |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. This decision, made in April 2023, is intended to ensure that we accurately represent and uphold the interests of our community. We reserve the right to use our NO or NO_WITH_VETO option in specific cases. These cases include, but are not limited to, situations where the proposal is considered spam (i.e., irrelevant to the respective chain/community), disproportionately infringes on minority interests, or violates or encourages violation of the rules of engagement as currently established by the respective chain/community. By maintaining this stance, we aim to protect the integrity of the community and its governance processes, promote transparency, and safeguard against actions that may compromise the well-being of our members or the broader ecosystem. However, we recognize that our delegators may have differing opinions on these matters. To ensure that their voices are heard and respected, our delegators have the option to override our decision by participating in the voting process themselves. This enables a more inclusive and democratic approach to community decision-making, empowering our delegators to actively shape the direction and values of the community in alignment with their own perspectives and priorities. |
| Proposal: | MANTRA ZONE #22 |
| Vote: | abstain |
| Title: | Increase Active set for Decentralization of Network (Polar Compass) |
| Rationale: | CryptoCrew abstains from Proposal #22 on increasing the active validator set, maintaining neutrality to avoid potential conflicts of interest tied to validator rewards and leaving the governance decision entirely to the community. |
| Proposal: | AKASH NETWORK #306 |
| Vote: | abstain |
| Title: | Decentralized Cloud Foundation Operational Expenses |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. This decision, made in April 2023, is intended to ensure that we accurately represent and uphold the interests of our community. * |
| Proposal: | INJECTIVE #568 |
| Vote: | yes |
| Title: | Whitelisting Strategic Partner Addresses for Controlled Rollout of EVM on Mainnet IV |
| Rationale: | CryptoCrew votes in favor of whitelisting the 44 designated strategic partner addresses for Injective’s controlled EVM rollout, enabling vetted builders to deploy smart contracts early while preserving governance oversight. |
| Proposal: | NOLUS #318 |
| Vote: | yes |
| Title: | Adjust MAG Threshold |
| Rationale: | CryptoCrew views the tightening of Market Anomaly Guards (MAG) as a refinement that enhances execution quality and strengthens user protection against high-slippage conditions. |
| Proposal: | NOLUS #319 |
| Vote: | yes |
| Title: | Update Oracle Swap Tree (Osmosis Noble USDC) |
| Rationale: | CryptoCrew recognizes the Oracle swap tree adjustment for stATOM long positions, redirecting routing to the deeper Supercharged stATOM/ATOM (id:1136) pool for stronger liquidity and reduced slippage. |
| Proposal: | DYDX PROTOCOL #296 |
| Vote: | yes |
| Title: | dYdX Chain Software Upgrade v9.3 |
| Rationale: | CryptoCrew acknowledges the dYdX Chain upgrade to v9.3.0 at block #59835000, introducing the insurance fund transfer sequencing fix, restoring full liquidation logic for isolated markets, aligning upgrade handlers from v9.1 to v9.3, and ensuring stable CLOB performance with the corrected collateral flow. |
| Proposal: | DYDX PROTOCOL #297 |
| Vote: | abstain |
| Title: | Reduce the active validator set to 42 |
| Rationale: | CryptoCrew abstains from Proposal #297 on reducing the active validator set to 42, maintaining neutrality to avoid conflicts of interest tied to validator rewards and allowing the community to decide on the network’s optimal validator configuration. |
| Proposal: | INJECTIVE #569 |
| Vote: | yes |
| Title: | Update ANTHROPIC/USDT PERP Hourly Funding Rate Cap on Injective Exchange dApps |
| Rationale: | CryptoCrew regards the reduced funding rate cap for the ANTHROPIC/USDT PERP market — from 0.0625% to 0.0002275% — as a technical refinement supporting smoother funding dynamics and ensuring more stable trading across Injective Exchange dApps. |
| Proposal: | INJECTIVE #571 |
| Vote: | yes |
| Title: | Update Community Burn Auction Maximum Caps For Auctioned Assets |
| Rationale: | CryptoCrew votes yes to adjust the inj_basket_max_cap and inj_auction_max_cap parameters by 4× to align with the new 28-day community burn cadence, a straightforward recalibration that ensures consistent burn throughput without altering existing mechanics. |
| Proposal: | PERSISTENCE #149 |
| Vote: | yes |
| Title: | PersistenceCore v15.0.0 |
| Rationale: | CryptoCrew supports the PersistenceCore mainnet upgrade to v15.0.0 at block #24345500, aligning with Cosmos SDK v0.50.14 and CometBFT v0.38.19, removing the custom SDK fork, and updating key dependencies including persistence-sdk v5.1.0-rc1, pstake-native v5.1.0-rc0, and ledger-cosmos-go v0.16.0, streamlining upgrade handlers, simplifies LSM message logic, and improves compatibility with IBC-Go v10.1.1 and Wasmd v0.55.1 |
| Proposal: | AKASH NETWORK #307 |
| Vote: | abstain |
| Title: | REVISED: Digital Immortality Framework - Autonomous Agent Infrastructure on Akash Network |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. * |
| Proposal: | OSMOSIS #987 |
| Vote: | yes |
| Title: | Recover expired IBC client for channel-95 to Bostrom |
| Rationale: | CryptoCrew backs the IBC client recovery between Osmosis and Bostrom after successfully validating the client states: Message #1: subject=07-tendermint-1597 substitute=07-tendermint-3612 Reference RPC: https://rpc.cosmos.directory:443/bostrom host: 1BFBB2DC8F7B3762DBF30E88F060A7278FB76D0FAA93D1D61419F3649F87979F reference: 1BFBB2DC8F7B3762DBF30E88F060A7278FB76D0FAA93D1D61419F3649F87979F host: 5FD76DB3E32253F0B98544B206EB9FCE33CBE3F93869E9A920C4B5F764B2AB91 reference: 5FD76DB3E32253F0B98544B206EB9FCE33CBE3F93869E9A920C4B5F764B2AB91 ---------------------------------------- ✅ subject client valid ✅ substitute client valid |
| Proposal: | MANTRA ZONE #23 |
| Vote: | yes |
| Title: | Governance Voting Period Change: 7 days; Expedited: 24h |
| Rationale: | CryptoCrew welcomes the governance voting period parameter changes from 48 to 168 hours for regular and from 3 to 24 hours for expedited proposals, allowing validators and stakeholders more time to review and decide on proposals. |
| Proposal: | DYDX PROTOCOL #298 |
| Vote: | abstain |
| Title: | Update Affiliate Whitelist |
| Rationale: | CryptoCrew abstains from voting on proposals related to incentive- or reward-structure adjustments as a fundamental policy since April 2023, allowing the community to dictate the outcome. We reserve the right to employ our NO or NO_WITH_VETO stance under circumstances such as proposals deemed as spam, those infringing on minority rights, or those contravening established community rules. Our approach is designed to uphold community integrity and promote transparency while recognizing that our delegators might hold diverse views and may override our abstention through their direct participation in governance. This democratic approach empowers our delegators to actively shape the direction and values of the community in alignment with their own perspectives and priorities. |
| Proposal: | AKASH NETWORK #308 |
| Vote: | yes |
| Title: | v1.0.0 |
| Rationale: | CryptoCrew supports the Akash Network Mainnet 14 upgrade to v1.0.0 at block #23939793, rolling out akash-node v1.0.0 alongside provider-services v0.4.8, upgrading the Cosmos SDK to v0.53, and introducing Expedited Governance Proposals together with IAVL storage improvements and protocol enhancements such as AEP-75: Multi-Depositor Escrow Account and AEP-39: Lease Termination Reason. |
| Proposal: | COSMOS HUB #1015 |
| Vote: | yes |
| Title: | Recover Expired IBC Client to XPLA Chain |
| Rationale: | CryptoCrew backs the IBC client recovery between the Cosmos Hub and XPLA after successfully validating the client states: Message #1: subject=07-tendermint-1113 substitute=07-tendermint-1438 Reference RPC: https://rpc.cosmos.directory:443/xpla host: CBBCA990EC57E765564F918CA40F94E8947E48FEE897ED25A4EDDB999544860F reference: CBBCA990EC57E765564F918CA40F94E8947E48FEE897ED25A4EDDB999544860F host: 112EF427DA188615885188F4B98D9566AFF7E2C37D93CF9D628E5031CA23E3AD reference: 112EF427DA188615885188F4B98D9566AFF7E2C37D93CF9D628E5031CA23E3AD ---------------------------------------- ✅ subject client valid ✅ substitute client valid |
| Proposal: | INJECTIVE #573 |
| Vote: | yes |
| Title: | Whitelisting Strategic Partner Addresses for Controlled Rollout of EVM on Mainnet VI |
| Rationale: | CryptoCrew supports proposal #573 to whitelist 44 strategic partners for Injective’s controlled EVM rollout, enabling early smart contract deployment under full governance oversight. |
| Proposal: | PERSISTENCE #150 |
| Vote: | yes |
| Title: | Recover expired ibc client on Injective |
| Rationale: | CryptoCrew backs the IBC client recovery between the XPRT and Injective after successfully validating the client states: Message #1: subject=07-tendermint-57 substitute=07-tendermint-182 Reference RPC: https://rpc.cosmos.directory:443/injective host: 4E725E37F266DBF65405D34898FF7A335524B00BEE967989B16BD6EE62B5D976 reference: 4E725E37F266DBF65405D34898FF7A335524B00BEE967989B16BD6EE62B5D976 host: B609CE37DEDB7F7770CC52BD81D9BCB6BE729719300364F1F54BD41EA10F8F0A reference: B609CE37DEDB7F7770CC52BD81D9BCB6BE729719300364F1F54BD41EA10F8F0A ---------------------------------------- ✅ subject client valid ✅ substitute client valid |
| Proposal: | CHIHUAHUA #96 |
| Vote: | yes |
| Title: | Upgrade v9.0.6 |
| Rationale: | CryptoCrew supports the Chihuahua mainnet upgrade to v9.0.6 at Woofblock #20523000 |
| Proposal: | MANTRA ZONE #24 |
| Vote: | yes |
| Title: | v6.0.0 MAINNET MANTRA Chain Upgrade |
| Rationale: | CryptoCrew welcomes the MANTRA Chain upgrade to v6.0.0 at block #9664888, upgrading the Cosmos SDK to v0.53.4, updating the upstream EVM to v0.5.0, and enabling static precompiles in the upgrade handler alongside general dependency and test improvements. |
| Proposal: | INJECTIVE #572 |
| Vote: | yes |
| Title: | Whitelisting Strategic Partner Addresses for Controlled Rollout of EVM on Mainnet V |
| Rationale: | CryptoCrew backs proposal #574 to whitelist 53 strategic partner addresses for Injective’s controlled EVM rollout and deployment under governance oversight. |
| Proposal: | INJECTIVE #575 |
| Vote: | yes |
| Title: | Whitelisting Strategic Partner Addresses for Controlled Rollout of EVM on Mainnet VIII |
| Rationale: | CryptoCrew also votes positive on proposal #575 to whitelist 54 strategic partner addresses for Injective’s controlled EVM rollout, allowing them to deploy smart contracts on mainnet under governance oversight. |
| Proposal: | INJECTIVE #576 |
| Vote: | yes |
| Title: | Whitelisting Strategic Partner Addresses for Controlled Rollout of EVM on Mainnet IV |
| Rationale: | CryptoCrew also backs the proposal to whitelist mentioned 59 strategic partner addresses for Injective’s controlled EVM rollout, allowing them to deploy smart contracts on mainnet under governance oversight. |
| Proposal: | INJECTIVE #577 |
| Vote: | yes |
| Title: | Whitelisting Strategic Partner Addresses for Controlled Rollout of EVM on Mainnet X |
| Rationale: | CryptoCrew supports proposal #577 to whitelist 65 strategic partner addresses for Injective’s controlled EVM rollout, enabling them to deploy smart contracts on mainnet under governance oversight. |
| Proposal: | NOLUS #320 |
| Vote: | yes |
| Title: | Pirin v0.8.2 |
| Rationale: | CryptoCrew welcomes the Nolus Pirin mainnet upgrade to v0.8.2 at block #17317500, upgrading the CosmWasm module to v3.0 with IBCv2 support, and introducing greater flexibility in the Tax Module by removing the previous 50% fee rate cap, also updating to stable versions of Cosmos SDK Core, API, and TX, bumps CometBFT and go-viper/mapstructure dependencies, and refines the upgrade handler and unit tests to ensure smoother governance-driven parameter management and improved chain stability. |
| Proposal: | OSMOSIS #988 |
| Vote: | yes |
| Title: | Update stEVMOS/EVMOS Scaling Factor Controller to Auto Update Contract |
| Rationale: | CryptoCrew votes yes regarding the stToken Scaling Factor Auto-update Contract Oracle address upgrade, effectively changing the responsibility of the scaling factor updates of pools #922, #810 and #817 by the Stride Association to the automated and fully trustless manner. |
| Proposal: | OSMOSIS #989 |
| Vote: | abstain |
| Title: | Recover expired IBC client for channel-95 to Bostrom |
| Rationale: | CryptoCrew abstains on the Osmosis <-> Bostrom IBC client revival proposal until the clients have been successfully verified by our team |
| Proposal: | DYDX PROTOCOL #299 |
| Vote: | abstain |
| Title: | Seed DODGERSWIN-USD Market Insurance Fund |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. This decision, made in April 2023, is intended to ensure that we accurately represent and uphold the interests of our community.* |
| Proposal: | PERSISTENCE #151 |
| Vote: | abstain |
| Title: | Incentivization of Persistence DEX pools with stkXPRT rewards for November 2025 |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. * |
| Proposal: | INJECTIVE #578 |
| Vote: | yes |
| Title: | Update SPACEX/USDT PERP Hourly Funding Rate Cap on Injective Exchange dApps |
| Rationale: | CryptoCrew votes yes on proposal #578, supporting the reduction of the SPACEX/USDT PERP hourly funding rate cap from 0.0625% to 0.0002275% to enhance market stability. |
| Proposal: | OSMOSIS #990 |
| Vote: | yes |
| Title: | Osmosis v31 Software Upgrade |
| Rationale: | CryptoCrew supports the Osmosis mainnet upgrade to v31.0.0 at block #47626000, introducing Cosmos SDK v0.50.10, CometBFT v0.38.11, and IBC-Go v8.6.0, alongside automated taker-fee burning, non-OSMO buy-back and burn routing |
| Proposal: | DYDX PROTOCOL #301 |
| Vote: | abstain |
| Title: | Compensate impacted Oct 10 incident users from Insurance Fund |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. * |
| Proposal: | OSMOSIS #989 |
| Vote: | yes |
| Title: | Recover expired IBC client for channel-95 to Bostrom |
| Rationale: | CryptoCrew backs on the Osmosis <-> Bostrom IBC client revival proposal after successfully validating the client states: Message #1: subject=07-tendermint-1597 substitute=07-tendermint-3614 Reference RPC: https://rpc.cosmos.directory:443/bostrom host: 1BFBB2DC8F7B3762DBF30E88F060A7278FB76D0FAA93D1D61419F3649F87979F reference: 1BFBB2DC8F7B3762DBF30E88F060A7278FB76D0FAA93D1D61419F3649F87979F host: 27CB7485150E7F7494466B1828855374C6D5B194AAFA66185342CB83E8998A1F reference: 27CB7485150E7F7494466B1828855374C6D5B194AAFA66185342CB83E8998A1F ---------------------------------------- ✅ subject client valid ✅ substitute client valid |
| Proposal: | PERSISTENCE #152 |
| Vote: | no |
| Title: | Recover expired ibc client on Injective |
| Rationale: | CryptoCrew votes against proposal #152 to recover the expired IBC client on Injective, as the replacement client introduces a mismatched 40 s clock drift instead of the original 45 s |
| Proposal: | PERSISTENCE #153 |
| Vote: | abstain |
| Title: | Recover expired ibc client on Injective |
| Rationale: | CryptoCrew abstains on the Persistence <-> Injective IBC client revival proposal until the clients have been successfully verified by our team |
| Proposal: | MANTRA ZONE #25 |
| Vote: | yes |
| Title: | v6.1.0 MAINNET MANTRA Chain Upgrade |
| Rationale: | CryptoCrew supports the MANTRA Chain mainnet upgrade to v6.1.0 at block #9911888, addressing IBC transfer reversion defects and upgrading core dependencies to Cosmos SDK v0.53.4-mantra, EVM, go-ethereum v1.16.2-cosmos-1, and wasmd, while introducing a new v6.1.0 upgrade handler |
| Proposal: | DYDX PROTOCOL #300 |
| Vote: | abstain |
| Title: | dYdX Trading Leagues Pilot Program |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. * |
| Proposal: | INJECTIVE #579 |
| Vote: | yes |
| Title: | Settle Deprecated Perpetuals Across Injective DEXs |
| Rationale: | CryptoCrew supports proposal #579 to settle the deprecated BTC/wUSDM PERP market using verified oracle pricing |
| Proposal: | DYDX PROTOCOL #302 |
| Vote: | no |
| Title: | Re-enable Support for the wethDYDX Smart Contract (the Bridge) on the dYdX Chain side for 12 months |
| Rationale: | CryptoCrew votes against the proposal to reopen the ethDYDX bridge due to unresolved legal exposure, potential compensation claims from ethDYDX holders, and unmitigated bridge-farming risks that could enable market exploitation and set undesirable precedents. |
| Proposal: | STARGAZE #329 |
| Vote: | abstain |
| Title: | Recover IBC Expired Client from AtomeOne |
| Rationale: | CryptoCrew abstains on the Stargaze <-> AtomOne IBC client revival proposal until the clients have been successfully verified by our team |
| Proposal: | BABYLON #16 |
| Vote: | yes |
| Title: | Update x/tokenfactory parameters to remove denom_creation_fee |
| Rationale: | CryptoCrew backs the Babylon proposal introducing denom_creation_gas_consume in place of denom_creation_fee, simplifying the developer experience, removing fee-handling logic, and preserving anti-spam protection. |
| Proposal: | AKASH NETWORK #309 |
| Vote: | abstain |
| Title: | Updated Zealy Q4 Proposal |
| Rationale: | CryptoCrew has decided to abstain from participating in any community pool spend proposals as a matter of principle. This decision, made in April 2023, is intended to ensure that we accurately represent and uphold the interests of our community. * |
| Proposal: | MANTRA ZONE #26 |
| Vote: | abstain |
| Title: | Redenominating $OM to $MANTRA |
| Rationale: | CryptoCrew abstains from proposal #26 concerning the $OM to $MANTRA redenomination and 1:4 token split, as it directly impacts financial structures and could pose a potential conflict of interest for validators; in accordance with our policy since April 2023, we leave the decision to the community to determine the outcome. |
| * Rationale condensed for readability; refer to the full version above for details. |
