5
(423)
Posts: 39
Earned: 0.01 XMR
Tipped: 0.005 XMR
pretty old one: when on digital download listing a person buys more than 1 piece, delivered is still only 1.
5
(21)
Posts: 20
Earned: 0 XMR
Tipped: 0 XMR
Bug report:
When I create a digital download listing, then click publish, it takes me to "Home New listing Earn Buy crypto" and changes the category to bank transfer and says "invalid category".
So on the click publish step, it is changing to some other category and failing to post.
Edit: I fixed it by deleting the back up draft post and just redoing it.
Edited: May 5 12:57
5
(8)
Posts: 9
Earned: 0 XMR
Tipped: 0 XMR
the bonds seem to only bond trades where we are buying XMR.
when we sell XMR there seems to be no bond enabled.
would taking out two bonds resolve this?
5
(53)
Posts: 29
Earned: 0 XMR
Tipped: 0 XMR
Editing a listing twice with a "," price e.g. 17,40$ removes the "," which can lead to the price being set as 174
how to reproduce:
1. create listing with price of 17,40 and save
2. edit listing, price is set as 17.4, save again without editing the price
3. price is 174
Edited: May 11 15:41
N/A
(0)
Posts: 1
Earned: 0 XMR
Tipped: 0 XMR
nitrok22
Hi i encountered a small problem for about one month on the xmr site i used to search Europe in the localisation and then browse the products listed but since some time when i am clicking next button to see other products listed in Europe the filter is restarted and i again see the products listed across the whole globe instead Europe only, right now i have to chose list more products on the site and chose the exact site i also tested in on google chromium but i did not work i am currently using zen browser thanks!
N/A
(0)
Posts: 13
Earned: 0.003 XMR
Tipped: 0 XMR
[Bug] Validator rejects certain valid subaddresses (Possible Regex/Base58 Issue)
Description:
The address validator on the listing creation page is incorrectly rejecting certain legitimate subaddresses while accepting others. The rejection appears to correlate with the specific characters used in the second position of the address string, suggesting a potential issue with the validation regex or an outdated validation library.
Steps to Reproduce:
Navigate to the listing creation page and locate the "Monero address" field.
Paste the following valid subaddress (starts with 84).
8444TyEm7jMXY1BEsfmM6vjZWHRsHrJPcWtG4HaZKFEfBSW1kHbsKw2aqhaQEtAVBAVPLHRQNre8AFznkKYsD7hkJRPRSn5
Result: The validator correctly accepts it.
Paste the following valid subaddress (starts with 8A).
8AJJt5FoxgKapYk69YgSLXPaSBYd88hghg32ie25ZXGSFFYgVeKT4ytLkPoCsnJGE3gQninbK6JDUAX4qNCRUqfXFwXe3Hm
Result: The validator correctly accepts it.
Paste the following valid subaddress (starts with 8C).
8C6RthZR9m7UJjEBSmbBPEDMyigok2Pte8hpBGtYZtCE2zrY1BRKgDy4DoC5Y7mrCQ2RPRei3pjRuBMeHGkBTzTLPW7AJGM
Result: The validator incorrectly rejects it with a "Please enter a valid address" error.
(Note: All test addresses were generated directly by the official GUI wallet and are mathematically valid).
Expected Behavior:
The validation logic should recognize and accept all mathematically valid subaddresses, regardless of their internal character variance.
Hypothesis:
A potential cause might be a legacy regex string. Primary addresses (network byte 18) restrict the second character to [0-9AB]. If the subaddress validation regex was adapted from the primary logic simply by allowing an 8 at the start (e.g., ^[48][0-9AB]), it will fail on valid subaddresses that use characters like C in the second position. Because the subaddress network byte is 42, the Base58 block encoding allows the second character to fall outside that traditional primary address range.
Would be great if this can be fix, as it'll come off as confusing for the end user that their tots valid address getting rejected.
Edited: May 25 21:22
N/A
(0)
Posts: 13
Earned: 0.003 XMR
Tipped: 0 XMR
[Bug] Silent image upload failure on initial listing creation (but succeeds when editing)
Description:
When creating a new listing, uploading images appears to work on the frontend. However, after clicking submit, the live listing is published with no images attached. There is no visible error message or warning prior to or during submission.
Crucially, if the user edits that newly published listing and uploads the exact same images, the upload works perfectly and the images attach. The failure occurred during the initial listing creation.
Environment:
Browser: Brave (Stable build) — Note: Brave Shields and all adblockers were completely disabled during testing, ruling out client-side blocking.
Steps to Reproduce:
Navigate to the listing creation page with all browser shields/adblockers disabled.
Upload an image to the listing.
Fill out the remaining required fields and click submit.
View the newly published listing.
Result: The listing posts successfully, but the image payload is missing (silent failure).
Click to "Edit" the published listing.
Upload the exact same images that previously failed.
Click to save/update the listing.
Result: The images upload and display perfectly.
Expected Behavior:
Images should attach to the listing during the initial creation process. If the initial backend request drops the image payload, the frontend should catch the error response and display a warning.
Actual Behavior:
A silent failure on creation. The frontend provides a visually false positive that the images are ready, but the data is dropped during the initial POST request.
Edited: May 26 02:35
N/A
(0)
Posts: 1
Earned: 0 XMR
Tipped: 0 XMR
Messenger always gives me an "invalid timestamp" error regardless of browser used