Topic: [PAID TESTERS NEEDED] Zenland Escrow Contract | Custom Agents | Up to $20 (open) (Read 1664 times)

Re-applying

Hi Bitcointalk,

Thanks to all the feedback and suggestions collected within all beta testing campaigns across different forums, we are closer than ever to perfecting our User Selected Arbitration feature. We still need a few more tests to be done before the official release of the feature and onboarding of our first agents.

So, feel free to apply now and contribute to developing the perfect escrow tool.

The second contract for this week has been created on Binance Smart Chain. Mr.suevie has been invited to it as an escrow agent.

https://bscscan.com/address/0x7073dA966ee4a9a24F4c56f72ADF67BD81A4818E

i logged into the zenland app using this wallet address 0x600aa6a1d725ac4306733de428b4f9ab4063d327 . waiting for the next step

My review :

The contract & dispute:

There was a disupute regarding the contract "Contest campaign management service on Bitcointalk".
Contract description: "Seller will design, launch and manage a contest on Bitcointalk.org on our behalf. Seller will be paid upon contest completion through this escrow contract."

I reviewed the chat. Both parties agreed to the contract at the start, as their conversation indicates. After 7 days, Buyer wrote to complain that the campaign for which Seller had been hired had not had the desired commercial repercussions and was dissatisfied with the service offered. Seller explains to Buyer that he was responsible for the design, but not for the success of the campaign as per contract description.

As the contract is not subject to a success quota, I consider that Seller has fulfilled the contract: he designed, launched and managed the contest on bitcointalk, he did what he was hired for. I therefore donate the funds to Seller minus the agent's 1% commission.


Suggestions and comments:

-In the "Profile", it might be useful to add a "last active" or "last connection" section, so that the agent/user can anticipate a response time. Likewise, a small section for other means of contact would be nice (although this can be done by modifying the bio).

-Would you consider creating a bot? on telegram for example? that could be practical. I think we could quickly run out of notifications "external" to the platform and therefore reactivity, especially if contracts expire soon or if a agent is waiting for an urgent answer.

-Your documentation is rich and precise, kudos guys! Are you thinking of creating a more "general" FAQ ? it could redirect to the documentation at some points, but something more "brief". I think it could be more begginer-friendly.

-You could let agents set fees at 0% if they wanted, so they could handle small contracts easily and build their reputation on the platform. I don't know if people will be all willing to give a percentage to an unknown agent who doesn't have a review.

-You could include a hyperlink to the Buyer/Seller profile on the Contract page.
"Contractee (buyer):" "Contractor (seller):".
Would be great to be able to click on "buyer" "seller" and access their profile directly from there.

-Otherwise it's not really problematic, but I wanted to point out that I have a red "The operation was aborted." message that appears in the bottom right-hand corner of every page I open in the Zenland App. It doesn't affect the platform functionnalities in any way though.

Conclusion :
I didn't encounter any difficulties during the whole process, everything was clear and smooth. Bravo, it's an excellent idea and a good platform. If you continue to listen to the community, and to provide good work like that, I think you have a bright future in the sector.

Telegram username: suasa01
Btc address:: bc1q6376nqhusx5hksgvuhzef34zncf43yygvp2e39

Reapplying

Is this campaign still available?
If yes then I’m reserving a spot

Reserve

I logged in to Zenland using this wallet address 0x993890cf06a11e7a8c8d32052dec701799f1b0d7. Waiting for the next step.

1. Your Telegram username. @Nalain0420
2. LTC Wallet address. MRZxsPmFNuvPnVC6UAG8PFHCxC7KHLXMkY

1. Your Telegram username: @UnknownOp77
3. Wallet address for payment: bc1qhgc56hf4ynpp9rmdxcv84aq9ma2l9kwpydk0rl

Hi, Bitcointalk! Here are the users accepted for this week. Instructions on how to proceed further are sent in PM.

• Quote from: Becassine on January 12, 2024, 05:46:28 PM
  Adress LTC: ltc1qmh0fer6ze0ms7xh6999wnpw7lf4gedmkung8jn
  Adress Metamask: 0xB4693f2231B3cFC20012FceCc7c595a82ce3E457
  Telegram @Becassine
  
• Quote from: Mr.suevie on January 04, 2024, 10:52:55 AM
  Telegram username: @Mr_suevie
  Btc address:: bc1qtwnndmhnxsfk8asjwdwh6ln8jdkt6d5txdpe5r
  
• Quote from: wallet4bitcoin on December 27, 2023, 10:13:27 AM
  1. Your Telegram username:  wallet4bitcoin
  2. Wallet address for payment:    bc1q6h86ucpa532ch4ndzwr8ug6p4cklyvd4sxkyjr
  

2 Full & Senior and 2 Hero & Legendary rank seats are still available for this week.

My review for this new experience as a custom agent :

Well, I was invited for a disputed case as it appeared on my notifications list, on a 1 USDT exchange to USD in Payoneer case on Polygon Network.

