<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Verista Journal</title>
    <link>https://verista.co/blog</link>
    <atom:link href="https://verista.co/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>Technology, engineering and craft behind verifiable provenance — from the Verista team.</description>
    <language>en</language>
    <lastBuildDate>Tue, 03 Nov 2026 16:25:21 GMT</lastBuildDate>
    <item>
      <title>Introducing the Verista Journal</title>
      <link>https://verista.co/blog/introducing-the-verista-journal</link>
      <guid isPermaLink="true">https://verista.co/blog/introducing-the-verista-journal</guid>
      <pubDate>Thu, 15 Oct 2026 13:56:38 GMT</pubDate>
      <category>Company News</category>
      <dc:creator>Verista Team</dc:creator>
      <description>Welcome to the Verista Journal: articles on technology, engineering and craft, guides for owners and brands, product updates and news — all in one place.</description>
      <content:encoded><![CDATA[
<p>Verista exists to make the story of exceptional objects verifiable: who made them, who has owned them, and whether they are what they claim to be. Today we are opening a place to share what we are learning along the way — the <strong>Verista Journal</strong>.</p>

<h2 id="what-you-will-find-here">What you will find here</h2>
<ul>
  <li><strong>Technology and engineering</strong> — how verifiable certificates work, and how we build the platform.</li>
  <li><strong>Luxury and craft</strong> — the objects, makers and traditions that provenance protects.</li>
  <li><strong>Provenance, regulation and resale</strong> — the forces reshaping how products carry their history.</li>
  <li><strong>Guides</strong> — practical walkthroughs for brands, distributors and owners.</li>
  <li><strong>Product updates and news</strong> — what is new on Verista, and what is next.</li>
</ul>

<h2 id="why-we-are-writing">Why we are writing</h2>
<p>Provenance sits where several worlds meet: craftsmanship and cryptography, retail and regulation, collectors and compliance teams. Each speaks its own language. We want this journal to be a place where those conversations meet in plain English — useful whether you run a brand, sell its products or own something you care about.</p>

<h2 id="what-we-believe">What we believe</h2>
<p>A few convictions shape everything we build, and they will shape what we write here too:</p>
<ul>
  <li><strong>Records should be independently verifiable.</strong> A certificate should not depend on a private database, a PDF or institutional memory. Anyone should be able to check it.</li>
  <li><strong>Ownership should have a clear exit path.</strong> Collectors and organisations deserve defined ways to keep or move what is theirs, including when they leave a platform.</li>
  <li><strong>The experience should feel simple.</strong> Nobody should need to understand wallets, gas or block explorers to receive and keep a certificate. The technology stays available for inspection and out of the way of daily use.</li>
</ul>
<p>Expect articles that explain the reasoning behind those choices as well as the choices themselves — including the trade-offs we made and the ones we are still weighing.</p>

<h2 id="how-to-follow-along">How to follow along</h2>
<p>New articles appear here first. If you use a feed reader, subscribe to the <a href="/blog/rss.xml">RSS feed</a>. Every article is also searchable and filed under a category, so you can follow just the topics you care about — engineering, say, or regulation.</p>

<h2 id="start-reading">Start reading</h2>
<p>A good first stop is <a href="/blog/what-makes-a-certificate-of-authenticity-trustworthy">What makes a certificate of authenticity trustworthy?</a>, or our overview of <a href="/blog/digital-product-passports-what-brands-should-know">Digital Product Passports</a>. You can browse <a href="/blog">every article</a> by category or search for a topic.</p>
<p>To learn more about us, read <a href="/about">about Verista</a>. And if there is something you would like us to write about, <a href="/contact">tell us</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Product update: branded vaults, organisation-wide two-factor, and more</title>
      <link>https://verista.co/blog/product-update-branded-vaults-two-factor-and-more</link>
      <guid isPermaLink="true">https://verista.co/blog/product-update-branded-vaults-two-factor-and-more</guid>
      <pubDate>Tue, 13 Oct 2026 13:56:38 GMT</pubDate>
      <category>Product Updates</category>
      <dc:creator>Verista Team</dc:creator>
      <description>A round-up of recent Verista work: issuer-branded vaults, organisation-wide two-factor authentication, co-signed shared wallets, background issuing with progress you can follow, and public brand profiles.</description>
      <content:encoded><![CDATA[
<p>Here is a round-up of recent work across the Verista platform. Some features depend on your plan, and some are rolling out gradually — your organisation's settings show what is available to you.</p>

<h2 id="branded-vaults">Branded vaults</h2>
<p>Brands can now offer their customers the Verista owner vault under their own identity: on a custom domain or a Verista subdomain, styled with the brand's own theme. Every theme renders the same features as the standard vault — the brand controls appearance, never what owners can do. See <a href="/#white-label">White Label Vault</a>.</p>

<h2 id="organisation-wide-two-factor-authentication">Organisation-wide two-factor authentication</h2>
<p>Owners of an issuer or distributor organisation can require two-factor authentication for everyone, themselves included, using an authenticator app. Members who have not set it up are guided through setup at their next sign-in. If someone loses their authenticator, the owner can reset their two-factor so they can enrol again.</p>
<p>Collectors can also turn on two-factor authentication for their own vault from the profile menu.</p>

<h2 id="co-signed-shared-wallets">Co-signed shared wallets</h2>
<p>Operations through an organisation's shared wallet — issuing, transferring, deploying contracts, changing owners — can now be co-signed: a team member and Verista must both approve, and Verista checks permissions and the operation itself before it does. We wrote about the design in detail in <a href="/blog/how-verista-protects-the-wallets-that-issue-certificates">How Verista protects the wallets that issue your certificates</a>.</p>

<h2 id="issue-in-the-background">Issue in the background</h2>
<p>Issuing a single certificate no longer ties up the dialog. Start an issue, close the dialog, and carry on: a progress badge follows you around Verista Cert, and several issues can run at once. Select a badge to reopen that issue.</p>

<h2 id="public-brand-profiles">Public brand profiles</h2>
<p>Issuers and distributors can publish a brand profile — a tagline, an introduction, a website, social links and a cover image — which appears wherever their name or logo does, including on certificate verification. Organisations choose exactly what to publish.</p>

<h2 id="also-new">Also new</h2>
<ul>
  <li>An audit log with readable, filterable event names across every console.</li>
  <li>Clearer handling when a team member leaves, including on-chain removal from the shared wallet.</li>
  <li>The Verista Journal — the blog you are reading.</li>
</ul>
<p>Questions about any of these? Visit the <a href="https://docs.verista.co">documentation</a> or <a href="/contact">contact us</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Digital Product Passports: what brands should know now</title>
      <link>https://verista.co/blog/digital-product-passports-what-brands-should-know</link>
      <guid isPermaLink="true">https://verista.co/blog/digital-product-passports-what-brands-should-know</guid>
      <pubDate>Sun, 11 Oct 2026 13:56:38 GMT</pubDate>
      <category>Regulation &amp; Compliance</category>
      <dc:creator>Verista Team</dc:creator>
      <description>The EU&apos;s Ecodesign for Sustainable Products Regulation brings Digital Product Passports — structured, product-level records that travel with goods. Here is a plain-language overview for brands, and how verifiable certificates relate to it.</description>
      <content:encoded><![CDATA[
<p>For decades, the story of a product ended at the till. Regulation in the European Union is changing that: products are increasingly expected to carry their information with them, in a form that customers, repairers, resellers and authorities can read. The vehicle for that is the <strong>Digital Product Passport</strong>.</p>
<p><em>This is a general overview, not legal advice. Confirm your obligations with qualified counsel.</em></p>

<h2 id="where-digital-product-passports-come-from">Where Digital Product Passports come from</h2>
<p>The EU's Ecodesign for Sustainable Products Regulation (ESPR), Regulation (EU) 2024/1781, entered into force in July 2024. It replaces the earlier ecodesign framework, which focused on energy-related products, with one that can cover most physical goods. One of its central tools is the Digital Product Passport: a structured digital record about a product, reachable through a data carrier such as a QR code.</p>

<h2 id="what-a-passport-is-for">What a passport is for</h2>
<p>The aim is to make product information available where decisions are made. Depending on the product group, a passport can hold information such as:</p>
<ul>
  <li>identification of the product and its manufacturer;</li>
  <li>materials and composition, including substances of concern;</li>
  <li>guidance on use, care, repair and end-of-life handling;</li>
  <li>information relevant to durability and recyclability.</li>
</ul>

<h2 id="not-everything-not-all-at-once">Not everything, not all at once</h2>
<p>ESPR is a framework. The concrete requirements — which products need a passport, what data it must contain and when — arrive in <strong>delegated acts adopted for specific product groups</strong>. Textiles and apparel are among the groups the European Commission has prioritised, alongside several industrial and household categories. Each act sets its own timeline, so the right question for a brand is not "does ESPR apply?" but "which acts cover our products, and when?"</p>

<h2 id="why-per-item-records-matter">Why per-item records matter</h2>
<p>Many passports are expected to work at the level of a model or batch. But luxury and collectible goods have always cared about the individual piece — this watch, this bag, this artwork. Item-level records bring benefits regulation alone does not demand:</p>
<ul>
  <li><strong>Authenticity</strong> — a record tied to one serial number, not a product line.</li>
  <li><strong>Provenance</strong> — a history of ownership that adds value at resale.</li>
  <li><strong>After-sales</strong> — warranty, servicing and repair attached to the specific item.</li>
</ul>

<h2 id="how-verista-relates-to-this">How Verista relates to this</h2>
<p>Verista gives every item a unique, verifiable record anchored on a public blockchain and reachable from a QR code. Each certificate is identified by its contract and token number, carries the brand's own template fields, and keeps a full ownership history. Brands manage it all through <a href="/platform">Verista Cert</a>, and every capability is available through the same APIs our own apps use, so ERP and point-of-sale systems can integrate directly — see <a href="/developers">Developers</a>.</p>
<p>A Verista certificate is not, on its own, a regulation-compliant passport: a passport must carry exactly the data its delegated act requires. But the hard parts — a unique identity per item, a data carrier, a record that can be checked independently — are already in place.</p>

<h2 id="what-to-do-next">What to do next</h2>
<ol>
  <li>Identify the delegated acts that cover your product groups and track their timelines.</li>
  <li>Audit what product data you hold today, and at what granularity.</li>
  <li>Decide whether item-level records serve goals beyond compliance — authenticity, resale, service.</li>
</ol>
<p>If you would like to talk through how verifiable certificates fit your plans, <a href="/contact">get in touch</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>What makes a certificate of authenticity trustworthy?</title>
      <link>https://verista.co/blog/what-makes-a-certificate-of-authenticity-trustworthy</link>
      <guid isPermaLink="true">https://verista.co/blog/what-makes-a-certificate-of-authenticity-trustworthy</guid>
      <pubDate>Fri, 09 Oct 2026 13:56:38 GMT</pubDate>
      <category>Provenance &amp; Authenticity</category>
      <dc:creator>Verista Team</dc:creator>
      <description>A certificate of authenticity is only as good as your ability to check it. Here are the five properties that make one trustworthy — and how Verista builds each into every certificate it issues.</description>
      <content:encoded><![CDATA[
<p>Every collector has seen one: a handsome card, an embossed seal, a signature — and no practical way to confirm any of it. A certificate of authenticity is meant to settle a question of trust, yet most of them only move it. You stop asking "is this object genuine?" and start asking "is this certificate genuine?"</p>
<p>A certificate earns trust when it holds up to checking, not when it looks official. Five properties make the difference.</p>

<h2 id="1-it-can-be-verified-independently">1. It can be verified independently</h2>
<p>If the only way to confirm a certificate is to ask the company that printed it, you are trusting that company's database, its staff and its continued existence. A trustworthy certificate can be checked against a record that no single party controls.</p>
<p>Verista anchors every certificate to a public blockchain record on Base. The record carries the certificate's serial number, its descriptive data and references to its images, and anyone can inspect it — through <a href="/verification">Verista's verification</a> or directly on-chain.</p>

<h2 id="2-its-issuer-is-identifiable">2. Its issuer is identifiable</h2>
<p>A certificate is a claim made by someone. The question is <em>who</em>. Each Verista certificate is minted from a contract that belongs to a specific issuer's template, and it records which wallet minted it. Verification shows the issuing organisation, so a convincing-looking certificate from an unknown source is immediately visible as exactly that.</p>

<h2 id="3-it-cannot-be-silently-altered">3. It cannot be silently altered</h2>
<p>Paper can be edited with a scanner and some patience; a row in a database can be changed by anyone with access. A trustworthy certificate makes tampering evident. Because a Verista certificate's data is written on-chain, every update is itself a recorded event rather than a quiet overwrite.</p>

<h2 id="4-it-records-every-change-of-owner">4. It records every change of owner</h2>
<p>Provenance is the story of an object's custody, and a story with gaps invites doubt. Each Verista certificate keeps an ownership history on-chain: every transfer, from the issuer to a distributor to a collector and onward, is part of the record.</p>
<table>
  <thead><tr><th>Question a buyer asks</th><th>Where the answer comes from</th></tr></thead>
  <tbody>
    <tr><td>Who made this?</td><td>The issuer behind the certificate's contract</td></tr>
    <tr><td>Who owns it now?</td><td>The current on-chain owner</td></tr>
    <tr><td>Where has it been?</td><td>The certificate's ownership history</td></tr>
    <tr><td>Is it still valid?</td><td>Its voided status</td></tr>
  </tbody>
</table>

<h2 id="5-it-can-be-revoked-visibly">5. It can be revoked — visibly</h2>
<p>Things go wrong: an item is reported stolen, or a certificate was issued in error. A trustworthy system lets the issuer invalidate a certificate and makes that fact impossible to miss. When an issuer voids a Verista certificate, verification reports it as voided, so it cannot quietly keep circulating as if it were good.</p>

<h2 id="identity-is-the-pair-not-the-number">Identity is the pair, not the number</h2>
<p>One detail matters more than it looks. A token number alone is not unique — every contract starts counting from zero. Verista identifies a certificate by its <strong>contract address and token number together</strong>, everywhere: in its records, its APIs, its QR codes and its audit logs. That is what stops two different certificates from ever being mistaken for one another.</p>

<h2 id="what-this-means-for-you">What this means for you</h2>
<p>For a brand, a certificate built on these properties protects the value of what you make long after the first sale. For a collector, it turns "trust me" into "check for yourself". Read <a href="/how-it-works">how Verista works</a>, or see the <a href="/use-cases">kinds of objects</a> it is built for.</p>
]]></content:encoded>
    </item>
    <item>
      <title>How to verify a Verista certificate in under a minute</title>
      <link>https://verista.co/blog/how-to-verify-a-verista-certificate</link>
      <guid isPermaLink="true">https://verista.co/blog/how-to-verify-a-verista-certificate</guid>
      <pubDate>Wed, 07 Oct 2026 13:56:38 GMT</pubDate>
      <category>Guides &amp; How-tos</category>
      <dc:creator>Verista Team</dc:creator>
      <description>Holding an object with a Verista certificate? This step-by-step guide shows how to check it, what each part of the verification result means, and what to do if something looks wrong.</description>
      <content:encoded><![CDATA[
<p>Whether you are buying a pre-owned watch, receiving a gift or simply curious about the QR code on a tag, checking a Verista certificate takes less than a minute. Here is how, and how to read what you see.</p>

<h2 id="step-1-open-the-certificate">Step 1: Open the certificate</h2>
<p>Scan the certificate's QR code with your phone's camera, or open the certificate link you were given. Make sure the page that opens is a genuine Verista page — look at the address bar — or go to <a href="https://verify.verista.co">verify.verista.co</a> yourself.</p>

<h2 id="step-2-check-the-issuer">Step 2: Check the issuer</h2>
<p>The result shows which organisation issued the certificate. It should be the brand or institution you expect. An unfamiliar issuer on a famous product is the first thing to question.</p>

<h2 id="step-3-match-the-details-to-the-object">Step 3: Match the details to the object</h2>
<p>Compare the serial number and the descriptive details — model, materials, dates — with the object in front of you. A certificate describes one specific item, so every detail should agree. Look at the certificate's images too.</p>

<h2 id="step-4-read-the-status">Step 4: Read the status</h2>
<table>
  <thead><tr><th>The result shows</th><th>What it means</th></tr></thead>
  <tbody>
    <tr><td>Verified on-chain</td><td>The certificate exists on the blockchain record and is in good standing.</td></tr>
    <tr><td>Activated</td><td>The certificate has been activated for its owner, for example at the point of sale.</td></tr>
    <tr><td>Voided</td><td>The issuer has invalidated it. Treat the certificate as no longer valid.</td></tr>
  </tbody>
</table>

<h2 id="step-5-look-at-the-ownership-history">Step 5: Look at the ownership history</h2>
<p>The history shows each time the certificate changed hands — typically from the issuer, sometimes through an authorised distributor, and then between owners. If you are buying, the seller should be the current owner, and once the sale completes you should receive the certificate through a transfer into your own vault.</p>

<h2 id="if-something-looks-wrong">If something looks wrong</h2>
<ul>
  <li><strong>The page is not a Verista page.</strong> Go to verify.verista.co directly rather than following the link.</li>
  <li><strong>Details do not match.</strong> Pause the purchase and ask the issuer to confirm.</li>
  <li><strong>The certificate is voided.</strong> Do not rely on it. Contact the issuer for the reason.</li>
</ul>

<h2 id="after-you-buy">After you buy</h2>
<p>Ask the seller to transfer the certificate to you. You will receive a one-time claim link or QR code; claiming it places the certificate in your own <a href="https://vault.verista.co">Verista vault</a> and adds you to its ownership history. Questions? Visit the <a href="/help-center">help center</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Why provenance matters when an object changes hands</title>
      <link>https://verista.co/blog/why-provenance-matters-in-resale</link>
      <guid isPermaLink="true">https://verista.co/blog/why-provenance-matters-in-resale</guid>
      <pubDate>Mon, 05 Oct 2026 13:56:38 GMT</pubDate>
      <category>Resale &amp; Circularity</category>
      <dc:creator>Verista Team</dc:creator>
      <description>Resale is where questions of authenticity and history are asked hardest. Here is how a transferable, verifiable certificate changes the second sale — for the seller, the buyer and the brand.</description>
      <content:encoded><![CDATA[
<p>The first sale of a fine object comes with a boutique, a box and a receipt. The second sale often comes with a photo, a story and a request for trust. That gap is where counterfeits hide, where good objects sell for less than they should, and where buyers walk away.</p>

<h2 id="the-second-sale-is-the-real-test">The second sale is the real test</h2>
<p>At resale the original seller is no longer in the room. Buyers can't ask the brand's staff, and paperwork can be lost, copied or forged. What they need is a record that survives the change of hands: proof the object is genuine, and a history of where it has been.</p>

<h2 id="a-certificate-that-travels-with-the-object">A certificate that travels with the object</h2>
<p>A Verista certificate is transferable by design. When an owner sells, the certificate moves to the buyer, and the ownership history gains a new entry. Nothing is reissued and nothing is re-keyed by hand: the same certificate, with the same issuer and the same serial number, now names a new owner.</p>
<ul>
  <li><strong>For the seller</strong>, it is evidence that supports the asking price.</li>
  <li><strong>For the buyer</strong>, it is something to check before paying, not a promise to take on faith.</li>
  <li><strong>For the brand</strong>, it keeps a thread to the product through every owner.</li>
</ul>

<h2 id="how-a-transfer-works">How a transfer works</h2>
<ol>
  <li>The current owner opens the certificate in their Verista vault and starts a transfer.</li>
  <li>Verista creates a time-limited, one-use claim, shared as a link or QR code.</li>
  <li>The buyer claims it into their own vault.</li>
  <li>The transfer is confirmed on-chain and added to the certificate's ownership history.</li>
</ol>
<p>Neither party needs to understand wallets or gas fees. The blockchain does its job in the background: it is the source of truth for who owns the certificate now.</p>

<h2 id="privacy-by-default">Privacy, by default</h2>
<p>A public history doesn't have to mean public identities. Ownership is recorded from wallet to wallet; names and email addresses are not part of the on-chain record. When an issuer or distributor sees details about a collector, Verista masks them.</p>

<h2 id="circularity-needs-trust-to-work">Circularity needs trust to work</h2>
<p>Keeping well-made objects in use for longer is good for owners and for the planet, but secondary markets only thrive when buyers feel safe. Verifiable provenance lowers the risk of every resale, which in turn makes it easier for objects to keep circulating. Explore the <a href="/use-cases">use cases</a> Verista supports, or read how we approach <a href="/security">security</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>How Verista protects the wallets that issue your certificates</title>
      <link>https://verista.co/blog/how-verista-protects-the-wallets-that-issue-certificates</link>
      <guid isPermaLink="true">https://verista.co/blog/how-verista-protects-the-wallets-that-issue-certificates</guid>
      <pubDate>Sat, 03 Oct 2026 13:56:38 GMT</pubDate>
      <category>Security &amp; Trust</category>
      <dc:creator>Verista Team</dc:creator>
      <description>An organisation&apos;s shared wallet mints and transfers its certificates, so it is worth protecting carefully. Here is how Verista&apos;s co-signing model, organisation-wide two-factor authentication and audit trail work together.</description>
      <content:encoded><![CDATA[
<p>When a brand issues a certificate on Verista, the certificate is minted by the brand's own <strong>shared wallet</strong> — a smart wallet that belongs to the organisation, with its team members as owners. Whoever controls that wallet can mint, transfer and void certificates. So how it is protected matters as much as anything else we build.</p>

<h2 id="members-sign-and-so-does-verista">Members sign, and so does Verista</h2>
<p>Verista uses a co-signing model. Each team member has a signing wallet for their organisation, controlled jointly: an operation goes through only when <strong>the member and Verista both approve it</strong>. Neither can act alone.</p>
<p>That second signature is not a rubber stamp. Before Verista co-signs, it:</p>
<ul>
  <li>decodes the operation and checks it is a function the platform allows;</li>
  <li>checks the member's permissions in the organisation, read fresh rather than from a session that may be out of date;</li>
  <li>confirms the operation targets one of the organisation's own certificate contracts and sends no funds;</li>
  <li>checks the operation matches what was prepared — for example, that a mint carries exactly the recipient and certificate data that were set up for it.</li>
</ul>
<p>And some requests are refused unconditionally: Verista will never co-sign an attempt to export a key.</p>

<h2 id="why-verista-can-never-act-alone">Why Verista can never act alone</h2>
<p>Verista holds two keys, a primary and a backup, so that losing one doesn't lock organisations out. But the two are structured as a single approval. Together they still cannot act without a member — so even a compromise of Verista's own systems would not, on its own, let anyone sign for your organisation.</p>

<h2 id="one-write-at-a-time">One write at a time</h2>
<p>A shared wallet processes operations in sequence. If two colleagues tried to issue certificates at the same instant, their operations could collide. Verista gives each wallet a short lease that one member holds while their operation is submitted and confirmed, so team members never trip over one another.</p>

<h2 id="two-factor-authentication-organisation-wide">Two-factor authentication, organisation-wide</h2>
<p>Organisation owners can require two-factor authentication for every member — themselves included — using an authenticator app. Once it is required, a member without it cannot sign in until they set it up, and a signed challenge is needed at every sign-in.</p>

<h2 id="when-people-leave">When people leave</h2>
<p>Removing someone from an app is easy; removing their ability to sign on-chain is the part that matters. Off-boarding a member is restricted to the organisation's owner, and it rotates that member's wallet out of the shared wallet's owners on the blockchain itself.</p>

<h2 id="a-trail-for-everything">A trail for everything</h2>
<p>Every significant action — issuing, transferring, voiding, membership and role changes, refused signatures — is written to an append-only audit log by Verista's servers, never by client apps, and organisations cannot delete their own trail.</p>
<p>Read more about our approach on the <a href="/security">security page</a>, or in the <a href="https://docs.verista.co">documentation</a>.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
