Advanced Cyber Security Infrastructure for Next-Generation Attacks

Using an Identity and Asset Control Gateway, AVEUM provides protocol infrastructure for public institutions, family offices and digital asset custody operators. Institutions define authority and policy, while custody operators retain responsibility for custody and signing.

Sovereign Identity

Identity systems under public authority.

Aveum’s sovereign identity work concerns national and institutional identity infrastructure. It is intended for environments in which a public authority must determine how identity is established, verified, maintained and used across authorised processes.

The architecture is scoped around the institution’s legal mandate and operating procedures. Registry policy, evidential standards and official decisions remain with the responsible authority; the protocol provides the structure through which those requirements can be applied consistently.

Government registries

Registry architectures in which records, permissions and changes remain subject to defined public authority, with clear separation between administrative and operational roles.

Forensic institutions

Controlled identity workflows for specialist examination and formal determination, designed around the procedures and evidential requirements of the institution concerned.

National identity

Infrastructure for national identity programmes that require defined enrolment, verification, recovery and continuity arrangements under sovereign control.

Controlled verification

Where a workflow requires confirmation rather than disclosure, verification can be scoped to the decision at hand. Institutions can define which functions are available to each participant without routinely exposing an entire underlying record.

Digital Asset Custody

Custody organised around separate duties.

Aveum applies the same authority model to digital asset vaults. Separate vault functions allow operation, protection and longer-term transfer to be governed through distinct roles and approval routes.

Two configurations address different operating requirements: an extended structure for family offices and a compact model for multi-party computation operators. Each deployment begins with the institution's mandate rather than a standard set of permissions.

Extended configuration

1+20Family Vault + Balaenoptera model

For family offices and other institutions requiring an extended vault structure. This is the initial production configuration, with customer access and adaptor integration forming part of the deployment environment.

Main vault
1
MVS vaults
up to 10
Family or Balaenoptera vaults
up to 10

The structure supports separation between day-to-day operation, asset-class segregation, treasury operations, designated key person succession protection and longer-term transfer for families in crisis. Vault roles, approval routes and transfer procedures are configured to the specific mandate, and smart contract locked.

Compact configuration

1+4MPC operator model

IDEAL FOR WAAS accounts within the MPC customer base that require unmatched forensic grade security.

Operational responsibilities and approval requirements are established during deployment, allowing the operator to retain a clear distinction between its own role and those of other participants.

Operator interface

A non-nameplate, adaptable customer interface is offered for 1+4 operators, allowing them to apply and carry their own design.

Ark-512P

A common protocol, expressed in operational terms.

Ark-512P is the protocol architecture used across Aveum’s identity and custody work. It provides a common way to describe authority, approvals and continuity while allowing each institution to retain its own policies.

In plain terms, the protocol addresses four questions: who has authority, how that authority is divided, which route an action must follow, and how control continues when people or circumstances change.

  1. Establish authority

    Define who or what is recognised, which institution stands behind that recognition and which responsibilities follow from it.

  2. Distribute approval

    Divide authority among designated participants so that actions can require more than one approval and need not depend on a single account or individual.

  3. Bound each function

    Assign operating, protection and transfer responsibilities to defined vaults or processes, with explicit routes for permitted actions.

  4. Provide for continuity

    Treat recovery, replacement and succession as governed changes to the system, rather than informal handovers outside its control structure.

What multi-party computation means

Multi-party computation, or MPC, allows participants to contribute to a cryptographic authorisation while retaining separate secret material. In operational terms, it supports shared control without placing the complete signing capability in one participant’s hands. Ark-512P places this mechanism within a wider structure of institutional roles and procedures.

Ark-512P ? authority layer for institutional MPC custody

MPC controls signing. Ark-512P controls entitlement.

Multi-party computation distributes signing capability across participants and enforces the custody provider?s approval policy. Ark-512P adds an independent authority gate before an instruction enters that MPC policy.

The layers have distinct responsibilities. The custody provider remains responsible for custody operations, quorum policy and signing. Ark-512P evaluates whether the principal and requested action are authorised under the institution?s configured rules. An instruction proceeds only after both control layers pass.

