Fixed Time.
Shared Understanding.

A Record.
Not A Provider.

Groups often need one unambiguous answer to a small question: which wallet has reserved this time window? Slotryx keeps that answer in a public state machine with an explicit current holder and a monotonically increasing reservation version.

The participants arrange the meaning of the time separately. This record does not supply a room, employee, appointment, calendar notification or delivery guarantee. It does not verify attendance, identity or performance.

The Shape Is Fixed.

The constructor fixes a future start time, the duration of each window and the number of windows. Duration can be 60–86,400 seconds; the count can be 1–128. Each slot starts at the first start plus its index multiplied by the duration. Indices begin at zero.

These parameters are immutable. There is no administrator, owner or proxy able to change the dates or take a reservation away. A different set of dates or rules needs a new contract address, clearly identified as a new schedule.

One Holder.
A Fresh Version.

A reserve action requires a future empty slot and its latest reservation version. It records the transaction sender as holder and advances that version. The caller cannot claim to be another wallet by supplying an address.

A release requires the same current holder, a future slot and the exact current version. It clears the holder and advances the version again. This matters when a slot is released and later reserved: an old release must not act on the new reservation, even if the same wallet holds it again.

One wallet may reserve several slots. Multiple wallets are allowed. This is not a one-person-one-slot mechanism or a proof of verified identity.

Read the contract

Before Means Before.

Both reserve and release require the current block timestamp to be strictly earlier than the chosen slot's start. At or after that boundary, neither action is allowed for the slot. Later windows remain independently editable until their own starts.

A started slot is not automatically erased or made empty. Its holder remains part of the historical record. There is no refund path, forced cancellation, arbitration or administrator override.

Public Data.
Network Costs.

The contract records the immutable schedule and each slot's holder and version. Reserved and Released events identify the slot, wallet and new version. Public network records may be indexed by third parties and cannot be erased by this interface.

There is no deposit, application fee, token, reward or funds-custody function. Actual writes on a future deployed network consume native network Gas. Connecting a wallet alone does not send a transaction or grant token approval.

Before asking the wallet, the interface must show the exact slot, UTC date, account, version, Gas estimate and maximum estimated fee. A changed network, account, holder, version, start boundary or deployed code invalidates the action. A successful result requires the matching transaction receipt and exact business event.

Prepared.
Not Publicly Deployed.

This project includes the website, separate schedule room, SlotryxSchedule source, local compilation, temporary-chain business tests and an unsigned deployment preview. Local tests are not a public deployment or an independent security audit.

A future deployment needs a reviewed network, compatible runtime, valid future parameters, public deployment account and Gas budget. The local preview does not sign or broadcast. A specifically authorized controlled signer is a separate step; no private key belongs in the website.

Useful later work could include read-only history and clearer timezone exports. Calendar delivery, identity checks, paid bookings and guarantees of real-world service are not current capabilities.