> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/case-study-library/government-and-public-services/votari.md).

# Votari

<figure><img src="/files/s1PJ6VpLYFPmWVLPMB1s" alt=""><figcaption></figcaption></figure>

### Project Overview

* **Company:** Votari App Ltd
* **Project:** Votari App
* **Industry:** Verifiable Digital Governance Infrastructure
* **Website:** [www.votari.app](https://www.votari.app)
* **Geographic Reach:** Global
* **Founder:** Rui Da Silva
* **Headquarters:** United Kingdom
* **Status:** Live — iOS and Android apps available; soft launch completed in January 2026 with multiple trial elections

### Business Challenge

**What inefficiencies or risks existed?**

* Many voting processes still rely on opaque digital platforms, manual counting, or centralised systems.
* Participants cannot independently verify votes, counts, or outcomes in most traditional systems.
* Paper-based voting is expensive, hard to scale, and difficult for remote participants.
* Physical voting creates friction for diaspora communities, younger voters, and geographically dispersed groups.
* Trust in election infrastructure has declined as scrutiny of transparency and manipulation risks has increased.

**Why traditional systems were insufficient**

* Centralised platforms store votes in private databases that participants cannot independently audit.
* Traditional systems force a trade-off between convenience and verifiability.
* Physical polling introduces delays, operational costs, and disputes over transparency.

### Why BSV Blockchain?

**What made the BSV blockchain the ideal solution?**

* Votari needs a public ledger that supports high-volume, low-cost, and data-rich transactions.
* Low transaction fees make large-scale voting practical because each vote can be recorded individually.
* Scalable throughput supports high participation without major cost barriers.
* Data-rich transactions allow election identifiers, rule commitments, audit references, and cryptographic proofs to be anchored on-chain.
* Stable protocol behaviour matters in governance environments where predictability is critical.
* SPV-compatible verification allows participants and auditors to verify results without running full infrastructure.

**BSV-specific features used**

* **Micropayments:** Each vote is recorded as an individual low-fee transaction.
* **Data storage:** Election identifiers, rule commitments, audit references, and cryptographic proofs are anchored on-chain.
* **SPV:** Lightweight verification supports mobile users and independent auditors.
* **Public auditability:** Election records are tamper-evident and historically auditable on an open ledger.

### Solution Architecture

**Overview of the implemented BSV-based system**

Votari is a mobile-first verifiable voting platform. It combines client-side cryptographic verification, a publicly auditable on-chain record layer, and lightweight cloud infrastructure. The system reduces reliance on trusted intermediaries while preserving voter privacy and keeping the experience simple for non-technical users.

Rather than treating a central database as the only source of truth, Votari uses tamper-evident on-chain records and cryptographic verification. This supports transparency and independent reproducibility in elections where results may be disputed.

**Election flow**

1. An organiser creates an election with predefined rules and timing.
2. The election rules are locked on-chain and cannot be changed after publication.
3. Participants join through a QR code.
4. Voters register by scanning a biometric passport using NFC and completing on-device facial verification.
5. Eligible voters receive a digital ballot and cast votes privately.
6. Votes are signed locally and recorded immutably on the BSV blockchain.
7. Auditors, organisers, and voters can independently verify the result at any time.

**Key components**

* Native iOS and Android apps available on the App Store and Google Play.
* Passport NFC and on-device facial verification against the ePassport chip image.
* Domain and email-based voter validation for election types that need it.
* Transaction broadcasting and indexing infrastructure for vote and rule recording.
* QR-code election onboarding.
* Audit tooling for independent verification and result reproduction.
* Cloud infrastructure hosted on Amazon Web Services.

### Implementation Process

**Phases of rollout**

* **Research and architecture phase:** Explored verifiable voting models, scalability, privacy, and election integrity requirements.
* **Product development phase:** Built native mobile apps, integrated BSV, and implemented verification, voting, and audit workflows.
* **Deployment and testing phase:** Ran live trial elections and governance votes, then refined infrastructure and user experience.
* **Soft launch:** January 2026 on iOS and Android, with initial trial elections opened through QR codes shared on social media.

**Milestones and partnerships**

* iOS and Android applications went live in January 2026.
* Multiple trial elections and governance votes were completed.
* Privacy-preserving on-device identity verification was implemented and tested in live environments.
* The project launched as a bootstrapped initiative with private early funding.
* Votari engaged with BSV ecosystem members, infrastructure providers, governance stakeholders, public sector contacts, and AWS.

### Outcomes & Business Impact

**Quantifiable results**

* iOS and Android applications are live and publicly available.
* Multiple trial elections and governance votes completed with end-to-end verifiable auditability.
* On-device identity verification is operational, with no personal data sent to remote servers.
* Low-cost vote recording has been demonstrated through BSV micropayments.

**Improved trust and transparency**

* Participants and observers can verify that votes were recorded and rules remained unchanged.
* Election outcomes can be reproduced independently from public blockchain data.
* Trust shifts from trusting the platform to verifying the process.

**Increased accessibility and participation potential**

* Mobile-first design reduces friction for remote voters and diaspora communities.
* Digital participation removes the need for physical presence at polling locations.
* The platform is well suited to younger users who already expect mobile interactions.

**Simplified governance processes**

* Organisations can reduce manual counting, physical ballot handling, and audit preparation.
* Governance bodies can lower operational complexity around election disputes and reporting.

**Stakeholder feedback**

* Governance and institutional stakeholders have shown strong interest in the platform.
* Feedback consistently highlights transparency, usability, and independent auditability.
* Remote and geographically distributed participation remains one of the clearest value areas.

### Challenges & Mitigations

**Technical or operational challenges encountered**

* Balancing verifiability, voter privacy, and a simple user experience.
* Preventing duplicate participation without exposing private identity data.
* Maintaining reliability in time-sensitive election environments.
* Building public confidence in a system where technical correctness alone is not enough.

**How the team leveraged BSV's capabilities to overcome them**

* BSV data storage supports anchoring hashes and proofs without exposing sensitive personal data.
* SPV-compatible verification makes independent auditing accessible without privileged infrastructure.
* Low-fee transactions make it viable to record every vote individually for fine-grained accountability.

### Future Vision

**Expansion plans**

* Scale from early deployments and governance pilots toward broader institutional and public sector use.
* Expand across organisational governance, membership voting, diaspora participation, and larger democratic processes.
* Keep improving accessibility without weakening transparency or auditability.

**Planned product development**

* Expanded election types and governance workflows, including weighted voting and ranked-choice ballots.
* Deeper audit and verification tooling for high-scrutiny elections.
* Additional identity verification options beyond passport NFC.
* Enhanced scalability infrastructure for high-participation elections, with support for up to 100,000 ballots in the Expert tier.
* Broader interoperability with external governance and identity systems.

**Long-term BSV strategy**

* BSV remains central because it combines low-fee scalability, data-rich transactions, public auditability, and SPV-compatible verification.
* Votari aims to help establish verifiable voting as a global standard for transparent digital governance.

### About Votari App Ltd

Votari is a UK-based technology company founded by Rui Da Silva. It builds verifiable digital voting infrastructure on BSV. The platform is designed with GDPR considerations and ISO 27001-aligned security principles in mind. Its goal is to make election legitimacy depend on cryptographic proof and public verifiability rather than institutional trust.

**Contact**

* Email: <support@votari.app>
* Website: [www.votari.app](https://www.votari.app)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.bsvblockchain.org/case-study-library/government-and-public-services/votari.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.