Documentation
    Preparing search index...

    Interface SessionsConfig

    Deployed ids the sessions builders address.

    accountPackageId / accountRegistry are the same shared-account ids AccountContract takes — sessions is an Account app, so it addresses the same registry. sessionsPackageId and sessionsConfig come from the sessions deployment.

    interface SessionsConfig {
        accountPackageId: string;
        accountPackageIdLatest?: string;
        accountRegistry: string;
        sessionsConfig: string;
        sessionsPackageId: string;
        sessionsPackageIdV1?: string;
    }

    Hierarchy

    • DeepbookSessionsConfig
      • SessionsConfig
    Index
    accountPackageId: string

    The ORIGINAL shared account package id. The derived account and wrapper ids and the session data key's type are built from it, so it never moves to an upgraded package.

    accountPackageIdLatest?: string

    The latest account package once the network has upgraded it: the call target for any account call composed into the same PTB as these sessions calls, which link it. A PTB can't call account at an older version (InvalidLinkage). Absent while the network runs v1.

    accountRegistry: string

    The shared AccountRegistry object id.

    sessionsConfig: string

    The shared SessionsConfig object id.

    sessionsPackageId: string

    The latest deepbook_sessions Move-call package id.

    sessionsPackageIdV1?: string

    Original ID for v1 structs. Omit only for an unupgraded custom deployment.