You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[optional??] Aggregate event subscriptions #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] Overhaul card collection display #93
If we don't have this, we can just not have a collection display at all, it's not essential for the PoC.
Infrastructure
We'll run with a burner account for now, and will deploy on a devnet using rollop (own L1 & L2).
[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.
Use a burner wallet with account abstraction #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.
Add a solo experience (bots?) #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
Itself a collection of issues. Aritra is doing good work there. Additionally needs...
Which I'll do ASAP.
shadcn/ui
as the primary component library. #99I'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.
If we don't have this, we can just not have a collection display at all, it's not essential for the PoC.
Infrastructure
We'll run with a burner account for now, and will deploy on a devnet using rollop (own L1 & L2).Make sure roll-op works correctly!
Can't run the thing for any good amount of time if the logs end up taking up the whole disk.
We should be able to deploy everything on a beefy server if this is not ready.
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.
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.
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.
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.The text was updated successfully, but these errors were encountered: