CanYaCoin

🗣 Happy Friday Everyone!

Hope you are all safe and well.

🐝 We've been fairly quiet in the channels but busy in the background:
- Team consolidation on our vision, short & medium-term goals, strategies and resources
- Preparation for CanWork client tests
- Continued CanWork improvements & plans to update CanYa.io.
- Business development
- And, exploring early access to Binance Smart Chain
https://www.binance.org/en/smartChain

🦻For those who've asked about the recently dropped topic of DeFi, the core team has simply been discussing the forthcoming Binance smart contracts for the CanYa ecosystem and its potential to realise some original decentralisation goals that were not initially available on Binance Chain. This includes the ability to decentralise the CanWork escrow— which is centrally controlled by CanYa currently.

None of this impacts any development or growth plans for CanWork.io 👌

👀 We have a couple of updates planned for next week to catch you up, so keep an eye out

Have a great weekend

CanYa Team

🎯 COMMUNITY TESTING OF BEP2 PAYMENTS & ESCROW

We will start contacting community members who expressed interest in testing tomorrow!

Please DM @johanlives:
-To confirm your interest
-To confirm if you already have a Provider or Client account on CanWork
-With your BNB address — to receive BNB & BEP2 tokens for testing (for selected 'Clients')

Note:
* Limited places— early responders get preference
* You will be engaged via a CanWork job request
* Fixed payment (in $CAN) will be released to you upon successful completion of the job
* Testing must be completed by Monday 4th May
* Task includes using CanWork as Client or Provider through a full job/payment cycle, simple data entry into a Google Sheet & completion of an optional feedback form
* Task should take < 30 mins of effort but may take longer to complete due to response times with your Provider/Client partner
* Full details will be provided
* BNB (for tx fees) & BEP2 tokens (for escrow) will be transferred to you when the job is accepted (for Clients)
* BNB & BEP2 transfer will be of little value but must be used for testing with CanWork's escrow —- or the job & payment will be forfeit

*🎉 BEP2 payments mainnet testing*

Preliminary testing has gone well. After a couple of tiny fixes for mainnet-related behaviours, we have demonstrated successful user testing of the BEP2 payment system with CanWork and our BEP Escrow service.

We will run a few more scenarios before we open up testing for community.

*Community Testing*
Please let @johanlives know if you are interested. This will be paid testing —in CAN via CanWork — that requires following a testing guide and entering results into a googlesheet.

🗣 Update on BEP2 payments for CanWork

🧩 We solved the outstanding escrow disbursal quirks
🎯 Testnet tests have all passed perfectly!

✅ User testing with multiple Binance Chain (BEP2) tokens
✅ End-to-end process success
✅ On-chain tx's created as expected
✅ Token valuations, amounts & disbursals as expected
✅ CanWork monitor updates job & tx logs accurately

What next?

💰 Mainnet Testing
We will now run limited user tests on mainnet to confirm the expected behaviours in the live Binance Chain environment.

🔧 Pre-release UI/UX fixes
Now the core functionality is working, we begin to tidy up & fix minor UI/UX issues .
(There might be some scope to put up some tasks on CanWork).

🙋🏽‍♀️ Community Tests & Feedback
We will recruit community testers soon to help us test live through CanWork.
Please submit expressions of interest for community testing to @Johanlives.
(Must have a Client or Provider account on CanWork linked to a valid Binance Chain wallet address)

CanWork Demo: Paying into Escrow with BNB

Here we see a Binance Chain testnet demo of a Client paying into escrow with BNB.

We still need need to test the entire end-to-end job payment flow with BEP2 tokens and all escrow functions (eg. Release, Refund).

Then, after some team testing on Mainnet we will recruit community members to help test in earnest.

There's also some UI improvements to come— like fixing that temporary confirmation modal you see at the end 😉