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.

SHNAKAS is the network coin. Here's how the whole thing fits together. TRAINING WHEELS OFF Since launch the Shielded protocol has run inside a tight sandbox on purpose. A key of ours sits in the loop so that if anyone found a hole we could stop it before it cost a holder anything. That was the safety net while we watched it under real load, real attacks and real money. It held. The next update removes it. No key of ours in the protocol, nothing of ours in the money path. Listing, repricing and cancelling become instant with nothing on chain until it sells. The sale is one transaction the buyer pays for. Anyone can run the indexer and trade Nakas on their own site. After that the full code goes open source. No date yet, it's close. CREDITS GONE Same update kills relay credits. No more buying tickets to do private actions. Your vault's own bitcoin pays the network fee, same as any wallet. Old credits still work if you have them, nobody loses anything. Prepaid relays stay as an option for people who want the extra privacy. The platform never pays for anything, which is what keeps it honest. THE TOKEN 21M SHNAKAS. Issued to Naka holders every block for 78 weeks. Rarer traits earn more, weighted by the live floor. You pay the claim fee from your own wallet, nobody else touches it. People keep asking about listed Nakas, so here it is plain. Every block a Naka sits listed, its share of that block is skipped. Not delayed, not pooled, not handed to the other holders. It is never issued, and it can never be bought back. Same for Nakas that were never minted. 21M is the ceiling, not the supply. With the amount of Nakas sitting listed right now a big chunk of that 21M will simply never exist. The burn started on block one. DATES This Friday: claims open. Claim all your weeks in one go from the vault. The week after: peer to peer SHNAKAS trading goes live inside the vault. Buy, sell and send the token privately, same rails as the Nakas. Burn for GTD ships with it. UTILITY Every Shielded launch reserves a limited number of GTD spots for SHNAKAS. Spots are taken by burning. There's a minimum burn per spot, and when a launch is oversubscribed the biggest burns win. Your vault shows the line live. Burned tokens leave circulation for good, and a burn that doesn't win rolls to the next launch. HOLDERS Holding a Naka doesn't hand you a spot. There are 3,333 Nakas and some launches are smaller than that. What holding does is pay you the token every block, so holders are always first in line with a bag they never had to buy. Don't own a Naka? Buy one off the floor, or buy SHNAKAS off the floor and burn those. VERIFICATION The original mint wallet list is retired. Too many of those wallets sold and moved on. From here on, GTD on this network is earned with SHNAKAS, nothing else. NETWORK COIN SHNAKAS is the only coin on the network. No other token launches here. Everything built from here on, verification, GTD, whatever comes next, runs on SHNAKAS and burns it. Supply only goes down. This is what makes privacy on Bitcoin go round.

首个隐私符文 $SHNAKAS 开始挖了！( 附钱包教程 ) 只需持有 @ShieldedNaka 合集且未挂单的地址，无需任何操作即可开挖，当前使用他们的隐私金库钱包可以看到代币领取的界面，以及 NFT 本周的算力倍速。 钱包传送门：ord-dropz.xyz/wallet 这钱包目前只能网页版，但里面集成了隐私发送资产，合集市场，域名等功能，可以说是该有的功能都有。且直接 UniSat 或者 Xverse 钱包链接签名下即可使用，非常的便捷，整体用下来的体验非常流畅，操作界面简单。 但目前还不知道这个隐私符文市场会怎么个交易，有点期待了，希望它能来个创新的交易体验。 下面就弄个简单的手机钱包演练教程： 1⃣：（如下图）手机打开 Shielded Vault 钱包的网页，并添加钱包到手机桌面。 钱包链接：ord-dropz.xyz/wallet （1/4）

首个隐私符文 $SHNAKAS 开始挖了！( 附钱包教程 ) 只需持有 @ShieldedNaka 合集且未挂单的地址，无需任何操作即可开挖，当前使用他们的隐私金库钱包可以看到代币领取的界面，以及 NFT 本周的算力倍速。 钱包传送门：ord-dropz.xyz/wallet 这钱包目前只能网页版，但里面集成了隐私发送资产，合集市场，域名等功能，可以说是该有的功能都有。且直接 UniSat 或者 Xverse 钱包链接签名下即可使用，非常的便捷，整体用下来的体验非常流畅，操作界面简单。 但目前还不知道这个隐私符文市场会怎么个交易，有点期待了，希望它能来个创新的交易体验。 下面就弄个简单的手机钱包演练教程： 1⃣：（如下图）手机打开 Shielded Vault 钱包的网页，并添加钱包到手机桌面。 钱包链接：ord-dropz.xyz/wallet （1/4）