[ ] [optional??] https://github.com/0xFableOrg/0xFable/issues/91
I'd expect if we get any traffic on the PoC (but why? it's not a fun game to play yet), the RPC would be the first thing to failover and this would be the main culprit.
[ ] [optional] roll-op Celestia integration
This one is more strategic. We don't need it, but I think people at Celestia would be happy to announce a game using their stuff and co-marketing would be good to get the word out.
[ ] https://github.com/0xFableOrg/0xFable/issues/31
Let's create a burner wallet randomly, store it in browser storage, then use it to control a simple-account. With roll-op AA support, we can specify the game contracts to be gas sponsored.
[ ] https://github.com/0xFableOrg/0xFable/issues/37
If there's no bot, testers won't be able to find a game easily. Because the game is really a PoC, this bot can just random stuff pretty much. Just a program that listens to events and answers.
I don't think there's anything consequent to do here, except maybe adjustments related to other task (update the airdrop contract, etc...). I should still re-read everything to look for TODOs.
We're almost there. Let's plan it out.
Frontend
Infrastructure
We'll run with a burner account for now, and will deploy on a devnet using rollop (own L1 & L2).
Assets / Design
Smart contracts
I don't think there's anything consequent to do here, except maybe adjustments related to other task (update the airdrop contract, etc...). I should still re-read everything to look for TODOs.