APEXIS Marketplace

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

1. S1

   Successful ERC721 listing creation

   7 steps, 2 screenshots

   high⊘ blocked

   

   

   • Navigated to /create page and viewed the Create Listing form.
   • Filled contract address, token ID 1, price 50 USDC, duration 7 days, and preview updated accordingly.
   • Navigated to /create and verified the listing form loaded correctly.
   • Selected ERC721 token [redacted], filled in contract address 0x8579882cfC7bb7087bdBb6722C985B89d94b553f, token ID 1, price 50 USDC, and duration 7 days.
   • Verified the listing preview updated dynamically with calculated fee and net receive amounts.
   • Attempted to connect wallet to complete listing; however, no Web3 wallet provider or connection modal is available in the test environment.
2. S2

   Successful ERC1155 listing creation

   7 steps, 4 screenshots

   high✓ pass

   

   

   

   

   • Navigated to /create listing page with token [redacted] options and listing form.
   • Selected ERC1155 token [redacted], revealing the Amount field and updating price label to Price per unit.
   • Filled ERC1155 listing form with contract 0x8579882cfC7bb7087bdBb6722C985B89d94b553f, Token ID 2, Amount 10, Price per unit 5 USDC, which computed Total price 50 USDC and You receive 48.75 USDC.
   • Navigated to /create and verified the listing form loaded properly.
   • Toggled token [redacted] to ERC1155, which revealed the Amount input field and updated the price input label to 'Price per unit (USDC)'.
   • Entered NFT contract address 0x8579882cfC7bb7087bdBb6722C985B89d94b553f, Token ID 2, Amount 10, and Price per unit 5 USDC.
   • Observed that the Amount field was properly accounted for in the live preview and summary: preview updated to 'ERC1155 · x10', total price calculated to 50 USDC (10 x 5 USDC), marketplace fee calculated to 1.25 USDC (2.5%), and 'You receive' computed as 48.75 USDC.
   • Observed that the 'Connect wallet to list' button became enabled upon filling the required listing inputs and handled the click action.
3. S3

   Create Listing missing required fields

   3 steps, 2 screenshots

   high✓ pass

   

   

   • Navigated to /create page where NFT contract address, Token ID, and Price (USDC) inputs have required attributes, and the 'Connect wallet to list' button is present and disabled without a connected wallet.
   • Navigated to /create page where required fields ('NFT contract address', 'Token ID', 'Price (USDC)') are marked with required indicators and HTML5 required attributes.
   • Verified that the listing submission button ('Connect wallet to list') is disabled and prevents form submission when fields are empty and no wallet is connected.
4. S4

   Marketplace fee and payout calculation

   3 steps, 2 screenshots

   high✓ pass

   

   

   • Navigated to Create Listing page (/create) where the form and preview card with summary are shown.
   • Entered 100 in Price (USDC) field; the Summary preview dynamically updated to Total price: 100 USDC, Marketplace fee (2.5%): 2.5 USDC, and You receive: 97.5 USDC.
   • The fee calculation dynamically and accurately computed a 2.5% marketplace fee (2.5 USDC) and net payout (97.5 USDC) for a listed price of 100 USDC.
5. S5

   Execute 'Buy now' on existing NFT

   2 steps, 2 screenshots

   high⊘ blocked

   

   

   • Navigated to Mushrooms #30 NFT detail page, showing listing price 1,000,000 USDC and button 'Connect wallet to buy'.
   • Navigated to the NFT detail page for Mushrooms #30 at /nft/0x8579882cfC7bb7087bdBb6722C985B89d94b553f/30.
   • Observed the listed item details including token ID #30, current price of 1,000,000 USDC, contract address, owner address, and transaction history.
   • Observed that because no Web3 wallet is connected in the browser environment, the purchase action renders as 'Connect wallet to buy' instead of 'Buy now'.
   • Could not trigger or complete the wallet purchase transaction prompt due to the lack of an injected Web3 wallet provider in the automated browser environment.
6. S6

   Invalid NFT contract address format

   5 steps, 3 screenshots

   medium✕ fail

   

   

   

   • The create listing form accepted 'invalid-address' without validating the Ethereum/EVM contract address format, updating the preview and enabling submission.
   • Navigated to the Create listing page at /create.
   • Entered 'invalid-address' in the NFT contract address field, '1' in Token ID, and '10' in Price (USDC).
   • Observed that the form did not display any error indicating an invalid address format, updated the preview with the invalid address, and enabled the submit button.
7. S7

   Zero or negative price validation

   3 steps, 1 screenshot

   medium✓ pass

   

   • Navigated to Create Listing page at /create.
   • Navigated to /create listing form.
   • Entered '0' and negative values ('-10') in the Price per unit (USDC) field.
   • Observed that the form disables the submission button ('Connect wallet to list') when the price is 0 or negative, while enabling it when a valid positive price (such as 10) is provided.
   • The application prevents zero and negative price submissions.
