This token does not support burning. To continue, please acquire a burnable token from one of these platforms:
Deployed Chat Contract Address:
Go to the chat: Click here
🔧 Set or switch the current chat contract address this admin panel interacts with. Make sure it's a valid deployed contract.
🔥 Set the token cost required to send a message in the chat. Higher cost can help reduce spam; lower cost encourages participation.
⏱️ Define the minimum wait time (in seconds) a user must wait before sending another message. Helps prevent flooding.
📝 Set the maximum number of characters allowed per message. Useful for keeping chats concise.
➕ Add a new ERC-20 token that users can burn to send messages. The token must implement burnFrom() and be approved by users.
➖ Remove a token from the list of accepted burnable tokens. At least one token must remain active.
⚙️ The burn cost to send messages automatically adjusts based on chat activity. If message traffic is high, the cost increases to reduce spam. If traffic is low, the cost decreases to encourage participation. These adjustments happen periodically and stay within the minimum and maximum limits you configure.
🧨 Permanently deletes all stored chat messages from the contract. Use only in special cases (like resetting chat).
📊 Shows how many messages are currently stored in the contract (max 1000).
Every time a user sends a message, it is permanently recorded as a blockchain event. Even though only the most recent 1,000 messages are stored on-chain, all past messages can be exported or archived by reading these events.
Messages are emitted using the MessageSent event, which includes the sender, message text,
timestamp, and message ID.
🔧 Advanced users can use Ethers.js or Web3.js to pull message logs, or set up a backend or subgraph to index and archive all activity.
🧹 Messages older than this will be pruned. Helps reduce storage and keep the chat fresh.