Staying Cool This Summer with New Features and Improvements​

Result sorting, enhanced schema evolution, improved ingestion and consensus performance, geo-blocking and more​​

Our engineering teams have released a number of cool new features and improvements over the last month. As always, see our Docs for the complete details of each new feature and our Examples for more guidance.

New Authorization Options

Vendia Share now supports multiple forms of authorization to a Node within a Uni.

API Keys

For those who prefer to create and use API Keys for authorization, this can now be performed through the Share UI, the Share GraphQL API, or the Share CLI. A Node can now support multiple API Keys and each key can have a unique expiration time.

share node add-api-key \
    --uni 'my-uni-name' \
    --node 'my-node-name' \
    --name 'my-api-key-name' \
    --expiry '2022-08-31'

When using an API Key, place the value of the key in the Authorization header when submitting GraphQL requests to the Node to which the API Key is associated.

curl '' \
    -H 'Authorization: MY_API_KEY_HERE' \
    -H 'content-type: application/json' \
    -H 'accept: application/json' \
    --data-raw '{"query":"query blocksQuery {  listVendia_BlockItems {    Vendia_BlockItems {      blockId      blockHash    }  }}","variables":null,"operationName":"blocksQuery"}' \


For those who prefer to use JSON Web Tokens (JWTs) for authorization, this can now be configured through the Share UI or the Share GraphQL API. JWT authorization requires a small handful of configuration properties, from which your Vendia Share Node can perform all the necessary JWT verifications needed on subsequent GraphQL API calls.

When using a JWT, place the value of the key in the Authorization header when submitting GraphQL requests to the Node whose configuration reflects the identity provider that issued the JWT. Note the Bearer prefix in the Authorization header value below.

curl '' \
    -H 'Authorization: Bearer MY_JWT_HERE' \
    -H 'content-type: application/json' \
    -H 'accept: application/json' \
    --data-raw '{"query":"query blocksQuery {  listVendia_BlockItems {    Vendia_BlockItems {      blockId      blockHash    }  }}","variables":null,"operationName":"blocksQuery"}' \

With the release of these new authorization options comes the end of the legacy authorization options previously supported.

Sorting Results

The ability to sort results based on a field was a frequent request from our users over the last few quarters. We ranked your feedback (in ascending order) and got to work!

Now, any indexed field can be used to sort the results returned by a list operation. For example, if the name field of the Inventory entity is indexed, the list of products can be returned in order by name:


query OrderedInventoryList {
  list_InventoryItems(limit: 100, order: {name: DESC}) {
    _InventoryItems {

Client SDK

Even better, the Vendia Share Client SDK makes sorting extremely simple.

const orderedProducts = await entities.inventory.list({ limit: 100, order: { name: 'DESC' } })

Schema Evolution

Because indexes can now be used to sort results, we've also made it easier to manage indexes (i.e. add and remove) during scheme evolution.

Share CLI

You can now remove an index, which was previously deemed a breaking change, using the --allow-breaking-change=INDEX_REMOVED flag available through the share uni evolve CLI command. This allows a user to add or remove an index simply and easily, likely enabling filtering and sorting on the fields of most interest to your users and applications.

Share UI

Likewise, the Share UI has been enhanced to allow schema evolution from the Schema view of a Uni.

Schema Evolution in Share UI

The Share UI view also includes a very helpful "diff" feature that allows you visually inspect a schema change priory to confirming the schema evolution.

Schema Diffs in Share UI

Control Plane and Data Plane Geo-Blocking

To help protect our customers, Vendia Share's Control Plane and all of its operations are now inaccessible to traffic originating from a set of high-risk countries. This technique, known as geo-blocking, blocks traffic originating from IP addresses in specified geographic regions.

This same mechanism is now also in place on our Enterprise customers' Data Planes (i.e. protecting the GraphQL interfaces of your Nodes).

This additional layer of protection is one of many security mechanisms in place to keep your Vendia account, your Unis, and the data in your Unis safe.

Improved Ingestion and Consensus Performance

Vendia Share heavily leverages the serverless services of the major public cloud service providers. The scale, resilience, and performance of those services is unmatched and, as a result, so is Vendia Share's own scale, resilience, and performance.

Over the last month, we've made substantial improvements to the throughput available to our customers. This includes both ingestion performance (i.e., the number of transactions accepted by a Node in a given time period) and consensus performance (i.e., the number of transactions ledgered across a Uni in a given time period). We have successfully increased ingestion performance and consensus performance by 10x and will continue to optimize our internal ingestion and consensus implementation to maximize the value of the serverless capabilities on which Vendia Share is built.

For more information about Vendia Share's current and near-term performance targets, as well as the real-time data sharing workloads for which Share is unmatched, contact us.

Developer Tooling

For those who are new to Share, you may find these packages helpful as you explore these new and improved Share features:

  • Vendia Share CLI - Interact with the Vendia Share Control Plane from the comfort of your CLI
  • Vendia Share SDK - Interact with the Vendia Share Control Plane from the comfort of your Node application
  • Vendia Share Client SDK - Interact with your Uni using a type-safe TypeScript & JavaScript client, with auto-generated code customized to match your Uni's schema