First, I had to check and read all the chat multiple times to understand everything and find who’s trying to scam the other. So here the buyer who created the contract with these details:

Is trying to receive 1 USD to his Payoneer account In exchange of 1 USDT that is already been reserved in the contracts.

First thing, I have checked the contractor and contractee profiles, and found out that

The buyer is very active on ZenLand and has many finished contracts which makes him more trusted than the seller who is having his first contract and it’s being disputed. (it’s just a point but doesn’t determine who’s trying to scam the other )

The seller is claiming to send the 1$ to the buyer address « [email protected] » so the contract state was signed and changed to fulfilled. The buyer than didn’t receive the funds as he claimed after almost an hour, also he was claiming that the screenshot sent to him is fake. That’s why he opened a case and disputed the contract.

My conclusion :
The Seller is a scammer, he didn’t send any money using Payoneer to the buyer .
Why? Because first Payoneer sending money limit is 50$ as a minimum to send.
Second, the screenshot the seller sent was obviously fake from a Paypal account.
Maybe the buyer didn’t notice the terms of Payoneer for sending a minimum of 50$ at least, but the seller here  definitely didn’t send any money. And that’s my job to only detect who is true and who’s lying.

Here the seller deserves 0% of the funds, the agent will only take 1%, and 99% for the buyer.

---

My honest review about the whole experience was really perfect and didn’t face any issues. The contract settlement approved in few seconds without any issue.
You will only need experienced agents to review every dispute and check the details of every case, the good thing is you can ask for more details and easily settle the case.

It’s a great thing to see you once again here, you are really doing a great job in creating a perfect solution for  escrow services.

The first contract for the fourth week has been created on Polygon. GxSTxV has been invited to it as an escrow agent.

https://polygonscan.com/address/0x78D06Ff315a0d9D43d3eD66008D94c6Ee31F176C

A list of new testers will be posted soon. Thank you.

Hello

Adress LTC: ltc1qmh0fer6ze0ms7xh6999wnpw7lf4gedmkung8jn
Adress Metamask: 0xB4693f2231B3cFC20012FceCc7c595a82ce3E457

Telegram @Becassine

Thank you for this chance once again.

My telegram : @masterxce
LTC address : LR6PWXp88D2MM2VsQXV7w7nsNtPwuN78jW

Metamask address : 0x16f8F8F2ad7BBfeaBA8E4484eB82Af3F66F2c5f6

Nice, but maybe you could consider using a system like on Agoradesk: like an auto-deletion of the contracts after a period of time. I mentioned Agoradesk because they state at the beggining of each chat "this chat will be saved for 180 days in case of dispute etc...etc..". This could help regarding the privacy problem.
Maybe 30 ou 60 days would be enough, but the idea is the same.

---

All the best with the ongoing test campaign!

Thank you once more to users who took the time to go through the arbitration process and post their reviews.

The campaign is ongoing and as usual, we will soon review all previous applications over and post the next list of accepted listers. Meanwhile, we'll be happy to have more applications from new users interested in testing out how being a Zenland agent works.

We wish everybody a great weekend,
Zenland Team

Hello. I want to personally thank everyone who completed the review with our new custom agent feature.

Also, I wanted to let you know that as soon as we conclude our beta test campaign, we will launch the official Zenland Custom Agents of Bitcointalk Thread.




At the beginning, we thought that keeping resolved dispute cases in an agent's profile might be a privacy issue. However, since we received many requests, we've updated the permissions for agents to view their old resolved contracts. Now agents will be able to see their contracts after they have been resolved.

---

There was a problem with rendering the reputation page for agents, but everything should work fine now.
Here is how the agent reputation page looks like - Agent Reputation Page
Here is how a regular user reputation page looks like - User Reputation Page

We are planning to expand the analytics for the agent reputation page to make it easier for contract parties to choose the right agent. We need more people using Zenland to gather the data.

---

Agent's decision is final. Once the money is sent from the contract, the case is closed. There is no appeal system as for now, but we currently have two options:

First, if a custom agent is bribed: We are launching custom agent features on Bitcointalk because here we have a community. If the buyer/seller believes that the contract was resolved unfairly, they can open a scam thread here on the forum, and we will double-check everything from our side and disable the agent if necessary.

The second option is the Zenland Forum, where custom agents will be submitting difficult cases to solve. As a community, we can help find the right consensus in more complex cases. These cases can be used as a precedent by other custom agents to help solve cases more efficiently in the future.

Also, the smart contract is build in a way that once the agent is invited into the contract, only agent can send money out of the contract. Buyer and seller loses rights to release the money.

---

In Contract Details, the buyer protection time is static to show the counterparty all the contract details before approving it. It's very important to read the draft contract before approving it.

---

Yes, we designed it so the buyer will not 'burn the money out of spite by never releasing it', as Satoshi once said here Bitcointalk Thread. If the buyer is not satisfied with the delivery, instead of freezing the money, they can always dispute the contract and stop the buyer protection time.

---

