Reference Implementation WG

Agenda

1. V4 deployment on testnet
2. Infrastructure: cluster separation, playground resource footprint, VS Agent multi-tenancy
3. VS-Agent / Credo DIDComm v2 state, Hologram and verana-demos
4. Credo contributions and credential response encryption
5. Frontend spec-compliance gaps
6. Deployment practice (devnet vs testnet) and possible automation
7. Namespace-scoped kubeconfigs for external demo repos
8. Indexer/VPR migration PR and upgrade plan
9. Mediator and wallet websocket / message pickup stability
10. Stuck DIDComm PRs in the Open Wallet Foundation repo
11. Old demo DNS alerts
12. Post-quantum verifiable credentials

Discussion

V4 and V5. Ariel Gentile reported that the V4 deployment on testnet was finally successful after the previous week's issues, with some polishing still needed in VS Agent before an official 2.0. Work on V5 has started following PRs on the specs and comments from Fabrice. Ariel wanted to review the items deliberately left out of the V5 specs because of their complexity, as well as the PRs moved to draft, but proposed doing this next week when Fabrice can attend.

Infrastructure. The clusters used for devnet and testnet have been separated so that core components (indexer, graph) run in a more stable environment. Ariel showed that the playground runs roughly 30 VS Agent instances (around 200 MB each), which is costly for mostly idle services; supporting multi-tenancy in VS Agent so several services can share one instance was named as immediate implementation work for the coming weeks. For now, resources were added to the test net cluster.

VS Agent / Credo. Many fixes landed in VS Agent and Credo for DIDComm v2. The store release of Hologram works with the playground over DIDComm v1; v2 support is being enabled in dev builds. After redeploying the playground, the duplicate-connection and race problems were described as almost gone. Ariel noted the verana-demos repo as a simpler example set (two issuers, two verifiers, chatbot and web flows) working with the latest VS Agent. He asked whether the new credential response encryption fix on the issuer side resolves the Swiss wallet incompatibility, or whether holder-side support is also needed; Maxime said holder-side support is needed. Ariel also noted the increased contribution activity in Credo from Tarun Vadde and Maxime.

Frontend. Andres Vallecilla said most of the gaps found against the V4 spec are now tracked as issues or have PRs; a final review may be needed but he believes coverage is largely complete.

Deployment practice. Ariel restated the rule: testnet uses stable versions, devnet tracks main. He suggested automating devnet upgrades (e.g. a daily job pulling dev versions) to avoid a PR per merge, noting the existing auto-approval for dev-net-only changes. Putting deployment back into source repos was rejected earlier to avoid sharing credentials, but could be reconsidered with scoped Kubernetes credentials. Andres offered to look at improving this.

Namespace-scoped kubeconfigs. Scoped kubeconfigs will be issued per external demo repo so they can deploy to the dev cluster with limits, instead of handing out full cluster access. The first case is Bernard's demo.

Migration. Pratik Kumar explained one PR adds a new store for faster queries and therefore needs a migration; he will group the smaller fixes into a single version and merge the migration PR last, since the upgrade plan lives in it. Ariel noted this will be the first real migration exercise since the previous practice of wiping state.

Mediator / wallet. Tarun is working on mediator and wallet improvements, studying real-time messaging systems (Signal, "edge award") and an optional spec field "live delivery" not implemented in Credo. He described dead sockets being dropped every 3–6 seconds while React Native does not observe pongs and TCP keep-alive is off, and proposed periodic status requests over the live socket with reconnect-with-jitter. Ariel gave background on websocket state handling across Android/iOS, the 3-second heartbeat, and the message pickup v2/v4 delivery acknowledgement history, and agreed stability needs work.

Other. Two DIDComm exchange protocol PRs in the Open Wallet Foundation Credo repo are blocked until the npm package naming/CI is fixed after the repo move; Ariel will handle it. The DNS alerts Andres saw relate to old V3-based demos, which will be shut down and later rebuilt on V4 in the dev environment. Ariel introduced Martin, a student working on post-quantum verifiable credentials, adding ML-DSA support to Askar, with Credo integration and a possible demonstration by year end.