8. S8

   ERC721 Amount field constraint

   3 steps, 3 screenshots

   medium✓ pass

   

   

   

   • Navigated to /create page where ERC721 is selected by default; no Amount field is present on the form.
   • Selected ERC1155 token [redacted]; the Amount field is visible and defaults to 1.
   • Toggled back to ERC721 token [redacted]; the Amount field is hidden from the form as expected for non-fungible 1/1 assets.
   • Navigating to /create displays ERC721 selected by default with no Amount field present.
   • Switching to ERC1155 displays the Amount field defaulting to 1 unit.
   • Clicking the ERC721 toggle hides the Amount field completely, locking the standard to unique 1/1 item semantics.
9. S9

   ERC1155 Zero Amount validation

   4 steps, 2 screenshots

   medium✕ fail

   

   

   • Navigated to /create page with listing form.
   • Selected ERC1155 token [redacted], displaying the Amount input field with default value 1.
   • Navigated to https://marketplace.apexisdefi.com/create and switched token [redacted] to ERC1155.
   • The Amount input field accepted 0 (and negative numbers) without any client-side validation error or rejection.
   • Form submission button 'Connect wallet to list' was enabled despite Amount being set to 0.
10. S10

    Execute 'Make offer' on existing NFT

    2 steps, 3 screenshots

    medium✕ fail

    

    

    

    • Navigated to Mushrooms #30 NFT page showing listing price and Make offer button.
    • Clicked the 'Make offer' button on the NFT detail page, but no modal or form appeared and the button was completely unresponsive.
    • Navigated to https://marketplace.apexisdefi.com/nft/0x8579882cfC7bb7087bdBb6722C985B89d94b553f/30 and verified NFT details rendered correctly.
    • Clicked the 'Make offer' button and verified that no offer modal, form, or feedback dialog appeared.
11. S11

    IPFS image CORS error handling

    2 steps, 1 screenshot

    low✓ pass

    

    • Navigated to the NFT details page for Mushrooms #30 and observed the main NFT media display rendered properly with image alt text 'Mushrooms #30' and complete metadata.
    • Navigated to /nft/0x8579882cfC7bb7087bdBb6722C985B89d94b553f/30 to observe NFT media display and IPFS handling.
    • The main NFT media display loaded cleanly without breaking the UI, showing the NFT image ('Mushrooms #30') along with complete token [redacted], pricing, and transaction history.
12. S12

    React hydration error check

    2 steps, 3 screenshots

    low✓ pass

    

    

    

    • Loaded homepage https://marketplace.apexisdefi.com/ and rendered the UI properly with listings and statistics.
    • Navigated to /collections; page rendered without client crashes or hydration mismatch artifacts.
    • The homepage loads cleanly and renders all components (header, navigation, stats, listing cards) as expected without errors.
    • Client-side routing and hydration function properly across views.

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

highconfirmed ✓functionalF3 · S10

'Make offer' button on NFT detail page is completely unresponsive

I navigated to the NFT details page at https://marketplace.apexisdefi.com/nft/0x8579882cfC7bb7087bdBb6722C985B89d94b553f/30. Clicking the 'Make offer' button did not trigger any action, such as opening a modal or showing an input form; the page remained unchanged. The page reported 5 console errors during the scenario.

Expected

Clicking 'Make offer' should open a modal or form allowing the user to enter and submit an offer price (or prompt for wallet connection if required).

Actual

Clicking the 'Make offer' button produces no action, modal, or input form.

Repro · 2 steps

1. Navigate to https://marketplace.apexisdefi.com/nft/0x8579882cfC7bb7087bdBb6722C985B89d94b553f/30
2. Click the 'Make offer' button under the 'Make an offer' section

S10-2.pngS10-4.pngS10-8.png

mediumconfirmed ✓functionalF1 · S6

Listing form accepts invalid NFT contract address without format validation

The observations in S6 explicitly state that the form accepted 'invalid-address' and enabled the submit button, confirming the absence of format validation. The page reported 3 console errors during the scenario.

Expected

The application should validate the NFT contract address format (e.g. 42-character EVM address starting with 0x), reject invalid input, and display an invalid address format error.

Actual

The create listing form accepts 'invalid-address' as a valid contract address, renders it in the live preview card, calculates fees, and enables the listing button without displaying any address format validation error.

Repro · 5 steps

1. Navigate to https://marketplace.apexisdefi.com/create
2. Type 'invalid-address' into the 'NFT contract address' field
3. Type '1' into the 'Token ID' field
4. Type '10' into the 'Price (USDC)' field
5. Observe that the form accepts the input and enables 'Connect wallet to list' with no validation errors

S6-9.pngS6-11.png

mediumconfirmed ✓functionalF2 · S9

ERC1155 listing form accepts 0 and negative values for Amount field without validation

The S9 observations confirm that the Amount field accepted 0 without error and left the submission button enabled, matching the claim. The page reported 3 console errors during the scenario.

Expected

The application should reject amount <= 0 and flag the Amount field as invalid.

Actual

The Amount field accepts 0 (and negative values) without validation errors and the listing button remains enabled.

Repro · 5 steps

1. Navigate to https://marketplace.apexisdefi.com/create
2. Click the Token standard ERC1155 toggle button
3. Fill NFT contract address, Token ID, and Price per unit with valid values
4. Set the 'Amount' field to 0
5. Observe the form validation and submit button state

S9-2.pngS9-4.png