Thank you, TryNinja, for your thorough review. We need more testers like you. The incorrect positioning of Seller/Buyer/Agent fields is fixed. New tooltips for the agent page are added. The TypeError on the nickname check is also fixed. Agents can now see their old contracts.

---

I have personally changed the terms in the chat and in most notifications from Contractee to Buyer and Contractor to Seller. The only place these labels are left is on the contract creation page.

---

Thank you for your contributions. I'm adding them to our To-Do list.

Telegram username: suasa01
Btc address:: bc1q9shzpnvy30yl4tcpqc2w3nsa67jthy7ug2xua6

I confirm that I've received payment, thank you Zenland, I enjoyed the testing and I look forward to being one of the actual agents on full launch. Goodluck to the Zenland team.

Payment received from ZenLand.  Thank you!

Here is my review  




I was assigned to a contract involving (Instagram Likes) trade, Contractee buying 50 (*premium) instagram likes from Contractor for 1 USDC.


The terms: Contractor must provide 50 likes to the post provided by contractee, the likes must come from quality accounts that have profile picture and simple and understandable name.


.The contractor marked the trade as fulfilled, and say that, I quote: [Done! I've sent over the likes. They're from real-looking accounts.]

.The contractee complains about the profiles that they have no posts and profile pictures.

.The contractor respond to that that they are real people with no posts on Instagram.

.The contractee do not agree and ask for refund or the fulfillment of the contract.

.Which the contractor reject and ask for release.

.Then the contractee raised the dispute.





-At first look on the instagram post, there was only 43 likes not 50.. and from the 12 accounts I was able to access there were few that were clearly bad quality: no profile pictures, non understandable names, private, or no-posts profiles with no following accounts and followers.

-At this point the contract is not fulfilled!

I solicited the Contractor/Seller on the chat, and after no responds I made the distribution like following:
 (Contractor/Seller: 5%)  (Contractee/Buyer: 92%)  (Agent: 3%)

---

*I was about to send this two messages on the chat after the distribution but once the distribution is made acces to the contract is not still availlable!

---

*About my decision, I would rater have redistributed to the contractor nothing but I wanted to significate to the buyer especially ragarding to the nature of transaction and the difficulty around it!



PS:

- While browsing I faced sometimes (a blank page), the page do not show or load, but is sure that this is a minor problem that will be solved.



And at last,
I would like to thanks and congratulates you for your work !  This is what the real entrepreneurship is.. remedy to the market's needs !

my feedback is this

I was invited as an agent in a contract consisting of a buyer who purchased an iPhone 7 128GB, the buyer received the item and observed that the phone is locked with a message which states that the phone has been reported as stolen. The seller keeps claiming that the damages was done during shipment of the phone, I saw from the seller's argument that the damage on the phone cannot be from the shipment, that in fact the phone seems to be stolen. The buyer couldn't react to that accusation, but instead pressured the seller to release his money as the goods was in a good condition when he sent it. The seller opted to involve an agent and leave the phone in the police station

My Judgement
From the drama and the failure of the seller to react to the allegation that the phone was actually stolen and not a packaging damage was evident that the seller was the defaulter here. The seller was only interested in his money being released at the expense of his reputation being tarnished with the allegation of theft, and having considered carefully the evidence of the buyer below, and asking the seller for his own evidence of acquiring the device legally, which he never replied to.



Also checking their reputation and reviews, I also observed that the seller has neither a good review nor reputation, while the buyer has over 7 reviews with excellent reputation..
I finally resolved the dispute in favour of the buyer, I sent 99% of the funds back to the buyer and 1% to agent.

Observatons
I saw that there is a documentation that helps even new and old users get more acquainted with the way Zenland operates and I must say its a very good feature.

I also observed the presence information and interaction channels like telegram and discord.

I observed the seperate buttons loading the contract and chats. It made the presentation cleaner and gives a very good user experience for the agent.

The contract creation date and the Due date had an excess of 4 days as against the 30 days buyer protection time, it was 34 days actually

I also saw these feedbacks when I sent funds to specific addresses, both "success" and "not found". please fix the bug


Recommendations

• use a conventional title for the disputed parties like buyer/seller and not contractor/contractee
• make provision for being precise when asking any party a question, like a button where you can choose to either ask the buyer or the seller specific questions in the chat and the indications of who the question is meant for.
• There should be extra layers of security like 2FA, Google auth etc because a compromised Zenland account might possibly mean a compromised metamask wallet since it is connected
• there should be a history of the dispute an agent settled and not disputes vanishing never to be found again

Conclusion
This platform is really promising, Thank you very much for the opportunity given to me to test it out, I wish Zenland the best in becoming a top escrowed tool, and I would love to be one of the actual agents in the near future

I want to confirm that I have received payment. Thank you to the Zenland team for the opportunity to review the agent side of their decentralized escrow service.

The case so far:

The escrow was for the exchange of 1 USDC for 10.000.000 SHIB.

I check the chat logs, the Contractee has sent 1 USDC on the Polygon network to the escrow contract, which I confirmed onchain.

