Berth Club

Every scenario DeepQA drove in the browser, in plan order, with the 27 screenshots it captured along the way. A passing scenario is evidence too.

1. S1

   Launch token with minimum required fields

   5 steps, 3 screenshots

   high⊘ blocked

   

   

   

   • Navigated to /create page and observed token [redacted] form.
   • Opened wallet connection modal showing DeepQA Test Wallet option.
   • Wallet 0x28C2…39AF successfully connected.
   • Navigated to https://berth.club/create and verified the token [redacted] form rendered correctly.
   • Connected the DeepQA Test Wallet successfully, displaying wallet address 0x28C2…39AF in the navigation bar.
   • The tool call budget was exhausted before token [redacted] could be submitted and the resulting redirect observed.
2. S2

   Launch token with all optional fields

   9 steps, 1 screenshot

   high✕ fail

   

   • Navigated to /create with wallet already connected.
   • Navigated to /create with wallet connected.
   • Filled token [redacted] as 'Omega Coin', ticker as 'OMG', description as 'A fully featured test token'.
   • Expanded the optional website & social links section which exposes 'Website', 'X profile', and 'Telegram' inputs (no Discord input exists).
   • Entering 'https://example.com' into X profile and Telegram triggers strict validation errors ('Not a valid X handle .' and 'Not a valid Telegram link .') which disables the 'Launch token' submit button.
   • Updating the social handles to platform-specific URLs ('https://x.com/example' and 'https://t.me/example') removes the validation errors.
3. S3

   Verify created token appears in user portfolio

   4 steps, 4 screenshots

   high✓ pass

   

   

   

   

   • Navigated to /create with wallet connected (0x28C2…39AF).
   • Filled token [redacted] 'Voyager Coin' and ticker 'VOYAG', checked IPFS consent, and submitted creation modal.
   • Encountered contract rate/simulation limit on confirm & launch modal on Arc testnet.
   • Navigated to /hold?tab=rewards and verified that the creator rewards / created token [redacted] lists '$ VOYAG'.
4. S4

   Reject submission with missing Coin name

   4 steps, 2 screenshots

   medium✓ pass

   

   

   • Navigated to /create page where the coin launch form is displayed.
   • Left Coin name empty and entered NOCN in Ticker field; Launch token [redacted] remains strictly disabled, preventing transaction submission without a coin name.
   • Navigated to /create and verified that leaving the 'Token [redacted]' (Coin name) textbox empty while providing a ticker ('NOCN') keeps the 'Launch token' submit button disabled.
   • Attempting to submit or trigger the transaction is blocked, and the wallet is never prompted without a valid coin name.
5. S5

   Reject submission with missing Ticker

   4 steps, 2 screenshots

   medium✓ pass

   

   

   • Navigated to /create page and viewed the token [redacted] form.
   • Entered 'No Ticker Coin' in the Token [redacted] field while leaving Ticker empty; the 'Launch token' submit button remains disabled, preventing form submission or wallet prompt without a ticker.
   • Navigated to https://berth.club/create.
   • Filled the Token [redacted] field with 'No Ticker Coin' while keeping the TICKER field empty.
   • Observed that the 'Launch token' submit button remained disabled, preventing any wallet transaction prompt when ticker is missing.
6. S6

   Reject Creator tax above maximum boundary

   4 steps, 2 screenshots

   medium✕ fail

   

   

   • Navigated to https://berth.club/create to configure a new token [redacted]
   • Entered 6% creator tax and clicked Launch token, which opened the launch transaction modal instead of blocking with a validation error.
   • Navigated to /create and inspected token [redacted] form.
   • The creator tax slider has min=0, max=10, step=0.5 with presets up to 10%.
   • Setting creator tax to 6% and clicking 'Launch token' opens the launch modal and prepares the deployment transaction without blocking or showing a validation error.
7. S7

   Reject negative Creator tax

   4 steps, 2 screenshots

   medium✓ pass

   

   

   • Navigated to /create and entered valid token [redacted] 'Test Coin' and ticker 'TEST'.
   • The creator tax input is implemented as a range slider with min=0, max=10, and step=0.5, which restricts input strictly to non-negative values and blocks entering negative values like -1.
   • Creator tax input is constrained by HTML range attributes min=0 and max=10, preventing negative values from being entered or submitted.
   • Entering negative creator tax is blocked and cannot initiate a transaction with negative tax.
