Vulcan Forge
  1. Core Concepts
Vulcan Forge
  • Introduction
  • Getting Started
  • Authentication & Authorization
  • Core Concepts
    • Terminology
    • Regulated Assets
    • Tenants
    • Mapping & Labelling
    • Solana Networks
    • Transaction Processing
    • Key Management
    • Read Layer
  • API Reference
    • Blockchain Accounts
      • Create Account
      • Fetch Account Details
      • Fetch Account Balance
      • Fetch Account Private Key
      • Fetch Accounts
      • Update Account
      • Inactivate Account
    • Financial Instruments
      • Create Financial Instrument
      • Update Financial Instrument
      • Fetch Financial Instrument Details
      • Fetch Financial Instruments
      • Token Extensions Calculator
    • Positions
      • State
        • Initialize Position
        • Close Position
        • Freeze Position
        • Unfreeze Position
      • Movements
        • Mint
        • Burn
        • Transfer Financial Instrument
        • Transfer SOL
      • Trades
        • Trade
      • History
        • Fetch Positions
        • Fetch Position Details
        • Fetch Position Balance
    • Loans
      • Create Loan
      • Fetch Loan Details
      • Fetch Loans
      • Swap Collateral
      • Repay Loan
      • Close Loan
      • Refinance Loan
    • Blockchain Transactions
      • Processing
        • Fetch Transaction Status
        • Sign Transaction
        • Submit Transaction
      • Durable Nonces
        • Create Durable Nonce Accounts
        • Fetch Durable Nonce Account Details
        • Fetch Durable Nonce Accounts
      • Address Lookup Tables
        • Create Address Lookup Table
        • Fetch Address Lookup Table Details
        • Fetch Address Lookup Tables
        • Extend Address Lookup Table
        • Update Address Lookup Table
      • History
        • Fetch Transactions
        • Fetch Transaction Details
    • Market Data
      • Update Feed
  • Schemas
    • Accounts
      • DKG
        • DKG Key Setup
      • Offchain References
      • Account Lookup
      • New Account
      • Tenancy Config
      • Account Balance
      • Offchain File
    • Transactions
      • Solana Transaction Config
      • Commitment Config
      • Transaction Lookup
    • Query
      • Query Components
        • Sort Model
        • Field Value Filter
        • Filter Model
      • Items Query
    • Reponses
      • Errors
        • Individual Error
        • Error Response
      • Accounts
        • Private Keys
          • Private Key Details
          • Database Private Key Details
          • Cloud Provider Resource Location
          • DKG Private Key Details
        • Account Response Detailed
        • Account Onchain Detailed
        • Account Offchain Detailed
        • Account Response Identifiers
        • Account Offchain Compact
        • Account Response Compact
        • Account Onchain Compact
      • Transactions
        • Solana Transaction Result
        • Solana Entity Result
      • Positions
        • Position Offchain Result
    • Positions
      • Position Lookup
      • Transfer Financial Instrument Definition
      • Burn Definition
      • Mint Definition
      • Transfer SOL Definition
      • Position Balance
    • Loans
      • Loan Duration
  1. Core Concepts

Tenants

TLDR#

The highest level concept representing a client to Vulcan Forge. Models and supports the complexities of a financial institution, regardless of its size.

Who uses Vulcan Forge#

As a multi-tenant software-as-a-service platform, Vulcan Forge allows the concurrent usage of its API endpoints by multiple financial institutions by providing clear separation of data associated with and used by each tenant.
There are 3 types of tenants supported by Vulcan Forge:
1.
Multi-org Tenants - Tenants which have a designated parent/root organization and a set of sub-organizations sitting directly underneath it.
2.
Single-org Tenants - Tenants which are setup with a single organization.
3.
The System Tenant - A default tenant created at Vulcan Forge's inception which performs special functions shared across the entire platform.
Alphaledger with its entities was the first non-system tenant which uses Vulcan Forge. Alphladeger issues onchain funds (e.g. T12 offered through its investor platform: Dominium).
Organizations onboarded in Alphaledger's tenant:
ALG -> Alphaledger Group - the parent org
ALIM -> Alphaledger Investment Management - the org that manages the issuance and onchain management of new funds through Vulcan Forge
DOM -> Dominium - an org that groups the investors' accounts which hold financial instruments issued by ALIM
The diagram below reflects the 3 flavors of tenants and their relationship to Vulcan Forge.

System Tenant Responsabilitiess#

The Vulcan Forge System (VFS) tenant peforms the following functions:
It onboards blockchain entities that are to be shared across tenants; it is the only tenant that can do so. Examples:
accounts for system prgrams and popular protocol programs
stablecoin tokens: USDC, PYUSD, etc
other frequently traded tokens that multiple VF tenants are interested in interacting with
oracle authorities and queues
Operates the Vulcan Forge Ingestor - a middlware component which listens to real-time network events pushed through the RPC provider and ingests transactions which involve blockchain accounts onboarded on the platform (regardless of which tenant they belong to) and setup with subscribeToNetworkEvents=true
Go here for more details related to on vs off platform blockchain accounts.

Tenants and offchain references#

The diagram below expounds how offchain references, used very frequently through most of the API endpoints, fit within a tenant's hierarchy.
alIds - map to financial instruments
organizationExternalIds & accountNumbers - map to the rest of blockchain entities (with Wallets being frequently mapped to accountNumbers)
Each organization has its own API Key(s) issued to it.
More details on the offchain references and blockchain account types can be found here.

Creation of offchain references#

1.
organizationExternalId(s) are 3-4 character codes assigned at the time a tenant signs-up to use Vulcan Forge
2.
alIds and accountIds:
a. can be created by Alphledger staff and assigned to the tenant
b. generated automatically if not supplied at account/blockchain entity creation
c. a separate set of API endpoints for setting up of Offchain Entities.
Option a. is available now, while b. and c. will be made available in the near future.
Modified at 2025-12-06 20:46:55
Previous
Regulated Assets
Next
Mapping & Labelling
Built with