Peerplays Weekly, 2 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Peerplays Weekly Townhall Meeting May 2, 2023

Description

Peerplays Weekly Townhall Meeting May, 2023

Peerplays is the first-ever blockchain, humanizing your experience of crypto.

Join the movement to bring you crypto ecosystems that
understand you, build relationships & maximize your freedom.
---------------------------------------------------------------------------------------
Time stamps:

Projects & Development Updates: 0:23
Collaborations 5:38
Q&A: 8:51
---------------------------------------------------------------------------------------
Stay Connected

Website: https://www.peerplays.com
LinkedIn: https://www.linkedin.com/company/peer...
YouTube:

/ peerplaysblockchain
Instagram: https://www.instagram.com/Peerplays/
Reddit: https://www.reddit.com/r/Peerplays/
Twitter: https://twitter.com/Peerplays
Telegram: https://t.me/Peerplays

A

A

Welcome everybody to today's weekly Town, Hall, Tuesday, May, 2nd 2023.. Today's agenda will be products and development updates and collaborations Robinson. Please start us off with project and development updates.

B

um Sean, thank you. So, on the uh software development side, we are actively working on on two projects on the blockchain and uh uh then uh two d-apps, one in the initial State and one the one and the final stage to begin with the Legacy blockchain updates. So we still working on the final uh QA and also still waiting on the Bitcoin uh server update.

B

So this has taken uh as little longer than what we anticipated and this last stage of verifying against the Bitcoin main net uh that is still pending, but in the meantime, we're making progress on the next uh implementing the UI for Ethans and ah few other changes uh like we're, bringing in support for uh for a block Explorer like interface, which can be used for uh listing ourselves with external uh portals, so those those kind of workers going on, and in addition to that right now we are also working on uh verifying the uh Ethan's functionality.

B

So once uh we complete the main net verification against uh Bitcoin uh using it in Bitcoin, we will be proceeding with the release, so the status remains uh pretty much the same. Apart from the uh new initiative on the ethereum sense. Okay, let's go to the next slide uh for pair place 2..

B

So in the pair please, to r d. For the past several weeks, our Focus has been uh solely on updating the code base so that we can align with the uh with uh polka dots version 0939.

B

And finally, we have managed to fix this last week, special thanks to uh vladislav for uh identifying and fixing this uh so right now the focus is now that uh we have fixed it. uh We are verifying the uh few bugs which which we had uh primarily with respect to uh deploying solidity smart contracts. So what is happen?

B

What happened is uh we had implemented a mechanism to uh link substrate style accounts and either m style addresses, but uh uh it had bugs, and uh uh with this update uh we have a new mechanism from the frontier project, which seems to be addressing a lot of the same items that we were working on. So at this point, uh we're verifying various smart contracts and see uh whether uh the changes which which we just brought in are of fixing the issues.

B

So that's in progress, and once this update is are done, we will move on with changes to uh consensus and other other core changes.

B

That's on the paper place too: let's move to the next slide um on together we have user stories and progress and we had multiple meetings with the QA and developers and team leads to identify uh various scenarios, which is uh so as SL. We had a question answer. We had multiple question answers sessions which is proving to be really helpful and in addition to that, uh we are also working with the ux design team.

B

So so far we have initial wireframes and uh mind maps to understand the product and uh the early sketches has been provided and we have. We are collaborating to verify uh these sketches.

B

So it's in progress and from a development perspective we have uh bootstrapped or rather initiated the repository with, uh with all the software components, that's required and now, since the front end is going to take a while uh we're trying to set up all the vacant components which is required for the project, so the various uh ER entity relationship models. Etc, we are trying to uh work on those uh while the designs are, the UI designs are fine-tuned, so these are the main updates from the software development team. Thank you. So much.

A

Jonathan collaboration updates, please.

C

A

These are these.

C

Within the standards category of the government, blockchain Association, we continue our collaboration in regards to decentralized ID. We have continued to work with the work group so that we can introduce decentralized, ID standards to their blockchain majority model and in our last meeting um there was some uh feedback given uh that, where we uh told them about uh mechanisms of attestation that was important to decentralize identification and uh that went well.

C

We also uh heard some good news from government blockchain Association that their blockchain and trading model seems to be gaining traction with some countries in the world so uh yeah the sooner. We can see our contributions being implemented with other high-level uh uh governments, if not other organizations, uh the better it'll be for peer plays. So we continue with that uh within the community sector, Avalon meta. We uh actually were working on a review with them this past week in regards to scene's platform, and uh they are.

C

We also had a call in relation to uh getting an update done to in, uh as we've discussed uh previously, with the peer plays, update, uh there's going to be a feature which will allow people to be able to incorporate pure plays with the token system, uh and so that's where they're going to start with an implementation and that's uh well underway. So that's going well uh in the dedicated team updates. uh We don't have any changes to our team.