The Contractor then sent the Contractee 10.000.000 units of a token on the Polygon network of contract 0x61b66853bdefe04dc058774b808163d65a9c947d, which is an ERC20 with the symbol “SHIBA”.

The Contractee contested the idea by claiming that those are not the real SHIB tokens, but a random/fake token with the same name on the contract.

The Contractor isn't collaborative, the contract is disputed.

---

My decision:

I sent the following message on the chat so both parties understood my way of thinking:


Then I split the money, which finished the case: 99% to the Contractee (buyer), 0% to the Contractor (seller), 1% to the Agent.

---

Thoughts:

• The link (coingecko page) on my message sent on the chat was broken. Screenshot:
  
  
  

• On the contract main details card, the Contractee (buyer) comes first and the Contractor (seller) comes second. When splitting the money, it's the opposite: the Contractor (Seller’s Percentage) comes first and the Contractee (Buyer’s Percentage) comes second. This change of orders and wording can be confusing, which is bad specially when you’re splitting the money, a sensitive action that can cause money losses.
  
  For a moment, I almost did the opposite of what I wanted and sent 99% to the Contractee (buyer) which was trying to scam the Contractor (seller). This would be a disastrous outcome.
  
  
  
  
  Suggestion: Be more consistent with the wording for both parties. I personally still don't like the words Contractee and Contractor as a non-native english speaker. Multiple times I caught myself having to think more than I should to avoid mistaking who's who. "Contractee = buyer = sent the USDC" and "Contractor = seller = sent the fake SHIBA".
  
  I would prefer if the contractee/contractor names would be ditched and the contract creator could choose if he's the buyer or seller.
  

• Hovering the “Seller’s percentage”, “Buyer’s Percentage” or "Agent’s Percentage” information icon on the Splitting Money card shows up a tooltip that blocks the input until the mouse leaves the area. It took me a couple seconds to understand why I couldn’t write on the input.
  
• The reputation page was down at the time of my review. Error “Cannot read properties of null (reading 'toLowerCase')” on line 74 of Profile.tsx: params.id.toLowerCase() !== auth.whoAmI.nickname.toLowerCase())
  
• After the dispute was concluded, I was sent directly to the Contracts page and an error message popped up with the text “Not found”. It would be better to show the final outcome and the previously disputed contracts on my list.
  

The next 4 contracts of the second week have been created on Binance Smart Chain and Polygon. nelson4lov, Danydee, DubemIfedigbo001, and TryNinja have been invited to them as escrow agents.

https://bscscan.com/address/0x621340a3883bff299e9aeb8c466598395408a53b
https://bscscan.com/address/0x54767383e44c00994d1e6d55311a0d51b4eedff6
https://polygonscan.com/address/0xfdc525526bfb59d08b2fe4456e203a76c01b673a
https://polygonscan.com/address/0xd949edc1db7a49f0bb494929051b046fd291c6c8

Since nelson4lov has already executed his arbitration, we're sending instructions on how to proceed further to the other 3 testers in PM.

All reviews that were posted so far are just great and full of wonderful ideas that we could potentially grow into whole new features. They all will be discussed with the team. Regarding the questions and concerns posted by the testers, we will soon make a post covering them all. Thank you.

Payment received, thank you

Zenland Escrow Review

