Showcase y Certificación WG LatAm (SHOW-LATAM-WG)

Agenda

1. Meeting language and scheduling of a separate Latin American session
2. Migration of all components to specification version 4 (VPR v4) and testnet reset
3. Updated documentation structure (Understand / Build / Ecosystems)
4. Verifiable services, VS agents and the trust graph
5. The new "corporation" concept: keys, governance, permissions, trust deposit and slashing
6. Fees and anti-spam on mainnet
7. Keplr wallet and key management
8. Impersonation / organization credential issuance
9. Onboarding and approval flows, and how demos in the Playground should work

Discussion

Language and scheduling. Fabrice Rochette asked whether the session should run in English or Spanish; the attendees present were mostly Spanish-speaking and the session continued in Spanish. An invited participant from Vietnam and "Esteban" did not join. Fabrice proposed reserving this time slot for Asia and Europe and creating a separate Spanish-language Latin American group meeting on Thursday afternoons. Yhon Marlon Orjuela Mejia said participants could attend both.

Migration to v4. Fabrice reported that the main work since the previous week was updating all components to version 4 of the Verana specifications. The change was drastic enough that the blockchain was completely wiped and reset rather than migrated; v3 (previously on testnet) is now obsolete. He stressed this reset will not be repeated: from now on changes will require migration. A roadmap of remaining development is published on the website (under "About"). Changes in v5 are expected to be less disruptive and should not affect deployed applications or the corporation concept.

Documentation. The documentation now has three tabs. "Understand" is complete and validated and covers the three pillars (ecosystems, service identity, service discovery). "Build" still needs work and explains how to create services: deploying a verifiable service, getting the green check and appearing in the trust graph, service-to-service connection and bootstrapping other protocols (e.g. A2A, MCP), joining an ecosystem, obtaining and presenting credentials, issuing credentials via OpenID4VCI, verification and business models, intelligent agents, and infrastructure/backup practices. MDOC format support is planned for v5. Fabrice noted that "Ecosystems" and "verifiable services with VS agents" are interdependent and the ordering of the sections is open. He thanked Maxime Mansiet for the screenshots in the step-by-step guides. A demo of agent-to-agent communication is planned for the Playground.

Corporations. Fabrice explained that Verana has no accounts, only keys; a corporation is a group of keys acting as the master owner of ecosystems and services, with governance proposals and a configurable approval threshold, so that lost keys do not mean lost assets. Corporations grant and revoke permissions, including spending limits so a verifiable service can pay for credentials from the corporation's wallet. Hardware wallets (e.g. Ledger) are recommended. Bernard Légaut asked how a holding with several companies maps to corporations; Fabrice answered that a corporation is deliberately not an organization: it may group several companies, services under it may present credentials from different organizations, and two corporations may manage services presenting the same organization credential (e.g. delegated management). Implications are that the corporation handles payments and holds the trust deposit and reputation, so slashing of a service's ecosystem participation hits the corporation's deposit. Corporations must publish a governance framework; a draft template exists in the drafts repository.

Fees. Yhon Marlon asked whether the number of corporations would be limited. Fabrice said there is no limit, but on mainnet operations such as creating a corporation or ecosystem will carry a cost (he mentioned roughly $10) purely as an anti-spam measure.

Keplr and keys. Bernard asked about the link between a Keplr wallet and a corporation. Fabrice clarified Keplr is only a Cosmos-compatible signing tool with no Verana-specific role; keys can also be managed with the veranad CLI, by VS agents' own wallets, or on a Ledger device. A key with no corporation authorization cannot join an ecosystem.

Impersonation. Bernard asked whether someone could create a corporation representing a company they do not own (example: Claro). Fabrice said the DID domain carries no value and anyone can create entries on the ledger, but without an organization credential issued after an issuer's onboarding and verification the service never appears in the trust graph, which is what counts. He invited reporting of any loophole found.

Onboarding and demos. Fabrice showed the pending-task approval flow for issuers and noted that holder onboarding mode is missing from the frontend and that "join" currently skips the verification step — known bugs to fix. Approvals can also be automated via an MCP server with corporation permissions. Bernard raised that Playground visitors would be blocked waiting for manual approval. Options discussed: auto-approving service on devnet only; two separate ESS ecosystems on testnet, one for demos (flagged, e.g. orange marker in wallets) and one official with real verification; or possibly two testnets, since the testnet is intended to be run almost like a mainnet with real onboarding. Fabrice said this was not yet settled and should be listed as an item to determine.

Decisions

• The testnet blockchain was reset for the v4 migration; no further resets will be done, future changes will require migration.
• This meeting slot is reserved for Asia and Europe; a separate Spanish-language Latin American meeting will be held on Thursday afternoons.
• No decision was taken on how to separate demo services from real services on testnet.

Action items

• Read the updated documentation (Understand, Build, Ecosystems) to get familiar with the v4 concepts (all participants)
• Create a Spanish-language Latin American working group meeting on Thursday afternoons (Fabrice Rochette, next week)
• Decide how to distinguish demo services from real ones (separate ECS demo ecosystem, separate testnet, or other) and record it as an open item in the summary (Fabrice Rochette)
• Fix the missing holder onboarding mode and the "join" flow skipping verification in the frontend (owner not stated)
• Add an agent-to-agent demo to the Playground (owner not stated)
• Add MDOC credential format support in v5 (owner not stated)