Walker

Here is a comprehensive Mega Prompt to copy-paste directly to your agent 👇 Set up RESET on this computer, connect it to my agent, and participate on my behalf. Where supported, also configure reliable ongoing participation after this conversation ends. Official repository: github.com/Trac-Systems/rese… Do the setup work yourself rather than simply giving me installation instructions. Ask me only for permissions, secure credential entry, resource limits, or decisions that genuinely require my input. This is an experiment, not an investment. Do not purchase tokens, move funds from other wallets, or promise earnings. CHECK THE ENVIRONMENT Identify this computer’s operating system, architecture, available tools and current agent application. Read the current README.md, docs/llms.txt and signer/README.md. Use the official documentation and inspect relevant code when instructions are unclear. Adapt installation commands, file paths, agent configuration and background operation to this actual environment. Do not assume a particular operating system or agent client. Check whether this agent can use the required local tools and whether it supports unattended execution. Explain any genuine limitation rather than pretending an unsupported feature works. INSTALL AND CONNECT Review installation commands before executing them. Install only the required missing dependencies from official sources. Preserve existing wallets, agent settings and unrelated files. Do not overwrite an existing RESET installation or wallet. Record the repository version or commit used. Create a dedicated RESET wallet if one does not already exist. Arrange secure local password entry and storage. Keep passwords, private keys and wallet backups out of this conversation, logs and shared repositories. Pause for my input when necessary. Explain how to back up and recover the wallet. Configure the documented local MCP connection for my agent. Preserve any existing MCP connections. Tell me if restarting the agent application or session is required. Verify the connection by actually calling the RESET tools: `rules`, `status` and `address`. Start the local dashboard and show me how to open it. CHECK ELIGIBILITY AND BEGIN PARTICIPATING Check the live game phase. Do not assume the initial lottery is still open or rely on an old announcement’s start time. Participate in the lottery when eligible, and use the documented tools to submit useful Bitcoin headers. Avoid duplicate actions and respect the service’s limits. If I need starting RESET coins, show my public RESET receiving address and explain the available routes. Do not invent a faucet or assume that lottery entries or header submissions guarantee rewards. Check the current minimum Mine deposit and withdrawal rules. Before locking coins or enabling unattended operation, agree with me on: - The maximum RESET amount that may be locked. - Whether overclaiming and potential penalties are permitted. - The model-usage budget and initial run duration. Explain any limits that cannot be enforced automatically. Within those approved limits, read the rules and decide how to participate. Keep the agent involved in the decisions; do not silently substitute a fixed claiming script. Record concise decision summaries, submitted actions and actual results. Distinguish between an accepted submission, an applied action and a settled payout. CONFIGURE CONTINUED PARTICIPATION Use a supported background service or task scheduler for this operating system, together with an agent interface that genuinely supports unattended runs. Do not rely on this conversation remaining open. Running the MCP server or dashboard alone is not ongoing participation. Use lightweight scheduling and state checks where practical, and avoid unnecessary model calls when nothing needs doing. Check actual game windows rather than assuming that one action every hour is sufficient. Persist the wallet identity and activity records between runs. Prevent overlapping workers and duplicate submissions. Inspect the current state before retrying an uncertain action. Give unattended runs only the permissions they need. Disable outgoing transfers in their tool configuration where supported. Do not disable system-wide security protections or grant blanket access to unrelated files and credentials. Handle connection failures with bounded retries. Stop safely when credentials, approved budgets or other requirements are unavailable. If reliable unattended operation is unsupported, explain what is missing and establish a working supervised setup instead. Do not claim background participation is running when it is not. TEST AND HAND OVER Test the unattended worker separately from this conversation. Verify that the scheduled process can launch, access its credentials securely and check the live game without needing an unexpected interactive prompt. Report: - My public RESET address and participation status. - What has actually been installed and verified. - Any remaining blocker or untested behaviour. - The dashboard address and activity-log location. - How to check, pause, resume and stop the automation. - What happens when the computer sleeps, restarts or logs out. - How to stop participating and recover locked coins under the game’s withdrawal rules. Do not report success merely because installation completed. Provide evidence of a working connection and worker run, and verify applied actions and settled results when available.