Scaling is synonymous with the business game, and automation is the key to doing it efficiently.

Knowing this, banks and traditional financial institutions have long used automation to increase their competitive advantage, maximize operational efficiency, and minimize human intervention required for day-to-day operations.

However, digital assets remain largely in manual mode. Most transactions are still done with the click of a mouse or the tap of a finger, and more than a few transactions per minute is usually out of the question.

Introduction: Compute Hosting

Qredo's compute hosting willDistributed Multi-Party Computing (dMPC)Combine with automation to raise the scalability ceiling of digital asset operations—enabling your organization to support millions of transactions per day.

It's like having a trustless escrow engine that automatically signs transactions on your behalf based on pre-determined criteria.

But how does this engine work?

How Compute Hosting Works

Computational hosting is powered by Qredo's powerful policy engine.

This policy engine enables you to build by choosing from building blocks of different role types including trader, administrator and approvercustom governance, each role type has its own activities and access rights. In this way, you can create secure transactional workflows that reflect your team's specific structure.

When a transaction is started, each assigned approver in that governance policy must sign the transaction before it can be sent. This initiation and approval is done through the Qredo Signature application.

To approve a transaction, the Signature app biometrically verifies the user with the touch of a fingerprint, and then authorizes the transaction using a digital signature.

In a nutshell, Compute Hosting replaces Qredo signing applications with secure servers (signing agents).

Using Qredo's open-source library, you can configure signing proxies to manage transaction routing based on specific criteria such as size, destination address, or originator.

This signing agent hosts your BLS keys to sign transactions, either on your own infrastructure or initialized in a escrow service.

What is a BLS signature?

Qredo uses BLS (Boneh-Lynn-Shacham) signatures to implement a threshold signature scheme that immutably records governance policies on the Qredo chain.

When initiating a transaction, each approval creates a BLS (Boneh-Lynn-Shacham)digital signature. After receiving the necessary threshold of BLS signatures, Qredo completes the transaction.

Compute Hosting Use Cases

In addition to alleviating signature fatigue caused by manually approving dozens of transactions per day, programmatic digital asset management presents multiple opportunities to strengthen governance policies and streamline operations:

Simplify operations with whitelists

Organizations can use Compute Escrow to set up whitelist rules that automatically approve transactions if they meet certain criteria (for example, if the destination address matches that of a known counterparty).

Alternatively, DeFi funds might use whitelists to safely interact with dApps by granting automatic access to certain smart contracts within the dApp while blocking other potentially malicious contracts.

Reduce latency by pre-confirming transactions

In the fast-paced digital asset market, milliseconds can make the difference between successfully taking an opportunity and being left out.

Pre-approving transactions can play a key role in minimizing delays. For example, a fund manager might give a trader the ability to trade at will within certain limits. Any trade that does not exceed these limits (which may be based on anything from the size of an individual trade to the total volume traded over a specified period) is automatically approved.

Therefore, when a market opportunity arises, traders can quickly seize it without being forced to wait for approval.

trade between multiple teams

By programming rules with basic Boolean operators (and, or, and not), compute escrow enables transactions to be routed between different teams and governance structures.

For example, your fund might structure a governance policy where all deal approvals below a certain amount are sent to policy group A, the operations team. Alternatively, if the transaction exceeds a certain amount, it is automatically routed to Group B for approval by the transaction team.

Alternatively, the designated approver may depend on who initiated the trade; junior traders have more oversight of their trades, and senior traders are automatically approved.

In another case, a particularly large order might be routed to multiple groups—for example, requiring approval from the operations team before final approval from the deal team. Each individual policy group will be structured in the same way as normal, requiring a certain number of "approvers" to approve transactions, but adding additional layers of governance as the transaction size increases.

When will compute hosting be available?

Compute hosting is currently in development and will be rolled out gradually over the next six months.

andLinkedInandTwitterQredo Chinese page:

Original link:https://www.qredo.com/blog/computational-custody-is-coming 

Qredo Chinese page:qredo.com/zh-cn