Absxyz: Abstract XP Retention and Acceptance
Cube, Inc.’s Terms of Service dated October 6, 2026 make valid acceptance the condition for its XP record-retention commitment during Abstract’s wind-down. The promise covers existing XP information linked to an account until six calendar months after Abstract permanently ends normal transaction processing, subject to specified early-deletion exceptions. It applies even if the user doesn’t start or complete an asset migration.
Valid Acceptance
Acceptance of this version requires selecting an initially unchecked agreement checkbox and confirming acceptance through a process that clearly links the terms. Viewing information, continuing to use the service, holding assets, connecting a wallet, or signing a transaction doesn’t by itself accept this version. Public wind-down information remains available without acceptance.
The Migration Hub has a separate agreement with its own acceptance requirements. Accepting the general Terms of Service doesn’t accept the Migration Terms. Where the new version hasn’t been validly accepted, previously validly agreed terms continue within their scope.
The Retained XP Record
Section 12.7 covers existing XP information associated with the account, including an offchain record and its link to that account. Cube must keep the retained information in a reasonably retrievable form. It can use a recordkeeping provider acting on its behalf, while remaining responsible for the commitment.
Record retention doesn’t require a continuing XP display, Portal access, or ongoing blockchain or migration operations. A retrievable record can therefore outlast the interface that previously displayed the XP.
Retention Timing and Deletion
Abstract’s October 6, 2026 wind-down announcement scheduled the chain’s shutdown for December 15, 2026. The retention period is measured from the Abstract blockchain’s actual Service Discontinuation Date: the permanent end of normal transaction processing, as identified through its official channels. A temporary outage isn’t that date, and other services can have different discontinuation dates.
Chain closure, termination of access, or replacement of the terms doesn’t shorten the retention period. If the commitment carries forward into the Migration Terms or another valid replacement agreement, it remains the same commitment. Repeated acceptance doesn’t restart the period or create another benefit.
Cube may delete the record earlier only to the extent required by applicable law, a valid deletion request that Cube must honor, or a binding privacy commitment concerning previously collected information. Any retention after the stated period is governed by the Privacy Policy and applicable law.
Example: Retention After Portal Access Ends
Hypothetical conditions: a user has existing account-linked XP, validly accepts the October 6, 2026 terms, and doesn’t migrate any assets. Assume the blockchain’s actual Service Discontinuation Date is the announced December 15, 2026 date, the Portal becomes unavailable before the retention period ends, and none of the early-deletion exceptions applies.
The contractual retention period then ends on June 15, 2027. Cube must retain the record during that period even though the user can’t view it through the Portal and hasn’t migrated assets. A valid replacement agreement carrying the same commitment forward wouldn’t start a fresh six-month period. A different actual chain discontinuation date would change the calculated end date.
Rewards and Asset Access
The retention commitment creates no right to a token, airdrop, reward, or XP redemption. An independent project could choose to recognize past participation under its own program, but Cube doesn’t promise that another project will receive access to the record, offer a program, or grant eligibility or benefits. Any sharing or verification remains subject to applicable law, the Privacy Policy, and appropriate arrangements.
Asset exit deadlines remain separate from XP recordkeeping. The retention promise doesn’t extend a route’s initiation, completion, or claim deadline, and it doesn’t keep assets transferable through discontinued services after normal transaction processing ends.