Custody and signing

The MPC operator retains its existing custody, key-management, approval and signing responsibilities.

Authority and context

Ark-512P checks the entitled principal, authorised operating environment and context of the requested action.

Governance rules

Institutional policy defines permitted actions, vault relationships, approval routes and continuity procedures.

How an instruction passes through the protocol

  1. Initiate

    An operator submits an instruction through the institution?s workflow with its transaction context.

  2. Verify authority

    The protocol checks the principal and registered operating environment against the institution?s authority record.

  3. Validate the request

    A fresh, single-use proof is bound to the requested action and evaluated against governance rules. Invalid, expired or reused proof is denied.

  4. Apply MPC policy

    An entitled request enters the custody provider?s established approval and MPC signing workflow. The signed transaction then proceeds to the relevant settlement network.

Independent pre-sign control

The authority decision sits before MPC policy approval. It addresses a different failure mode: a technically valid signing request that the legitimate authority did not permit. The integration review identifies every path to MPC policy and verifies that no unapproved path bypasses the authority gate.

Governance and failure behaviour

Configured rules can constrain eligible destinations and vault relationships, separate operating and protection duties, limit actions, and define lock, recovery and succession procedures. A failed authority check stops the request and records the failure for the configured response.

Security boundary

Ark-512P complements MPC controls; it does not replace them. Custodian bypass, compromised devices, coercion, integration errors and software defects remain risks that require independent controls, testing and incident response. Each deployment requires a threat-model review and evidence that the authority gate is enforced at the transaction boundary.

Detailed implementation and assurance materials are provided through controlled technical review.

Non-production environment

The new-site sandbox is being prepared for Mainnet.

The existing 24-hour testnet remains available at https://aveum.systems.

Mainnet support is being added to the new site's sandbox, which is under development. Licensed subscribers will receive the secure-site link for the Adaptor Store and Mainnet access.

The sandbox is a non-production environment and does not provide production custody or a production signing path.

Institutional Engagements

Engagements shaped by institutional requirements.

Aveum’s work is relevant where identity or asset control must remain aligned with a formal mandate. The engagement begins by establishing that mandate, the operating boundary and the responsibilities of each participant.

Government and public bodies

Sovereign identity infrastructure, registry control and continuity arrangements operating under public authority.

Forensic organisations

Controlled identity procedures with defined evidential handling, examination responsibilities and formal decision routes.

Family offices and advisers

Segregated digital asset control, multigenerational governance and structured arrangements for protection and transfer.

Custody and MPC operators

Configurable custody infrastructure, distributed authorisation and control over the operator’s customer-facing interface.

A long-term presence across Liechtenstein and Switzerland.

Aveum Systems is relocating its corporate headquarters to Vaduz in Q1 2027 and planning its Lucerne Canton offices for Q2 2027. The DACH structure assigns distinct functions to research, intellectual property, operations, licensing and marketing in Vaduz and Lucerne.

Corporate headquarters · Q1 2027

Vaduz

Liechtenstein

Our new headquarters will house sovereign research, intellectual property management and financial operations from our private foundation.

Planned offices

Lucerne Canton

Switzerland

The Lucerne Canton offices will support intellectual property licensing related to digital asset cybersecurity, as well as our full digital asset business with its own financial and administrative functions.

Corporate status

U.S. operations are suspended. The Delaware registered office is closed.

Operational updates

Current notices.

Sandbox testing

The AVEUM Sandbox is being updated and will be available for testing soon. For testing enquiries, contact [email protected].

EUCC EAL4 evaluation

Evaluation procurement is underway. For further details, contact [email protected]

Contact

Direct enquiries to the appropriate function.

Please identify your institution and jurisdiction, and outline the operating requirement in general terms. Technical and implementation details can be established after initial contact.

Sovereign identity and institutional systems

[email protected]

Legal and institutional matters

[email protected]

General administration

[email protected]

Security matters

[email protected]

Do not send private keys, recovery material, identity evidence or confidential records by email. Security enquiries should include only the information needed to establish initial contact and arrange an appropriate channel.