Welcome!

Proposal owner:
Marina Siradeghyan
X - https://x.com/dashygrl
Discord - Marine5001
t.me/pfeffa

This initiative is designed to complement, rather than duplicate, the ecosystem development work already being led by Daria Chernozub (Web3Daria) and her team.
Daria has established a strong international growth framework for Dash, particularly across APAC and Southeast Asia. Her work combines conference representation, business development, regional community building, developer outreach and educational initiatives.
Marina's would extend this emerging infrastructure into Europe rather than create a separate or competing program. Daria’s experience, existing processes and insights from APAC can provide a tested foundation, while I would adapt these initiatives to the specific characteristics of the European market: its strong university and developer ecosystems, multilingual communities, GDPR-driven approach to data, and complex regulatory environment.

Travel and event expenses:
This proposal seeks funding to establish and maintain an active European developer community around Dash Evolution, also known as Dash Platform.
The objective is not simply to increase short-term brand visibility. It is to build a repeatable developer adoption pipeline:
Awareness → technical interest → hands-on experimentation → continued community participation → applications and ecosystem contributions.

Executive Summary
This proposal establishes a dedicated European adoption function for Dash, with a primary focus on growing the developer ecosystem around Dash Platform and Evolution. Europe represents a particularly strong opportunity: it has one of the world’s largest concentrations of Web3 builders, universities, research institutions and privacy-conscious technology communities. At the same time, GDPR, MiCA and growing concerns around digital sovereignty create demand for infrastructure that supports verifiable data, user-controlled identity, native digital assets and privacy-aware application design. Rather than positioning Dash in Europe primarily as a cryptocurrency, this initiative will present Dash Platform as infrastructure on which developers can build practical Web3 applications.

The work will combine direct participation in European conferences and developer events, university outreach, relationships with experienced Web3 builders, support for hackathons and ambassador initiatives, and continued engagement with projects entering the Dash ecosystem. It will also establish a structured feedback loop between European developers and the wider Dash ecosystem, collecting insights about documentation, SDKs, onboarding, websites and marketing materials and turning them into actionable recommendations. The objective is not simply to generate awareness, but to create a measurable pipeline from initial contact to onboarding, prototype development, long-term ecosystem participation and, where appropriate, grants, integrations or commercial adoption.

This initiative will be developed in close coordination with Daria Chernozub (Web3Daria) and her team, building upon their existing work in international ecosystem development, APAC expansion, regional hubs, conferences, partnerships, hackathons, educational programs and the emerging Dash ambassador framework. Daria’s team has already demonstrated the value of this model through initiatives such as the first Dash Platform hackathon in Malaysia, which produced 11 prototypes from 41 participants, as well as partnerships resulting from sustained conference and business-development activity. My role will be to adapt and extend these foundations into the European market, adding permanent regional ownership, European university and builder relationships, GDPR- and privacy-oriented positioning, and consistent follow-up. Together, these efforts can form a connected global adoption system rather than a series of isolated regional activities.

The work will combine:

• Direct representation of Dash and Evolution at relevant European events;
  
• Cooperation with universities, blockchain research centers and student Web3 organizations;
  
• Direct relationship-building with experienced developers and technical community leaders;
  
• Support for developer-focused initiatives, including an ambassador or contributor program;
  
• Continued support for the existing Dash community;
  
• Collection and communication of developer feedback to the relevant Dash teams.
  

Dash has invested years of development into Evolution. The platform is live, documented and accessible through developer tools and APIs, but it remains significantly underrepresented in European developer circles.
This proposal addresses that distribution gap.

Why This Work Is Needed
Developer adoption does not happen through announcements alone.
Developers normally discover a platform through trusted peers, technical events, university programs, workshops, documentation, practical examples and direct conversations. After the first contact, they need follow-up, access to technical support and a clear path from curiosity to building.
At present, Dash does not have a consistent person responsible for this complete journey in Europe.
As a result:

• Potentially valuable event contacts are not always followed up systematically;
  
• Universities and student blockchain organizations rarely encounter Evolution;
  
