AVM Email & Algo.fun - Proposal # 3464401706

# Algo.fun & AVM Email Proposal

## What is AVM Email?

  • AVM Email is a fully decentralized, on-chain, encrypted communication system — users purchase email servers eg; @algolinks.avm @asastats.avm @ethereum.avm, etc. and receive commissions on email names created under those servers, or trigger buyback & burn events for any token of their choice (mutable state). Server owners can create staking pools through their servers to incentive users to purchase email names under their server, and of course any email owner can communicate with another email owner of their choice.

AVM Email contains the following contract implementations:

  • AVM Email Registry

  • Server Contract Factory

  • Email Contract Factory

  • Spam Email Factory

Is Application Live: Yes

Application Will Be Open-sourced: Yes

What is Algo.fun?

Algofun contains the following contract implementations:

  • The Algofun Shares System (>$20,000~ of Algo distributed)

  • Algofun Main, a token launchpad that is unique in that it allows reflection/burn tokenomics and the option for guard rails during bonding curve to prevent abuse of users by token creator

  • Algofun DEX, a Beta DEX that branches off of the Algofun launchpad, allowing persistance of reflection/burn tokenomics while still acknowledging existing liquidity pools live on Tinyman & Pact

  • Algofun Games, including a slot machine contract implementation, Algoscape [OSRS on AVM] & Coin Flip, a 50/50 stakes game, all utilizing VRF

  • Algofun LEVY, a Tinyman leveraged trading implementation

  • Algofun Petition System, create & vote on petitions for any topic to share with others and present at a later time

  • Algofun Chat, a communication thread system triggered on certain Algofun contract calls

Is Application Live: Partially

Application Will Be Open-sourced: Yes

Why Fund This Proposal?

  • Open-sourcing of 15 Unique Smart Contract Implementations across two platforms with months of developer hours & research behind them

  • Retribution for weeks of unpaid work & maintenace, followed by morally correct ownership of the unmaintained platform, subsequent community blowback, and continued development

  • Funds forwarded to Algofun Shares System for Relief for >200 users with >$100,000 in funds locked forever

  • Fund injection will include the developers of all current, open-sourced work on Algo.fun & AVM Email (15 Contracts)

  • Breathe life into a highly developed, low-resource Algorand project

Where is Algo.fun Today?

Algofun is hosted on algo.fun, a pricey domain worth the cost at the time of our excitement in getting the project together. The live app deployments @ Algofun are the Algofun Shares System & Petition System. All fees generated by these applications & sister platform AVM Email are forwarded into the Algofun Shares system contract. We never *sold* Algofun shares — but instead decided to give nearly half of them away to users affected by the *Gainify Catastrophe*. The project creators of Gainify disappeared overnight, leaving > 200 users lost, confused, and without their funds. This was an unfortunate instance of low-resource project development paired with unmaintained code due to those same lack of resources.

The Gainify team bestowed upon our developer team the keys to their platform before vanishing, and we immediately took ownership, but piled-up bugs and rushed fixes paired with a momentary oversight lead to > $100,000 in unrealized, perhaps theoretical, ASA value locked forever. So far we have generated 37,782 Algo back into the Algofun Shares system to assist these users, a few months ago this was a noticable $20,000 milestone.

What is the Ask?

The value proposition is based not only partly in the funds lost and unpaid developer time for emergency aid, but in the open-sourcing of our development so far on the Algofun Platform & the live AVM Email platform. In total, months worth of developer hours, research, and testing has been poured into the development of Algofun, with over 5,500 lines of Python code (Not AI Slop), consisting of 15 smart contracts and testing files. **We are requesting 300,000 Algo which we will inject into the Algofun Shares System as we have done in the past, these funds are distributed to over 200 users with varying retroactive stake locked forever** from the Gainify dilemma, and portionally to ourselves of course as we also own a % of shares in the Algofun Shares system.

Contracts

