The xGov Council: Shaping the future of xGov

Will applicants be required to disclose their affiliation with any Algorand projects? And if so, will this information be made available to the community?

Regarding a lack of doxxing and the ability for council members to propose their own projects for funding… the Council might look something like this: We end up with a partially or completely pseudonymous council. We wouldn’t know the members’ qualifications or hands-on experience. Their affiliation...

For example, if the reviewer works for a business built on Algorand, it produces a conflict of interests that biases their reviews in favor or against certain projects. I don’t feel strongly pro doxxing, but it seems reasonable. Crypto is a hellhole of scams and manipulation, so we should aim for transparency.

Doxxing seems like a reasonable way to keep people accountable. It also helps everyone understand the reviewers’ experience, skills, biases, and conflicts of interest.

1. “Any community member, including xGovs, with Algorand technical expertise and a strong reputation can run for the council.”
   We should aim for a broad definition of ‘technical expertise’ beyond just engineering. We’ll need experienced business, product, and finance people. And given the emphasis...

xGov-204: Everyone Launchpad Security Audit

We are pleased to announce that the Everyone platform beta phase is starting! We’ll begin providing access to testers this week, initially prioritizing user interviews with community members, followed by a gradual rollout to other testers. It’s been a long road to get to this point. We’re excited...

Hi Ghost, I can understand your suspicion and I also agree that we could have released a working but unpolished product a long time ago. Please note that we did offer to do a walkthrough via Zoom at the end of May. No one responded to that offer, and I have to admit that we only had a few people...

Thanks for your comments. We are not kicking the can, we are just focused on improving our project a bit longer. We have worked diligently on Everyone for a long time and have not accepted the approved xGov funds, so I hope that there is no big issue here. We are a committed team and our priority is...

I have tested the app and see that if you input the various parameters it will generate a JSON file. In my test, I skipped many of the fields and input the word “hello” for addresses, etc – the app still created a JSON file with the partial and invalid info. As the ARC specifies that no fields are required...

Yes totally agree with this. We will ensure that users have a decent amount of time in Testnet before we accept any funds. We have been building this product for a long time, bootstrapping with our funds, and we want to make sure that users get the best experience possible from the get-go.

As mentioned, we are currently adding some onboarding steps to help users navigate around the app. We are also adding some more features unrelated to the launchpad. If there is an urgent need to review the app, I would be happy to do a walkthrough next week via Zoom.

We need to demo the platform to projects and users prior to signing teams up for launches. While we wait for the audit to be funded and performed, we are busy testing, iterating, and improving features. We are also building onboarding steps into the user flows. At some point later in June, we will release the full beta...

Thanks. We’re looking forward to getting Everyone released very soon! All the great projects receiving funding this session, combined with the Python update should have a big impact in the ecosystem! Check out the Everyone beta site and sign up for Testnet here: https://beta.everyone.space

The beta signup page for the Everyone platform/launchpad is now live at: https://beta.everyone.space
Please explore and sign up in preparation for Testnet access in the near future. The beta page provides a ton of info about the Everyone platform’s features. Our xGov proposal just relates to this.

Regarding open-sourcing, our proposal states that we commit to open-sourcing all code within our audited contract, in the event that the project is sunset at some future date.

We’ve updated the proposal text to include more detailed info about the liquidity pool creation process.

A core feature of this ARC are workflows designed to establish a bidirectional link connecting the metadata of an Asset Set with any associated entities (e.g. Child Assets, Contributor Addresses, and Contributor Assets), allowing them to reciprocally reference each other. Linkage is established during the asset creation process.

The ARC-40 proposal aims to promote a more interoperable and inclusive Algorand NFT ecosystem by defining clear yet flexible standards for configuring and verifying NFT Collections and other types of asset sets. It facilitates attribution for contributors and adaptable IP rights management for creators.

In the upcoming Everyone platform, we will integrate decentralized voting and agreement signing tools alongside additional features that will serve to enhance user experience.

We are true believers in the principles of decentralization and accountability, and we hope our tools will foster community engagement and transparency in decision-making processes across the ecosystem.