Skip to main content
Multi-Layer Security Wallet has a shared set of platform concepts and API/SDK resources. Every action in the web application can be performed via the API and SDK.

Platform concepts

These concepts describe how assets and governance are organized in the platform:
  • Organizations are the entities that own accounts and define governance.
  • Members are people and API members (programmatic identities) in an organization.
  • Groups are collections of members (for example, a Finance team).
  • Accounts hold funds and execute on-chain transactions.
  • Policies describe which transactions are allowed and who can approve them.
  • Admins are privileged members that can change organization configuration.
  • Transactions move value or interact with smart contracts from an account.

API and SDK building blocks

The API and SDK expose the platform concepts as resources and operations:
  • Resources represent organizations, members, groups, accounts, policies, and transactions.
  • Operations are proposed changes that require signatures before execution.
  • Signatures are collected to approve or reject an operation.
  • Execution applies the proposed change on-chain or within the organization.

Operation types

The platform exposes two types of operations. Account transactions handle on-chain activity from a specific account, while organization operations handle governance changes. Each type uses different signer roles and approval rules.
TypeDescriptionGoverned By
Account TransactionsValue movement and contract interactions for a specific accountPolicy rules
Organization OperationsGovernance changes like members, groups, policies, and adminsAdmin threshold

Account transactions

Account transactions are on-chain actions initiated from an account and governed by a policy. Examples include token transfers, smart contract configuration, and DeFi interactions. The lifecycle is:
  1. Propose the transaction with a policy.
  2. Collect signatures (approve or reject).
  3. Execute once the policy threshold is met.
Key rules:
  • A policy must be selected at transaction creation.
  • An initiator signature is required to authorize the transaction.
  • The initiator signature is distinct from approval or rejection signatures. It must come before other signatures and does not express a decision.

Organization operations

Organization operations are governance changes such as modifying members, groups, policies, or admins. The lifecycle is:
  1. Propose the change.
  2. Collect signatures (approve or reject).
  3. Execute once the admin threshold is met.
Key rules:
  • Only admins can propose, sign, and execute.
  • Unlike account transactions, no initiator signature exists.