I was invited to try a Zenland escrow contract as an agent. The contract is 0x621340a3883bFF299E9AEb8c466598395408a53B on Bsc Chain (contract on bscscan: https://bscscan.com/address/0x621340a3883bFF299E9AEb8c466598395408a53B)


Contract terms: 
Exchange of 1 BUSD to 0.000022 BTC

However, there is a small mistake in the contract details, USDT is used instead of BUSD as quoted below:


What happened:
The buyer was supposed to receive BTC from the seller. The seller sent an invalid TX hash since it doesn’t include the buyer's BTC address as a recipient. The buyer pointed this out to the seller who insisted it was a blockchain congestion problem which isn’t the case. The seller persuaded the buyer to coerce him/her to release the BUSD when the seller hadn’t fulfilled his end of the contract. 

Given the seller's dishonest behaviour and no further response from the seller, after I requested an appropriate transaction hash to be sent as proof, I was inclined to resolve the escrow contract in favour of the buyer and I did. Agent fee is currently set between 1-3 % for the agent for successful resolution as seen below: 





I took a 1% fee and returned the other 99% to the buyer.
 

Observations:

• Messages in chat by the agent can’t be edited once sent.
• The buyer protection time countdown is stuck at 1 days, 0 hours, 0 minutes in the UI even if it is enforced at the contract level.
• After the buyer protection time is elapsed, the seller can call

and take 100% of the buyer's money and there is nothing the buyer can do about it. [/li]

• Contract code looks good and secure but lacks comments and some gas optimizations can be done to reduce the gas costs for users (buyer, seller, agent) eg: changing some require statements to custom error and other best practices like using constants instead of magic numbers.

Telegram username: @Frankolala
Btc address:: bc1qymald8m889fjfmt0fyc406f3lxywuwhxu65lft

I logged in to Zenland using this wallet address  0xD2245bAbf3A48e2fB293C6b59923200b1ebFA439.  Waiting for the next step.

Thank you.

In this case, here is my original post:

Telegram username: @Mr_suevie
Btc address:: bc1qtwnndmhnxsfk8asjwdwh6ln8jdkt6d5txdpe5r

Same please, consider updating my payment address to LTC: edit:ltcaddresspaid2

Thank you!  

As requested I logged in using the new wallet address:

Apologies for any inconvenience !





About this, can you please consider updating my payment address to Litecoin:
Thank you so much !

I had the opportunity to do the test as an agent for the https://arbiscan.io/address/0x5194D97A7D9bc5E093AE6b8189c52873eEdfcC9b contract.

Contractee wanted a text translated from English to French.
Contractor promised Contractee a professional quality translation.
Contractee was not satisfied with the quality of the work provided and suspected the use of online translation tools such as Google Translate.

Who are the two parties?
Well, I don't have much info.
However, Contractee has 10 reviews, all 5/5 and all positive comments. Contracotr has none, and no feedback at this time.

At first glance, I didn't really know what to make abut this dispute. The translation seemed not perfect but more or less OK.
On re-reading the chat again, I realised that Contractor received the text to be translated at 13:44. He sent the translated version at 13:45. This first point suggests the use of a translation tool.
Then, when I read the text, I realised that there were some mistakes in the translation and some grammatical errors.
Contractee was quite insistent at the beginning of the exchange, emphasising the fact that he required a professional quality translation. In my opinion, therefore, the contract has not been fulfilled, and I have agreed with Contractee.

So I sent a quick message in the chat, explaining my decision, and then sent the funds back to Contractee. I chose a 1% agent fee.
I did not propose a 50/50 arrangement as Contractor was clearly acting in bad faith. (If there had not only been ONE minute between receiving the text and sending the translation, I would have proposed a 50/50 or some other arrangement.)

Comments and observations:
-Perhaps a page/history for the agents, so that they can be trusted in disputes?
-The contract is no longer visible at all once the funds have been sent, perhaps it would be practical to keep them for a while in case of a problem with one of the parties?
-Perhaps you could incorporate the possibility for agents to invite a third party agent into the chat, in case there are any doubts? For example, if the agent in my test didn't speak French, he could ask another agent for help? How was supposed to do an non-FR speaking agent to deal with this case?

Another question: is there an appeal system for the agent's decisions?
Or is his decision final and absolute?

Otherwise, I love the principle of your service, guys! I heard about you on Dread, and I'm pleased to have had the opportunity to try out your services as an agent. I'd love to be an agent and handle real disputes in the future if I get the opportunity, it's very interesting and necessary in our world to have access to real escrow services.

We all know that in a free and decentralised market, trust and reputation are essential. Your service offers to add trust and build some reputation, it can become a MUST if you continue like this. You might want to consider listing yourself on tor.taxi for more visibility, as many people are looking for trusted escrows. Likewise, why not list yourself on kycnot.me?

Last question: I haven't found a way of adding 2FA, is this planned for the future?

---

I'll continue to browse your documentation and your site, and I'll add my comments/questions here if I have any.

Thanks @Zenland, that was really interesting!

Telegram username;  @Mia_vic
BTC address;. bc1qxw775lqnzd90hta5mfyvhcsgajml2skuypu2aw

I'm one of the participants of your previous rounds of Zenland beta test. If possible I would love to leave my feedback once again after testing the Zenland and it's current state and new features if any of those are added. I will try to explain in detail about my experience of using Zenland's escrow platform.

The first contract of the second week has been created on Arbitrum with paid2 and further instructions are sent in PM.  

https://arbiscan.io/address/0x5194D97A7D9bc5E093AE6b8189c52873eEdfcC9b

We had some issues with creating contracts with Danydee, nelson4lov, and DubemIfedigbo001 which are being sorted out in PM.

We highly value the opinions of reputable forum users and those who participated in previous rounds of Zenland beta tests. GxSTxV and TryNinja, please log in to Zenland App using a new Metamask address and post this address and your Telegram username in this thread. We will use the quotas of the next week, this week is almost over anyway

We added LTC as a reward payment option due to the recent growth in BTC transaction fees. So please provide your LTC wallet in your application if you want to be paid in LTC.

0 Hero & Legendary and 3 Full & Senior rank slots are still open for this week.

Telegram username: @Hatchy89
Btc wallet address:bc1q3s4jzryhp2lr7eynhlzvecx6egqmvq43w2ntqt
Ltc address: ltc1qypxrvppddhlf3vkfjfglpme7asmn9haxdqlemy

Telegram: @DaNNy001x
Wallet address for payment: bc1q8y85d0kegf9y2g536acps0pjcdypk6yv8wu0pk

Zenland should have made exception for you.

edit: removing after 24h, didn't see Legendary was full

thanks @TryNinja for the notice, remove after 24hours

I logged in to Zenland using this wallet address 0x91D34d65A8672812b49932FFbfc0A513F411D0A3.  Waiting for the next step.

Thank you

I logged in to Zenland using this wallet address <0x7AA29143c9398c21fA337E58ACb7f0f062712E48>. Waiting for the next step.

I confirmed that I received payment. Thanks Zenland team and hope that Zenland will be known top escrow platform soon. Good luck

Thank you 

I logged into Zenland using this wallet address 0x9861A331f62b7Dc49E0A221FE023d5a811e03752. Waiting for the next step.

shasan has been invited to the last test contract of the first week.

https://bscscan.com/address/0xcdf66916caeff91a1dae3bba95a3724b1e757710

Here are the users accepted for the second week. We sent detailed instructions on how to proceed further in PM.

• Quote from: nelson4lov on December 26, 2023, 08:11:35 AM
  Telegram: nelson4lov76
  BTC address: bc1q6xc4ajrd9u8w9h6c4a8j2shkxn6q89cnt3feuc
  
• Quote from: DubemIfedigbo001 on December 27, 2023, 01:35:12 AM
  Telegram: Dominic Dubem
  BTC address: bc1q500rp4r47w3tvds9syq7klx0ckw645m2gqc9cu
  
• Quote from: paid2 on December 29, 2023, 01:29:22 PM
  1. Your Telegram username: @e0p000a
  2. Wallet address for payment. BTC : bc1qdtm5008egcn7zc9374w3g6k64uugxgpxqlzxey
  
• Quote from: Danydee on January 01, 2024, 08:36:29 PM
  1. Your Telegram username:  Danydee
  2. Wallet address for payment:  bc1qsgnfrndxj20lvz5m2f6n2xggk85pjtzahjtnda
  

3 Full & Senior rank seats are still available for this week.

My metamask address is 0xD959fF6822EeE24f3C24db07eC66674d76D774BE I am ready for next step

1. Your Telegram username:  Danydee
2. Wallet address for payment:  bc1qsgnfrndxj20lvz5m2f6n2xggk85pjtzahjtnda

Your Telegram username: Dunamisx1
Wallet address for payment. bc1q4w6lrh3rv45e5htlvghz3c8xpyqmvsqf8yhuum

I have been invited for disputed escrow where buyer and seller were already there. Now my work is to check the issue and resolve it fairly.

Deal
Exchange 1 usdt to 0.000023 BTC

First I would like to tell a story what actually happened there in chat before disputes.

The seller was claiming in chat that he send the btc to the seller address provided in the contract while seller was claiming that he has not received any payment yet

Buyer sent Transaction hash which was showing invalid. Buyer was trying to convince seller that it is just network congestion and he will get payment soon. Just release usdt but seller was smart and he disputed to agent (me)

---

When I checked whole chats, I asked a true transaction hash from buyer. He send me same invalid transaction and was claiming that seller is trying to scam, agent should release the fund. I gives him 6 hours to give valid transaction hash or resend btc if he wants to continue this trade as buyer has no valid proof of transaction.

Buyer was actually trying to scam and doesn't reply and I send 99% fund back to buyer(1% agent fee).

When I clicked on send button the contract automatically vanished

Review:
This was my first time to become agent between two traders to solve issue and it went smoothly. This feature will allow trader to trade a risk free trade with very low chances of scam. The best platform to make an escrow deal where active agent will solve the issue in best way. It remember me a binance P2P agent. I am completely satisfied with this platform,rest I couldn't say what will happen in future.

I confirm that I received the payment.

I will do within 24 hours from now, thanks.

Posting my application for futures batches of reviews/tests if it is ok for you  

1. Your Telegram username: @Nalain0420
2. Wallet address for payment: bc1q2zljfzmv8vqft60wvplda57wndr9at76ufp3c5

Your Telegram username: @UnknownOp77
Wallet address for payment: bc1qhgc56hf4ynpp9rmdxcv84aq9ma2l9kwpydk0rl

1. Your Telegram username: amphenomenon
2. Wallet address for payment: bc1q5h3fghn0qs5sa9gvf37l3nyd37x36unldfcpvw

   1. Your Telegram username:  BenjaminDFItrader
   2. Wallet address for payment.    1G4zyMeoG6wnunm2jf84q2N8AY2GkoBAvh

   1. Your Telegram username:  wallet4bitcoin
   2. Wallet address for payment.    bc1q6h86ucpa532ch4ndzwr8ug6p4cklyvd4sxkyjr

^ thank you for inviting, here is my experience & feedback:

---

I was invited to resolve a dispute, where buyer was purchasing 1 USDC worth BTC.

I confirmed the details given by buyer and seller, whether buyer had actually locked 1 USDC in escrow contract as he said, which he did.

Seller was required to send BTC to buyer, upon receiving BTC, buyer would confirm and release the agreed upon USDC balance held in escrow contract.

Then, I look at the chat.

Seller says he sent the BTC to buyer and asks him to release the USDC. He gives transaction hash, which buyer says contains different receiving address than of his.

I check the legitimacy of above data and find it to be true. Now, I check buyer's btc address, if there was some mistake in giving transaction hash and if he's received the money, buyer's btc address remains empty.

Seller keeps making few more lies along the lines, and keeps pressuring the buyer into releasing the funds. Buyer disputes.

I look at buyer's profile (Zenland Team), he is old member on platform and also his profile was filled with genuine 5 star reviews.

I look at seller's profile, his profile was created this month and had no reviews on his profile.

I had nothing more to look for, buyer didn't receive his btc, and there was no defense from seller's side, he was trying to extort money from buyer by giving false details.

The seller was allotted two days to complete the transfer, and there was still 1 day left to complete the transaction, but looking at seller's shady behavior I went on to resolve dispute in buyer's favor, with 1% cut for myself, which I received promptly on my address.

Suggestions:

- as soon as I resolved dispute, it disappeared from my profile. No where to be found.

- Agent reputation page

- I personally find buyer/seller term easier than contractor and contractee.

- Quote option in chat

- Written chat in text box should stay if you by mistake reload the web page.

---

It was fun, let me know how I did.

The first two contracts have been created on Arbitrum. Gladitorcomeback and libert19 have been invited to them as escrow agents. The third contract will be created as soon as shasan replies to the PM.

https://arbiscan.io/address/0x4B2b03Da0972B85ec913d02E3C0b792230Ea9528
https://arbiscan.io/address/0x61e3eae7653329e3e1582f97d53c0c66d0629fcf

0 Hero & Legendary and 4 Full & Senior rank seats are still available for this week.

Telegram: Dominic Dubem
BTC address: bc1q500rp4r47w3tvds9syq7klx0ckw645m2gqc9cu

res

Telegram: nelson4lov76
BTC address: bc1q6xc4ajrd9u8w9h6c4a8j2shkxn6q89cnt3feuc

I logged in to Zenland using this wallet address
0x5CA19D326D99EDbe75bD73ae88Ca7AF8a677Cbaf
Waiting for the next step.

I have taken part in many review campaigns and all does not require telegram account as a requirement for application. These review campaigns I am talking about here are big names here and the process was okay. Most people don't like putting up such information to avoid hackers and scammers spamming their accounts with links. I will suggest you review your modalities for applying  as it is not encouraging. Most people don't like it and it might scare away reliable and competent persons who could give you a genuine and honest review based on their engagement with your website.  

Thank you for accepting. First step done,

I logged in to Zenland using this wallet address: 0xF656D3E706E422Ad1Ceb2d7b83dda31A24004EFf

Waiting for the next step.

Zenland team wishes all Bitcointalk members merry Christmas and a happy New Year ⛄⛄⛄

We are excited to see all the applications but we have a quota of 3 Hero & Legendary rank and 4 Full & Senior rank members for the first week of the campaign (Dec 25 - Jan 1).

Here are the users accepted so far. We sent detailed instructions on how to proceed further in PM.

• Quote from: Gladitorcomeback on December 25, 2023, 10:16:37 AM
  Wallet address for payment. bc1q4u8eqda8sy79hw7uc30zrnhrymt0g38p45qkrq
  
• Quote from: shasan on December 25, 2023, 08:32:40 PM
  Wallet address for payment. BTC address: bc1qe49zeuwmg8whqa26jgn5pzm6ul4fzpdccz9s4l
  
• Quote from: libert19 on December 25, 2023, 11:13:15 PM
  Wallet address for payment(In ZENF): 0x47e68dfd8b04ac91cd09c9df6e4e38387464f68a (Polygon)
  

If you applied before this post and you don't see your application in the list above, it doesn't mean you will never be accepted. We will check all the applications before accepting the next batch of testers.

Now, applicants are not required to include their Metamask addresses in their application to the campaign. Only a Telegram username and a wallet for reward are enough.

0 Hero & Legendary and 4 Full & Senior rank seats are still available for this week.

1. Your Telegram username: @LibertBrown
2. Metamask address: 0xF656D3E706E422Ad1Ceb2d7b83dda31A24004EFf
3. Wallet address for payment(In ZENF): 0x47e68dfd8b04ac91cd09c9df6e4e38387464f68a (Polygon)

1. Your Telegram username: t.me/shasan32
2. Metamask address: 0x74894513e0eD3722Cc0ab977C4610Ff18300f55F (BNB smart Chain)
3. Wallet address for payment. BTC address: bc1qe49zeuwmg8whqa26jgn5pzm6ul4fzpdccz9s4l

Reserve

Reserved

1. Your Telegram username: Cannot post publicly
2. Metamask address: Cannot post publicly
3. Wallet address for payment. BTC address for BTC, ETH address for ZENF*.

If selected I will send details prirvately to avoid any un-wanted spam.

Telegram: 404
Metamask: 0x75D1D6E6c1436C2409fC4f460C7e43c30d7E21D6
Payment address: bc1q457tpmranx49v0khcdtrp7mtfeq279w8zq2lu

Telegram: https://t.me/SamReo1
Payment address: bc1qg4zetkc85jml2d4x8l5h6cvffq63xtpyqm4u3p

Telegram: https://t.me/Asiska02
Metamask: 0xCc0C77D5DAa8BB5f389950C7BD60B43f2D9828e3
Payment address: bc1qfgtagr9ntmngk95xyjyv2gs46h5tpjalnd94zm

Telegram: https://t.me/mfahad420
Metamask: 0x9aB1AbDc478A872952C92c0F9f11496a5B668858
Payment address: bc1qj4d2t3tq6hm3jxts09awutuu9wxkuzllj7d0fd

1. Your Telegram username: @UnknownOp77
2. Metamask address: 0x7b53A20eDb2CCE5dDE0d901B9ca6B6D001dA45aB
3. Wallet address for payment: bc1qhgc56hf4ynpp9rmdxcv84aq9ma2l9kwpydk0rl

Res

R

1: Your Telegram username:@Gladitorisback
2. Metamask address: 0xf4604124e11462BDB8CE74bD61E6874A1E2c8CEF
3. Wallet address for payment. bc1q4u8eqda8sy79hw7uc30zrnhrymt0g38p45qkrq

1. Telegram username: Cyberczar
2. Metamask address: 0x47f600987a626ee080BEDe38B625Bd637B1724D2
3. BTC address: bc1qvalem3mxmtyfwtu45hqpspqngxzgt0hnd8hz0p

R

Telegram username: MakusBTT
Bt. Wallet address: bc1qw2exnyn34ek7dtt8rj98ule607j07c3klqpyu0

Res

Reserve

Reserve

Telegram username :  https://t.me/simcardbit
BTC wallet address:  bc1qw47uda85zmpsm28vgppq0jqql4nmpu5k0c6883

Dec 26, 2023. Metamask address is removed from the list of required items for applications. The first list of testers accepted for the first week is announced. 4 Full & Senior member quotas are still open for the first week (Dec 25 - Jan 1).
Jan 1, 2024. LTC is added as a new reward payment option.  

Hello Bitcointalk!

We invite you all to participate in beta testing our new User-Selected Arbitration feature. Unlike previous rounds, this beta testing round will happen on Mainnets.



Now, anyone can become a Zenland agent. You can read the official announcement about the new feature here.

What will you test?

You will test the role of the agent (arbitrator) in a disputed escrow contract.

You will need to go through the contract chat and arbitrate the case* based on the collected evidence. You can message the buyer or seller for additional information if needed.

*testers will be provided with the funds necessary to cover gas fees associated with the use of the escrow tool.

Rewards

Test rewards will be paid in BTC, LTC or ZENF after the participants have completed the testing process and posted their feedback on this thread.

- Full & Senior members $10
- Hero and Legendary members $20

How to apply?

If interested, reply to this thread with:


*if you choose ZENF, also specify the chain you want. ZENF is available on Ethereum, Binance, Arbitrum, and Polygon chains.

How does the testing process work? (steps to do if you are accepted)

Step 1. Log in to Zenland App using a new Metamask address* and post the address on this thread.
Step 2. Wait a few hours before we assign you as an agent and invite you to a disputed escrow contract.
Step 3. Go back to the Zenland App, and find the contract you’re invited to. Proceed to collecting evidence and arbitrating the case.
Step 4. Come back to this thread and post your feedback on your experience.

*using a new Metamask address is highly recommended because addresses used in the campaign will be blocked on Zenland and cannot be used in the future.

Tips for arbitrating a case

1. Review the contract details thoroughly. Look for inconsistencies in the contract creation date, due date, and buyer protection time.
2. Inspect the chat between the buyer and seller. Sometimes it is easy to catch unfairness by how people construct what they say.
3. Pay attention to the sequence of events in the contract log. Unfairness might be evident if the buyer's actions seem rushed or if the seller delays crucial steps without valid reasons.
4. Study the reputation data of both parties involved which you can find on their profile page.
5. If necessary, communicate with the buyer or seller through the contract chat page to gather extra evidence. Uncooperative behavior, aggression, or refusal to provide essential information could hint at unfairness or victimization.
6. Make your arbitration decision by considering the actions and evidence. Aim for a fair split* that reflects the level of wrongdoing or compliance with the contract terms by each party.

*depending on the effort put in and the time spent to arbitrate the case, agents can set their fee at 1 to 3% of the contract price, a.i. the agreed amount.

Special notice to testers

Zenland supports 5 major EVM-compatible networks. Since we want to beta-test them all, testers will be randomly selected for different networks. More detailed information will be provided via DM.

Make your feedback detailed and on point. Express an original opinion, not based on other reports. Provide screenshots if you encounter a technical bug.

There is no fixed turnaround time for running and submitting your reports, however, we expect it to be done within 5 days after we have accepted your application.