Profil Dropverse | Binance Square

PINNED

·

--

Zobrazit překlad

🚨 This is insane… this guy built a clawdbot that turned $50 into ~$248K overnightSomeone in a Discord chat said he pulls in $200 a day - and it took him six years to reach that point. Asked whether Polymarket is basically gambling. Another person responded with a screenshot. $248,000 overnight. The chat went quiet. The Setup (Secure Version) From fresh Ubuntu VPS to hardened private AI server. Do it in this order. 1) Lock Down SSH → Keys only, no passwords, no root login. 2) Default-Deny Firewall → Block everything incoming by default. 3) Brute-Force Protection → Auto-ban IPs after failed login attempts. 4) Install Tailscale → Your private VPN mesh network. This is what makes everything reachable only from your devices. 5) SSH Only via Tailscale → No more public SSH exposure. 6) Web Ports Private Too → ClawdBot gateway only accessible from your devices. 7) Install Node.js 22 → ClawdBot requires version 22+. Ubuntu’s default is older. 8) Install ClawdBot 9) Lock ClawdBot to Owner Only → Only you can message the bot. Add this to your ClawdBot config: Never add ClawdBot to group chats. Every person in that chat can issue commands to your server through the bot. 10) Enable Sandbox Mode → Runs risky operations in a container instead of your actual system. Check the security docs and enable isolation. If something goes wrong, the blast radius is contained. 11) Whitelist Commands → Don’t let the agent run arbitrary commands. Explicitly list only what it needs: If the agent gets hijacked through prompt injection, it can only execute what you’ve whitelisted. 12) Scope API Tokens → When connecting GitHub, Gmail, Google Drive: do not use full-access tokens. Give minimum permissions. Read-only where possible. If something goes wrong, damage is limited to what that specific token could do. 13) Fix Credential Permissions → Don’t leave secrets world-readable. 14) Run Security Audit → Catches issues you missed. Don’t skip this. If this fails, do not deploy. Fix whatever it flags first. Verify Everything Result should be: No public SSHNo public web portsServer only reachable via TailscaleBot responds only to you #HarvardAddsETHExposure #MarketRebound #PEPEBrokeThroughDowntrendLine #BTC100kNext? #CPIWatch

🚨 This is insane… this guy built a clawdbot that turned $50 into ~$248K overnight

Someone in a Discord chat said he pulls in $200 a day - and it took him six years to reach that point. Asked whether Polymarket is basically gambling. Another person responded with a screenshot. $248,000 overnight. The chat went quiet.

The Setup (Secure Version)
From fresh Ubuntu VPS to hardened private AI server. Do it in this order.
1) Lock Down SSH
→ Keys only, no passwords, no root login.

2) Default-Deny Firewall
→ Block everything incoming by default.

3) Brute-Force Protection
→ Auto-ban IPs after failed login attempts.

4) Install Tailscale
→ Your private VPN mesh network. This is what makes everything reachable only from your devices.

5) SSH Only via Tailscale
→ No more public SSH exposure.

6) Web Ports Private Too
→ ClawdBot gateway only accessible from your devices.

7) Install Node.js 22
→ ClawdBot requires version 22+. Ubuntu’s default is older.

8) Install ClawdBot

9) Lock ClawdBot to Owner Only
→ Only you can message the bot. Add this to your ClawdBot config: Never add ClawdBot to group chats. Every person in that chat can issue commands to your server through the bot.

10) Enable Sandbox Mode
→ Runs risky operations in a container instead of your actual system.
Check the security docs and enable isolation. If something goes wrong, the blast radius is contained.
11) Whitelist Commands
→ Don’t let the agent run arbitrary commands. Explicitly list only what it needs: If the agent gets hijacked through prompt injection, it can only execute what you’ve whitelisted.

12) Scope API Tokens
→ When connecting GitHub, Gmail, Google Drive: do not use full-access tokens. Give minimum permissions. Read-only where possible. If something goes wrong, damage is limited to what that specific token could do.
13) Fix Credential Permissions
→ Don’t leave secrets world-readable.

14) Run Security Audit
→ Catches issues you missed. Don’t skip this. If this fails, do not deploy. Fix whatever it flags first.

Verify Everything

Result should be:
No public SSHNo public web portsServer only reachable via TailscaleBot responds only to you
#HarvardAddsETHExposure #MarketRebound #PEPEBrokeThroughDowntrendLine #BTC100kNext? #CPIWatch

Dropverse

🚨 This is insane… this guy built a clawdbot that turned $50 into ~$248K overnight

Trendující témata