feat: Add message explorer #84
Conversation
This commit introduces a new message explorer application in `web/apps/messages`. The main page (`index.php`) displays a list of unique addresses that have sent or received messages in recent transactions. Users can specify the number of blocks to search. The address page (`address.php`) displays all messages associated with a specific address, showing both sent and received messages. Both pages filter for transactions of `type=1` and with non-empty message fields.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This commit introduces a new message explorer application in `web/apps/messages`. The main page (`index.php`) displays a list of unique destination addresses that have received messages in recent transactions. Users can specify the number of blocks to search. The address page (`address.php`) displays all messages associated with a specific address, showing both sent and received messages. Both pages filter for transactions of `type=1` and with non-empty message fields.
This commit introduces a new message explorer application in `web/apps/messages`. The main page (`index.php`) displays a list of unique destination addresses that have received messages in recent transactions. Users can specify the number of blocks to search. The address page (`address.php`) displays all messages sent to a specific destination address. Both pages filter for transactions of `type=1` and with non-empty message fields, and both pages now exclusively focus on the destination (`dst`) address as per the requirements.
This change adds a new web application to browse transactions with messages. The main page lists addresses with recent messages, and a separate page shows all messages for a specific address. The implementation is self-contained within the
web/apps/messagesdirectory.PR created automatically by Jules for task 7263006278081333867 started by @attogram