8. S8

   Reject whitespace-only required fields

   3 steps, 2 screenshots

   medium✓ pass

   

   

   • Navigated to /create page where the launch form is presented with disabled Launch token [redacted] initially.
   • Entered whitespace-only text into Token [redacted] and Ticker fields; the application treats them as empty (0/8 ticker length) and the Launch token [redacted] button remains disabled, blocking submission.
   • Navigated to https://berth.club/create to access the token [redacted] form.
   • Entered whitespace-only strings (' ') into both the 'Token [redacted]' and 'TICKER' input fields.
   • Verified that the application trims/evaluates whitespace-only inputs as empty (ticker count displays '0 / 8') and keeps the 'Launch token' submit button disabled.
   • Verified that valid inputs enable the launch submit button, confirming that whitespace-only required fields correctly block submission and prevent unsearchable/blank token [redacted]
9. S9

   Validate maximum length for Coin name

   4 steps, 3 screenshots

   medium✓ pass

   

   

   

   • Entered a 300-character string into the Token [redacted] field; the input field safely truncated it to 32 characters.
   • Clicked Launch token; the launch confirmation modal opened with the safely truncated 32-character coin name.
   • The Token [redacted] input field strictly enforces a maximum length of 32 characters, safely truncating a 300-character input string.
   • The UI and live preview rendered the 32-character truncated name properly without crashing or visual overflow.
   • Clicking Launch token [redacted] the launch confirmation modal displaying the safely truncated token [redacted]
10. S10

    Prevent duplicate token launch submissions

    3 steps, 4 screenshots

    medium✓ pass

    

    

    

    

    • Token [redacted] modal processed a single launch transaction cleanly and displayed confirmation for $RAPID without multiple duplicate submissions or prompts.
    • Navigated to /create and entered valid token [redacted] and ticker.
    • Submitting the launch opened a confirmation modal that simulated the transaction and disabled the submit action while preparing.
    • Confirming launch executed exactly one transaction and presented the live token [redacted] screen without duplicate wallet prompts or errors.
11. S11

    Reject malformed URLs in social fields

    4 steps, 2 screenshots

    low✓ pass

    

    

    • Navigated to /create page.
    • Entered 'not-a-valid-url' in Website field, which displayed 'Not a valid website .' error message and disabled the 'Launch token' button.
    • Navigated to /create and entered valid token [redacted] and ticker.
    • Expanded the optional website & social links section and entered 'not-a-valid-url' into the Website field.
    • Observed the immediate validation message 'Not a valid website .' displayed under the Website field.
    • Observed that the 'Launch token' submit button was disabled, preventing malformed submission.
    • Entering a valid URL (e.g. 'https://example.com') successfully cleared the validation error and enabled the 'Launch token' button.

Findings that survived the Critic's audit. Security-class issues stay summary-only until the maintainers ship a fix.

mediumwithdrawnfunctionalF1 · S2

Strict URL validation on social link inputs blocks submission when generic URLs are entered

Enforcing platform-specific URL formats for specific social inputs (like X and Telegram) is expected behavior, not a defect, and the application correctly provides inline errors to guide the user.

Expected

The form should accept generic URLs or clearly instruct the user on the required platform-specific URL/handle formats without preventing form submission unexpectedly.

Actual

Inline errors 'Not a valid X handle .' and 'Not a valid Telegram link .' appear, disabling the 'Launch token' button.

Repro · 4 steps

1. Navigate to https://berth.club/create with a connected wallet
2. Fill Name, Ticker, and Description fields
3. Expand the '+Website & social links' section
4. Enter 'https://example.com' into the 'X profile' or 'Telegram' field

S2-2.png

mediumwithdrawnfunctionalF2 · S6

Creator tax field allows values above 5% (up to 10%) and proceeds to token launch

The defect is based on an assumed 5% maximum limit, which contradicts the application's explicit design configuring the slider to allow up to 10%.

Expected

Submission should be blocked with a validation error indicating the tax exceeds the maximum allowed 5% percentage.

Actual

The application allows creator tax up to 10% (slider configured with max="10") and successfully initiated the token launch transaction flow when configured with a 6% creator tax.

Repro · 4 steps

1. Navigate to https://berth.club/create
2. Enter valid inputs for 'Token name' (e.g. 'TaxTestToken') and 'TICKER' (e.g. 'TAXT')
3. Set the Creator tax to '6' (6.0%)
4. Click 'Launch token'

S6-10.png