$HOTEL is live.
0x5b335a9e079c23062c97ed4504ac31e08df9b170
This is why crypto is so powerful.
Forget the vaporware and endless “future infrastructure” pitches.
Every creator fee generated by $HOTEL trading is routed on-chain to RoomService and distributed back to eligible hotel guests every 15 minutes.
If you’re in the Top 100, you can Check In for 1 hour and get 1.5x Room Service reward weight while your stay is active.
No manual treasury decisions.
No off-chain promises.
No “rewards coming soon.”
Trading generates fees.
Fees go to RoomService.
Guests earn from the hotel.
That’s the product.
p.s. the dev wallet was burnt.
https://t.co/G7asoya7Vk
@Manatane79 Connect your wallet on site and claim your rewards, only 7% have been claimed and we can’t access them as admins, there’s 0.35 ETH waiting to be claimed
How HOTEL100 rewards actually work 🏨
Every trade on $HOTEL generates creator fees.
Those fees flow through Pons, into the HOTEL100 RoomService contract, and are distributed to eligible Top 100 holders.
The contracts are public:
$HOTEL
0x5b335a9e079c23062c97ed4504ac31e08df9b170
RoomService
0x50b8a10c877e4d51ec05f6b173318354312c4d63
Pons FeeEscrow
0xd3AFEB2a57f70eF218Aa82451c51B2fb0416Ac9e
How rewards work:
Top 100 holder = eligible for Room Service
Normal HOTEL balance = 1.0x reward weight
Checked-in HOTEL = 1.5x reward weight
Check-In lock = 1 hour
New Room Service rounds = roughly every 15 minutes
Unclaimed rewards = accumulate until you claim
The reward mechanics are enforced by the deployed on-chain contracts, so the rules aren’t something we can quietly change behind the scenes.
So the hotel earns from trading activity, and the rewards flow back to the guests.
You can verify the whole thing on-chain.
We’ve spent launch day tightening the parts you only really find once real users hit them.
We’ve now:
fixed the database connection bottleneck
moved the web app onto the right pooler setup
hardened the live state endpoint
removed fragile request-time RPC work
added last-known-good data fallbacks
stopped transient failures from making the hotel look pre-launch
improved mobile Room Service claims
The core HOTEL100 mechanics are live.
Now we can get back to the fun part:
building the hotel. 🏨
We’ve isolated the remaining HOTEL100 issue.
The chain, indexing and Room Service are running — the problem is the frontend hammering the live state endpoint while Vercel occasionally times out acquiring a DB connection.
We’re now hardening that path so the site reads from a stable snapshot, avoids duplicate polling and doesn’t blank out during a short connection wobble.
Core infra is fine.
We’re fixing the last bit of frontend reliability now.
If Vlad built a hotel, it probably wouldn’t charge you to stay.
It would pay you.
Welcome to HOTEL100 🏨
Top 100 $HOTEL holders get a room.
And if you want to Check In, you can lock part of your $HOTEL for 1 hour.
While checked in, that locked amount gets 1.5x Room Service reward weight.
So:
hold $HOTEL → get a room
check in → lock for 1 hour
checked-in amount → earns at 1.5x weight
hour ends → tokens unlock
Room Service → claim whenever you want
Basically a hotel where the guests get paid for staying.
Very Vlad.
@RaizenDegen There’s no fixed cooldown between claims. Room Service updates on a 15-minute cycle, so once a new round is finalized and you have a new claimable balance, you can claim again. Unclaimed rewards simply accumulate, so you don’t need to claim every 15 minutes.
We’re currently resolving a data connectivity issue affecting the HOTEL100 frontend.
The core infra is unaffected — $HOTEL, Room Service, indexing and onchain activity are all still running as expected.
Some live data may appear intermittently while we finish the fix.
Should be fully stable shortly.
Fixed the HOTEL100 data issue.
The problem was how the frontend was connecting to the database under serverless load.
We’ve now moved the web app onto the correct transaction-pool setup and stability checks are passing.
Core infra, $HOTEL, Room Service and indexing were unaffected throughout.
Live hotel data should now stay connected and update reliably.
$HOTEL creator fees don’t go to us.
They flow into Room Service and are distributed back to eligible Top 100 holders.
The mechanism is already working fees are being generated, collected and allocated onchain.
What we’re fixing right now is the data layer around the site.
Vercel was intermittently losing database connections, which meant rooms/rankings could disappear even though the underlying HOTEL activity was still there.
We’re moving the web app onto a more appropriate database connection setup so the hotel stays synced with the market.
No change to the fee model. No change to Room Service.
Just making the live hotel more reliable.
On-chain fee summary for guests.
Collected in RoomService: 0.239672 ETH
Pending in Pons escrow: 0.058713 ETH
Already claimed: 0 ETH
Total generated: 0.298386 ETH
@watisdesser the fees are all routed to our roomservice contract, nothing comes to us, we're just updating the database now with a redeploy, on-chain is working, give us 5-10 mins
The token launch, dev burn, RoomService deployment and creator-fee handoff are all complete.
We’re just finishing the final data cutover now so the hotel can start displaying live rooms, rankings, activity and Room Service data from the production indexer.
The important part: the onchain side is done.
Now we’re syncing the hotel to the market.
$HOTEL is live.
0x5b335a9e079c23062c97ed4504ac31e08df9b170
This is why crypto is so powerful.
Forget the vaporware and endless “future infrastructure” pitches.
Every creator fee generated by $HOTEL trading is routed on-chain to RoomService and distributed back to eligible hotel guests every 15 minutes.
If you’re in the Top 100, you can Check In for 1 hour and get 1.5x Room Service reward weight while your stay is active.
No manual treasury decisions.
No off-chain promises.
No “rewards coming soon.”
Trading generates fees.
Fees go to RoomService.
Guests earn from the hotel.
That’s the product.
p.s. the dev wallet was burnt.
https://t.co/G7asoya7Vk