Hi there!
Just a quick update on the most recent suggestions and questions in the thread.
Feature suggestion : a demo mode.
That is a good idea to demonstrate what the actual escrow smart contract process looks like, and will be considered for future releases. That said, there would be explainer videos in multiple languages to give the user a sneak peek into the escrow process.
During the contract, I haven't faced any difficulties. I would recommend Zenland keep the chat option enabled if the deal is done. So that buyers/sellers can communicate later to do another deal by communicating through the platform in case they lost communication outside the platform.
The chat is associated with a specific contract, and so is discontinued once the contract executes (when the amount locked up in the contract has been released). In case they lose communication outside Zenland but have more deals for one another, they can always create a new contract with the in-built chat.
Well, to be honest, in the first one I mistakenly chose DAI instead of BUSD, because DAI is the option that appears by default, and this is something I would suggest you to change because it is not the most popular stablecoin.
This is a good point. While the default order for stablecoins is alphabetical, the one suggested makes sense as more users accidentally create escrow contracts with default tokens.
To suggest something, I would also add the average stars of the reviewer, or some kind of information to assess his credibility at a glance.
-It would be nice if there were a list of contracts that were currently being reviewed, in order to indicate the percentage of how many successful deals a user has completed.
4. When the transaction is completed, I can leave a review, but please add technical information to the reviews about which network the transaction was on and for what amount. After all, using test networks or just small transactions in the main networks, it is possible for scammers to grow up the rating with the help of their own wallets.
Currently, the profile review page displays the rating (including the average star rating suggested), the review text, the date, and the user's wallet address. In v. 1.1 we have implemented the "buyer"/"seller" tag suggestion so that users can easily see who is leaving the review for the contract. Full profile review analytics with more details, like the number of successfully executed contracts, is on our To Do list. Indeed, the contract amount and network are worth adding to it.
-Lastly, when releasing the funds as the buyer a message was there that “Contractor will be able to release the funds after O days 1 hrs 56 mins 47sec”. The buyer was the contractee who is releasing the funds, that message popping out there makes it looks confusing as the contractee.
The dispute request** will stop the buyer protection time countdown, and prevent the Contractor from releasing funds by the end of it. The purpose of doing so is to let the Contractee reach out to the other party to discuss disagreements and settle the issue between the two parties." - Question: is this a bug?
This is an alert message for a buyer (Contractee) to watch out for when the buyer protection time runs out (displayed by the countdown). This is not a typo or bug but a warning for the buyer about the seller's permission to release the payment as soon as the buyer protection time (BPT for short) is over. The goal is to remind the buyer how much time is left to dispute a contract if the product/service is unsatisfactory.
- It would be nice to include other cryptocurrencies for variable selection, possibly a well-known coin, and a few more languages as well. I understand that you want to keep users anonymous, but if they can communicate with one another without being hindered by a language barrier, it would be nice if a language translator were compatible with the application.
As mentioned in my earlier responses, adding language selection and more cryptocurrency options is in plan for future releases. The way how to implement language translation is yet to be fully developed. Third-party extensions will be considered as more users suggest this feature.
The entire process is perfect to me, the only place i will make a suggestion is to improve the aspect of funds transfer to the buyer.
i notice the seller can click on fulfilment even when the buyer has not click on fulfilled, i could have suggest the fulfilment button should only be active when the buyer has also click on the am contract fulfilled button from his/her end.
Because currently what only needs the buyers attention is to confirm the transaction and approved and after that the seller can do all other things without the knowledge of the buyer.
I think there is a little confusion in the escrow process because a tester acts as both the buyer and the seller. Buyer and seller both go through the Fulfillment stage of the escrow contract, but they do different actions. A seller fulfills the contract by clicking the "Complete" button on his side, while the buyer fulfills the contract by clicking the "Release" button after receiving the product or service from the seller. Aside from confirming completion, there is no action for a seller to do "without the knowledge of the buyer".
Only if the buyer has not released the payment (and not disputed) within inspection time (buyer protection time), the seller would be able to release payment from the contract himself. Before the buyer protection time is up, the seller cannot click the "Release" button on his side (it is disabled).
The addition of estimated transaction costs is also very helpful for users to save more on transaction costs when using tools from Zenland, especially the ETH network whose gas costs are quite high
- Zenland fee is transparently displayed (Suggestion: I would love to see the estimated network fees as well before creating the contract.)
The estimated cost for each transaction is already displayed in Metamask. Cost estimation per contract execution for each network will be added in future releases.
Change the font color of the notifications. The nuances are close to each other and that it makes them harder to read.
This will be the next thing to do (along with other UI adjustments) as soon as we finish the development of major features that the team is currently working on.
- I chatted with the seller and they agreed to reimburse me 20% of the funds (2 BUSD). However I haven't found any option on the platform to change the terms of the contract (Suggestion)
At this point, the current functionality does not allow a buyer or a seller to split the amount between themselves. That said, the Agent invited through a dispute is able to handle reimbursements if the funds have not been released from the contract yet. Inviting an Agent, who will be voted by the community, will cost an additional fee paid from the amount locked in the contract directly to the Agent.
1) I can set the profile name as bitcointalk_manager or pornhub_owner. This opens up quite a lot of sorts of different phishing options. Look at how much scam there is in the telegram because of this. Make it possible to change the profile name with some serious restrictions, or information in the profile of another user about when he last changed the profile name and in general how many times he did it.
2) I found that I can't set the profile name in Cyrillic. I haven't tried it, but I assume that it won't work to use other languages that don't use the Latin alphabet. It would be great if there was such an opportunity.
3) As it turned out, each field also has a limit on the number of characters. Why not warn about this in advance? Maybe I wanted to write something about myself in verse form, but in the end I received a warning only when I had almost finished the poem.
4) And allow user to connect an image for profile from NFT. It's such a hype, so if you're on trend, it will only benefit you.
These are all relevant suggestions to advance Zenland functionality and reach. The maximum character limit will be implemented within the next releases, while others are added for future implementations.
2) Got the error "a valid integer is required".
Accordingly, there is needed hint where it would say which values are valid for this field.
I see the input field allowed you to enter an array of numbers, which is not practical for an escrow contract in itself. It will be fixed in the next releases and suitable limitations will be applied when setting buyer protection time. This will also be clarified to the user.
3) For some reason, it is impossible to set the amount with a comma. That is, it turns out that it will already be problematic to send $ 100.5
At this point, the escrow contract can only accept whole numbers without decimal points. Though this will be reviewed as we receive more feedback from our users.
Thank you for the reports! Your feedback and suggestions help us make Zenland better with every version.
The Phase II of testing is still open. Members of all ranks are free to apply to be a part of our journey.
