A Guide to Local-Government Web3 Pilots

Netsujo Inc. · Published April 7, 2026

A growing number of Japanese local governments are running pilots that use blockchain, NFTs, or DID (Decentralized Identifiers, a form of digital identity not controlled by a single central authority). This guide surveys four areas where Japanese municipalities are applying Web3 — tourism and relationship population, digitizing administrative procedures, regional currency and points schemes, and transparency of administrative data — then lays out a five-step process for running a pilot (identifying the problem, choosing the technology, securing budget, running the pilot, and evaluating whether to continue) and three factors that distinguish pilots that get renewed or scaled up. It closes with Netsujo's own participation, since March 10, 2026, in Chain Up KYOTO, a Kyoto Prefecture working group for this kind of work, and what to weigh when selecting an implementation partner.

Four areas of local-government Web3 use in Japan

Reviewing cases in and outside Japan, local-government use of Web3 falls broadly into four categories. Understanding the relationship between each technology and the administrative problem it addresses is a prerequisite for choosing where to start.

• Tourism and relationship population — NFT stamp rallies and proof-of-visit tokens let a municipality capture visitor behavior data; some municipalities are also piloting NFT-based digital resident certificates, mainly to make relationship population visible and encourage ongoing engagement.
• Digitizing administrative procedures — DID-based identity verification is being explored as an alternative to relying on Japan's My Number Card (the national ID card) for resident authentication, with pilots also exploring digital certificates for residency status or education history.
• Regional currency and points — token-based local economic circulation redesigns existing points-card schemes on a blockchain, with point interoperability across member merchants and preventing value from leaking outside the region as testable goals, alongside reduced issuance and administration costs.
• Transparency and trust in data — recording administrative records on a blockchain aims at tamper-resistance and audit trails, mainly for data the public expects accountability on, such as subsidy disbursement records, meeting minutes, or tender results, often combined with open-data initiatives.

Running a pilot: five steps

A local-government Web3 pilot adds administrative processes on top of a private-sector PoC — council approval, notification to Japan's Personal Information Protection Commission, and public communication. It is worth designing the pilot within a PoC (proof-of-concept) structure, so that everyone involved shares the same understanding of why it's being run and what would count as success.

• Identify the problem — clarify what problem Web3 is meant to solve. Starting from the technology rather than the problem tends to produce a pilot disconnected from resident needs; sort out the department's operational issues, budget constraints, and council-facing considerations, and ask whether this specific problem can actually be solved with Web3.
• Choose the technology — the choice between a public chain, a consortium chain, and a private chain depends on the scope of data disclosure, cost, and governance requirements; government use cases often favor a consortium model because a clear, accountable data owner is required.
• Secure budget — several Japanese subsidy programs exist for Web3/DX projects (for example, the Digital Garden City Nation Initiative grant and Cabinet Office digitalization subsidies); work backward from the grant application schedule to the planned pilot start date, and prepare on the assumption of being selected. Cost-sharing with a private partner is also worth considering.
• Run the pilot — keep the pilot scope to the minimum resident-facing footprint needed to test the hypothesis. Starting with roughly 50–200 participants surfaces UI, onboarding, and support issues; being able to report progress to the council and the head of the municipality weekly is directly tied to keeping approval.
• Evaluate and decide — after the pilot ends, produce an evaluation document that decides to continue, expand, or stop. Evaluate against three axes — KPI attainment, resident feedback, and operating cost — and, if recommending expansion, present the budget, structure, and any ordinance changes needed for full operation at the same time.

Three factors behind pilots that get renewed

Analyzing Japanese local-government Web3 pilots that were continued or scaled up shows a common design pattern. Technical polish matters less than how the pilot is designed around the organization, residents, and partners.

• Designing for residents — prioritize whether residents can actually use it over technical sophistication. Onboarding design tailored to who the users are — NFT wallet setup, support for people without a smartphone, multilingual support — tends to determine whether a pilot succeeds.
• Staged rollout — start with a single department and a single use case rather than aiming for organization-wide rollout at once. A cycle of feeding what was learned from a small pilot into the design of the next phase minimizes risk and cost, and this 'start small, then expand' structure is also easier to align with the timing of any ordinance changes needed.
• Choosing the right private-sector partner — for a local-government Web3 pilot, it matters to choose a partner with a track record supporting subsidy applications and a feel for local community engagement and regulatory issues, not just technical implementation capability. Since an early technology choice affects the cost of every later phase, spending time evaluating a partner is a reasonable investment.

For DID-based identity verification specifically, two points need attention: whether it counts as "personal information" under Japan's Act on the Protection of Personal Information requires legal review, and municipalities acting as an issuer are advised to consult Japan's Personal Information Protection Commission in advance. Interoperability also needs checking from the pilot stage — confirming alignment with standards such as the W3C DID specification so that DIDs remain compatible across different municipalities and private services.

Kyoto's Web3 initiative: Chain Up KYOTO

Within Kyoto Prefecture, a working group called Chain Up KYOTO, which grew out of the Kyoto Big Data Utilization Platform, is active. Its main activity is exchanging information toward creating business models that use Web3-related technologies (blockchain, the metaverse, XR, AI, IoT, and similar) to address social challenges. Netsujo joined this working group on March 10, 2026, and participates in discussions on the social implementation of Web3 and blockchain through study sessions and project reviews. The working group brings together Kyoto Prefecture, municipalities within the prefecture, private companies, and university research institutions; Netsujo's role within it is technical validation, pilot design support, and acting as an implementation-side private partner.

For anyone planning a subsidy application: preparing the technical justification, cost estimates, and delivery structure needed for a grant application typically takes around two to three months, so it is worth starting before the budget is confirmed rather than after.

What is a PoC? Process, cost, and keys to success（日本語）

What is Web3 consulting? 5 points for choosing a firm without regrets（日本語）

Web3 requirements definition: a checklist for project success（日本語）