xGov-156 - Open Source ARC53 Tooling

id: 156
period: 3
title: Open Source ARC53 Tooling
author: krby.algo (@kylebeee)
company_name: Akita
category: dApps
focus_area: Defi
open_source: Yes
amount_requested: 25000
status: Final


This proposal aims to build out & open source tooling for decentralized self-soveriegn project details on Algorand. ARC53 is a community page spec that enables projects & companies with onchain assets to trustlessly share details about their business for exploration by the community and other business entities on-chain. NFT marketplaces, wallets, and other dapps can utilize this spec to enable users to explore projects & companies on-chain. This proposal aims to build out open source tooling to enable this spec to be easily utilized by the community.


Krby (https://twitter.com/kylebeeeee) has been a full time software engineer for over 7 years and has been spending his evenings building Akita for the better part of the last 2 years following the original dev teams departure. He’s built a number of massive features for the Akita community including a staking platform, discord payment & verification bot (integrated with NFD’s), Yoink Ball (an in person king of the hill game utilizing Freeze & Clawback) and a permissionless Community spec (ARC-53).

Experience with Algorand

For nearly the last 2 years Krby has been spending his evenings building on Algorand. From writing smart contracts to building the base components of a longer term vision; a social platform built ontop of Algorand, NFDs, subscriptions & the community page spec. To date he’s delivered an astounding amount of value to the Algorand / Akita community and has been the driving force behind the growth of the Akita platform:

  • The most flexible staking platform on Algorand
  • A discord bot that enables payments, verification, and more
  • Yoink Ball, an in person game of king of the hill utilizing Freeze & Clawback
  • Author of ARC53, a permissionless community spec that enables NFT and project exploration with some of the best UX on Algorand
  • A shuffle system for Akita Omnigems where the NFTs have no data attached to them before sale
  • Co-Author of ARC58, the Abstracted Account spec.

Present Proposal

This proposal aims to build open source tooling for parsing & caching ARC53 community data. This will enable dapps to easily integrate and display consistent information about projects & companies on-chain. Open source libraries will be written in Golang & Typescript.

Benefits for the community

Projects & Businesses on Algorand currently deal with a centralized and fragmented landscape when it comes to sharing information about their business. ARC53 allows them to share this information in a verifiable and trustless manner thats easily consumable for dapps like NFT marketplaces, explorers, etc. Creating tooling for these dapps to more easily adopt the spec will enable a more consistent & convenient experience for users across the ecosystem. As an example, we have many NFT marketplaces and if you want to launch a collection you will need to go fill out repitive forms on each marketplace, if ARC53 we’re easy to integrate with, you would have automatic propegation of your project details across the ecosystem.

Additional information

1 Like
  1. Can you expand a bit more about what you are proposing to build? I understand what issue ARC53 is supposed to address. I’m not a dev, so I’m just not sure I understand what you are building in relation to it.

  2. My understanding is that ARC53 is not yet final and adopted. Is that correct? If so, is there a danger in building tools around an ARC that is not adopted? What happens if the ARC changes while you are building (or worse, after you are done)?


Yes, specifically this is a proposal to build out and open source the code that does all the heavy lifting for finding the info on chain and saving it as well as tracking the chain for updates to the community info that projects publish.

Its new and this proposal is meant to lower the barrier for businesses to adopt this standard and help create seamless consistency across any places where token/nft collection and other info is displayed.

I proposed it as a living standard so i hope it does change overtime, it’s meant to be expanded upon, customized and added to. There’s a version number baked into it so if/when changes are made it’s easy to distinguish between the new and old.

I think you can reason about this similarly to nft standards in that it felt like everyone had to implement parsing and caching code on their own and it was a lot of redundant work for a lot of people. Similarly, every explorer/marketplace currently has to build all this extra infra for collections/projects to submit the information manually to them and its just a ton of extra work for everyone involved with lots of room for creating inconsistencies and errors. The goal of this xgov proposal is to help make this standard substantially easier to adopt and thus alleviate all that extra work currently being done while improving the experience of creators that want to share information about themselves and their projects.


Thanks Krby. Appreciate you, and I’m not picking on you. I’ve tried to go through every single proposal and provide some type of feedback or question.

I assume that if the ARC changes, someone will just need to fork your code at that time and modify it to meet the ARC change.

1 Like