The glass wall is open on BOT Chain: post, pullDown, and claim at a flat 0.01 BOT, with every unclaimed pane frosted in the interface.
Exactly 0.01 BOT each way. Posting sends 0.01 BOT with the body; claiming sends 0.01 BOT and that amount is paid to the author, not kept by the contract lead. There is no other fee.
No. The string is stored on-chain and a chain reader can see the bytes. The wall frosts unclaimed text in the interface, which is a display choice, not encryption. Treat every post as public.
Yes, while it is still unclaimed. Call pullDown(id) as the author and the full 0.01 BOT post fee is refunded. Once someone claims it, the pane is open and cannot be pulled.
No. The contract rejects a claim from the author's address, so a secret needs a second person to open it. You also cannot pull someone else's hanging secret.
BOT Chain mainnet, chainId 677, with BOT as the native token. Post and claim payments are sent in native BOT to the SecretHole contract. You can check any transaction on https://scan.botchain.ai.
It stays with the contract as the archive fee for a secret that is now open on the wall. The claim fee of 0.01 BOT has already gone to the author at the moment of the claim.
The glass wall is open on BOT Chain: post, pullDown, and claim at a flat 0.01 BOT, with every unclaimed pane frosted in the interface.
Tighten the frost rendering and the pane reading view so a claimed secret opens cleanly without hiding its on-chain nature.
Add a simple way to page back through claimed panes by author address, still reading only from the contract and the explorer.
Keep the contract small and the fees fixed; any change to the wall goes through a new deployment rather than an admin switch on the existing one.
One short string, 0.01 BOT, and a wait for someone else to pay the same to open it. If no one does, pullDown gives the post fee back — that is the whole exit.
Back to the plate