Algo.fun

  • Algofun Launchpad Master

  • Algofun Token

  • Algofun DEX Master

  • Algofun DEX Pool

  • Algofun Shares System

  • Algofun Leverage

  • Algofun Leverage History Ledger

  • Algofun Petition System

  • Algo-Flip

  • AlgoScape

  • Algo Slots

Avm.email

  • AVM Email Registry

  • AVM Email Server

  • AVM Email Name

  • AVM Email Spam

300,000

DeFi

Retroactive

About the team

Team

  • Leo Costa

  • Allan Diamante

  • Ulrik Diamante

Previous Works

Additional Info
avm.email
https://algo.fun/
Context for Developer Retribution Request: AVM Email & Algo.fun - Proposal # 3464401706 - #13 by Atsoc1993

Good afternoon all —

The Algo.fun / AVM Email team would like to begin a discussion on proposal submission, including but not limited to: Requested Amount, Proposal relevance to current xGov proposal standards, General feedback & opinions.

We are very avid on the amount requested and submitting the proposal in this mixed fashion, and we are aware that it may rock the boat by going against the grain in some ways — not only by xGov standards but also in the community as some statements are a highly sensitive subject for some, regardless of whether or not they were affected.

1 Like

Added a small comment regarding the proposal at the end if this was not read yet — thank you.

I think this proposal should be split into multiple separate ones (e.g. to algo.fun and AVM email, or even more granular). This way, it would be easier to digest the delivery scope and generated results.

Moreover, I think certain aspects of the proposal are out of scope for the xGov program (even though nobel), e.g. relief for users and retribution for unpaid work stemming from dispute between two third-party entities.

Areas where some points feel out of scope should be treated more as context, which I think is important to include for voters.

There is a larger picture to the story comprising driving forces for Algo.fun & AVM Email, intent, and contributions so far that are ambiguous without the context IMHO.

A more important point is that by separating certain aspects of the proposal we risk missing qualifying factors for a valid proposal to be approved by council.

So again I circle back to my point to treating out of scope materials as context. Algo.fun, AVM Email & the absorbed Gainify project (including its unfortunate fallout, the creator’s abandonment and users affected) should be considered as 1 entity under parent Algo.fun — I could try to format the proposal around Algo.fun as an emphasis but than it’ll feel moreso like you must be in the know to interpret the proposal in a less ambiguous way — which again risks voter sentiment without proper context and understanding.

And of course thank you for taking the time to provide this feedback / recommendation, we’d like to make this proposal work and are willing to compromise but it’s important that the context sticks for voters. There are actually several other proactive and conditional actions on passing we’d like to package into the proposal but cannot because of the way proposals are evaluated now. Eg; Continued development / usage of funding

I did however hear that open-sourcing can be conditional based on whether the proposal passes or not from one of the other council members recently.

Even with this context I feel like I’m missing something. algo.fun just gives a 404, and there are no GitHub links despite the open-source claim. All we are left with is an unclear story about how some users lost funds and this grant will help make them whole.

Yeah I got a notice last week regarding a monthly billing issue with Hetzner, looks like it went down over the weekend. Thank you for catching this — you should see it online within 24-48 hours. I’ll update when they’re both back online.

image

Also us open-sourcing is conditional on the proposal passing, I believe it is no longer mandatory to open-source prior to submitting the proposal. I have adjusted the proposal wording to reflect this.

@funk Both are back online if you wanted to take another look:

algo.fun: Algo Fun

avm.email: avm.email

Since you are asking for honest feedback, if you were to submit this proposal it would be a hard NO from me even if the amount were much lower. The projects themselves are not public goods, and the prospect of open sourcing a collection of contracts from a development team that already made errors leading to large monetary losses doesn’t present much value.

It feels like you are asking xGov to pay for your past mistakes.

4 Likes