• Developers may know Dash only as a payments cryptocurrency;
  
• Feedback from external developers does not consistently reach the teams responsible for the platform, documentation and tooling;
  
• The existing Dash community and the new developer ecosystem are not yet sufficiently connected.
  

The proposed role will create continuity between these activities and turn isolated interactions into an ongoing developer acquisition and retention process.
ObjectivesThe main objectives of the proposal are to:

1. Position Evolution as a credible decentralized application and data platform for European developers;
   
2. Build long-term relationships with universities and technical communities;
   
3. Bring qualified developers into the Evolution ecosystem;
   
4. Create an understandable onboarding path for developers who are new to Dash;
   
5. Support developer-led initiatives and local advocates;
   
6. Maintain active communication with the existing Dash community;
   
7. Produce transparent and measurable results for the Dash network.
   

Scope of Work
1. European Event Representation
I will represent Dash at carefully selected European blockchain, Web3, developer, fintech and open-source events.
The focus will be on events where we can meet developers, technical founders, researchers, student organizations and ecosystem leaders—not only general crypto audiences.
The work will include:

• Selecting events based on their relevance to Evolution;
  
• Seeking speaking, workshop, panel and community-partnership opportunities;
  
• Presenting both the Dash brand and the specific capabilities of Evolution;
  
• Organizing or supporting technical demonstrations and side events;
  
• Holding direct meetings with developers and potential ecosystem partners;
  
• Recording contacts, interests and next steps;
  
• Conducting structured follow-up after every event.
  

Success will not be measured only by attendance or impressions. The primary metrics will be qualified conversations, follow-up meetings, workshop participation and movement toward experimentation with the platform.

2. Cooperation with European Universities
Europe already has a strong network of blockchain research centers, cryptoeconomics institutes, student blockchain associations and university innovation labs.
I will build relationships with professors, researchers, program directors and student-led organizations to create opportunities such as:

• Guest lectures and webinars;
  
• Introductory Evolution workshops;
  
• Technical demonstrations;
  
• Student research and thesis topics;
  
• Hackathons and developer challenges;
  
• Capstone and industry projects;
  
• Collaboration with university blockchain clubs;
  
• Participation in summer schools and academic conferences.
  

Evolution will be presented as a technical case study and development platform, rather than as a token promotion campaign. This makes the outreach more suitable for academic environments and helps create relationships based on education and experimentation.

3. Direct Developer Outreach and Relationship-Building
I will communicate directly with experienced developers, technical founders and developer-community leaders in relevant European ecosystems.
This work will include:

• One-to-one conversations with developers;
  
• Identification of their technical interests, requirements and objections;
  
• Introducing developers to the appropriate Evolution documentation, tools and technical contacts;
  
• Supporting the transition from initial interest to practical experimentation;
  
• Maintaining a structured pipeline of contacts and follow-ups;
  
• Collecting recurring feedback about SDKs, APIs, documentation and developer experience;
  
• Communicating this feedback to Dash Platform engineers and other relevant contributors.
  

This role will not replace engineering or technical support. Its purpose is to create the bridge between external developers, the Dash community and the technical teams capable of answering deeper implementation questions.

4. Developer and Ambassador Initiatives
I will support initiatives that allow developers and local community members to become active contributors rather than passive followers.
Depending on available resources and coordination with existing Dash organizations, this may include:

• A pilot Evolution developer ambassador program;
  
• Local university or city representatives;
  
• Regular developer office hours;
  
• Community workshops and demo sessions;
  
• Educational and onboarding materials;
  
• Small challenges, bounties or prototype programs;
  
• Recognition for active technical contributors;
  
• Support for community-created tutorials, tools and example applications.
  

The program will begin as a limited pilot with clear expectations and measurable activity. The goal is to identify people who can create sustained local impact, not merely recruit a large number of nominal ambassadors.

5. Continued Support for the Existing Dash Community
The existing Dash community remains one of the network’s most important assets.
Alongside developer acquisition, I will continue supporting community communication and participation through:

• Regular updates about Evolution activities and opportunities;
  
• Support for community questions and discussions;
  
