My first "hello!" to the BitcoinTalk forum this year! Here's to new beginnings in 2023! Wish you and your loved ones a prosperous year ahead. With that said, my due responses to our marketplace testers
I'm just wondering why does the minimum delivery date is 12 hours? Why it can't be set to a lower time frame which makes the buyer easily get the item?
Actually the minimum delivery time is 1 hour. The placeholder (as 12*) has been displayed incorrectly and has already been fixed on the test server. You should see them once the updates are live.
On choosing the network, Is it more easy to make the list in drop down form and state the name of the network instead of just the symbol of the Blockchain network?
While choosing a network, I will suggest that the name of the network be visible rather than just it's symbols to make things easier.
I see the confusion here is likely because of both test and main networks with the same icons (for Eth and BSC for example). Once live, only major and well known EVM networks will be represented and so the confusion should no longer persist. That said, these suggestions are taken into account and will be reviewed once more user feedback is in.
Lastly, Is there a way to null and void the existing contract without finishing the transaction? I made a mistake for not checking the pre approved box and I don't know how to close the existing contract so that I can sell the item in new settings.
The future contracts for the same item will not be impacted by not checking the pre-approved box if you edit the item. Also because the pre-approved feature impacts only the pre-approval stage, there is no need to void the existing contract. If checked, it will let buyer(s) deploy and transfer payment without your manual approval. If not, you should just approve the contracts created and the rest is the same for both escrow contracts.
I just want to request for an easy share link for an item
Oh yes, that's on our To-Do list and will be live in the upcoming releases.
First:: I tried to change Nickname of my accounts from anonymous to Seller and Buyer but i was unable to put a space between "Seller_account"
Spaces are not allowed in usernames. We'll add username and bio tooltips to the settings page to make requirements clearer.
Third:: I have fullfilled it from both (Buyer and Seller) sides but it was not updating itself. so i thought maybe i should refresh the page and come back then this issue solves by itself on refreshing.
From the screenshot provided, I see the backend did not auto-refresh the contract state in buyer because the transaction has not been successfully processed by the network yet (thus, button displays "Confirming"). Once the blockchain transaction is complete, changes are made to a contract. Then, the backend receives request results and the frontend displays them to the user.
Fourth:: I filled the whole forum my internet was also working fine but when i try to add the item then it was not working so i just refreshed the page and all of my information that i filled was gone. maybe it could be possible to keep them there even after refreshing the page. and is it possible to send pdf or other attachments through this platform? if, yes! then it would be really good for freelancers.
I see your point and taking note of it. Yet the information is not recorded before the user takes any contract action (create is one of them). Also, for security reasons, we do not store any file attachments on our servers. Also, suggestion #5 will be reviewed as more users request this feature.
Third step:[/b] logging into my second account to buy the item i have just created, i copied the item link and gave the first approval from my buyer account after that i had to login into my first account to give the seller approval for the product, and come back once again to my buyer account ( it would be better if i worked with two browsers or devices but fine)
And this is the key reason why we've introduced pre-approved contracts right here! Ticking off "Pre-approved item" in the Additional settings saves time for both parties. The seller does not have to manually approve every single contract for a specific item, and the buyer can deploy the contract and deposit payment into it without waiting for the seller.
There something that maybe if a buyer didn’t notice he can be in a lot of troubles, which is if the seller set like a big time for delivery time, the buyer can’t open a dispute until that time. What if the seller set like 30 days or more. It’s better if you set a maximum time for it IMO
There is no maximum hours or days for the delivery time to not limit the provision of products or services. We believe that putting a stricter limit of say, 10 or 15 days or even 30 will not be suitable for different circumstances (a.i. logistics, certain safety requirements (if any), etc.). Users on both sides are advised to get familiar with the purchasing terms before taking any action with the contract.
Things that can make your marketplace better
-Adding categories for each item such as, Design, accounts, products , collectibles, translating for example
-Adding the option of making your item public or not, so people can search on Zenland marketplace for the items or products they want
-Adding an option of promoting items for some extra fees, where sellers can make their items show on first page of Zenland marketplace
These suggestions are already a part of our pre-launch list and will be implemented when our public marketplace is officially live (planned for Q1)
1. On the Login page, you could improve UX by letting people know beforehand that they will need to sign a message and what that means (especially that they won't pay any gas).
Hmm, there is a message saying wallet connection does not charge any gas fee in Metamask sign message, but I see the point. The message is not visible if the user is not logged into his/her Metamask wallet and this may raise concerns over the cost. It will be further discussed with the developers and changes should be live in the next version updates.
2. Maybe this is just me overthinking, but I just feel that "who is buying" and "who is selling" would suit better rather than "buyer" and "seller" on the "New Contract" card. More of this is in the next point.
TryNinja, thank you for taking the testing one step further and trying our default escrow contracts! They are already live at
https://app.zen.land and additions can be made as we gather more feedback from the users.
4. Another UX improvement, maybe turn the "Buyer protection time" input red (as in "error") when the value is invalid (i.e < 24 hours) instead of just warning about this when the user clicks the "Create" button.
...
14. Let the seller deny/delete a contract draft before both parties approve it. Also maybe block an address from buying if someone is spamming contracts.
Invalid input warning while form-filling along with the item URL fix and share button will be implemented in the next releases. Also, the bug fix for Contract editing for buyer protection time has been sent to Team Lead.
Suggestion #5 has been requested by the majority of users and thus, has already been implemented on the test server and should be live on our next version updates.
Suggestion #6 makes sense, but personally I am (and I am sure a lot of other people as well) not a fan of pop-up windows. Though I'll keep this as a notice.
Next, adding the number of items in stock was the original idea that we had to withhold. This is because our item contracts are both for products and services that have no stock. Same with the buyer choosing the number of products to buy. Though unquestionably the right way to do for a typical marketplace, it may have unforeseen difficulties for different types of sellers.
For extra details, such as account id or email, buyer can always use the Contract Chat. It does not require any additional credentials to use and saves the relevant information for a specific contract between the two participants.
We do not store any information about contracts, including often selected networks. Yet this will be further discussed and implemented once the separate Network settings are available to the seller.
Finally, the question about the block explorer. It isn't clear to me whether you mean the source code or the code of the specific contract a user deploys. In the first case, the code can be publicly viewed on GitHub here
https://github.com/zenland-dao/contracts. In the second, we didn't not want other users to know that the contract is escrow because it rises privacy issues what if the buyer or a seller don't want others to know that they deployed escrow contract? That's why it's hidden. But now I am thinking that we should add an option if a user agrees to make the contract data fully disclosed in a block explorer or not.
Deny/delete option is on our To-Do list and should further be developed once the ground work for a marketplace is over.
~ I will also suggest that you work on improving the mobile version access of this entire process as I think most users from my country deal more on mobile phones rather than laptops.
Noted. The team is working on device compatibility already and it will further be discussed.
~ When creating an item, I think it should also be possible to search for the item created rather than copying the profile link of the seller.
Upon the launch of the public marketplace users will be able to both search for items and see user profiles/stores with the displayed items.
~ the protection time should also be worked on as there are possibilities of either the buyer or the seller not being available at the moment.
Buyer protection time starts whenever the seller clicks "Complete". If buyer has not received anything and see no changes in the contract state (contract is active and not fulfilled), the buyer may open a dispute and try to contact the seller (through the Chat or externally). If this has no effect, the dispute can be escalated to a neutral third party. I believe that setting automatic control over the contract terms that the two users decided is not right. Also, as a web3 project, we cannot impose influence over users' smart contracts.
~ I Didn't notice a notification outside the site and I think a drop-down notification and also an offline notification will really help when a transaction is going on just in case either of the parties aren't online.
In the best practices of web3, we do not intend (at least in the foreseeable future) to support push notifications.
~ I really don't think the deployment fee should be charged from just the buyer's account but be split.
Contract deployment just like funds transfer and contract completion are direct contract interactions its participants take. The fees go directly to the blockchain and, to my knowledge, they technically cannot be split between the parties.