@funk As I said there are months of development work poured into Algo.fun & AVM Email, if you want to point at a different, fully-built finance platform that we received pennies on the dollar for because work was simply not available (in-total $700 per dev [3]) because of errors we:

  • could not anticipate until the application was months into production (not our project or platform to maintain)
  • were forced to drop everything in our lives for to fix at a moments notice without the project leaders or funding
  • mis-deployed the update at 2am because we were running on fumes after days of rushing for a TESTED and CONFIRMED fix

And make an inflammatory & actually, pretty defamatory statement of “You just want funding cause your team messed up”, then you’re free to do that.

We poured our hearts into Algo.fun & AVM.email — even if it was true, which it is NOT, that as you supposedly believe the entire proposal revolves around,

  • tragedy following our forced ownership of another project’s failure
  • failure from the other project’s team to take responsibility and plan out a fix with developers they haven’t interacted with in over 6 months instead of disappearing

, then I truly believe you are contributing to a disservice not only to dedicated Algorand developers that have been here for years, have helped build (not lead) extremely engaging & unifying projects like rxelms, but also to community members that have already lost so much and yet continue to stick around.

By approving this proposal the community not only shows that it values development and developers who work on things like AVM Email, an on-chain communications service that has generated value for affected users, and work done so far on Algo.fun , which we strongly believe is a powerhouse of uniqueness on AVM — but also value the morale, and acknowledge the need to take care of, their fellow community members.

At the end of the day, the 300,000 Algo translates to $30,000 — 50% will go to affected users, the other 50% will go to the 3 developers ($5,000 each) which is not a whole lot considering the, again, months of work poured into all of this.

If it makes you feel better, we can lower the ask to 150,000 and not distribute the other 50%, because that is the alternative.

Apologies for the rant, although I welcome it, I just found your feedback awfully frustrating considering the hell this team has been through with 0 support or assistance from anyone, only fingers to point when the founders are gone. Algo.fun & AVM.email are also not mistakes…

Edit: What we plan to do with the funds is not pertinent to the proposal, and again should be treated as context.

I would however like your opinion on what you consider a public good and more importantly why you feel we have no qualifying factors:

  • Is open-sourced material not quantifiable as such?
  • Are the actual platforms themselves not public goods because they are not non-profit?
  • Is retroactive funding no longer attainable unless a proposal points directly to a public good?
2 Likes

I don’t know the history of Gainify. I tried to piece together what happened but I ran into a bunch of dead Twitter links. In the absence of any facts, I said what it “felt like” you were doing. If you feel I have the wrong take then by all means defend yourself and set the record straight.

Also, I know you’re just asking my opinion, but I’m not on the xGov Council so my opinions around what constitutes public goods or whether that’s even a requirement aren’t relevant (except to my own vote). I invite the Council to weigh in on that topic.

Meta-rant:
I’m frustrated in general by the Discussion Phase of xGov on this forum. There is very little engagement, and almost none of it is critical of proposals. I get it. No one is getting paid to be an xGov and so why would they spend the time to read, understand, and comment? There may be ways to improve this, but they probably belong in a new thread.

3 Likes

No worries, I have made my case several times in the past, especially on Twitter, but my account is no longer active so those links are probably no longer available. I will try to keep it brief —

The Gainify Story

Gainify was a project we (two colleagues and I) accepted to build; although the outline seemed reasonable at the time, the project leaders quickly began scope-creep for several months, holding our lump sum payment hostage — followed by a demand for free maintenance after launch in production phase as they did not foresee we would decline partial ownership after the fulfilled lump-sum payment for its MVP state. The lump sum payment was only enough for around $700 for each developer, but we ended up working for them for months.

They did a fantastic job at marketing and community engagement but severely overestimated our responsibility to maintain the platform after launch. They refused to pay for maintenance and passive-aggressively blackmailed us with our reputations to continue working on it now that they then had large amounts of user liquidity staked on it — they would just blame us if it suddenly stopped working or worse.

