DBO provides the ability to deploy and manage various types of nodes own OTC cloud platform, which is fully secure and EU-compliant. This is the default option, and the first node on any instantiated GBE blockchain will always be an OTC node.

As illustrated by recent service failures, a blockchain in which all nodes reside on a single cloud provider is not a true blockchain. Therefore, it is absolutely necessary for any production blockchain solution to support the creation of nodes that run on a number of different clouds; it is also extremely important for mission-critical infrastructure such as validator nodes in order to maximize uptime. GBE provides the capability to establish DLT nodes on most of the major cloud providers currently in operation.

Despite the increasing prevalence and advantageous cost case for cloud computing, there are a number of situations and use cases where it still makes sense to run a DLT node on provider-owned servers or data centers. GBE provides the capability for users to instantiate DLT nodes within their own infrastructure.

Our long track record in securely running mission-critical infrastructure for a large number of German industry players and state institutions allows us to guarantee security and efficiency for your blockchain infrastructure and your applications. The Open Telekom Cloud, Deutsche Telekom's public cloud offering, is the only cloud available in Germany to be awarded the "Trusted Cloud" certificate initiated by the German Federal Ministry of Economics and Energy - Data Center Insider.

In many countries and many use cases, there are strict data residency rules that insist on customer data never leaving defined international boundaries. GBE’s infrastructure capabilities allow the construction of DLT solutions that are capable of fully complying with such data residency requirements.

In this deployment model, GBE users have the ability to create and manage new, dedicated DLT ledgers, for use in creating completely new public or permissioned DLT solutions. To private ledgers are under the full control of their creator, and accessible only to whom the creator makes them visible. This capability automates the setup and configuration of any supported DLT protocol, and allows the ledger to be visible and manageable via the full set of GBE tools.

Many DLT projects are not about instantiating new ledgers, but implementing new solutions for existing ledgers; this is particularly true for some of the larger permissionless ledgers like the main Ethereum ledger. For these situations, GBE provides a Model Public Chain, an environment in which projects can develop and test their solutions prior to using the publicly visible ledgers or their testnets. GBE provides a Model Public Chain for each of its supported DLT protocols.

For projects that wish to use other DLT protocols, GBE provides the option to create a Protocol SanGBEx. The Protocol SanGBEx does not include the native substantiation, node creation, or monitoring tools provided for the natively supported DLT protocols, but it does provide a secure space in which projects can manually set up and configure nodes for any DLT protocol they wish.

The GBE Realizations include fully completed design artifacts that can be used as templates and as starting points to accelerate the delivery of projects built on GBE. Available artifacts include
►Personae
►User journeys
►dApp wireframes
►User stories
►Data models
►Project plans

GBE provides a full management dashboard for monitoring and configuration of all GBE services and capabilities. This dashboard is built over a fully functional set of supported API’s, so that GBE users have the option of integrating GBE capabilities within their own systems management dashboards, tools, scripts, and analytics.

To properly test the behaviour of both distribute ledgers and smart contracts under load, GBE provides a mechanism for simulating live solution traffic. Projects can define a Transaction Injector that accepts comma-delimited files in a specified format with input transactions for the solution being developed. Transaction injectors can be used for performance/stress testing, functional acceptance testing, and sales demos.

In the majority of enterprise blockchain use cases, a group of enterprises agree to share a single version of truth about a particular class of assets or services (e.g. insurance policies, shipping containers, land deeds, medical records, etc.) amongst a trading network of enterprises that do business with one another. Often, this trading network will require a known and accepted single source of truth for information; for instance, an application that tracked shipping containers would need a source of weather information that everybody agreed was the reference point for weather. Trusted authorities like this have come to be known an as Oracle (no relation to the software company of the same name). GBE provides tools that make it easy to set up and establish oracles for DLT solutions built by GBE users. These oracles will be accessible by all network users of the deployed solution, whether those users are on GBE or not.

GBE includes the capability to perform bulk data loads, both onto distributed ledgers and off-chain storage.

Since almost all DLT use cases involve multiple parties agreeing a single version of the truth, it is often desirable to let multiple parties validate transactions without divulging private or protected data. GBE includes a zero-knowledge proof module that allows for trusted validation (e.g. of identity, status, location, etc) without needing to share the underlying data.

Since a significant number of blockchain solutions have a functional requirement of being able to accept payments, GBE will include integrated support for a curated number of secure payment gateway providers.

In addition to the value-added services offered directly by T-Systems, GBE will include a solution marketplace that allows carefully selected third parties to offer their own extensions of GBE functionality.

To ensure that DLT project teams spend their time adding value rather than wasting time on purely mechanical coding tasks GBE supplies working dApp templates that already include the necessary code to connect to distributed ledgers and off-chain storage hosted on DLT. Project teams can start with these templates and customize them to meet their specific design requirements.

Since the whole point of GBE is to allow project teams to get their solutions up and running as quickly as possible, T-Systems has invested in the creation of working blockchain prototypes that can serve as delivery accelerators, starting from a point where all of the basic functionality for a working blockchain solution has already been in place, so that your project team can focus exclusively on the parts of your solution that add value. We call these prototypes Realizaitions. The initial GBE Realizations focus on the two areas of blockchain solution development that are currently most prevalent:
►Supply Chain Track and Trace:
Establishing the provenance of components in a supply chain is difficult, time-intensive, and critically important in many situations, and because of its inherently multi-party nature, supply chain provenance is particularly well-suited to blockchain solutions. To this end, GBE includes a Supply Chain Realization that allows individual project teams to start with a provenance solution that already works, so all they have to do is adapt it to their own particular data, UX, and business process requirements.
►Shared Record Management:
Many blockchain use case domains, such as medical records, land registry, and identity, have a strong degree of functional similarity, in that they are all focused on multiple parties holding a single source of truth that is shared and kept synchronized between all members of a business network. The GBE Shared Record Management Realization provides all the functional basics for separate legal entities sharing a single version of a data record.