Add silicon casino

[piglig]

🔗 Linked Issue

#129

Closes #

✅ Type of Change

• ✨ New Project/Feature
• 🐞 Bug Fix
• 📚 Documentation Update
• 🔨 Refactor or Other

📝 Summary

This PR adds Silicon Casino, an agent-vs-agent poker arena powered by Compute Credit (CC).

Key features:

• Agent-native gameplay: Agents join via HTTP, perform actions via API, and receive real-time updates over SSE.
• CC economics: Vendor key budgets are minted into CC and settled through the poker ledger.
• Public observability: Humans can watch live tables and leaderboard updates via public APIs/SSE.
• Strict guardrails: Vendor key verification, top-up limits, cooldown, and blacklist protections.

Tech stack: Go 1.22+, PostgreSQL 14+, Node.js 20+ (for web/SDK).

📖 README Checklist

• I have created a README.md file for my project.
• My README.md follows the official .github/README_TEMPLATE.md.
• I have included clear installation and usage instructions in my README.md.
• I have added a GIF or screenshot to the assets folder and included it in my README.md.

✔️ Contributor Checklist

• I have read the CONTRIBUTING.md document.
• My code follows the project's coding standards.
• I have placed my project in the correct directory (e.g., advance_ai_agents, rag_apps).
• I have included a requirements.txt or pyproject.toml for dependencies.
• I have added a .env.example file if environment variables are needed and ensured no secrets are committed.
• My pull request is focused on a single project or change.

💬 Additional Comments

• This project uses Go (with go.mod/go.sum) instead of Python, so dependencies are managed via Go modules rather than requirements.txt.
• The project includes comprehensive documentation in AGENTS.md, deploy/DEPLOYMENT.md, and API skill docs.
• Demo GIF and screenshots are provided in docs/readme/.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic Password	b87ff6d	advance_ai_agents/silicon_casino/docker-compose.yml	View secret
-	-	Generic High Entropy Secret	be37241	advance_ai_agents/silicon_casino/cmd/game-server/main.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[piglig]

There is no secret in "cmd/game-server/main.go" file, it's the fixed params

[shivaylamba]

No Nebius, plz use Nebous

[piglig]

No Nebius, plz use Nebous

Now I have supported it

[shivaylamba]

we dont see it

[piglig]

we dont see it

Hi, the support has been added in this commit:
b87ff6d

Please check the updated changes. Let me know if anything else needs to be adjusted.