We eventually put our foot down and closed that chapter with them, but lack of maintenance over months started piling up festering bugs and bloated contract state from frequent activity, until there was a breaking point for box_get opcode that you are probably familiar with — > 4096 bytes on the stack. This affected only a few users at first but eventually spread across all users in most pools, this was a platform-ending break that could have been avoided.

Overnight they panicked as they assumed it was not fixable and disappeared, thankfully leaving me a vague message and the private keys before doing so. We were already reading and writing to boxes dynamically, we just needed to patch in such a way that we could read and write to the boxes dynamically and account for scenarios where the boxes are > 4096 bytes.

With 200~ users waiting anxiously and no options or pay, we spent about 2 weeks working, testing, and updating a fix on testnet non-stop, which was successful. Unfortunately, a part of the patching process required updating two values in a .env on mainnet— the POOL_MANAGER_APP_ID and POOL_TEMPLATE_APP_ID — we unfortunately swapped in the wrong ID’s and locked all pool instances with pool manager bytecode that had a check in critical methods, including update methods, for a local state that did not exist in pool instances. Over $100,000 in ASA asset / liquidity was unretrievable and still is to this very day.

Although these things could have been avoidable and we tried our best to fix it, there was no one else to point a finger at. Being as dedicated to the community as we are, we decided to try to make everyone whole, and so began the inception of the Algofun Shares System — an idea where we would tokenize a platform we were developing and provide shares to affected users for free. These shares represented a portion of ownership in the platform, and guaranteed a % of all revenue generated — this is in production now and as stated in the proposal we have generated 35,000 Algo in fees alone for all users so far. This number may not feel impactful now but it certainly was when we were at a higher price point, at the latest update it was around > $15,000 generated for the community IIRC.

The fees generated came from sister platform AVM.email & a petition system on Algo.fun. AVM.email was intended to be a separate project but due to the circumstances was faster to develop than Algo.fun. We intend on merging this with Algo.fun at a later time but keep the domains separate for now until all Algo.fun features are in production.

2 Likes

It is difficult to accurately measure the value of the code we have created, but it is clear that, beyond more common contracts, we have delivered innovative ones. Two contracts come to mind that function as core components capable of adding value to any project: one core abstracts the responsibility of managing an application’s profits by distributing them in a tokenized manner to shareholders/investors; the other is an encrypted byte-based messaging system, visible only between the involved wallets. And this represents only the smart contract layer.

Our proposal includes the framework of a complete product, avm.email, which is already live and delivering value on its own. The other is a partially developed product, which we associate due to its connection to the payment system. Additionally, we will provide fundamental contracts for a DEX, as our objective was to scale the algo.fun product in that direction.

We included the context surrounding the issues with the Gainify group because, to this day, we have not received any support beyond our own efforts and the community. Since a significant part of our motivation comes from the community itself, we believe its importance should be reflected in the proposal.

2 Likes

Proposal created: https://xgov.algorand.co/proposal/3464401706

1 Like

I am skeptical about the product market fit for AVM email. Mail systems are like social media. Community may show interest. But perusing them to use it is going to be a tough task.

Also what is the revenue model you are thinking for AVM mail. Google is using mail id like an DID (Digital ID) for their other services. Is there enough use cases on algorand that are ready to use AVM mail as a digital ID.

This has got to be the most ridiculous proposal in here ever! Asking for a grant to compensate users of a failed project and then trying to wrap multiple things into one because you spent “time” on it. Talk about grifting…

Thats exactly what this is…

The revenue model already exists for AVM Email — in server & email creation, as well as a % fee of the relative Algo value of staking pools created.

The emphasis of AVM email has always been privacy, all messages are encrypted and only readable between two users. This was a unique and difficult implementation that I reached out to JAWS on to consult, as encrypting in a decentralized manner on a chain whose wallets did not (I’m not sure if this has changed in the past few months) do not support encrypting a custom blob as a built-in method.

Regarding this statement:

Google is using mail id like an DID (Digital ID) for their other services. Is there enough use cases on algorand that are ready to use AVM mail as a digital ID.