• AMAs, webinars and educational sessions;
  
• Coordination with existing community leaders and Dash organizations;
  
• Promotion of community-created initiatives;
  
• Connecting existing Dash supporters with new developers and university partners;
  
• Ensuring that European activities remain visible and accountable to the wider network.
  

This work will maintain continuity with the community support I previously provided while expanding the focus toward Evolution and developer adoption.

6. Community Feedback and Product Experience Improvement
The existing Dash community represents an important source of product knowledge and practical user experience. I will establish a structured process for collecting feedback on:

• Dash products and product flows;
  
• Dash and Evolution websites;
  
• Developer and user onboarding;
  
• Documentation and educational materials;
  
• Campaigns, presentations and other marketing assets;
  
• Calls to action, messaging and conversion paths.
  

Feedback will be gathered through community discussions, surveys, individual interviews, usability sessions and direct observation of recurring questions or difficulties.
The collected feedback will be organized into actionable insights rather than presented as an unstructured list of community opinions. Recurring issues, points of confusion and conversion barriers will be documented, prioritized and communicated to the relevant product, development, design and marketing teams.
Where possible, I will also help validate proposed improvements with community members and close the feedback loop by informing participants how their input was used.
The objective is to use the knowledge of the existing community to improve:

• Product usability and user journeys;
  
• Developer and user onboarding;
  
• Clarity of Dash and Evolution positioning;
  
• Website navigation and calls to action;
  
• Conversion performance across Dash websites;
  
• The quality and effectiveness of marketing and educational assets.
  

This will give the community a meaningful role in improving the Dash ecosystem while providing Dash teams with continuous access to real user insights.

Initial Deliverables and KPIs
The following targets are proposed for the initial term.

Monthly deliverables

• At least 10 qualified conversations with developers, technical founders, researchers or community leaders;
  
• At least 5 targeted university or developer-community outreach contacts, with documented follow-up;
  
• At least one public Evolution-focused activity, such as a webinar, workshop, AMA, presentation or developer session;
  
• Maintenance of a structured developer and partner pipeline;
  
• One public Dash Central progress report covering activities, results, expenses, feedback and next steps.
  

Quarterly deliverables

• Representation of Dash at a minimum of two strategically selected European events, subject to approved travel budget and event availability;
  
• At least two university or student-organization activations;
  
• At least one technical Evolution workshop, demonstration or developer challenge, delivered with support from qualified technical contributors where necessary;
  
• A structured report summarizing developer feedback, recurring questions and onboarding obstacles;
  
• A review of the developer pipeline and its movement through the following stages:
  

Contact → follow-up → technical session → platform experimentation → prototype or active contribution.
Initial-term deliverables

• A reusable Evolution presentation and webinar package;
  
• A university outreach package;
  
• A mapped database of relevant European universities, blockchain clubs, developer communities and events;
  
• A pilot framework for an Evolution ambassador or contributor program;
  
• A documented developer onboarding and follow-up process.
  
• One structured community and user feedback report identifying recurring product, website, onboarding, messaging and conversion issues, together with prioritized recommendations for the relevant Dash teams.
  

The proposal will not promise a fixed number of production applications. Application development depends on independent developers, technical feasibility and product decisions outside the proposal owner’s control. Accountability will instead be based on consistent activities, qualified opportunities and measurable progress through the developer funnel.

Why Dash Evolution Is Particularly Relevant to Europe
Dash Evolution gives Dash a substantially broader European proposition than cryptocurrency payments alone.
Dash Platform combines decentralized identities, human-readable usernames, schema-based data contracts, queryable documents, native tokens, payments, a decentralized API and cryptographic proofs within one network.
According to the official Dash Platform documentation, developers can build applications around structured decentralized data without deploying arbitrary application code directly on-chain. Through DAPI, applications can request data together with cryptographic proofs that allow clients to verify the validity of the response instead of simply trusting the server that provided it.
This creates a distinct proposition:
Dash Evolution is a decentralized backend for applications that need identities, structured and verifiable data, tokens and payments.
It should therefore not be presented as another general-purpose smart-contract chain or an Ethereum replacement. Its strongest position is as an application and data layer with its own identity, verification and payment primitives.