Decisions

• V5 specification review (excluded items and draft PRs) is deferred to next week's meeting with Fabrice.
• Namespace-scoped kubeconfigs will replace full cluster kubeconfigs for external demo repos.
• The old V3-based demos will be shut down rather than fixed.
• The migration PR will be merged last, after the smaller indexer/VPR fixes, grouped into one version with an upgrade plan.

Action items

• Create the demo repo and issue a namespace-scoped kubeconfig for Bernard (Ariel Gentile and Andres Vallecilla, after the meeting)
• Investigate automating dev net deployments to avoid a PR per merge (Andres Vallecilla, today)
• Fix npm package naming/CI after the repo move to Open Wallet Foundation and merge the pending DIDComm PRs (Ariel Gentile, today)
• Raise a backport of the Askar dependency fix to the 0.6.7 branch (Tarun Vadde)
• Cut a new Credo release so the mediator can be upgraded (Ariel Gentile, tomorrow after the meeting)
• Group the small indexer/VPR fixes into one version and merge the migration PR last, then plan the upgrade exercise (Pratik Kumar)
• Prototype and validate the live-delivery / websocket stability approach and share a report (Tarun Vadde, by end of week)
• Confirm whether the Swiss wallet incompatibility needs holder-side encryption support (Maxime, absent)
• Begin work on VS-Agent multi-tenancy to reduce playground resource usage (owner not assigned)

Agenda

1. Test net migration to V4 and move to a new cluster
2. Deploy repo centralisation and the ECS deployment PR
3. Hologram app update and store release
4. Playground wallets and DIDComm v1/v2 status
5. Indexer issues, TRQP gaps and the 2.1 release
6. Frontend issues and front-end documentation PR
7. V5 roadmap, tokenomics, governance and upcoming business context
8. Communication about test net downtime

Discussion

Test net migration. Ariel Gentile introduced the main topic: migrating the test net to V4 and moving it onto a dedicated cluster so it is no longer sharing resources with the playground and demo services. Andres Vallecilla reported that deployment of the blockchain had been started the previous day; after some problems it was fixed and the chain is now running. Services were being redeployed on the new cluster: dashboard, indexer and the "fer" service were already deployed, with more to follow. Andres questioned whether the graph needed to be deployed at this stage; Fabrice Rochette stated that everything must be deployed, including the graph and the search.

Deploy repo and ECS PR. Andres explained that the deploy repo now centralises blockchain deployment, with a full deployment path and a binary-refresh path, replacing a previously multi-step and complex process. Ariel presented a PR extending the ECS ecosystem/organisation issuer setup (previously devnet only) to the testnet, removing the older V3 transactions and fixing the schema mode issue Fabrice had raised. He noted new secrets (mnemonics per environment) would be needed and that he had left pre- and post-merge instructions in the PR body, some of which may no longer apply after the cluster move. Andres said he would review the environment structure for consistency and also address Maxime's comments on the configuration file, requiring a front-end update he described as not complicated. Ariel noted the wiped devnet had taken under an hour to redeploy with demo services.

Hologram. Ariel said the Hologram app is already updated for V4 and only awaits publication. Maxime Mansiet had tested on dev-net and would test the test net once migration completed, after which the update could be published. Known issues remain: dark-mode support for some widgets (issue opened by Fabrice) and a presentation-request QR code showing the invitation screen before the presentation request; Ariel was unsure whether the cause is in Hologram or in how VS Agent constructs the invitation. The plan is to publish now and release store updates more frequently.