I’m not entirely sure what the question is here, but I definitely would like to understand it so I can provide you an answer. If you don’t mind me assuming, and I can correct myself later:

My current answer would be there is nothing Algorand lacks for any usecases (aside from some unique cases that all chains struggle with, eg; storage costs) that would prevent us, or anyone else in that matter, from utilizing it for some usecase IMO— it was just not our original direction or something we have on the horizon, although it is entirely possible to move in that direction. The open-sourced work could be picked at to help someone else iterate on their own DID implementation.

There is a lot of offchain infrastructure and integration that is needed, AVM Email is purely on-chain aside from the UI which we host.

1 Like

Just to make things clear, we’re open-sourcing two platforms — one is live, one is partially live. I understand there is a negative sentiment surrounding the Gainify fiasco, but the reality is that developers (not project creators) worked for free before and after its development — we have been doing what we can to remedy that by involving them [affected users] in our own ventures.

The proposal structure is atypical, but if you don’t mind me saying, calling it ridiculous seems emotionally bloated — there are products included in the proposal that, alone, we feel is grounds for the amount being asked; we include other points, like how we have been helping affected users, and how we plan to continue to help them, for context.

Note, and I hope this does not come off the wrong way, that all proposals are based off a team or individual spending “time” on something — it confused me that you stated this in a sarcastic manner, it grossly undermines the efforts we have, and others generally across xGov, contributed so far (read the former).

The xGov system is purely retroactive IIRC, there are no proactive initiatives that can receive funding

So let me get this straight…

Youre open sourcing 2 platforms.

First, algo.fun of which you never completed or launched does the exact same thing that Haystack just launched. A leading project in the ecosystem ran by a team that shows execution and consistency and didn’t deliver some half a$$ finished utility. You probably didnt even know that though since youre no longer involved in the ecosystem.

Second, email avm. A project you delayed at the last minute and when finally launched no one took notice other than another grifter in the space that abused it and used it to try to impersonate and blackmail people. Nice!

Third, just because you and other “developers” and or “business partners” made terrible business decisions and planning doesn’t mean you should come on here asking for pity and money because you guys wasted your time.

Fourth, you recently applied for a grant, received the funds and disappeared.Then a week ago decide to post to the account you received funding for for the first time in 2 months right as you put out this proposal. Incredible!

Fifth, I’m not taking away from anything youve done in the past with Algorand and your contributions, but im sure not okay with you and your buddies syphoning funds from the ecosystem for something no one wants or asked for, especially considering the fact that your more recent actions have shown that youre not here to help and support the growth of Algorand.

Sixth, yes there are a lot of b/s proposals this time around.

Lastly, this proposal is no different than the VC’s that dumped everything on us during the vesting period.

More grifting…

1 Like

(I typed this on my phone during my break so forgive me if there are any typos or formatting issues, I’ll review when I get home)

Firstly, I want to thank you for your more verbose answer, as it gives me an opportunity to clarify things and answer questions that others may also have, and I welcome this and your input as always in the Algorand space. I’m going to touch on a few key statements, some I do think are inflammatory but I’m sure this was not your intention.

I will say that I feel you are making contradicting and incorrect statements in some places in your response, some of them are valid, some come off a bit speculative and perhaps not backed by much but assumption — but this is partially my fault for not perpetuating enough context in the space, although I do think I spent a lot of time hosting X spaces and making twitter posts in the past discussing and showcasing updates, as well as what comprises Algo.fun and AVM Email, as well as what happened with the Gainify team (I posted my story a few comments above for more context)

First, algo.fun of which you never completed or launched does the exact same thing that Haystack just launched.

Algofun and Haystack are not the exact same thing, if you mean the Algofun launchpad and Haystack’s launchpad are the same thing, this is still incorrect. Although the Algofun’s launchpad is also reverse compatible with existing liquidity providers, the launchpad is closely tied to its own DEX among many other features, some I can’t verify as I have not tried Haystack’s launchpad, to allow new functionality with our own token standards.