Alignment with European Digital Priorities
The European Commission’s current blockchain and Web3 strategy identifies digital identity, interoperability, cybersecurity and trusted data exchange as important areas for blockchain development.
The European Digital Identity framework is also increasing attention around digital credentials, user-controlled identity and the ability to prove particular attributes without unnecessarily exposing additional personal information. The EU’s European Digital Identity initiative is expected to make digital identity and credential infrastructure relevant to a much wider group of European developers, businesses and institutions.
Evolution is not a replacement for the European Digital Identity Wallet, nor should it be presented as automatically compliant with eIDAS, GDPR or any other EU regulation. However, its underlying capabilities are directly relevant to the same technical conversations:

• Persistent digital identities that are separate from wallet addresses;
  
• Data contracts that enforce an agreed data structure;
  
• Cryptographically verifiable application data;
  
• Proof-based access through a decentralized API;
  
• Human-readable usernames;
  
• Native token and payment functionality;
  
• Shared application state that is not controlled by a single platform operator.
  

This makes Evolution suitable for technical exploration in areas such as:

• Verifiable educational and professional credentials;
  
• Membership and reputation systems;
  
• Product provenance and audit trails;
  
• Shared registries and cross-organization data;
  
• Loyalty and reward programs;
  
• Event and community credentials;
  
• Marketplaces with identity, data and payments;
  
• Fintech and payment-enabled applications.
  

These examples should be presented as potential application categories rather than claims of regulatory compliance.

Verifiable Data Without Trusting a Central API
A particularly relevant European argument is not simply that data is placed on a blockchain, but that applications can verify the data returned to them.
Many conventional applications depend on a company-controlled database and API. The application user must trust that the operator has returned complete and unmodified information.
Dash Platform can return cryptographic proofs through DAPI. This allows a client to verify that the response corresponds to the state confirmed by the network.
This is relevant to European discussions around trusted data exchange, digital sovereignty, infrastructure resilience and reduced dependence on centralized platform operators.
It does not mean that every piece of data should be placed on-chain. Personal or sensitive information may need to remain off-chain, with only non-personal records, references, hashes or proofs stored on Platform. Responsible application architecture will remain essential.

A Natural Fit for Universities and Applied Research
Evolution contains several technical subjects that European universities are already teaching and researching:

• Distributed systems;
  
• Digital identity;
  
• Cryptographic verification;
  
• Data governance;
  
• Decentralized storage;
  
• Tokenization;
  
• Payment infrastructure;
  
• Privacy-aware application design;
  
• Blockchain interoperability.
  

This gives university outreach genuine educational substance. Dash does not need to approach universities with a speculative token narrative. It can offer a working environment in which students can create identities, define data models, submit documents, query decentralized data, issue tokens and build complete prototypes.
This makes Evolution suitable for:

• Guest lectures;
  
• Practical workshops;
  
• Student blockchain clubs;
  
• Research and thesis projects;
  
• University hackathons;
  
• Capstone projects;
  
• Developer certification programs.
  

A More Accessible Entry Point for Conventional Developers
Evolution can also reach beyond the existing population of Solidity and smart-contract developers.
Data contracts use structured schemas, while SDKs and APIs provide a development experience that is closer to conventional application and backend development. Developers can focus on identities, data models, queries and application flows rather than learning an entirely new on-chain programming environment before they can begin experimenting.
This opens outreach to:

• JavaScript and web developers;
  
• Backend engineers;
  
• Application developers;
  
• Technical founders;
  
• Fintech developers;
  
• Computer science students;
  
• Researchers who may have no previous Dash experience.
  

The result is a larger potential developer audience than would be available through a cryptocurrency-only or smart-contract-only message.