Playground wallets and DIDComm. The basic use cases (Vesta, Verandia, BHI, crypto exchange) worked on devnet with Hologram, WWWallet, Inji and EUDI. Maxime reported the Swiss wallet introduced encryption in version 1.18 which Credo does not yet support; version 1.16 works on devnet and will be used on the playground, with the fork updated once Credo supports the encryption. Hologram still uses DIDComm v1 for stability while inter-service communication already uses v2; once remaining Credo fixes land, VS Agent, Hologram and the mediator can be upgraded.

Indexer and TRQP. Open indexer issues remain, including an open PR with unaddressed review comments. Andres said he had reviewed the specs and listed several small TRQP gaps that still need finishing, but is occupied with the migration. Pratik Kumar accepted taking over these issues. Ariel said release 2.1 could follow once they are done.

Frontend and documentation. Maxime reported many issues already closed; roughly three or four remain without PRs, and he considered issue 503 (onboarding service, join wizard and new screens) the top priority. He had opened a documentation PR for the front end including screenshots in light and dark mode, aimed at non-technical users onboarding their service. Fabrice said this was on his own roadmap, welcomed it, and would review and merge; he added the VS-Agent build section of the documentation is confusing and that a new working group starting Thursday would cover documentation and playground demo deployment.

V5 and context. Fabrice outlined what follows V4: schema attribute additions on the blockchain with impact on VS-Agent, the tokenomics update agreed with Philip (a pull request from Pratik is pending review), a new governance model, and Cosmos SDK upgrade / group module work already underway. Most effort would shift to applications, including the Colombia commercial chamber project, plus a planned SaaS offering (indicative price mentioned: $10 per month), a certification programme, and a Colombian company joining the foundation as an associate member.

Downtime communication. Fabrice stressed that people use the playground daily for demos, cited a cancelled meeting caused by uncertainty about testnet availability, and asked Andres to post progress and estimated restoration times in Discord roughly every three hours. Andres acknowledged this.

Decisions

• Everything, including the graph and search services, is to be deployed on the new test net cluster.
• Hologram's V4 update will be published once Maxime confirms it works against the testnet, with fixes released in subsequent store updates.
• The Swiss wallet will be integrated at version 1.16 until Credo supports the 1.18 encryption.
• The open indexer/TRQP issues are reassigned to Pratik Kumar.

Action items

• Finish deploying the remaining services (visualizer, graph, search, ECS) on the new test net cluster (Andres Vallecilla, today)
• Review the environment/secrets structure and the ECS deployment PR, then proceed with deployment (Andres Vallecilla)
• Update the front-end configuration per Maxime's comments (Andres Vallecilla)
• Post regular Discord updates on test net status and expected restoration time (Andres Vallecilla)
• Test Hologram against the migrated test net and publish the store update if it works (Maxime Mansiet)
• Implement front-end issue 503 (onboarding service / join wizard) as next priority (Maxime Mansiet)
• Close or update the outdated July documentation PR (Maxime Mansiet)
• Review and merge the front-end documentation PR with screenshots (Fabrice Rochette)
• Address the review comments on the open indexer PR and finish the TRQP gaps (Pratik Kumar)
• Review the pending tokenomics pull request (Fabrice Rochette)

Agenda

1. DIDComm v2 PR review feedback and Trust Ping support in Credo
2. Specification writing practice (functional spec vs. system design)
3. Playground: personal wallets integration and conformance testing
4. Playground / test net migration to V4 and basic use cases
5. DIDComm v2 connection establishment issue (concurrent first messages)
6. VS-Agent, Indexer and Frontend spec-compliance gaps; TRQP endpoints
7. Wallet forks, app stores and upstreaming
8. Deployment repo simplification

Discussion

Credo DIDComm v2 PR Ariel Gentile and Tarun Vadde discussed review comments received on the DIDComm v2 work. Ariel accepted that most of the raised points were valid and should be fixed, but objected to re-architecting the module, citing the issue-credential module in Credo, whose abstract protocol interfaces created type complexity and a difficult setup experience while no new issue-credential protocol has appeared in four years. He said he had replied that he would welcome a cleaner architecture proposal at the moment only if it would be possible to merge to main within one month. Tarun agreed that the pursuit of perfect clean code had delayed simple features for years.