You can read more about Algo.fun, including but not limited to the launchpad, here: https://docs.algo.fun/

They were each created with their own unique visions in mind. Even if you are pointing at two different platforms and claiming they are similar at surface-level that is irrelevant to its inherent value— that’s like saying Asalytic and Algogems, or Pera Explorer & Allo are the exact same thing, so one of them should not be recognized for funding opportunities.

I’ll also note that obviously these two projects are in different stages of development, and one is in production.

“You probably didn’t know that because you’re not in the community anymore”

Being on Twitter does not define my involvement in the community. Twitter is a cesspool and I should not need to participate on a social media platform to be considered an Algorand community member. The Algorand community extends beyond twitter.

There is a subreddit and discord (as well as this forum which I am moreso a spectator for the most part) that I chime into, discontinuing use of twitter is not a disqualifying factor as to whether or not I am a community member. But to answer your question, I heard of the Haystack launchpad beta a week or two ago, this was and is not a deterrent for us in proceeding with Algo.fun or submitting this proposal.

“half-a$$ utility”

To be fair, it is not entirely clear you have the information available to certainly make this assumption, and I am not so sure you have researched into the platform’s documentation to justify saying this so confidently. If you are meaning to say that the Algofun launchpad specifically is not live, you are correct but again I think you are mincing words here.

We stand by the quality of our developments to Algo.fun and AVM Email, and although we do accept ownership for previous oversights [See Gainify story above] that is not representative of what we have built so far and are continuing to develop. These two platforms are our passion-projects we pour our hearts and souls into, we hold them, uniquely to other projects mentioned, to an extremely high standard, and this should be understandable.

Some other things I mentioned earlier in this comment should also resonate here. I will again recommend this link to Algofun docs for more context: https://docs.algo.fun/

“email avm. A project you delayed at the last minute and when finally launched no one took notice other than another grifter in the space that abused it and used it to try to impersonate and blackmail people.”

AVM Email — we delayed the launch by a week or two, this is a very normal occurrence for new platforms and I’m not sure why this is a huge concern — some new products do this intentionally to build hype, although this was not our reason for doing so.

Contrary to your statement, we feel people did take notice and there was notable but not extraordinary usage / revenue from the platform.

Although the current AVM Email community is small, I assure you it is not one, or even a handful of people that back or invested into the project, admittedly its usage is not ground-breaking for TPS or anything, but this is also expected when our chain has its lower humps of activity. AVM email is the sister platform to Algo.fun and revenues from AVM email are forwarded to Algo.fun — a lot of people root to support AVM Email, and are looking forward to its success, as they have seen proceeds from it as I stated in my proposal.

Admittedly we wanted to foster a decentralized approach, so we did not gatekeep, monitor, or micromanage server & email creations. I do, however, apologize for what happened to you uniquely. I am not sure what relationship you had with the particular individual I know you are referring to, but unfortunately my understanding is that they created a server on behalf of your IGA project — although I sympathize you cannot truly blame me for not locking a server name for any one person from being purchased by others.

A whitelisting process for existing projects was just never on our docket, although it is a process that I’ve seen be used before, but we had announced and warned about this weeks before our launch. This wasn’t the day we launched, or even on Day 2 — the platform was live for at least a week before this person strolled by and minted a server for your project, this is not us dropping the ball as a platform IMHO.

If you did not see any urgency in creating it yourself for your project and now in hindsight are upset that someone else did it for you (From what I’ve seen they were coming at this from a positive place and are invested in your project, and only retaliated when certain things were expressed to him from your end), I am sorry to say that it was not our responsibility, however servers are transferable should this person ever decide to list it on the marketplace.

“Third, just because you and other “developers” and or “business partners” made terrible business decisions and planning doesn’t mean you should come on here asking for pity and money because you guys wasted your time.”

