• © Goverland Inc. 2026
  • v1.0.5
  • Privacy Policy
  • Terms of Use
MarginswapMarginswapby0x6e0e75B64010da83bA46A18e4cFD7BeCC23401Ba0x6e0e…01Ba

Growing the community through scalable and transparent communication

Voting ended over 4 years agoSucceeded

Current status

The platform's bottleneck continues to be a lack of liquidity, user, and volume. Without liquidity, there can be no users, and without users, there's no volume.

For this to change, we need to be able not only to attract people to the telegram group but to maintain and nurture them so they use app.

I've studied MFI's telegram chat since March 20, and there are several recurrent subjects:

Word Number of messages
Price 785
Marketing 674
Team 596
Presale 345
Market cap 105
Partners and Partnerships 92
Investors 92

Perhaps unsurprisingly, marketing is the second most significant concern for the community, right after price.

These numbers align with the controversial (50-50 vote) proposal made on October 18. This proposal suggested that 50% of the fees should be used for buybacks (for price) and 20% of the MFI to be invested in marketing.

Lack of communication

MFI has been unable to attract enough people to join and grow the community. This is primarily due to the lack of constant, proactive efforts in communication and community management.

Recently, we've seen people leaving the telegram group after asking for basic information and either not getting any reply or not being satisfied with the clarity of the answer, even calling the project a scam. This has happened with team-related details, but also with price and marketing.

One could propose to hire a community manager that will politely return to these people with straight answers. Not only would this person have to answer the most tedious and repeated questions, but they would also regularly update the community about what is proven the community cares about: price, marketing, and team.

Scalable communication

The problem with hiring a community manager is that not only it's a fixed cost, but they also can only be available during a humanly possible schedule.

For this reason, I propose the development and deployment of a community bot.

This bot should give generic but satisfactory replies to the most common subjects. These would be the available commands:

  • /price - returns MFI price based on the different exchanges;
  • /team - provide team information;
  • /links - medium, reddit, twitter, discord, telegram, github links;
  • /marketcap - returns current MFI marketcap;
  • /supply - returns the circulating and max supply;

Additionally, we might create aliases like /mkt for /marketcap, /circulating to /supply, and so on.

The team will develop the bot with public information; however, to improve the messages, the original core team should create a document including:

  • Team - Name, relevant social profiles, and short bio (1 or 2 sentences);
  • Partnerships - Relevant names, dates, URLs, and roles;
  • Investors - List of presale investors, how much they invested and for how much; and share that document with the community.

Deployment

The development team will deploy the bot in a test group, open to everyone.

After being tested for a couple of days, the admins of the groups "Marginswap Protocol" and "MarginSwappers" should add the bots to the groups, giving it the necessary privileges to function perfectly.

The code will run inside a docker container, ensuring portability and easy, reproducible deployment.

Fees

Development

I have a development team ready for the development and deployment of this bot.

The work is estimated to take one/two weeks to complete, from gathering project information and APIs, formalizing the work and deployment.

The bot would cost 4191.63 USDC, to be transfered to 0xd1579377f33a830Cb226b7a9dB6ab85285565acd.

The USDC should come from the collected trading fees as a part of a marketing effort.

Hosting

The development team will share the code publicly on Github after payment. They will also host the bot for the first two months, giving plenty time for the core team to deploy it on MarginSwap's infrastructure.

If required, the community might vote to extend this period through another proposal.

Off-Chain Vote

For
155.28K 85.6%
Against
26.14K 14.4%
Download mobile app to vote

Timeline

Oct 22, 2021Proposal created
Oct 22, 2021Proposal vote started
Oct 24, 2021Proposal vote ended
Oct 26, 2023Proposal updated