Enable EVM Mapping for $OYCI Token
Injective proposal #700: This proposal creates an ERC20 token pair mapping for the $OYCI token (factory/inj1jdt04erw6jdmh6c939u87kldf3mvvmkedsjp3w/OYCI), ena...
Yes
35%
No
0%
Abstain
65%
Veto
0%
Original Proposal Text
This proposal creates an ERC20 token pair mapping for the $OYCI token (factory/inj1jdt04erw6jdmh6c939u87kldf3mvvmkedsjp3w/OYCI), enabling seamless interoperability between the Cosmos bank module and the EVM environment. $OYCI (Oyster Cage Initiative) is a real-world asset token on Injective backed by working oyster aquaculture operations, currently two vessels under operation on the James River. Project details are published at https://oyci.info. The token has a fixed supply of 1,000,000,000 OYCI (6 decimals) with the token factory admin set to the burn address (inj1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqe2hm49), ensuring no additional tokens can ever be minted and providing immutable supply guarantees. Bank metadata is already set on-chain (name "Oyster Cage Initiative", symbol OYCI, 6 decimals), so the auto-deployed MTS-compliant ERC20 will inherit the correct values. Because the admin has been permanently renounced, no account is able to submit MsgCreateTokenPair for this denom directly, and governance is the only available path to enable EVM interoperability. This mirrors the precedent set by proposal 594 ($DRUGS), which mapped a token whose minter authority was likewise set to the burn address. OYCI trades against INJ on Choice Exchange. This mapping will allow $OYCI holders to utilize the token across both native Injective and EVM-compatible applications, and broadens access to an RWA asset within the Injective EVM ecosystem.