Guides for backers

Status: Built, runs on simulatorStatus: ProvisionalStatus: Coming soon

A backer needs to distinguish eligibility, a purchase, and a claim before interpreting a balance or a status.

These guides explain what to check at each stage. The transaction walkthroughs remain unpublished while the backend changes and the required release documents are missing. A status badge reports implementation progress; it is not an invitation to send funds.

Begin with the information boundary

A holder can see public transaction records and the information the service permits them to read. Holding a position does not give access to the issuer’s raw income documents or personal reasons for a pause.

Read what you cannot see and why before interpreting a report. The glossary defines the terms used across the guides.

Keep the records separate

The allowlist controls entry into specified activities. The auction records a bid’s commitment, later disclosure, result, and delivery. The payout vault records payments that can be claimed. Those are different records: approval does not establish a purchase, and a submitted bid does not establish delivered units.

A series also has its own terms and lifecycle. The generated status reference shows the implementation’s state names. It does not establish that a particular app workflow has been released.

What the other side sees

Bid deposits, revealed bids, positions, and claims are public onchain. An encrypted reveal backup has a different visibility rule: the server stores ciphertext, and the account owner retrieves it. The issuer does not receive its contents through that backup route.

What can go wrong

An app summary can describe a pending operation. Check the underlying result before treating it as complete. A public record also cannot establish future payments or remove the need to understand the agreement and its unresolved terms.