Dash Academy as the Conversion Layer
Initiatives such as the proposed Dash Academy can give European outreach a concrete and measurable conversion mechanism.
An event presentation or university webinar normally creates only temporary awareness. Without a guided next step, interested developers often leave without ever interacting with the technology.
Dash Academy can change that journey:
Event, lecture or direct outreach → Academy registration → guided lessons → verified testnet actions → certificate → hackathon, prototype or ecosystem contribution.
Instead of directing a new developer to documentation and hoping they return, the Academy can provide:

• A structured learning path;
  
• Short and accessible lessons;
  
• Real testnet interaction;
  
• Visible progress and completion;
  
• Identification of the modules where developers encounter difficulties;
  
• A verifiable completion credential;
  
• A clear transition into hackathons, ambassador initiatives and community activities.
  

This would also make European developer outreach measurable. We would be able to track not only how many people attended a presentation, but how many registered, completed modules, created Platform identities, registered data contracts, performed testnet actions and finished a project.
The Academy certificate itself could become a practical demonstration of Evolution. A certificate associated with a Dash identity—and potentially issued as a Platform document—would allow the educational product to demonstrate the same identity and verifiable-data capabilities that it teaches.
The Academy should not be described as an established resource until it is built and launched. Before launch, this proposal will support its testing and initial community cohort. After launch, it can become one of the primary onboarding tools used in university, event and developer outreach.

Why Europe Is a Low-Hanging-Fruit Opportunity
Europe should be considered low-hanging fruit not because developer adoption will happen automatically, but because most of the expensive prerequisites already exist.

1. The Underlying Technology Already Exists
Dash has already funded the difficult and expensive work: protocol research, engineering, network infrastructure, identities, data contracts, DAPI, proofs, tokens, payments, SDKs and technical documentation.
This proposal does not ask the network to fund another speculative protocol. It focuses on exposing an existing platform to developers, helping them understand it and creating a path toward practical use.

2. The European Distribution Network Already Exists
Europe already has a dense network of:

• Universities teaching blockchain and distributed systems;
  
• Blockchain research centers;
  
• Student Web3 associations;
  
• Developer conferences;
  
• Hackathons;
  
• Open-source communities;
  
• Fintech ecosystems;
  
• Digital identity and data-governance initiatives.
  

Dash does not need to build these distribution channels from the beginning. It needs a consistent person responsible for entering them, presenting a credible technical proposition and following up with interested participants.

3. Dash Academy Can Turn Outreach into Measurable Product Usage
The planned Academy addresses one of the largest gaps in the existing developer journey: the distance between discovering Dash Platform and successfully building something with it.
If implemented, every conference, webinar and university partnership can direct participants into the same measurable onboarding funnel.
This makes outreach more efficient and allows the network to compare channels based on real developer activity rather than impressions alone.

4. Evolution Has a Less Crowded Positioning Opportunity
European developers are already exposed to a large number of general-purpose L1s, L2s and EVM-compatible platforms. Competing only on speed, transaction cost or token incentives would place Dash in an extremely crowded category.
Evolution offers a more distinctive conversation around:

• Schema-enforced decentralized data;
  
• Identity-based applications;
  
• Human-readable usernames;
  
• Proof-verifiable queries;
  
• Native tokens and payments;
  
• A decentralized application backend accessible through APIs and SDKs.
  

Not every component is unique by itself. The opportunity lies in their integration within one established network and in presenting that combination through practical developer use cases.

5. The Product Can Be Introduced Without Leading with Token Promotion
European academic and technical institutions may be cautious about cryptocurrency promotion, particularly where it appears speculative or investment-focused.
Evolution allows Dash to begin with application infrastructure, identity, data verification, developer education and open-source experimentation.
DASH still plays an important role in the network, but the first conversation does not need to be “buy or use this cryptocurrency.” It can be “build and verify something on this infrastructure.”
This creates a more credible entry point for universities, developers and institutional partners.

6. Existing Community Knowledge Can Improve the Developer Funnel
The Dash community already contains long-term users, developers, masternode owners and contributors with extensive knowledge of the ecosystem.
By collecting structured feedback on the Academy, Platform documentation, Dash websites, onboarding flows and marketing assets, this proposal can convert that knowledge into product and conversion improvements.
The same process can be used with each new European developer cohort:

