## **Executive Summary**

Over the past two quarters, YRAL has undergone a **fundamental product and strategic transformation**.

YRAL has evolved from a **crypto-powered social application into a fully AI-native consumer platform**, where:

- All content is **AI-generated**
- All influencers are **AI agents with distinct personalities**
- The platform experience has shifted from **“scroll & earn” → “interact, engage, and build relationships with AI agents.”**

This transition represents a **category shift**, positioning YRAL not as a social media app, but as a **consumer AI platform built around short-form video distribution and AI agent interaction**.

At the same time, the team has:

- Reduced burn from ~$200K/month → ~$100K/month
- Built early-stage **real revenue (user-paid, not experimental)**
- Re-architected infrastructure for **massive cost efficiency and scalability**

We are now entering a phase focused on:

- **Retention and habit formation**
- **Monetization scaling**
- **AI agent quality and experience**

To sustain operations and execute Q2 2026 priorities, we request a **withdrawal of 150,000 ICP** from the DOLR AI SNS DAO treasury. This is the fifth part in the series of proposals. (Link to the [first proposal](https://dashboard.internetcomputer.org/sns/67bll-riaaa-aaaaq-aaauq-cai/proposal/510), [second proposal](https://dashboard.internetcomputer.org/sns/67bll-riaaa-aaaaq-aaauq-cai/proposal/511), [third proposal](https://dashboard.internetcomputer.org/sns/67bll-riaaa-aaaaq-aaauq-cai/proposal/512) and [fourth proposal](https://dashboard.internetcomputer.org/sns/67bll-riaaa-aaaaq-aaauq-cai/proposal/552))

## **1. Strategic Evolution: Social Crypto App → AI-Native Platform**

### **1.1 What Has Changed**

Over the last few months, YRAL has undergone a **significant product pivot**:

1. Crypto-led social app → AI-native consumer platform
2. User-generated content → AI-generated content
3. Human Influencers → AI agents with personalities (AI influencers)

This shift is geared toward making YRAL:

> **A consumer AI platform where users discover, interact with, and build relationships with AI agents, discovered through short-form video.**
> 

This positions YRAL at the intersection of **agentic AI, social distribution, and consumer entertainment.**

## **2. Product & Infrastructure Progress (Q4 2025 – Q1 2026)**

### **2.1 AI-Native Product Stack**

1. **AI Influencer Ecosystem:** Launched a complete AI influencer account system enabling users to create AI influencers through a three-step process.
2. **AI Chatbot & Companion Services:** Deployed an AI chatbot infrastructure allowing users to interact with AI companions with customized personality traits created by other users.
3. **AI Content Creation:** Implemented an end-to-end AI video generation pipeline with drafting and publishing workflows, allowing users to review outputs before publication.
4. **Monetization Infrastructure:** Implemented a comprehensive subscription system for recurring bot subscriptions (₹9 for 24 hours) and premium AI content unlocks.

These systems validate a key thesis:

> Users are willing to pay for **AI interaction and content**, not just passive consumption
> 

### **2.2 Infrastructure & Cost Optimization**

1. **Infrastructure Migration for Cost Optimization:** Migrated from Google Cloud Platform to self-hosted infrastructure, delivering ~90% cost savings and enhanced operational control.
2. **Data Infrastructure:** AI chat system migrated from SQLite to PostgreSQL with Litestream backup integration, enabling scalable conversation storage, real-time data replication, and operational redundancy.
3. **Security & Secrets Management:** Integrated HashiCorp Vault for centralized secrets management with automated unsealing and multi-host deployment.
4. **Video Processing Infrastructure:** Enhanced video upload service with V3 API supporting multipart/form-data for Storj integration and optimized it for reliable data processing.
5. **Platform Stability:** Removed deprecated infrastructure and eliminated dead code to improve codebase maintainability and reduce technical debt.

This has resulted in **lower burn, greater control, and better scalability,** with a cleaner, more focused product direction centered on AI.

## **3. Traction & Key Metrics**

### **3.1 Current Snapshot**

- **800,000+ downloads** (primarily Android, India)
- **~100,000 Monthly Active Users (MAU)**
- **~8 minutes average daily usage**
- Early **revenue has started** (still very small, but real and growing)

We’re intentionally focused on India first, and will expand globally once we hit strong product-market fit.

## **4. Monetization: Current & Roadmap**

### **4.1 Current Revenue**

- Early revenue: **a few hundred USD/month (user-paid, real)**
- AI chat paywall (freemium model) and premium AI-generated content are the primary revenue streams right now

### **4.2 Roadmap**

**Phase 1: India PMF**

- Low CPI (~$0.04) enables rapid experimentation
- Focus on retention and building a habit

**Phase 2: Product Improvement**

- Better AI memory, personality, proactivity
- Increase engagement → increase conversion

**Phase 3: Global Expansion**

- Expand to high ARPU markets such as the USA, Japan, and Southeast Asia

## **5. Expected Roadmap for Q2 2026**

### **5.1 Product & AI Agent Experience**

1. **AI Agent Quality Improvements:** Enhance memory, personality consistency, and contextual relevance of AI agents to improve response quality and drive deeper user engagement.
2. **Content Generation Enhancements:** Expand AI video generation capabilities to support multi-modal inputs, including image, audio, and text, while ensuring more consistent output quality.
3. **Onboarding & Activation Optimization:** Streamline onboarding flows and reduce time-to-first-interaction, enabling new users to engage with AI agents and experience immediate value quickly.
4. **Self-Hosted Infrastructure Completion:** Complete the migration from Google Cloud Platform to self-hosted infrastructure to optimize costs further.

### **5.2 Retention & Engagement**

1. **Feed Recommendation Optimization:** Improve feed personalization using behavioral signals to increase content relevance and drive higher user engagement.
2. **User Experience Improvements:** Reduce friction across core user journeys, including content discovery, interaction, and payments, while improving overall app responsiveness and stability.
3. **Conversion Optimization:** Improve free-to-paid conversion for AI chat interactions by refining paywall placement, pricing strategies, and the overall payment experience.

## **6. Financial Overview**

### **6.1 Current Burn**

- Reduced from ~$200K/month → ~$100K/month

### **6.2 Monthly Cost Breakdown**

- Payroll: ~$60,000
- Infrastructure: ~$30,000
- Legal: ~$5,000
- Operations: ~$5,000
- Miscellaneous: ~$10,000

### **6.3 Funding Ask**

We request **150,000 ICP (~$350,000)** for Q2 2026 operations as we explore additional financing options to extend the runway until the system becomes self-sustaining. 

## **7. Closing Statement**

YRAL has evolved from a social crypto app to

> A **consumer AI platform** where users interact with, consume, and build relationships with AI agents — powered by short-form video.
> 

We have:

- Validated early user demand
- Achieved meaningful cost discipline
- Built early monetization signals

The next phase is clear:

- **Retention → Monetization → Scale**

We remain fully committed, deeply hands-on, and actively building every day.

We appreciate the continued support of the ICP community as we push forward in building a **new category at the intersection of AI, social distribution, and consumer interaction**.
--------------------------------
<br><br>
This proposal was created using [https://ic-toolkit.app](https://ic-toolkit.app)
<br><br>


DOLR AI Treasury Proposal Q2 2026 - Part 5

This proposal executes grant permission to asset canister.

Execute grant permission to asset canister.

This proposals registers revoke permission to asset canister with the SNS governance canister.

Register revoke permission to asset canister.

This proposals registers grant permission to asset canister with the SNS governance canister.

Register grant permission to asset canister.

This proposal registers dapp's canisters with SNS.

Register dapp's canisters with SNS.

This proposal upgrades user_index canister

Upgrade user_index canister

This proposal upgrades post_cache canister

Upgrade post_cache canister

This proposal upgrades configuration canister

Upgrade configuration canister

This proposal upgrades data_backup canister

Upgrade data_backup canister

This proposal includes Step 1 for removing a legacy access_control field from the canister internal storage

This proposal includes Step 2 (final step) for removing a legacy access_control field from the canister internal storage

Upgrade Hot or Not SNS Governance canister to next version.

See the linked NNS proposal: https://dashboard.internetcomputer.org/proposal/123495

Upgrade SNS to the next version

This proposal refactors user_index internal data structure. It moves the known_principal map under configuration field and adds a new configuration value for sign-up control

This proposal introduces a new mechanism for us to account for cycles consumption. Along with the backend changes, we are also building a dashboard that should provide insight into our cycles usage across the fleet. This will also help us prioritize optimisations to be worked on to keep costs sustainable.

**Proposal Overview:**

This test proposal aims to ensure the smooth and accurate execution of HOT token transfers from the SNS token treasury to the destination account. We propose a test transfer to verify that the source and destination accounts, as well as all related processes, are functioning correctly and without human errors. This test transfer is a crucial step to ensure the robustness of our token transfer system before conducting significant transfers.

**Test Transfer Details:**

**Transfer Amount:** 100 HOT token

**Source Account:** SNS Token Treasury (SNS Ledger)

**Destination Account:** ndztf-hbboh-svwx2-njiyp-zeo7w-2jvum-64gms-nygf5-vovlj-fpdgb-7qe

**Purpose:**

- Validate the accuracy of the source and destination account addresses.
- Confirm the correct execution of the token transfer process.
- Ensure that the memo, if applicable, is correctly handled.

**Validation Steps:**

- Cross-reference the source and destination account addresses with the correct addresses specified in our system.
- Carefully monitor the transaction status and verify its completion.
- Confirm that the correct amount of tokens is received in the destination account.
- Ensure that any memo or additional information is correctly associated with the transaction.

**Conclusion:**

This test transfer aims to enhance the confidence and reliability of our token transfer system by verifying its accuracy and robustness. After the successful completion of this test, we will proceed with proposals concerning large HOT token transfers from the treasury, with the assurance that our processes are functioning correctly.

Verify Token Transfer Functionality

**Proposal Overview:**

This proposal entails transferring 5.83 million HOT tokens to facilitate the distribution of rewards for the HotOrNot "Pre-SNS Airdrop.”

**Transfer Details:**

- **Transfer Amount:** 5,832,757 HOT token or 5_832_757_00_000_000 e8s
- **Source Account:** SNS Token Treasury (SNS Ledger)
- **Destination Account:** ndztf-hbboh-svwx2-njiyp-zeo7w-2jvum-64gms-nygf5-vovlj-fpdgb-7qe

**Airdrop Background:**
This airdrop is dedicated to HotOrNot users who participated in the "Pre-SNS Airdrop" campaign, which took place from May 23, 2023, to July 15, 2023. Initially, 10 million HOT tokens were allocated for this airdrop, distributed based on users' COYN token balances. This allocation represented 1% of the total initial supply of HOT tokens.

**Revised Allocation:**
Following successful claims by participants and the submission of their NNS IDs on the platform, it has been determined that 5.83 Mn HOT tokens are eligible for distribution.

**Airdrop Details:**

- **Airdrop Amount**: 5.83 Mn HOT tokens
- **Eligibility Criteria:**
    - Users must have completed the airdrop form within the stipulated time period, which was during the HotOrNot Pre-SNS Airdrop campaign from May 23, 2023, to July 15, 2023.
    - Users must have subsequently submitted their NNS ID to claim the airdrop through the platform.
- **Airdrop Distribution Algorithm:** For the distribution algorithm, please refer to HotOrNot’s Airdrop Guide at **https://hotornot.wtf/airdrop-guide**.- 

Transfer of 5.83 Million HOT Tokens for Pre-SNS Airdrop Reward Distribution

This proposal is to transfer 30,000 ICP from the HotorNot SNS DAO to GoBazzinga Inc. to cover the costs of the core dev team and other expenses for Q4 2023 (until the end of December 2023).

These expenses are critical for the sustained growth and development of HotorNot, including operational costs, team salaries, legal and compliance fees, and strategic investments.

Budget Breakdown: The requested funds will be allocated as follows:

### 1. Team Salaries:

- 4 Core Developers
- 1 AI Developer
- 1 Product Manager
- 1 UX/UI Designer
- 2 Social Media/Community Managers
- 1 HR Manager

### 2. Incorporation Fees and Foundation Fees:

- Costs associated with legal incorporation of Hot or Not non-profit Foundation and to protect HotorNot’s IP.

### 3. HR/Operations:

- Operational expenses, including HR-related costs and administrative overhead.

### 4. Legal Fees:

- Legal services required for compliance, regulatory matters, contractual obligations, and employment contracts.

### 5. Third-Party Services:

- Costs related to third-party tools, technologies, and services necessary for HotorNot’s seamless operation (ex. Cloudflare).

### 6. Marketing:

- Marketing campaigns, advertising, and promotional activities to increase HotorNot’s visibility and user base.

This proposal does not include ICP for cycles to run the HotorNot dapp, or other on-chain costs which will continue to be funded by proposal as required.

Our "best efforts" plan for Q4 2023 is as follows:

- **Multi-Subnet Architecture:** Expand to more than one subnet to facilitate new sign-ups in our multi-canister app, enhancing platform scalability to accommodate a growing user base.
- **Content Gamification:** Create and refine a new gamification feature tentatively called “Up/Down”, iterating through versions to achieve Product-Market Fit (PMF).
- **N-Phones NFT Game:** Integrate the N-Phones NFT game mentioned in our Whitepaper into the app, focusing on the user interface (UI) for a seamless gaming experience.
- **Mobile App Development:** Develop dedicated mobile application to provide users with a seamless experience across various devices and platforms.
- **Social Ecosystem:** Enhance the leaderboard feature and explore the integration of chat functionality, fostering a more interactive and engaging social ecosystem within the app.

HotorNot DAO Proposal for Q4 2023 Funding

Test transfer 1 ICP from SNS treasury

You can now easily submit these proposals from the [Hot or Not Proposals](https://oc.app/group/qpj6u-uyaaa-aaaar-aq6mq-cai) group in OpenChat!

> Submitted by [@Hamish](https://oc.app/user/3skqk-iqaaa-aaaaf-aaa3q-cai) on [OpenChat](https://oc.app/group/qpj6u-uyaaa-aaaar-aq6mq-cai)

Upgrade SNS to next version

Test transfer 1 ICP from SNS Treasury

We are pleased to share with you the progress report of the Hot or Not DAO project, which aims to create a decentralized short-video social media platform on Internet Computer Protocol. We successfully completed the SNS Decentralization Sale for Hot or Not DAO in July 2023, and since then, we have been working tirelessly towards the development of the Hot or Not platform. The main areas of focus have been:

1. **Hiring:** Based on our research, we have decided to build the entire platform on RUST, a programming language that offers high performance, reliability, and memory efficiency. This would make the platform more nimble, responsive, and better performing than the current JavaScript-based interface. Hence, we are rewriting the entire platform in RUST. To achieve this, we have been hiring RUST Developers over the last five months and have grown the developer team from two at the launch of SNS DAO to the current size of five, with several more developers in the pipeline.
2. **Multi-Subnet Architecture:** To achieve the goal of one million users on the Hot or Not platform and beyond, implementing the multi-subnet architecture is of utmost importance and hence has been a primary focus over the last five months. This architecture will allow us to scale the platform efficiently and securely, leveraging the power of the Internet Computer Protocol (ICP).
3. **Legal Compliance:** To contribute to Hot or Not DAO as a public good, the establishment of a Non-Profit Foundation in Switzerland is being pursued. Additionally, fulfilling the various compliance tasks, such as obtaining the trademark for Hot or Not across geographies is another key area of focus to prevent any potential future complications/issues.

We submitted a treasury proposal to withdraw 30,000 ICP towards the end of September 2023 to fund the fourth quarter of 2023 (October 2023 to December 2023).

This particular one-time proposal is for funding required to complete the legal compliance tasks (setting up the Hot or Not Foundation and completing other current compliances of Hot or Not to operate in different regions) and to hedge against the market risk of ICP while creating an emergency treasury fund for covering emergency salary expenses and day-to-day expenses of the Non-Profit Foundation for a few months. Therefore, we are submitting a request to withdraw 75,000 ICP from the Hot or Not SNS Treasury for this purpose.

Please note that this proposal is a one-time proposal and is independent of the regular budgetary proposals that will be submitted every quarter.

We hope that you will support our proposal and help us achieve the vision for Hot or Not DAO. Thank you for your continued trust and support!

HotorNot DAO Proposal: Progress Report and Funding Request for 75K ICP

Test Transfer for 1 HOT Token

We are requesting your approval to transfer 202.5 Million HOT tokens, which is 20.25% of the total initial supply, from the HotorNot Treasury to the Hot or Not Swiss Foundation. This transfer is part of our planned token distribution, as outlined in our [Whitepaper](https://www.notion.so/Hot-or-Not-Whitepaper-c539179e51f44867979f4372e4635f59?pvs=21). The Swiss Foundation is a vital entity that will develop and manage the infrastructure of the Hot or Not platform, a decentralized social network that empowers users to rate and discover new content.

We will stake 50% of the tokens allocated to the Swiss Foundation for voting purposes, enabling the Foundation to actively participate in the governance of the HotorNot platform. We believe that this will align the Foundation’s interests wcaleith the community and ensure transparency and accountability.

The proposed token allocation is in line with the HotorNot Foundation's mission to develop, govern, and enhance the Hot or Not platform. These tokens will be instrumental in securing top talent, seeking expert advice, and driving continuous innovation.

We seek the community's support in approving this allocation to empower the Hot or Not Foundation in its mission to contribute to the growth and development of our ecosystem.

HotorNot Foundation Token Allocation Proposal

Add memory manager to Individual_user_template canister

Add memory manager to Individual_user_template canister.\n GitHub Pull Request: https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/198

This is the proposal for step-2 of adding memory manager to individual_user_template canister.

## Changes

Add memory manager in post_upgrade hook to work with stable memory along with heap memory.
GitHub Pull Request: https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/199

This is the proposal to fix virtual memory manager in individual user template canister.

## Changes
Re-running upgrade again with reduced bucket size.

GitHub Pull Request: https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/203

This is the proposal is to start user_index canister and will not upgrade any individual canisters.

## Changes
Upgrade user_index to start user_index canister.

GitHub Pull Request: https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/204

This is the proposal is to fix ndexes for get top posts methods in the canister.

## Changes
- fix indexes for 
- fix indexes for 
- added tests

GitHub Pull Request: https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/210


  # Upgrade ${CANISTER_NAME}

  ## Bugfixes
- add permissions for release workflow ([#214](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/214) by [ravibazz](https://github.com/ravibazz))
  

Upgrade ${CANISTER_NAME} Canisters


  # Upgrade user_index

  ## New Features
- add module hash in release workflow logs([#216](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/216) by [ravibazz](https://github.com/ravibazz))
- add user canister status apis ([#215](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/215) by [ravibazz](https://github.com/ravibazz))
  

Upgrade user_index Canisters


  # Upgrade post_cache

  ## New Features
- add module hash in release workflow logs([#216](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/216) by [ravibazz](https://github.com/ravibazz))
- add user canister status apis ([#215](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/215) by [ravibazz](https://github.com/ravibazz))
  

Upgrade post_cache Canisters


  # Upgrade configuration

  ## New Features
- add module hash in release workflow logs([#216](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/216) by [ravibazz](https://github.com/ravibazz))
- add user canister status apis ([#215](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/215) by [ravibazz](https://github.com/ravibazz))
  

Upgrade configuration Canisters



# Invitation to Invest in Neutrinite DAO

We are excited to extend an exclusive invitation for your organization to participate in the Neutrinite DAO launch. This initiative offers an investment opportunity of 5000 ICP, aligning with our mutual interests in decentralization and innovation.

Your participation in this launch is not just about investment; it's about collaboration and contributing to a new frontier in decentralized governance. This venture represents a significant step in our shared journey towards building a more interconnected and collaborative decentralized ecosystem.

Technical info:

1) This proposal sends ICP from your DAO treasury to an address in Neutronite SNS Swap that belongs to your SNS governance canister.
{owner: SNS Swap, subaccount: DAO Governance canister}
Verify the text account representation with your own tools or https://github.com/infu/verify_dao_sns_account/blob/main/check.js 

2) Once the NTN Launch is complete, your DAO will receive ICP back or NTN neurons.

3) Your DAO can assign a delegate with hotkey or fully control NTN neurons with generic proposals.  



Invitation to invest in Neutrinite DAO


  # Upgrade user_index

  ## New Features
- upgrade fleet of canister using streaming futures ([#217](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/217) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade post_cache

  ## New Features
- upgrade fleet of canister using streaming futures ([#217](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/217) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade configuration

  ## New Features
- upgrade fleet of canister using streaming futures ([#217](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/217) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade user_index

  ## New Features
- add parameter to stop and resume upgrades ([#219](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/219) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade post_cache

  ## New Features
- add parameter to stop and resume upgrades ([#219](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/219) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade configuration

  ## New Features
- add parameter to stop and resume upgrades ([#219](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/219) by [ravibazz](https://github.com/ravibazz))
  

I'm making this proposal as a concern member of the ICP community who is passionate about the success of projects within the ecosystem and who is also concern about the interest of investors that are supporting these projects with their hard earned money.

Since the end of Hot or Not SNS sale, what I expected from the team is for their first proposal to be about adding LP to Dexes inoder to make the token tradable for both small investors and whales but the team ignore doing this and I have made several post on X about this of which the team ignore them all and same team have made numerous proposals to withdraw ICP and tokens from the treasury solely for the benefits of the team and I don't know why they continue to ignore their investors and all ICP community members that help shilled their project to success and I believe actions like this will continue to discourage investors in participating in SNS projects.

In view of this, I'm making this proposal to add LP from the treasury of Hot or Not to Sonic Dex, which will help the token to be more tradable to all and sundry.

Following the success of this proposal, I will submit 2 additional proposals to apply for the transfer of 50,000 ICP which is less than 5% of the ICP raised through SNS swap and 25 million HOT tokens, respectively from the HOT OR NOT DAO treasury to the ICP/HOT Swap canister owned by Sonic Dex (https://app.sonic.ooo/)

> Submitted by [@ICP_Insider](https://oc.app/user/riafv-fyaaa-aaaaf-adriq-cai) on [OpenChat](https://oc.app/group/qpj6u-uyaaa-aaaar-aq6mq-cai)

Proposal to Add Liquidity on Sonic Dex

Dear HotOrNot community!

We genuinely appreciate the passion and enthusiasm you bring to the Hot or Not (SNS) project. Your engagement is the heartbeat of our community, and your opinions and suggestions are invaluable to us.

Recently, there has been a groundswell of interest in adding liquidity to various ICP Decentralized Exchanges (DEXs) such as Sonic, ICP Swap, and ICDEX. We understand and respect your eagerness to see Hot or Not thrive, and we want to assure you that your concerns have not fallen on deaf ears.

As a team, we are committed to fostering transparency, collaboration, and long-term success for Hot or Not and the entire Internet Computer Protocol (ICP) ecosystem. We have carefully considered your requests to add liquidity to DEXs at this juncture and wanted to share our perspective on why we believe it's in the best interest of the community to wait.

The core development team has been working tirelessly on a strategic plan that includes listing the HOT token on major Centralized Exchanges (CEXs) like Binance, Kraken, Coinbase, among others. We firmly believe that this approach will not only attract a broader audience of investors but also lead to healthier liquidity and more accurate price discovery.

Listing on CEXs first will open up Hot or Not to a global audience, bringing in a diverse range of investors and contributors. This wider participation is crucial for establishing a robust ecosystem that benefits everyone involved. While we understand the urgency many of you feel, listing on DEXs right now may limit the potential growth and will lead to inaccurate price discovery, which will hamper the listing process while devaluing the token price while also limit the exposure we can achieve in the larger cryptocurrency landscape.

We kindly ask for your patience and support during this crucial period. We believe that with your understanding and trust, we can work together to make Hot or Not a significant player in the crypto space. The development team is committed to expediting the process, and we aim to have the HOT token listed on CEXs within the next 4 to 6 months.

As the Hot or Not Dev Team, we are aware of the pressures from certain community members and individuals with varied interests who might seek to tarnish the reputation and brand of Hot or Not. A quick examination of other SNS projects and their management of treasuries reveals that, as one of the early SNS projects, Hot or Not has diligently safeguarded its treasury with honesty and vigor. Our treasury remains one of the most robust, shielded from those who aim to profit at the expense of the community or their own projects.

We want to caution our community members to be discerning and vigilant in the face of potential false narratives being circulated by these elements. Please rely on information only from our official channels before making decisions. As a community, we are stronger when united against misinformation, and we are committed to providing you with accurate and timely updates.

Your passion for Hot or Not is inspiring, and we value your input. Let's work together to build a strong foundation for Hot or Not and the ICP ecosystem as a whole. We are all in this journey together, and with your support, we are confident that the benefits will be felt by each and every member of our community.

Thank you for your dedication, understanding, and ongoing commitment to the success of Hot or Not.

Please Note: The HotOrNot team would not be voting on this proposal. The result of this motion proposal would be adopted and executed by the team as soon as possible.

> Submitted by [@saikatdas0790](https://oc.app/user/3f3q7-giaaa-aaaaf-aatrq-cai) on [OpenChat](https://oc.app/group/qpj6u-uyaaa-aaaar-aq6mq-cai)

Should HotOrNot refrain from adding liquidity to DEXes at this moment and stay committed to our initial vision?

After I initiated a proposal yesterday for liquidity to be added to Dex for proper trading of HOT tokens, an unposing proposal has been created that is well disguise in confusing the community on how to vote that will be in their overall interest rather than the interest of the team.

A simple summary of this proposal is about the DAO to refrain from adding liquidity to DEXs and wait for the next 4 to 6 months when the team will be able to list on CEXs. They listed A list CEX that they will work in getting listed in any of them, which will be very hard for them to do.

A list exchange like Binance charges huge funds of which Hot or Not DAO won't be able to pay. Though some of these exchanges do list tokens for free without charging the project but such a project will have a good reputation, community engagement, product traction, market makers, and arbitrage opportunities; Hot or Not don't have any of these and don't see it having them in the next few months.

The best thing for the DAO to do is to add liquidity to DEXs within the ICP ecosystem and leave the token to be freely traded by its holders, which will help it in price discovery the way other SNS projects did.

Anything less than adding liquidity to DEXs will not be in the best interest of holders of the tokens, and I'm persuading Hot or Not DAO members to massively vote individually to support this proposal to add liquidity in one or more DEXs in the ICP ecosystem. Hot or Not devs and team members should kindly abstain from voting in this proposal if they're truly sincere to their community.

> Submitted by [@ICP_Insider](https://oc.app/user/riafv-fyaaa-aaaaf-adriq-cai) on [OpenChat](https://oc.app/group/qpj6u-uyaaa-aaaar-aq6mq-cai)

Add Liquidity to Dexes and CEX later with Initial Vision

In reply to the increased number of spam proposals, the Hot Or Not DAO community urges the Hot Or Not Developer team to change the Proposal Reject Cost to 1,000 HOT tokens to combat spam from known spammers and to align parameters more closely to other DAO's on the SNS that have higher reject fees.

> Submitted by [@AlphaDog](https://oc.app/user/r5szg-lyaaa-aaaaf-ae2pa-cai) on [OpenChat](https://oc.app/group/qpj6u-uyaaa-aaaar-aq6mq-cai)

Increase Proposal Reject Cost to 1,000 HOT tokens


  # Upgrade user_index

  ## New Features
- nsfw flag in posts ([#208](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/208) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade post_cache

  ## New Features
- nsfw flag in posts ([#208](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/208) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade configuration

  ## New Features
- nsfw flag in posts ([#208](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/208) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade user_index

  ## New Features
- upgrade user_index with generic proposal to reset canisters and use semver version([#224](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/224) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade post_cache

  ## New Features
- upgrade user_index with generic proposal to reset canisters and use semver version([#224](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/224) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade configuration

  ## New Features
- upgrade user_index with generic proposal to reset canisters and use semver version([#224](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/224) by [ravibazz](https://github.com/ravibazz))
  

This will reset given canisters and install the latest wasm module

Add a new custom SNS function to Reset Individual User Canisters

This proposal executes generic functions to reset corrupt canisters.

Execute generic functions for reset corrupt canister.


  # Upgrade user_index

  ## New Features
- remove configuration dependency from user index ([#230](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/230) by [ravibazz](https://github.com/ravibazz))

## Bugfixes
- repl test to include nsfw field in post ([#226](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/226) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade post_cache

  ## New Features
- remove configuration dependency from user index ([#230](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/230) by [ravibazz](https://github.com/ravibazz))

## Bugfixes
- repl test to include nsfw field in post ([#226](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/226) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade configuration

  ## New Features
- remove configuration dependency from user index ([#230](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/230) by [ravibazz](https://github.com/ravibazz))

## Bugfixes
- repl test to include nsfw field in post ([#226](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/226) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade user_index

  ## New Features
- drop known_principal_ids from user_index canister ([#231](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/231) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade post_cache

  ## New Features
- drop known_principal_ids from user_index canister ([#231](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/231) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade configuration

  ## New Features
- drop known_principal_ids from user_index canister ([#231](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/231) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade user_index

  ## Other Changes
- add post cache filters ([#238](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/238) by [psykomal-baz](https://github.com/psykomal-baz))
  


  # Upgrade post_cache

  ## Other Changes
- add post cache filters ([#238](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/238) by [psykomal-baz](https://github.com/psykomal-baz))
  


  # Upgrade configuration

  ## Other Changes
- add post cache filters ([#238](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/238) by [psykomal-baz](https://github.com/psykomal-baz))
  

**Proposal Summary:**

This proposal seeks a routine top-up of 8000 ICP for cycle maintenance to ensure the uninterrupted operation of HotorNot's top-level and user canisters.

Routine top-ups of cycles are essential for sustaining our 52,000+ user canisters. Additionally, we intend to provision 3-4 more subnets and activate approximately 20k canisters across each of these subnets to scale further. This initiative will necessitate an initial load of cycles.

**Conclusion:**

Approval of this routine top-up proposal is necessary to ensure the continuous operation and scalability of HotorNot.

Transfer 8,000 ICP for Cycle Maintenance


  # Upgrade user_index

  ## Other Changes
- added sns submodule ([#247](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/247) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade post_cache

  ## Other Changes
- added sns submodule ([#247](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/247) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade configuration

  ## Other Changes
- added sns submodule ([#247](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/247) by [ravibazz](https://github.com/ravibazz))
  

Upgrade the SNS canisters to the next verstion. This proposal will deploy a maintenance upgrade from August 2023 for the swap canister.

Upgrade swap canister to next version


  # Upgrade user_index

  ## Other Changes
- Feat/platform orchestrator stage 2 ([#245](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/245) by [ravibazz](https://github.com/ravibazz))
  


  # Upgrade post_cache

  ## Other Changes
- Feat/platform orchestrator stage 2 ([#245](https://github.com/go-bazzinga/hot-or-not-backend-canister/pull/245) by [ravibazz](https://github.com/ravibazz))
  

The purpose of this proposal is to transition HotorNot from a single-subnet architecture to a multi-subnet architecture on the Internet Computer blockchain.
### Background:
HotorNot has been built upon the Internet Computer Protocol (ICP) blockchain with a unique architecture where each user is allocated a dedicated canister, managed within a single subnet. This architecture has served us well in our initial stages of growth, providing stability and reliability to our users.
### Moving Towards Multi-Subnet Architecture:
To accommodate our expanding user base and enhance the resilience of our platform, we are now moving towards a multi-subnet architecture. In this new setup, user-canisters will be distributed across multiple subnets, with each subnet having its own set of user-indexes.
### Introducing the Platform Orchestrator:
To efficiently manage the allocation and maintenance of user-canisters across multiple subnets, we have developed a Platform Orchestrator. This orchestrator will be responsible for assigning new users to subnets based on the availability of user-indexes within each subnet.
### Proposal: Transferring Ownership of User-Indexes:
In line with our transition to a multi-subnet architecture, we are submitting a proposal to transfer the ownership of user-indexes from the HotorNot SNS DAO to the Platform Orchestrator canister. This transfer of ownership will empower the Platform Orchestrator to effectively manage user allocation and ensure the seamless operation of the platform in the new architecture.
### Next Steps: 
Once we have thoroughly tested the multi-subnet architecture and addressed any bugs or issues, and once we are confident that the Platform Orchestrator is performing as expected, the ownership of the Platform Orchestrator will be transferred to the HotorNot SNS DAO.

As we embark on this exciting journey towards a multi-subnet architecture, we remain steadfast in our commitment to innovation, scalability, and the continued growth of HotorNot.

Transitioning HotorNot SNS to a Multi-Subnet Architecture: Proposal for User-Index Ownership Transfer

Deploy a maintenance upgrade for the SNS token ledger index canister.

Upgrade SNS token ledger index to next version

## Proposal Summary:
The last budgetary proposal for funding the day-to-day operations of HotorNot was submitted on 26 September 2023 (the SNS Sale was completed on 12 July 2023) and was expected to cover the expenses for a period of 3 months between Q3 and Q4 2023. We have managed to sustain the operations for the last 7 months (instead of the designated 3 months) by prudent management of these funds. No budgetary proposal has been submitted for Q1 2024.

We are putting up a budgetary proposal for H1 2024 for the withdrawal of 96,000 ICP. We are extending the funding period for this proposal to a period of 6 months (from the earlier 3 months), in view of the increased team size, continued growth hiring plans, and the flexibility required (including a longer runway) as we gear up for an upcoming high-growth trajectory, owing to the scalable multi-subnet architecture and increased marketing efforts.

## Detailed Rationale for Extension:

1. **Increased Developer Requirements:** The evolving scope of our projects necessitates a larger development team. We have onboarded new Rust developers and plan to bring on additional developers, to enhance the robustness and efficiency of our platform.
2. **Elevated Legal Costs:** Our anticipated legal costs have increased due to the complexity of compliance, regulatory matters, contractual obligations, and the need for specialized legal services.
3. **Flexibility for High-Growth Operations:** As a rapidly evolving startup, extended funding for a longer runway allows us the flexibility to adapt and pivot operations based on emerging opportunities and challenges. This agility is crucial for sustained growth and market responsiveness.
4. **Shift to Rust Development:** Recognizing the benefits of Rust for our specific requirements, we propose allocating funds for Rust developers, benefitting long-term performance and scalability.
5. **Favorable Market Prices:** The favorable movement of the current market price of ICP provides a unique opportunity to secure more funds at a lower cost, optimizing our financial resources for an extended development period.

## Revised Budget Breakdown:

### **1. Team Salaries:**

- 10 Core Developers (including Rust developers)
- 2 AI Developer
- 1 Product Manager
- 1 UX/UI Designer
- 4 Social Media/Community Managers
- 2 HR Manager
- 1 Finance Manager

### **2. Incorporation Fees and Foundation Fees:**

- Legal incorporation of Hot or Not non-profit Foundation
- IP protection costs

### **3. HR/Operations:**

- Operational expenses, including increased HR-related costs and administrative overhead.

### **4. Legal Fees:**

- Compliance, regulatory matters, contractual obligations, and employment contracts.
- Additional budget for heightened legal complexity.

### **5. Third-Party Services:**

- Costs related to third-party tools, technologies, and services necessary for seamless operation.

### **6. Marketing:**

- Marketing campaigns, advertising, and promotional activities for extended visibility and user base growth.

## Updates on Quarter 4, 2023 Efforts:

1. **Multi-Subnet Architecture:**
    - **Progress:** We have moved towards a multi-subnet architecture. In this new setup, user-canisters will be distributed across multiple subnets and our Platform Orchestrator will dynamically provision canisters across subnets. (Refer to the [Proposal 85](https://dashboard.internetcomputer.org/sns/67bll-riaaa-aaaaq-aaauq-cai/proposal/85))
    - **Next Steps:** Given the proposal for the implementation of the same has been accepted, we will test thoroughly test the architecture and address any bugs and issues.
2. **Content Gamification - "Up/Down" Game:**
    - **Progress:** Successful launch as a separate experimental website, with ongoing community engagement for improvements.
    - **Next Steps:** Allocate resources for continuous iterations and prepare for integration into the HotOrNot gaming ecosystem.
3. **N-Phones NFT Game:**
    - **Progress:** On reopening of the sign-ups, the game mechanics would be finalized and gamification renamed to “Creator DAOs”. (More information to follow soon)
4. **Mobile App Development/Progressive Web App:**
    - **Progress:** Pivoted to enhancing the progressive web app for accessibility and seamlessness, including a one-step authentication system and Rust frontend development for a better user experience.
    - **Next Steps:** Continue web app improvements, allocate resources for optimization projects, and reevaluate mobile app development based on user feedback.
5. **Social Ecosystem:**
    - **Progress:** Features such as the leaderboard, gamification, and profile enhancements are ready for deployment.
    - **Next Steps:** Prepare for the seamless rollout of social features after sign-ups open up. Allocate resources for community engagement and support during onboarding.

## Additional Initiatives Taken in Quarter 4, 2023:

1. **Authentication System:** Enables faster onboarding to the app and ICP ecosystem. (Details to be announced soon).
2. **Transition to Stable Memory:** Improvements in canister upgrade management by starting the transition from heap memory to stable memory.
3. **Rust Video Player Exploration:** We spearheaded a pioneering engineering endeavor by rebuilding our front end entirely in Rust, using leptos, a first on the ICP platform. This initiative aims to revolutionize user experience with breakthrough performance, enhanced stability, and improved functionalities, leveraging Rust's memory safety, performance optimization, and cross-platform compatibility advantages. The initial results are very promising and are comparable (faster in some cases) to the best Web2 web-based platforms such as Youtube Shorts, TikTok, etc.

## Initiatives for H1, 2024:

1. **Creator Community Building:** Expand HotorNot's ecosystem by actively engaging and onboarding creators through community events and outreach programs. A small production house/creator house is also been set-up in India to facilitate new and upcoming creators to create original content for the platform. The aim is to foster connections, enhance content diversity, and attract a wider audience.
2. **AI Recommendation System:** We have initiated candidate generation as the initial step for training Machine Learning models using user embeddings and content embeddings to deliver personalized feed for each user on the platform. This is taking some effort owing to the challenges involved in collecting private user data crucial for initializing these models, especially in overcoming the hurdles related to the cold start problem.
3. **Moderation and Dual Feeds:** Implement a moderation system based on user tagging to create a safe content environment. Introduce dual feeds for a personalized content consumption experience, aligning with the platform's commitment to a customizable and inclusive user interface.
4. **Revamp UI:** Enhance the visual appeal, navigation, and usability of HotorNot's platform through a UI revamp. We have been reaching out to our active users to get real-time feedback on the usage of the platform. This user feedback would be incorporated, along with industry best practices to create a more intuitive and enjoyable user experience.
5. **Rebrand:** Undertake a comprehensive rebranding effort to reflect HotorNot's growth, values, and dynamic community. Branding agencies has been onboarded, along with user feedback to rebrand the platform. (More information to follow soon)
6. **Legal Incorporation of Swiss Foundation:** Initiated the legal incorporation of a Swiss Foundation for a stable and reputable legal framework in Switzerland for abled governance of the DAO (on the same lines as Dfinity Foundation). This move aligns with transparency and regulatory adherence, contributing to HotorNot's long-term stability and credibility.
7. **Enhanced Gamification:** Build on the initial success of the "Up/Down" game experiment by introducing and experimenting with new enhanced gamification elements. This initiative aims to keep users entertained and motivated, contributing to an immersive and rewarding user experience. (More information to follow soon)
8. **Addition of Notifications:** Introduce a comprehensive notification system, including push notifications and alerts, to keep users informed about new content and platform updates. This aims to increase user engagement and retention with a dynamic and interactive experience.
9. **Explore Comments and Direct Messaging on Video Feed:** Foster deeper connections among users by exploring the introduction of comments and direct messaging features tailored for video content (exploring all options including integration with external providers such as OpenChat, etc.). This initiative aims to facilitate discussions, feedback, and collaboration within the community.

## Conclusion:

We appreciate your consideration and support in securing the resources needed to propel HotorNot to new heights.

In conclusion, these initiatives collectively demonstrate HotorNot's commitment to innovation, user satisfaction, and sustainable growth in H1 2024. The platform seeks to leverage technology, community engagement, and strategic partnerships to solidify its position in the market and deliver a compelling and evolving user experience.

HotorNot DAO Proposal for Extended Funding (H1 2024)

Maintenance upgrade from August 2023 for the SNS token ledger archive canister.

Upgrade SNS ledger archive

Deploy a maintenance upgrade from August 2023 to the SNS token ledger canister.

Upgrade SNS ledger canister

The changes in this upgrade mainly affect the decentralization swap and are thus not important to HotOrNot. As all SNS canister upgrades are applied in sequence, though, this upgrade has to execute before subsequent ones can go in.

Upgrade SNS swap canister

The upgrade fixes several bugs in the SNS governance canister: (1) add a check for maturity modulation when spawning a neuron, (2) ensure tallies are updated upon votes even when the proposal is executed, (3) disallow top-up of neurons' fund neurons.

Upgrade SNS governance canister

This is a resubmission of [proposal 92](https://dashboard.internetcomputer.org/sns/67bll-riaaa-aaaaq-aaauq-cai/proposal/92), which failed due to a low cycle balance of the swap canister.

Deploy a maintenance upgrade from October 2023 to the root canister.

Upgrade SNS root canister

Maintenance upgrade from October 2023 for the SNS swap canister.

This upgrade for the swap canister enables matched funding during the decentralization swap. This change is only relevant for new SNSs. As all SNS canister upgrades have to be applied in sequence, however, this upgrade has to be performed before subsequent ones.

The proposal involves transferring ownership of the Platform Orchestrator, which manages user indexes across multiple subnets for the Yral App, from the development team to the HotorNot SNS DAO. This transfer is seen as necessary to ensure decentralized control over the Yral platform.
#### Background:
The Yral App (previously HotorNot) has transitioned to a multi-subnet architecture to handle a growing user base and improve platform resilience. The Platform Orchestrator was developed to manage user-canisters across these subnets and has proven effective in maintaining platform operations within this architecture.
#### Proposal Details
1. Transfer of Ownership: The ownership of the Platform Orchestrator canister, currently held by the development team, will be transferred to the HotorNot SNS DAO.
2. Governance Integration: Upon ownership transfer, the HotorNot SNS DAO will assume full control and governance responsibilities over the Platform Orchestrator. This includes decision-making authority regarding updates, modifications, and overall management of the orchestrator.
3. Verification and Validation: Following the ownership transfer, thorough verification and validation procedures will be conducted to ensure the seamless integration of the Platform Orchestrator under DAO governance. Any issues or discrepancies identified during this phase will be promptly addressed and resolved.

As we move towards decentralizing control over our platform, we reaffirm our commitment to transparency, community empowerment, and the continued growth of HotorNot SNS.

 Ownership Transfer of Platform Orchestrator to HotorNot SNS DAO

The crypto market is currently in the midst of a bull run, with the markets being significantly buoyant over the last 4-5 months. The bull run in the blockchain markets is typically followed by a bear run, lasting a daunting 2-3 years (as witnessed post the bull run in 2017 and 2021). The bear run is marred with significant market risks, which can result in erosion of the value locked in ICP held in the treasury. This fund is strategically designed to counteract these inherent market risks that we might face during bear run in the blockchain markets, periods that can potentially last for 2-3 years.

In recent months, our project has witnessed significant growth, accompanied with the expansion of the team, since the SNS Decentralization Sale. To maintain this momentum, we have set ambitious plans in place to further expand our team in the future. This expansion is designed to support and facilitate the continued growth of the project.

However, we are cognizant of the fact that expansion also brings with it increased financial obligations. These obligations, paired with the inherent volatility of the blockchain market, add an element of risk to our project. Keeping these factors in mind, we believe that the creation of a backup fund is not only a strategic move but also a necessary one.

By establishing this backup fund, we can ensure that we have the necessary resources to maintain operations and continue development, even during a challenging bear market. This proactive approach is expected to strengthen our project's financial stability. Furthermore, it will likely increase investor confidence as they see that we are prepared and equipped to handle market fluctuations.

Hence, we are submitting a proposal for the withdrawal of 150,000 ICP from the DAO Treasury to establish a resilience fund as a financial backup for the project. We are going to divide this proposal in 2 parts to ensure compliance with the rules set forth for the SNS DAOs by the Internet Computer Community. The first proposal would be put up for the withdrawal of 86,500 ICP and the remaining 63,500 ICP would be withdrawn in the second proposal.

We firmly believe that this proposal is a prudent and strategic step towards managing market risks. It not only serves the immediate needs of our project but also ensures its long-term sustainability. We look forward to your support in this endeavor, as we work together to strengthen the project.

Title
DOLR AI Treasury Proposal Q2 2026 - Part ...	16 Jun, 2026	17 Jun, 2026	Active	2,813.196t	357519443489809.06
Upgrade platform_orchestrator to v10	7 Jun, 2026	11 Jun, 2026	Defeated	43.933t	4366764035917.61
Upgrade platform_orchestrator to v9	7 Jun, 2026	11 Jun, 2026	Defeated	43.933t	4366791008072.24
DOLR AI Treasury Proposal Q2 2026 - Part ...	1 Jun, 2026	6 Jun, 2026	Executed	43.955t	10647338344388.01
Upgrade platform_orchestrator to v8	21 May, 2026	25 May, 2026	Executed	43.926t	10580940727165.36
Upgrade platform_orchestrator to v3	20 May, 2026	20 May, 2026	Executed	43.925t	8461715622223.66
Upgrade platform_orchestrator to v2	20 May, 2026	20 May, 2026	Defeated	43.925t	8469887571283.89
Upgrade platform_orchestrator to v1	20 May, 2026	20 May, 2026	Defeated	43.925t	8469887786773.29
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.925t	8462520709187.42
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.925t	8462502253058.74
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.925t	8462493090779.21
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.925t	8462465780989.50
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.925t	8462452048635.77
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.924t	8462323536572.66
Upgrade Canister user_index	20 May, 2026	20 May, 2026	Executed	43.924t	8462930934092.99
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.924t	8462305433959.21
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.924t	8427223185777.40
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.924t	8462260077839.08
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.923t	8461965644806.54
Upgrade Canister user_index	20 May, 2026	20 May, 2026	Executed	43.923t	8462123320496.48
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.923t	8461949013860.33
Upgrade platform_orchestrator	20 May, 2026	20 May, 2026	Executed	43.923t	8461848240280.59
Upgrade Canister individual_user_template...	19 May, 2026	19 May, 2026	Executed	43.922t	8461644741953.30

DOLR AI

Activity

Max Votes

Activity

Max Votes