I don’t know what to say to this honestly, community demands help and that we involve ourselves and then turns the other cheek when we ask for the same. Whether you feel the proposal itself could have been avoided by building not 1, but 2 extremely successful platforms and then therefore not needing to open-source it… ? I don’t really know what to do with this comment. It seems to be a jab at the Gainify fall through and how that could have been coordinated better but this is not the reality and of course in hindsight this is quite obvious, no?

“Fourth, you recently applied for a grant, received the funds and disappeared.Then a week ago decide to post to the account you received funding for for the first time in 2 months right as you put out this proposal. Incredible!”

I didn’t receive the funds and disappear, this is an extreme exaggeration and has been discussed twice already. I have no reason to disable the AF Wallet Watcher script and respective AF Wallet Watcher twitter account, it costs nothing to run and I actually think it’s pretty neat.

When I disabled my personal account on twitter, I publicly asked that if anyone noticed anything off with the AF Wallet watcher to just send me a message and I’d get it back up and running. I also started a new software engineer job in January that has kept me extremely busy.

No one said anything — I had no idea it was even offline. I am not on twitter because as I mentioned earlier it is a cesspool of nonsense and extremely toxic for the mind. I understand that this is a personal preference and not favorable in moments where there is downtime. However if you read to the end of this section I do propose a solution.

It was argued that it’s “not our job to let you know”; I am not going to login to Twitter every morning to authenticate the bot is running, as xGov proposals are not conditional on proactive commitments like that — I did that as a courtesy, and I expected that if people valued the account that they would return that courtesy and just let me know that it went offline and I could have turned it back on with minimal effort, it is not disruptive to me in any way to reach out and I encourage this so we can all persist the AF Watcher use-case together and uniformly.

Instead, somehow through active voices in the spaces, it became some sort of scandalous act, this is why I don’t participate on twitter anymore. Anyways, the bot has been back online since last I checked, and only should have been down for a week or two because of a server shutdown due to billing issues. I actually planned on putting together a discord bot version of the watcher later today as a compromise so that we can have a dedicated channel to discuss its effectiveness and reach me directly, as well as a summary of any missed transaction notifications in the last two weeks or so.

Fifth, I’m not taking away from anything youve done in the past with Algorand and your contributions, but im sure not okay with you and your buddies syphoning funds from the ecosystem for something no one wants or asked for, especially considering the fact that your more recent actions have shown that youre not here to help and support the growth of Algorand.

Thank you for the initial comment here although it took a quick downturn afterwards. We are not siphoning funds, you can agree with the proposal or disagree with it — disagreeing with it does not mean the proposer is just trying to siphon funds, there are completely valid works and efforts that were made.

To be fair you cannot speak for the entire ecosystem and claim no one wants or asked for these things — I can think of 200 people that did, many of them demanded it, some of them performed daily checkins, and a decent amount that are still present. I would hope that this is reflected during the voting process and not in a singular comment.

I hope some of my previous explanations clears up that I do support Algorand, I thought this was a wild accusation initially to be honest with you.

Sixth, yes there are a lot of b/s proposals this time around.

I have not had a chance to look too deeply into other proposals, hopefully it’s not too bad — vibe coding has been wreaking havoc everywhere I turn so I’m not surprised if there’s a ton of random stuff up there. Algo.fun and AVM Email have history here, that I know for sure.

“Lastly, this proposal is no different than the VC’s that dumped everything on us during the vesting period. More grifting…”

I have no comment on the VC thing, Algorand has seen its share of nonsense in that department — but I think we need to be more careful as a whole, and not just you, even myself, as to what we label as grifting. Most of the time it is not an objective discernment, and more attached to sentiment. Again, I think we are all guilty of this in some way, shape or form.

Lastly, I thank you for taking the time to read this and for making these statements, I am a huge advocate for myself, my team, and my efforts — even if you don’t find yourself absorbing all of it (which is understandable given the length of this comment and would be impressive otherwise) it is never a bad thing to put these things out there. I get some self-reflection, you get some perspective, everyone gets context — all-around positive.