Your first steps in T0.

Version 5.0 · 29 September 2026 · web v0.1.20

First sign-in

1. Open fundqool.com and choose Workspace. Your administrator must first approve your exact email address; no special invitation link is needed.
2. Sign in using the exact invited email address and enter the code delivered to that mailbox.
3. Set up the separate second factor as shown on screen. Store its QR code in your authenticator app or Apple Passwords; use that same app for subsequent codes.
4. Your approved membership activates after the second factor. Open FundQool · T0. Complete first activation within 7 days of email approval; after that, the administrator can renew it.

Forwarding the link does not grant access to another email address. Each person sets up their own second factor. Researchers do not need MetaMask or test ETH to inspect the data.

Working with the project

• Data: select a published dataset and browse issues and transfers. Filter by fund (for example FUND_A), event type, participant, address or transaction, then press Filter.
• Show: inspect event addresses, the transaction explorer link, actual block time and scenario model time.
• Holdings and issued supply: inspect balances reconstructed from all events in the selected dataset. Filtering the event type does not alter the balance calculation.
• CSV / JSONL / Parquet / Manifest: download data for independent analysis and checksums for integrity verification. Reload the workspace to discover newly published versions.
• Stages: inspect the recorded project status.
• Messages: post questions and replies within the project thread. This version does not send email notifications or support attachments.

The Researcher role cannot invite people, change permissions, approve publication or control the simulation. The server runs the scenario; researchers do not manually submit issues or transfers through this interface.

Reading the evidence

Participants are synthetic and tokens are test tokens on Base Sepolia. Model prices are neither payments nor market prices. The table contains only verified finalized events from the selected published dataset; pending transactions are not included.

Scenario time simulated_at describes model time; block_timestamp is the actual time recorded in the block. Model time does not replace 72 hours of live validation. Regular CSV, JSONL and Parquet exports are distinct from the complete 21-file research bundle, which requires separate completion and approval.

How data grows

The server runs the activated scenario in the background. Your browser and computer do not need to stay open. Each operation is submitted to the test network, checked for finality and data consistency, then included in a published dataset. This creates a delay between submission and visibility.

To load new data: reload the workspace and select the latest Dataset version. An open table does not automatically switch versions. Record the dataset version and retain its Manifest alongside the export for reproducible analysis. An older export does not become a newer version when additional transactions occur.

Data arrives in verified batches, not at a guaranteed hourly rate. Network confirmation, a completed phase, a pause or an error can stop new publication. More events provide more research evidence; they do not automatically improve the software or prove project completion.

Roles and responsibilities

Researcher

Inspect and analyse data, download exports and use the project thread.

Supervisor

Additionally review operational evidence, pause/resume the scenario and prepare the next phase after review.

Project lead

Appoint supervisors from active members, record stage acceptance and pause/resume the scenario. The lead role alone does not authorize phase advancement.

Technical administrator

Manage approved emails, access, leads and technical operations, with fallback authority for phase control and stage acceptance.

The lead assigns supervision in Responsibilities. Leads cannot assign themselves supervision; only the administrator may explicitly combine lead and supervisor roles. Changes require recent two-factor authentication and are audited. A responsibility attached to an approved email takes effect only after that mailbox is verified and the native second factor is completed.

Operational phases

Calibration

100 operations: 10 issues and 90 transfers; verify the transaction-to-export flow.

Initial dataset

3,000 operations: 300 issues and 2,700 transfers.

Acceptance run

300 operations across three daily batches, at least 72 hours of validation and review of acceptance evidence.

Pilot

100 operations per day for 30 pilot days, 3,000 total.

The minimum is 6,400 operations. The pilot lasts 30 days. Successful enrollment or a published dataset does not establish full T0 acceptance.

How the supervisor advances a phase

1. Review the preceding phase results, finalized counts, data/export consistency and any errors. Record the conclusion with dataset and evidence references in the project thread.
2. Renew verification through Two-factor authentication; sensitive commands require verification within ten minutes. In Operations, enter a reason and pause the scenario.
3. Select the next phase, enter the review conclusion and evidence reference, confirm the review checkbox and save.
4. Phase selection leaves the scenario paused. Check the resulting state, then separately choose Resume after data verification. The server executes subsequent batches automatically.

The server rejects skipped phases, incomplete counts, failed reconciliation and stale form versions. Before the pilot it additionally requires at least 72 hours since acceptance phase selection, three completed daily batches and documented T0 acceptance by the lead or administrator. The supervisor must separately check time since any critical repair and the remaining plan requirements; the timer alone does not establish them. Ordinary researchers do not make these changes or approve individual transactions.

Workspace handover and completion of the experiment are separate milestones. Researchers can use the workspace during validation. Pre-pilot T0 acceptance requires at least 3,400 operations and the required operational evidence; the full experiment also includes the 30-day pilot and at least 6,400 operations overall. Read the project for its current phase and acceptance state, and the latest dataset for available data. This guide is not an acceptance certificate.

Suggested first session

1. Open the latest dataset and check its issue and transfer counts.
2. Filter one fund, such as FUND_A, and compare an issue with a subsequent transfer.
3. Open Show for a transfer and inspect its sender, recipient, amount and transaction link, then inspect Holdings and issued supply.
4. Download CSV and Manifest for your analysis. Use JSONL or Parquet as appropriate for your tools. Import CSV without inadvertently rounding long identifiers or integer values.
5. Post questions or discrepancies in Messages, including the dataset and event identifier. Never post passwords, verification codes or personal data of actual investors.

If no new records appear, reload the workspace and check the selected version first. Then contact the administrator through the project thread. Signing in repeatedly or changing authenticator apps does not affect dataset growth.

Access problems

Check your exact email and its approval by the administrator. Find the second-factor code in the app used to store its QR code. Do not share passwords, QR codes or one-time codes. The owner can remove or renew email approval or suspend membership.