Observe where developers struggle → document the friction → improve the onboarding asset → test it with the next cohort.
This creates a feedback loop in which every outreach activity helps improve the effectiveness of the next one.

The strategic opportunity is not simply that Europe has many developers.
It is that Dash now has:

• A live application platform;
  
• A differentiated technical story;
  
• A planned guided education layer;
  
• Existing documentation and testnet infrastructure;
  
• An established community that can provide the first testing cohort;
  
• European universities and developer organizations that already welcome technical collaboration;
  
• A proposal owner who can connect these components and maintain the full relationship from first contact to active participation.
  

The technology, potential audience and distribution channels already exist. The missing layer is coordinated execution: positioning, outreach, education, onboarding, follow-up and community retention.
That is why European developer adoption represents a comparatively accessible and capital-efficient opportunity for the Dash network.

Why I Am Suited to Lead This Work
I previously worked directly with Dash as Product Marketing & Communications Lead and already understand the product, network structure, community and internal context.
My relevant experience includes:

• Translating complex technical products into clear positioning and educational narratives;
  
• Supporting Dash product launches and adoption campaigns;
  
• Working with the existing Dash community across multiple communication channels;
  
• Conducting customer, partner and community interviews;
  
• Building advocacy and communications programs;
  
• Public speaking and representation at international blockchain events;
  
• Working with European fintech and crypto organizations;
  
• Creating repeatable communication, onboarding and community processes.
  

Because I already know the Dash ecosystem and many of its contributors, this proposal has a low onboarding cost. I can focus immediately on execution while preserving continuity with the existing community.
Reporting and Accountability
A public report will be posted on Dash Central each month and will include:

• Activities completed;
  
• Events, workshops and university engagements;
  
• Number and type of qualified contacts;
  
• Developer pipeline progress;
  
• Community and ambassador activities;
  
• Developer feedback and identified obstacles;
  
• Travel and event expenses;
  
• Priorities for the following month.
  

Where appropriate, presentations, recordings, educational materials and public event results will also be shared with the community.

Funding Scope
The requested amount covers:

• Strategy and coordination;
  
• Developer and university outreach;
  
• Community management;
  
• Event preparation and participation;
  
• Follow-up and pipeline management;
  
• Educational materials;
  
• Ambassador-program development;
  
• Reporting and accountability.
  

Major sponsorships, hackathon prize pools or substantial third-party production costs will not be committed without separate approval or an explicitly defined budget.

Conclusion
Dash Evolution has moved Dash beyond being only a digital payments network. It gives developers access to decentralized identities, structured application data, queries, APIs and settlement within one ecosystem.
The technology now needs sustained human distribution.
By combining European event representation, university cooperation, direct developer relationships, developer initiatives and continued community support, this proposal will create a practical path from platform awareness to active ecosystem participation.
The goal is not activity for its own sake. The goal is to build the relationships, processes and local advocates required for Evolution to become visible, understood and used by European developers.
I am asking the network to fund an initial term in which this model can be implemented, measured and refined transparently.

## Potential European Events

We are currently in active communication with the organizers of the following European Web3, blockchain, privacy, developer and digital asset events:

* Cypherpunk Week — Amsterdam, August 31–September 6
* Web3 Warsaw — Warsaw, September 9–10
* ETHRome — Rome, September 11–13
* CONF3RENCE — Dortmund, September 15–16
* European Blockchain Convention — Barcelona, September 16–17
* ETHSofia — Sofia, September 24
* CV Summit — Zurich, September 29–30
* Digital Assets Week London — London, October 6–7
* BRAINS 2026 — Florence, October 13–16
* Plan ₿ Forum — Lugano, October 23–24
* MERGE Madrid — Madrid, October 27–29

The final selection will be based on audience relevance, opportunities for speaking, workshops or community partnerships, potential access to developers and strategic partners, participation costs and the expected value for Dash. Following these discussions and evaluation, two events will be selected for direct participation during this proposal cycle. The final choices and the rationale behind them will be communicated to the Dash community.

Dash EU Outreach Longlist: Events & Universities