Executed

Transitioning $INST to $FLUID


ID 65

ID 65

Proposed on: Dec 12th, 2024

Proposed on: Dec 12th, 2024

Votes

Actions

Type

Address

Details

Custom

0x2386...1F4c

executePayload(..)

Custom

Account

0x2386...1F4c

Method

executePayload(..)

Proposal

Summary

This proposal aims to transition $INST to $FLUID as part of a rebranding to better align with the protocol’s vision.

Code Changes

Migration of $INST -> $FLUID

  • Execute changeName('Fluid') on the $INST contract: 0x6f40d4a6237c257fff2db00fa0510deeecd303eb
  • Execute changeSymbol('FLUID') on the $INST contract: 0x6f40d4a6237c257fff2db00fa0510deeecd303eb

Description

This proposal facilitates the rebranding of $INST to $FLUID by updating the token’s name and symbol on the existing contract. The changes will be implemented as follows:

  • Change Name: Update the token name to Fluid by calling the changeName function on the $INST contract at 0x6f40d4a6237c257fff2db00fa0510deeecd303eb
  • Change Symbol: Update the token symbol to FLUID by calling the changeSymbol function on the $INST contract at 0x6f40d4a6237c257fff2db00fa0510deeecd303eb

These updates will ensure that the token reflects the new branding effectively.

Conclusion

The transition from $INST to $FLUID represents a significant step in aligning the token with the protocol’s vision and market objectives. By updating the token’s name and symbol, this proposal ensures a seamless rebranding process, enhancing the protocol’s identity and positioning for future growth.

Forum Link: Rebranding and Growth Plan for Fluid Protocol

Votes
Status