C

However, uh we are starting to look for a back-end tester, someone who has uh some experience in solidity as well as rust. uh They would have to be someone who's senior uh somebody who has uh a curious mind, basically someone who's more like an ethical hacker, so to speak. uh Who would basically, who would do back-end testing uh with the core of the blockchain to try to find ways to manipulate, if not game it for uh functions that are not supposed to operate as intended?

C

So uh we're looking for somebody like that who would be able to uh join with peer plays as we're looking to incorporate that into uh peer plays two. uh The work that we're doing with solidity uh and rust is primarily what's coming out with our substrate stack, because it will support evm, that's where the solidity part comes in, so we're looking for somebody than that.

C

uh If you do know someone who fits the description, I just gave uh please uh direct them to Alka through our LinkedIn page and she'll be happy to speak with them and that's the updates for uh collaborations of peer plays this week. Thank you.

A

Thank you Jonathan. uh We have one question coming from the community, Bob and Son correct me if I'm wrong, but I think this question would be for you. How are we using Inc to become evm compatible and how are we different from movie.

B

C

B

Okay, I think I can I can try to answer it.

B

um So we're not uh first of all we're not using uh Inc uh usage, so Incas, uh nothing, but a like a sub type or a subset of uh rust programming language, so we're not using Inc for anything so far, uh I'm not sure we'll be using uh like we, as in like for the blockchain development I.

B

Don't think we'll be uh using think at all, because our primary workers in uh rust, so uh Inc will be mostly be used by application developers or basically Dr developers and uh small contract developers to achieve smart contact like somebody who wants to develop, let's say defy protocols or any other protocols, I think that's where Inc will uh come into come handy now. At the same time, uh the only uh exposure to ink to us is in terms of making sure that the Ink Smart contract support is there.

B

So we have support for uh Inc smart contracts. So one of the unique features that we have is uh we are not removing the Ink Smart contracts like what projects like Moonbeam has done, so we're not removing the support. So, let's say: if there are operations like uh random function, random generators which people wants to use in their smart contracts, Inc uh Inc will be able to access this verifiable, verifiable, verifiable random number function from substrate, so uh so that is one so essentially from Moonbeam. We have nothing to do with uh Moonbeam at all.

B

That is a blockchain from a blockchain product, uh we're not using blockchain for anything uh we're not we're, not forking we're not looking into the Moonbeam code or anything like that. So uh and the difference is that Moonbeam? What what they've taken and I think the similarities that uh Moonbeam uses the same evm the same evm implementation is used by Mont beam. I, think that is what the uh similarities ends, but there's uh the evm is not implemented by mode Bay meters, It Is by polka dots uh parity itself.

B

So that is where the similarities ends. So what Moonbeam has done is uh they have created or they forked the framework and they have a? uh They have a new account system which is uh which essentially removes most of the uh polka dot or substrate functionalities. So.

C

B

Not we're not uh doing that, and um we are also not going to uh maintain all the all these softwares like substrate, because that will put us in the same situation like ending up to maintain uh various softwares like FC, uh which was like an hour kill in the graphene space.

B

So the only uh area where we are using our uh or using mode Beamers, uh the d-app teams, so this was discussed last week also, so the diap team wanted a uh starting place to look at uh smart contracts and uh verify uh the solidity functionality or the evm functionality, so so to verify the evm functionality to verify it's already smart contracts and also to get some guideline about how to write and deploy contracts into evm.

B

uh That's the only area where we are using uh mode B. So from a blockchain development perspective. We have nothing to do with not uh using the Moonbeam project at all from a document, but the diab team. They are referring the moon, beam uh documentation for smart contracts. So the only relation uh that we have we as a organization has with Moonbeam is that the DF team is referring to the sample documentation for deploying solidity smart contracts.

B

So, apart from that, uh we we don't have any code or any repository is uh taken from Mountain project.

B

Yeah I think I. Think uh I should also clarify this. uh In the beginning, when we started uh working with a substrate uh framework, um our understanding was that uh Moonbeam uh could be a part. So we had uh mentioned Moonbeam in in multiple discussions. Diet will be uh using the moon beam like uh development path, but uh for the, but what we have understood is right.

B

uh We are better of handling it ourselves, so the are purely written on use, written using substrate uh and there's no way not taking any pro any any code from any other planet change. So for that matter, no para chains or uh no, uh not even Paul cutter we're not taking. Obviously we are using everything from substrate, so uh polka dot itself was written in substrate. So obviously there are.

B

There are like a lot of overlaps with uh polka dot itself, the relay chain of portrait.b precise, but uh we're not taking anything from uh any of the polka dot. Parrot chains. I hope uh that answers the question.

A

B

A

All right that concludes today's weekly town hall meeting May 2nd 2023.. Thank you all very much for joining us. I hope you have a great week and we will see you next Monday.

C

Thanks everybody.