Specification practice. Ariel described an experiment on an unrelated personal project (a ham-radio logging website), splitting documentation into a one-line-per-requirement functional specification and a separate system design document containing database and technical constraints. He suggested a similar approach for the V5 specifications, while acknowledging the Verana system is far more complex.

Playground wallets. Maxime Mansiet reported that the integrated wallets (Hologram, WWWallet, Inji, EUDI, Swiss) are all working. He plans to keep a set of main wallets visible on the playground with an expandable card for additional ones. He integrated an "EUDI dev testing suite" repo (shared on Discord) into CI and opened a PR on the specifications describing how conformance testing should work. More wallets are supported than on the test net; the Hologram implementation still needs finishing.

V4 migration. Ariel is working on a V4 branch of the playground, aiming to replace the current test net rather than migrate existing objects, ideally before the end of the week. The personal-wallet aggregated issuer/verifier examples work; of the four basic use cases, Vesta, the crypto exchange and Verandia appear deployed (not yet verified by hand), while "Better Hiring Institute" still has workflows to fix.

DIDComm v2 connection handling. Ariel explained that in DIDComm v2 a connection is established by the first message, whatever it is. When a client (e.g. Hologram) sends two messages almost simultaneously (discover-features query and profile request) to a public DID, the receiving agent can create two connections, especially in multi-instance deployments. He observed this in testing. A possible client-side convention is to send a Trust Ping first and wait for the response before sending anything else; Tarun said he had assumed this behaviour already. Ariel conceded this is opinionated and not required by the spec, but argued it is practical and also verifies the other end is reachable, since trust resolution only queries the indexer endpoint. He raised whether Credo needs additional connection states (the current RFC-derived states being inaccurate) and proposed discussing it further.

Spec compliance. Andres Vallecilla opened an issue on missing VS Agent endpoints and found further gaps in the indexer, two of which he considered important; Patrick has started work on them. Frontend gaps exist but he wants to review before filing issues. Ariel asked that Maxime's non-essential PRs be marked draft rather than closed. He also flagged that the TRQP endpoints are untested and should become the preferred mechanism for third-party wallet integrations, at least for accreditation checks.

Wallet forks and stores. Maxime works via personal forks and pull requests; the changes are mainly UI (the Verana trusted/untrusted card). Fabrice asked for Play Store/App Store versions for business demos, as some users will not install APKs. Ariel said publishing clones to the stores would likely be rejected and that upstreaming to wallet maintainers is the long-term goal; Inji is considered likely to accept a PR. One wallet (native Swift/Kotlin) has no fork in the organisation yet.

Deployment. Andres asked for review of a PR in the deploy repo that simplifies deployment.

Decisions

• The current test net will be replaced by a new V4 testnet rather than migrating existing objects.
• Non-essential open PRs from Maxime will be marked as drafts, not closed.

Action items

• Create a fork of the Swiss wallet repo under the Verana Labs organisation and send the link to Maxime (Ariel Gentile)
• Mark the non-essential spec-compliance PRs as drafts and verify whether they are still needed (Maxime Mansiet)
• Finish the Hologram wallet implementation and continue conformance testing work (Maxime Mansiet)
• Verify the deployed basic use cases (Vesta, crypto exchange, Verandia) and fix the remaining workflows for the BHI use case (Ariel Gentile)
• Migrate the test net to V4 (Ariel Gentile, target before end of week)
• Review the frontend spec gaps and open issues for them (Andres Vallecilla)
• Review the deployment-simplification PR in the deploy repo and comment (Ariel Gentile)
• Think about connection-state handling / Trust Ping-first convention in Credo and discuss further (Ariel Gentile, Tarun Vadde, tomorrow)
• Test the TRQP endpoints (owner not assigned)