Skip to content

Arkova Monthly

August 2026 issue

Product, security, and partnership updates — no filler. Read the August 2026 issue as published. Feature and partnership status reflects that date and may have changed; check the current app or contact us for availability.

Issue · August 2026

A month of proving things: the DocuSign integration goes live, the MCP server and Python SDK ship for agents, Arkova launches in Kenya, and fifty records round-trip through the Credential Engine registry.

Archived August 2026 issue. The PDF preserves the original issue text.

Download August 2026 PDF

Who are we

Arkova is the trust layer for records, humans and AI agents alike. We create a cryptographic fingerprint of each document and anchor that proof to an immutable public ledger, so anything issued once can be verified forever, by anyone, without trusting us or anyone else to hold the original. Our updated deck can be found here.

This month at Arkova

August was a month of proving things rather than announcing them.

We put proposals in front of 8 organizations ranging from legal and web3, to cybersecurity and AI governance. We've also seen strong early interest from representatives of the current Presidential Administration when it comes to implementing Arkova into the federal government's legal workflows, as well as utilizing Arkova for Track and Trace policy enforcement.

We've made some big strides in Africa. Aside from launching to Hakichain - our partners in Nairobi - Uyiosa represented Arkova at Decentralized World in Lagos on 15 August and has been converting that room into meetings since, with multiple solid leads already in the pipeline. He is also building out prospecting across the continent and giving us a much clearer read on the regulatory picture market by market. We enjoyed conversing with founders building stablecoin and wallet infrastructure, as well as representatives from the largest collective of blockchain organizations in Nigeria, VASPA.

What we can talk about in detail is the work underneath.

The Credential Engine registry test.

In June, Credential Engine allowed us to run a small consuming test against their registry to ensure a few records resolved end to end. We ran fifty. All fifty resolved. All fifty round tripped to the correct identifier. Median response time was 213 milliseconds. A deliberately invalid identifier failed honestly rather than returning something misleading. We also ran a control with our credential stripped out, which correctly refused the request, confirming the key was doing real work. Nothing was anchored during this test, which was read only by design. We shared the full results with Credential Engine before anyone else, including the one transient episode we saw and the two design questions it raised.

Jenny Parks has spent August opening conversations across higher education and professional licensing, including introductions we would not have reached cold. Recently we spoke with Holly Zanville, Executive Director of the Learn and Work Ecosystem Library about the challenges employers, job seekers are facing when it comes to verifying professional licenses and academic records, a problem Arkova is poised to solve.

Kenya.

We are happy to announce that we have successfully launched Arkova to our friends in Kenya. While the code has been ready since July, the data protection agreement was not. While the risk in launching without the paperwork being completely finished was nearly zero, we felt as a compliance company we should lead by example. A big thank you to our friends at MNA Africa in Nairobi for working across three continents to get this done so seamlessly

Security and governance.

We formalised our arrangement with Sekura covering static and dynamic scanning plus continuous monitoring, and began an exploratory conversation with a Washington DC government affairs firm on credential verification in immigration and in defence supply chains.

Product update

This month we shipped:

  • Our Docusign Integration went live (and Adobe Sign and Google Drive are right behind it). Right now your Arkova organization can connect your organizations Docusign account so that every time you issue a contract, and it is executed, that contract is anchored to an immutable ledger, leaving behind an anonymized proof record of that contract that links back to the issuer account, and the contract itself. Perfect for anyone looking to have their agents quickly verify the validity of a contract in case of a dispute. Carson and Sarah think this is the coolest thing since sliced bread. Unfortunately most people don't find sliced bread particularly hip.
  • We now accept 20+ file types. Including .docx, .pdf, .svg, .mp4, and even .gif
  • MCP server live for agent integrations, and Python SDK published. Agents can now verify a document before acting on it, authenticated by API key or OAuth, and receive a machine readable answer covering authenticity, timestamp and issuer. Every check returns a receipt that becomes part of the agent's audit trail. The SDK is available on PyPI as arkova 2.2.0 on an MIT License, the license from MIT is the only thing anyone on our team has ever received from MIT.
  • Speaking of Education, Arkova did a CTDL registry, fifty record consuming test. Covered above.
  • Anyone can check a record at search.arkova.ai without an Arkova account using a public ID. Give it a shot: ARK-DOC-GDUP4G

Partnerships

Partnerships are going strong, with more in the pipeline and a few conversations we're not ready to talk about yet.

On the calendar

Sarah will be attending Tech Everest Event in Sydney on 3 September.

Carson will be hosting an event at Grand Rapids Tech Week on 15th September.

Carson is speaking at the Midwest Bitcoin Conference, 23rd & 24th September 2026.

Get the next issue

Monthly product, security, and partnership updates.

Subscribe to Arkova Monthly by email for product, security, and partnership updates, about once a month. To withdraw your request, email hello@arkova.ai. See how we handle your details in our Privacy Policy.