The fundQool public website is live. This guide explains the research scenario, roles and data workflow. Available datasets are listed in the data overview; workspace access is activated for invited participants.
Experiment model
The scenario uses three synthetic funds and a registry of 100 synthetic actors. The target corpus contains 6,400 modelled business events, including a thirty-day pilot. It is not a real fund, investment, cash settlement, or trading venue.
Two times, two semantic layers
simulated_at is the time in the scenario. block_timestamp is the time recorded in a block if the event is written to the public testnet. Model time is not live operating time.
Who does what
Researcher
Reads assigned data, exports, and messages. Does not change membership, stages, or scenario operations.
Operator
Monitors status, pauses or resumes an existing scenario, and handles incidents. Does not manage membership or invitations.
Owner
Creates stages, manages masked invitations and roles, approves publication, and accepts stages. Sensitive commands require recent native TOTP.
Access
The public area does not require registration. The workspace is invite-only: the owner creates an invitation for an exact email address and role, the invitee uses Google or an email one-time code, and verifies a separate authenticator code before entering the workspace. The hosted flow is not yet evidenced.
Data and exports
After verified publication of a snapshot, the Data page offers CSV, JSONL, and Parquet with a manifest of sizes and SHA-256 values. The complete research bundle is a separate set of 21 files approved by the owner; private labels are excluded. LOCAL_EVM_ONLY is not evidence of a public testnet or a published snapshot.
Stages, messages, and recovery
The owner creates T0, P0, and T1–T3 as planned stages. A status or acceptance is an evidenced decision. Do not use the project thread for keys, one-time codes, or invitation tokens. If history differs, the scenario is paused; new qualification requires evidence, recent TOTP, an expected version, and consent. The scheduler does not resume itself.
Order before publication
Infrastructure, security, provider, deployment, calibration, and restore gates come first. Only then may the first verified public snapshot be created; it is followed by a 72-hour acceptance period and only then by the thirty-day pilot.