A clear edge
around a shared circle.

Coordination needs a limit.

A wallet-native community may need a bounded list of participants for a shared session. A list hidden in one person's inbox is difficult to verify; an unbounded list does not answer whether there is room.

Eventryx addresses that narrow problem with one public roster and a fixed capacity. Its target is a community that prefers an explicit wallet record over a private account system. It does not organise or deliver the real-world event.

Join once. Leave yourself.

The session capacity is selected at deployment, between one and five hundred places, and cannot later be changed. A wallet joins only if it is not already active and the session is not full. Leaving releases only the caller's own place.

The contract has no owner, administrator removal, wait list, priority access, ticket transfer or capacity override. Multiple wallets can belong to the same person; a wallet is not a verified human identity.

The actual user action.

The independent session page connects a wallet, reads the contract state, validates an action and estimates gas. The user then approves the transaction in their own wallet. A successful receipt and matching Joined or Left event are required before the interface reports success.

Keep the record small.

• Fixed session capacity and current occupied count.
• An active-participation boolean for each wallet.
• Joined and Left events naming the caller and occupied count at the time of the event.

There is no name, email, phone number, uploaded document or private message in the contract. A transaction still exposes its wallet, timing and public chain history. A displayed event count is not a live participant list unless freshly read from a configured deployment.

All actions are nonpayable. There is no application payment, token purchase, allowance, custody, yield, reward or investment product. Network gas is the only expected transaction cost; a reverted transaction can still consume gas.

A record is not admission.

Leaving updates active participation but does not delete public transaction history. Do not connect a wallet if you do not want its participation publicly associated with the session.

Once deployed, this immutable contract cannot erase history, enforce identity uniqueness or moderate harmful users. Those limitations are deliberate, not undisclosed future features.

What exists in this Demo.

The long homepage, independent session page, project documentation and Solidity source are available. Local in-memory-chain tests cover capacity, duplicates, caller boundaries, events, gas and rejected operations.

The public-chain contract is not deployed. No target network, address, explorer or live session capacity has been fabricated. The frontend is configured to disable writes, even when a wallet connects. This is not an independent security audit.

Deploy only by a separate decision.

A later phase must choose a compatible network and a reviewed capacity, inspect the deployment account and fee budget, then generate an unsigned backend CLI preview. Signing and broadcasting need a separate explicit instruction.

After deployment, verify the receipt, source, bytecode and initial state before enabling frontend writes. The contract is non-upgradeable; a changed version requires a new address and an explicit migration decision, not an invisible overwrite.