Proposal “Consensus-Hong-Kong-2026-DevRel-BD“ (Active)Back
| Title: | Consensus Hong Kong 2026 + Developer relations + Business development |
| Owner: | ravenor |
| One-time payment: | 175 DASH (6584 USD) |
| Completed payments: | no payments occurred yet (1 month remaining) |
| Payment start/end: | 2026-01-06 / 2026-02-05 (added on 2026-01-11) |
| Final voting deadline: | in 1 month |
| Votes: | 18 Yes / 5 No / 0 Abstain |
| Will be funded: | No. This proposal needs additional 313 Yes votes to become funded. |
|
Manually vote on this proposal (DashCore - Tools - Debugconsole): gobject vote-many dbc3fdd467fec94b0205dff9165283917c900b4f1cf41fc89f5f7be651becc49 funding yes Please login or create a new DashCentral account for comfortable one button voting! | |
Proposal description
Disclaimer
Dash now takes a substantial part of both my and Yarik’s time. Please read this proposal carefully until the end - it includes progress and results from the previous proposal. Each part is important and represents a connected piece of ongoing work for the Dash ecosystem.
Part 1. Conference attendance - Consensus Hong Kong (February)
https://consensus-hongkong.coindesk.com
In February, I plan to attend Consensus Hong Kong. As with previous conferences, my focus will be direct, on-the-ground engagement.
I will spend time at project booths and side events, connecting with key speakers and representatives where a relationship is relevant for Dash. Depending on who I meet, conversations usually focus on one of three areas: Dash as a payment solution, Dash Platform, or the broader Dash ecosystem. This varies by audience - potential integration partners, developers, influencers, community organizers, traders, and other ecosystem participants.
I also have a specific task from Joel to meet with existing Dash partners at the conference, maintain ongoing relationships, share recent Dash updates, and explore opportunities for co-marketing where appropriate.
Throughout the conference, I represent Dash in official Dash merchandise, engage with media present at the venue, and give interviews when opportunities arise. I actively document Dash’s presence through photos and content created during the event.
This content is shared both on my personal social channels and on Dash social platforms. This is important for two reasons: first, Dash community channels benefit from real, authentic content rather than only generated visuals; second, external audiences can clearly see that Dash remains active, visible, and engaged alongside other major players in the industry.
Part 2. DevRel support for the pshenmic team
Another part of my work is focused on developer relations and visibility for the pshenmic team. I regularly share their development progress and technical results on my social channels and help distribute this content through Dash’s global community channels.
I also invite Mikhail to participate in joint public appearances and AMA sessions about Dash in Russian-speaking (CIS) communities. These sessions focus on explaining ongoing development, recent updates, and technical direction in a clear and accessible way.
In parallel, I am currently supporting the hiring process for a frontend developer position for the pshenmic team. The vacancy has received 158 applications so far. I am handling the initial screening and resume review, communicating with candidates about the specifics of working within Dash and a DAO-based structure, shortlisting suitable profiles, and passing them to Mikhail. I also assist with interview coordination.
Part 3. Community Engagement and Ecosystem Communication
I actively participate in the life and development of the Dash community on an ongoing basis.
I regularly engage with the global Dash community, especially on X (Twitter) together with Joel during Dash spaces, answer questions from community members (including direct messages - I am listed as an admin in the global Dash Telegram chat), and consistently share Dash-related content across my social channels (X, Instagram, Facebook, LinkedIn), not limited to conference activity.
For the Russian-speaking Dash community, we have planned a bi-weekly live format where members of the pshenmic team and I (and other Russian-speaking contributors when available) will explain, in clear and accessible language, what is currently happening in Dash - including ecosystem updates, development progress, and important changes.
Given the size of the Russian-speaking Dash community, this initiative is expected to significantly improve awareness, understanding, and engagement with ongoing developments across the ecosystem.
Part 4. Business Development
Conference participation consistently generates a large number of new contacts and potential Dash-related initiatives. These opportunities do not convert automatically - they require structured B2B follow-up and ongoing negotiations, which I manage directly, involving Joel where relevant.
In parallel, inbound leads have also started coming through my social media activity, as I regularly write and share content about Dash across multiple platforms.
Because Dash has a non-standard structure (there is no traditional company entity for KYB), business development discussions are often more complex. Partners frequently request additional context and documentation, much of which has not existed in a consolidated form before and therefore needs to be gathered and clarified during the process. This makes the work more time-intensive and requires sustained follow-up beyond conferences.
To make this work more systematic - especially in the area of listings and exchanges - I have started structuring this process together with Joel. We now maintain a shared table covering major exchanges: where Dash is already listed, where it is not, and where re-listing discussions may be relevant. LINK
For exchanges where Dash is not listed, we actively look for direct contacts and explore listing opportunities, even though listings are often paid. In parallel, for exchanges where Dash is already listed, we proactively reach out to re-establish communication and identify marketing or listing teams we can work with.
Our focus here is co-marketing wherever possible. This allows Dash to gain visibility through joint announcements and activities with exchanges without requiring large marketing budgets. In most cases, this is a win-win approach for both sides and one of the most cost-efficient growth channels available to the Dash ecosystem.
Finally, I’d like to note that this work is not done by Daria Chernozub alone. Yaroslav (Ravenor) is deeply involved as well - handling a large part of the organizational and operational work. Even though he does not attend conferences, the volume of work outside of events has grown significantly and we are working on all of this together as a team.
Regarding the Ambassador Program: I will also be submitting a separate pre-proposal for it. At the moment, I am calculating the budget, as the landscape has changed since I last ran an ambassador program two years ago. Some platforms are no longer active, while new and more relevant ones have emerged (Kaito.ai Guild.xyz layer3.xyz galxe.com zealy.io). I am currently in contact with these platform teams to clearly understand placement options and pricing before finalizing the budget.
In parallel, we are reviewing how other networks and Web3 projects structure their ambassador programs, including formats and budget ranges, to ensure Dash’s approach remains competitive and aligned with current ecosystem standards.
Progress Update on the Previous Proposal
Key Achievement
As a result of my meeting with Alchemy Pay at the conference, we have reached a partnership agreement. A joint announcement is currently in preparation. The partnership includes Dash integrations across multiple services within the Alchemy Pay ecosystem.
Additionally, contacts have been established and active communication is ongoing with the following partners and communities:
• CoinMarketCap - discussions around co-marketing and increasing Dash visibility on the CMC platform
• CoinW and MEXC - exchanges where Dash is already listed; currently discussing co-marketing opportunities
• Friendly relationships established with Trust Wallet, Circle (USDC), and 1inch
• Agreements reached for interviews and AMA sessions about Dash with Loop Space, Techub News, CryptoNewsZ, and TheCoinRepublic
• Connections made with influencers who shared Dash-related stories: Sarvar Rasulev, Amos Tan, and TheBitcoinMan (Instagram)
• Engagement and onboarding support provided to developers interested in Dash Platform and building services within the ecosystem: RateXAI and Arcane
• Became members of the Crypto Hunters community (enabling Dash promotion within the community); additionally, received an invitation to co-host their influencer-focused conference as a supporting brand, with no budget required
• Established connections with the ITMO Web3 community; currently working on a joint proposal for Dash
• Provided support to the ClearSwap service during their Dash integration process, with co-marketing activities planned
• Participated in a live broadcast from the Bitcoin MENA conference and gave an interview to the official media partner, Web3TV
• An AMA session was organized in the KuCoin CIS channel: questions and answers were prepared, Pshenmic was invited, co-marketing was executed, and the AMA was successfully held
Conclusion
Recent Dash price declines have resulted in an approximate $3,000 shortfall across the last two proposals. Expenses are currently covered from personal funds.
Budget:
$3,000 is allocated to cover our work.
$3,000 is allocated as the budget for the Consensus conference in Hong Kong (conference ticket, flight from Koh Phangan, local transportation in Hong Kong, meals for 4 days, hotel stay from February 10 to 13 (3 nights), mobile connection/eSIM).
$500 is reserved to account for Dash volatility (we are in the red after the previous two proposals).
$6500 - 175 DASH
Dash now takes a substantial part of both my and Yarik’s time. Please read this proposal carefully until the end - it includes progress and results from the previous proposal. Each part is important and represents a connected piece of ongoing work for the Dash ecosystem.
Part 1. Conference attendance - Consensus Hong Kong (February)
https://consensus-hongkong.coindesk.com
In February, I plan to attend Consensus Hong Kong. As with previous conferences, my focus will be direct, on-the-ground engagement.
I will spend time at project booths and side events, connecting with key speakers and representatives where a relationship is relevant for Dash. Depending on who I meet, conversations usually focus on one of three areas: Dash as a payment solution, Dash Platform, or the broader Dash ecosystem. This varies by audience - potential integration partners, developers, influencers, community organizers, traders, and other ecosystem participants.
I also have a specific task from Joel to meet with existing Dash partners at the conference, maintain ongoing relationships, share recent Dash updates, and explore opportunities for co-marketing where appropriate.
Throughout the conference, I represent Dash in official Dash merchandise, engage with media present at the venue, and give interviews when opportunities arise. I actively document Dash’s presence through photos and content created during the event.
This content is shared both on my personal social channels and on Dash social platforms. This is important for two reasons: first, Dash community channels benefit from real, authentic content rather than only generated visuals; second, external audiences can clearly see that Dash remains active, visible, and engaged alongside other major players in the industry.
Part 2. DevRel support for the pshenmic team
Another part of my work is focused on developer relations and visibility for the pshenmic team. I regularly share their development progress and technical results on my social channels and help distribute this content through Dash’s global community channels.
I also invite Mikhail to participate in joint public appearances and AMA sessions about Dash in Russian-speaking (CIS) communities. These sessions focus on explaining ongoing development, recent updates, and technical direction in a clear and accessible way.
In parallel, I am currently supporting the hiring process for a frontend developer position for the pshenmic team. The vacancy has received 158 applications so far. I am handling the initial screening and resume review, communicating with candidates about the specifics of working within Dash and a DAO-based structure, shortlisting suitable profiles, and passing them to Mikhail. I also assist with interview coordination.
Part 3. Community Engagement and Ecosystem Communication
I actively participate in the life and development of the Dash community on an ongoing basis.
I regularly engage with the global Dash community, especially on X (Twitter) together with Joel during Dash spaces, answer questions from community members (including direct messages - I am listed as an admin in the global Dash Telegram chat), and consistently share Dash-related content across my social channels (X, Instagram, Facebook, LinkedIn), not limited to conference activity.
For the Russian-speaking Dash community, we have planned a bi-weekly live format where members of the pshenmic team and I (and other Russian-speaking contributors when available) will explain, in clear and accessible language, what is currently happening in Dash - including ecosystem updates, development progress, and important changes.
Given the size of the Russian-speaking Dash community, this initiative is expected to significantly improve awareness, understanding, and engagement with ongoing developments across the ecosystem.
Part 4. Business Development
Conference participation consistently generates a large number of new contacts and potential Dash-related initiatives. These opportunities do not convert automatically - they require structured B2B follow-up and ongoing negotiations, which I manage directly, involving Joel where relevant.
In parallel, inbound leads have also started coming through my social media activity, as I regularly write and share content about Dash across multiple platforms.
Because Dash has a non-standard structure (there is no traditional company entity for KYB), business development discussions are often more complex. Partners frequently request additional context and documentation, much of which has not existed in a consolidated form before and therefore needs to be gathered and clarified during the process. This makes the work more time-intensive and requires sustained follow-up beyond conferences.
To make this work more systematic - especially in the area of listings and exchanges - I have started structuring this process together with Joel. We now maintain a shared table covering major exchanges: where Dash is already listed, where it is not, and where re-listing discussions may be relevant. LINK
For exchanges where Dash is not listed, we actively look for direct contacts and explore listing opportunities, even though listings are often paid. In parallel, for exchanges where Dash is already listed, we proactively reach out to re-establish communication and identify marketing or listing teams we can work with.
Our focus here is co-marketing wherever possible. This allows Dash to gain visibility through joint announcements and activities with exchanges without requiring large marketing budgets. In most cases, this is a win-win approach for both sides and one of the most cost-efficient growth channels available to the Dash ecosystem.
Finally, I’d like to note that this work is not done by Daria Chernozub alone. Yaroslav (Ravenor) is deeply involved as well - handling a large part of the organizational and operational work. Even though he does not attend conferences, the volume of work outside of events has grown significantly and we are working on all of this together as a team.
Regarding the Ambassador Program: I will also be submitting a separate pre-proposal for it. At the moment, I am calculating the budget, as the landscape has changed since I last ran an ambassador program two years ago. Some platforms are no longer active, while new and more relevant ones have emerged (Kaito.ai Guild.xyz layer3.xyz galxe.com zealy.io). I am currently in contact with these platform teams to clearly understand placement options and pricing before finalizing the budget.
In parallel, we are reviewing how other networks and Web3 projects structure their ambassador programs, including formats and budget ranges, to ensure Dash’s approach remains competitive and aligned with current ecosystem standards.
Progress Update on the Previous Proposal
Key Achievement
As a result of my meeting with Alchemy Pay at the conference, we have reached a partnership agreement. A joint announcement is currently in preparation. The partnership includes Dash integrations across multiple services within the Alchemy Pay ecosystem.
Additionally, contacts have been established and active communication is ongoing with the following partners and communities:
• CoinMarketCap - discussions around co-marketing and increasing Dash visibility on the CMC platform
• CoinW and MEXC - exchanges where Dash is already listed; currently discussing co-marketing opportunities
• Friendly relationships established with Trust Wallet, Circle (USDC), and 1inch
• Agreements reached for interviews and AMA sessions about Dash with Loop Space, Techub News, CryptoNewsZ, and TheCoinRepublic
• Connections made with influencers who shared Dash-related stories: Sarvar Rasulev, Amos Tan, and TheBitcoinMan (Instagram)
• Engagement and onboarding support provided to developers interested in Dash Platform and building services within the ecosystem: RateXAI and Arcane
• Became members of the Crypto Hunters community (enabling Dash promotion within the community); additionally, received an invitation to co-host their influencer-focused conference as a supporting brand, with no budget required
• Established connections with the ITMO Web3 community; currently working on a joint proposal for Dash
• Provided support to the ClearSwap service during their Dash integration process, with co-marketing activities planned
• Participated in a live broadcast from the Bitcoin MENA conference and gave an interview to the official media partner, Web3TV
• An AMA session was organized in the KuCoin CIS channel: questions and answers were prepared, Pshenmic was invited, co-marketing was executed, and the AMA was successfully held
Conclusion
Recent Dash price declines have resulted in an approximate $3,000 shortfall across the last two proposals. Expenses are currently covered from personal funds.
Budget:
$3,000 is allocated to cover our work.
$3,000 is allocated as the budget for the Consensus conference in Hong Kong (conference ticket, flight from Koh Phangan, local transportation in Hong Kong, meals for 4 days, hotel stay from February 10 to 13 (3 nights), mobile connection/eSIM).
$500 is reserved to account for Dash volatility (we are in the red after the previous two proposals).
$6500 - 175 DASH
Show full description ...
Discussion: Should we fund this proposal?
Submit comment
|
No comments so far?
Be the first to start the discussion! |
I welcome a more healthy split between Development / Marketing & PR / Other, through proposed budget proposals in the Dash DAO.