Allo Protocol
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Help
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    ### Allo / Arbitrum Hackaton Hosted by [BuidlBox](https://buidlbox.io), [Allo](https://allo.gitcoin.co) & Arbitrum --- Hackaton run dates: 12/8/23 - 01/10/24 tl;dr Writing a retrospective to consolidate our learnings, share insights, and reflect on the overall experience of the most recent Allo/Arbitrum hackathon. ### 1. Introduction This hackathon presented a trio of exciting challenges, each offering a slice of the substantial 40,000 ARB token prize pool. That's right, an impressive 40K ARB tokens up for grabs! These challenges, more aptly categorized as 'realms' of innovation, were: 1. Best Novel Funding Distribution Tool 🚚 2. Best Review and Evaluation Tool 🔍 3. Best Use of the Project Registry Throughout the hackathon, I led a workshop and, alongside my teamates 0xKurt, thelostone-mc and 0xZakk, actively engaged with participants by addressing their questions and providing guidance. ### 2. Highlights and Achievements Innovative Projects & (our winners for the above 3 categories): 1. **Best Novel Distribution Tool** * Third Place (3000 ARB) [DAO Driven Crowdfunding](https://app.buidlbox.io/projects/dao-drive) I think we all love to see crowdfunding. This was a good choice for a prize winner, it was a novel way to inject investor money into a funding mechanism. The way a committee is formed and voting power is set proportional to their investment is a great way to keep the participants receiving the funds accountable. Also a new area that was explored was the ability to revoke the milestone if no progress is made. Curious to how the rewards system plays out 👀 * Second Place (7000 ARB) [Spray](https://app.buidlbox.io/projects/spray) is a Windows 95 vibe, funding mechanism with a novel way to use an Allo custom strategy and the [Hedgy Protocol](https://hedgey.finance/) to create linear streams of funds to approved projects. They also took advantage of using the pools to manage who votes using a sub-DAO type architechture, pretty neat. * First Place (10000 ARB) [Conviction Voting App](https://app.buidlbox.io/projects/convictio) showcases the use of conviction voting within communities and takes first place. Its continuous funding model and features like dispute resolution are tailored to the needs of early-stage web3 projects. The focus on a user-friendly interface design highlights a deep understanding of user needs, distinguishing the project as a forward-thinking solution in the realm of grant distribution. 2. **Best Review and Evaluation Tool** * Third Place (2000 ARB) [Build3r](https://app.buidlbox.io/projects/builder): This presents a fascinating application in the realm of real estate development. I'm particularly intrigued by the process of converting cryptocurrency into fiat currency and ensuring that the actual supplier, builder, or developer receives the funds. Given that this system operates on a milestone-based approach, a key question is how to verify the completion of these milestones. This leads us into a deeper exploration of the supply chain aspect. It's exciting to contemplate the potential real-world applications of this concept. * Second Place (3000 ARB) [Allo Explorer](https://app.buidlbox.io/projects/allo-expl) I appreciated the Allo-Explorer's effectiveness in tracking pool fund flows. Its map graph feature is particularly impressive, offering clear insights into application statuses and submissions. The tool is also invaluable for observing applications that draw from multiple pools, displaying received amounts from each. This not only aids in monitoring fund distribution but also helps pool managers gauge the reputation of applications, making it a vital resource for informed decision-making. * First Place (5000 ARB) [AGDM](https://app.buidlbox.io/projects/rrd) or The Arbitrum Grants Defence Manager (AGDM) stands out as a robust dashboard offering grant managers an array of essential tools for effective grant round management. With features like a user-friendly interface for round statistics overview, it simplifies tracking progress and performance. The advanced threat detection and isolation system is particularly noteworthy, enabling managers to quickly identify and neutralize potential threats like attack bots and recycling attacks. AGDM's innovative defense capabilities and integration with a Sybil database significantly enhance the security of grant rounds. Additionally, the platform’s invitation for contributions, including new detection methods and accompanying write-ups, fosters community involvement and continuous improvement, making AGDM not just a tool but a collaborative project in enhancing grant management security. 3. **Best Use of the Project Registry** * Third Place (2000 ARB) [Magari](https://app.buidlbox.io/projects/margari) effectively addresses the challenges in decentralized, cross-chain work environments. Integrating with the Allo Protocol, it enables the smooth transfer of funds across different chains, ensuring contributors get paid regardless of their location in the blockchain ecosystem. Leveraging the Allo Registry for security and Chainlink CCIP for transferring 'Gilts' (bonded fund NFTs), Margari simplifies fund distribution while providing flexibility and safety. This makes it a noteworthy solution for managing decentralized project funding and mitigating the complexities of cross-chain transactions. * Second Place (3000 ARB) [SolidGrant](https://app.buidlbox.io/projects/solidgran), built on the Allo Protocol within the Arbitrum network, presents a functional and straightforward DAO dapp. Its core features include proposal submissions and voting, treasury management, and tracking community activities. The ability to register recipients and distribute funds is a useful addition but doesn't particularly stand out in the crowded DAO tool space. Overall, Solidgrant offers a competent, if not exceptional, user experience for those looking to engage in decentralized governance. * First Place (5000 ARB) [Alloliance](https://app.buidlbox.io/projects/allolianc) streamlines web3 KYC processes for grant seekers with a comprehensive tech stack including PostgreSQL, Prisma, TypeScript, React, Solidity, Fastify, and IPFS. It introduces the Allo Profile Metadata Standard for secure, standardized grant application credentials. The user experience is efficient, allowing KYC submissions with various ID forms and integrating third-party verification. Results are securely hashed and stored on IPFS. Future roadmap plans include expanding third-party KYC integrations, adding email notifications for submission statuses, and deploying on Arbitrum One. Alloliance represents a secure and user-friendly solution in the web3 compliance space. **🥳 Personal Favorite 🥳** Alloliance emerged as one of my personal favorites in the web3 compliance sector. Its adept handling of KYC processes for grant seekers is particularly impressive. The protocol's robust tech stack lays a solid foundation for reliability and efficiency. The introduction of the Allo Profile Metadata Standard is a game-changer, ensuring secure and standardized KYC documentation for grant applications. What I find most commendable is the user-friendly approach to KYC submissions, allowing various ID forms and leveraging third-party verification for authenticity. The secure storage of results on IPFS further enhances trust in the system. Looking ahead, the roadmap promises exciting developments like expanded third-party integrations, email notifications, and deployment on Arbitrum One, suggesting a bright future for the platform. Overall, Alloliance's mix of security, user convenience, and forward-looking features make it a standout choice in my web3 toolkit. **Key Milestones**: 1. 303 Participants 👨‍👩‍👧‍👦 2. 86 Projects Submitted 📦 3. 40K ARB tokens up for grabs (from 40K USD 🔥) ### 1. Challenges and Solutions Many of the technical challenges encountered were linked to the learning curve faced by new developers. It was noteworthy that the teams with completed projects and top submissions navigated these challenges smoothly, showcasing their adeptness with Allo's documentation and setup process. Recognizing that Allo is an advanced allocation and funding protocol, it's understandable that beginners may face hurdles. This not only highlights the protocol's complexity but also underscores the impressive learning journey of all participants. ### 2. Feedback and Learning (GPT from Discord chat) Let's talk about our participant feedback. Discord was our main channel for communitcation, which I was comfortable with and seemed the participants were active there. One of the challenges with Discord is when more than a few members DM you instead of posting on a public channel for everyone to see and support if capable. I can't stress enough how important it is to post in public when working in public. Too many times have DM's gone on too long when the issue(s) should have been brought to the attention of the applicable team (or in public). There were some doubts from a couple of our participants about the objectivity of the judges, with some projects allegedly receiving high scores despite not meeting key criteria. Buidlbox representatives have responded, apologizing for the situation and indicating that they are looking into the matter. They clarify their role in the judging process and promise to discuss the concerns raised and provide updates and the community is actively discussing the issue, with some expressing disappointment and frustration. The BuidlBox team will consider suggestions for improving future hackathons to avoid similar issues. ### 3. Developer Experience It became evident that the developer experience encountered certain setbacks, partly due to the Allo team's limited availability over the December holiday period. In future planning, it's essential to account for global holidays to avoid such scheduling conflicts during events like hackathons. Additionally, the enhancement of available resources is crucial. This includes not only a broader range of video content showcasing Allo's functionalities and its diverse applications but also an improvement in our general documentation. More comprehensive SDK documentation, enriched with practical examples, and an expanded suite of video tutorials would greatly benefit our users. ### 4. Impact on Blockchain Community The hackathon served as a dynamic convergence point for experts and enthusiasts keen on exploring and advancing blockchain technology. A notable success of the event was its substantial contribution to the Allo Protocol, particularly in the context of funding public goods. Teams engaged in a deep dive into Allo's intricacies, aiming to harness its potential for improved efficiency and scalability in blockchain projects. This joint effort led to the birth of innovative concepts, fostering new ways to utilize the blockchain in supporting social and public causes. These collective explorations and contributions resulted in tangible advancements, offering significant benefits to the wider public goods sector. The outcomes of the hackathon, including the developed ideas and prototypes, are set to make a lasting impact. Their influence extends beyond providing immediate solutions, as they fuel ongoing dialogues and inspire new projects within the realm of public goods. The advancements made to the Allo Protocol, in particular, have opened up fresh perspectives on how to fund and support public initiatives, merging technological innovation with a commitment to social welfare. This event transcended the bounds of mere technological advancement; it marked a significant leap towards future developments in the public goods arena. By nurturing innovative approaches to both Arbitrum and Allo, the hackathon made a meaningful contribution not just to the participants and immediate stakeholders, but also to communities funding public goods. ### 5. Acknowledgments A heartfelt thank you to everyone who contributed to our hackathon's success 🥳. Immense gratitude goes to our dedicated team, whose hard work and creativity were instrumental in orchestrating the event. To all the participants, your innovative spirit and enthusiasm were the heart of the hackathon, bringing invaluable ideas and energy. A special thanks to our sponsors for their generous support and commitment to innovation, making this event possible. Lastly, our appreciation extends to mentors, judges, and volunteers for their expertise and guidance. Together, we created a memorable and successful event, and I look forward to more collaborative and innovative endeavors in the future! 🎉 🥳

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully