Business utility
Hospitality operations plus transparency infrastructure
TikiDeco explores how public records and off-chain operations could support clearer future loyalty workflows.
No-offer disclaimer: business utility is design-stage only. TIDE is not offered for sale, has no stated monetary value, is not deployed on mainnet, and independent audit not started.
Why Hospitality Needs Transparent Loyalty
- Eligibility clarity
- Published rules and snapshot blocks can reduce confusion around limited pilot eligibility.
- Operational trust
- Reports and hashes can help show when rules, outcomes, or corrections were published.
- Guest experience
- Clear status pages can separate current, planned, and conceptual features.
On-Chain Reports And Off-Chain Operations
- On-chain
- Sepolia contracts and report hashes provide public reference points.
- Off-chain
- Staff review, inventory limits, blackout dates, privacy handling, and disputes remain operational processes.
- Boundary
- A blockchain record does not replace legal review, privacy review, operations, or safety decisions.
Before Real Guest Utility
- Legal
- Counsel review and terms are required before any real guest utility claim.
- Security
- Independent audit not started; V2 remains non-canonical candidate code.
- Operations
- Inventory rules, cancellation process, staff training, privacy handling, and dispute process must be ready.
Legal / Audit / Operations Gates
- Legal gate
- No sale, no stated monetary value, no mainnet, no hotel ownership, and no revenue rights.
- Audit gate
- V2 freeze baseline exists, but external audit not started and V2 is not canonical.
- Operations gate
- Pilot reports, manual review, staff override, and privacy controls must be documented before launch.